Last updated: 2026-08-27
This Privacy Policy explains what data is involved when you use Dock, the Mac app for App Store Optimization published by dimix.it di Dimitri Giani (“we”, “us”, “our”), a sole proprietorship established in Italy.
It covers four things:
- the Dock macOS app;
- the Dock Web App at app.dock-app.com, the browser version of Dock;
- the Dock — ASO Tracker MCP extension (the
.mcpbdesktop extension for Claude Desktop and other MCP clients); - the dock-app.com website.
Sections 1 to 15 describe the Mac app. The Web App works differently in one important way — it runs on our servers — and has its own part further down, followed by the MCP extension and the website.
There are two versions of the Mac app, and one sentence of this policy depends on which one you have. The version from the Mac App Store sells its subscription through Apple and never contacts Lemon Squeezy. The version downloaded from dock-app.com sells the same subscription through Lemon Squeezy, using a licence key. Everything else in this policy is identical for both; the difference is set out in section 6.
For any privacy question or request, write to info@dock-app.com.
In short
- In the Mac app, your App Store Connect keys and Google account tokens stay on your Mac. We never receive them, and neither does the MCP extension.
- In the Web App, those same credentials are necessarily stored on our servers, encrypted at rest, because the app runs there.
- Your store data — listings, screenshots, reviews, sales and finance reports — is cached locally on your Mac in the app’s database.
- Some features send content to our servers to be processed: screenshots and listing text for AI analysis, translation and generation, and review text for sentiment analysis. Dock asks for your permission before the first one runs, and those requests are not tied to your identity.
- We collect pseudonymous usage analytics (which screens you open, which features you use, whether you’re subscribed) linked to a random identifier — not to your name or email.
- If you bought Dock outside the Mac App Store, Lemon Squeezy is told your licence key and the name of your Mac — nothing else. Your Mac’s hardware identifier never leaves your computer.
- We do not sell your data, we do not share it for advertising, and we do not use it to train AI models.
- You can ask us to access, correct or delete your data at any time.
1. Data that stays on your Mac
Most of what the Mac app handles never leaves your computer. (This does not apply to the Web App, which runs on our servers — see the Web App part below.)
1.1 Credentials
| Credential | Where it is stored |
|---|---|
App Store Connect API keys (Issuer ID, Key ID, .p8 private key) | Your macOS keychain |
| Google Play Console OAuth tokens (access + refresh) | Your macOS keychain |
| Google Search Console OAuth tokens | Your macOS keychain |
| Licence key and activation receipt (only in the version downloaded from dock-app.com) | Your macOS keychain |
These credentials are read only by Dock on your Mac, and are used only to call Apple’s and Google’s own APIs directly from your machine — with one exception, the licence key, which is sent to Lemon Squeezy to check that your subscription is still valid (section 6.2). None of them is ever sent to our servers, and the MCP extension cannot read or export any of them.
They are stored in your login keychain, encrypted by macOS and protected by an access control tied to Dock’s code signature, so no other application can read them without your explicit permission. Versions of Dock before 3.3 kept them in the app’s preferences file instead; on first launch, Dock 3.3 moves them into the keychain and clears the old copy.
You can remove them at any time by deleting the account inside Dock, and you can revoke them independently from App Store Connect or the Google Cloud Console.
1.2 Your store data
Everything Dock downloads from Apple and Google is cached in a local database on your Mac: localized listings (name, subtitle, description, keywords, promotional text, what’s new), screenshots and other store images, app metadata, user reviews, ranking history, sales and financial reports, and any drafts you have not published yet.
This data is not uploaded anywhere by Dock, except for the specific features described in section 3, which you trigger explicitly.
Deleting the app, or using the reset options inside it, deletes this local data.
2. The store accounts you connect
2.1 Apple App Store Connect
Dock uses the App Store Connect API with the key you provide, directly from your Mac. What Dock can read and write is exactly what your key’s role allows. Apple’s handling of that data is governed by Apple’s own privacy policy.
2.2 Google Play Console
When you connect a Google Play account, Dock asks Google for the following OAuth scopes:
| Scope | Why Dock needs it |
|---|---|
androidpublisher | Read and edit your store listings, release notes and images; read your reviews and post replies |
playdeveloperreporting | List the apps in your developer account |
openid, email, profile | Show you which Google account is connected, and tell multiple connected accounts apart |
Dock stores the resulting tokens and the account’s email address and display name locally, so you can recognise the account in the accounts list.
2.3 Google Search Console
The Web Presence section connects Search Console through a separate authorisation, with these scopes:
| Scope | Why Dock needs it |
|---|---|
webmasters.readonly | Read your verified properties, their sitemaps, search performance data and URL inspection results — read only |
openid, email, profile | Show you which Google account is connected |
Search Console data is fetched by your Mac directly from Google and stored locally. It is never routed through our servers.
2.4 Google API Services — Limited Use disclosure
Dock’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically:
- we use Google user data only to provide and improve the features you see in Dock;
- we do not transfer Google user data to third parties, except as necessary to provide those features, to comply with the law, or as part of a merger or acquisition;
- we do not use Google user data for advertising;
- we do not allow humans to read Google user data, unless you give explicit consent for a specific support case, it is necessary for security purposes or to comply with the law, or the data is aggregated and anonymised;
- we do not use Google user data to develop, improve or train generalised AI or machine learning models.
You can revoke Dock’s access at any time from your Google Account permissions page, or by disconnecting the account inside Dock.
3. Dock’s online services
Some features cannot run on your Mac alone. When you use them, Dock sends the data they need to our own backend at api.dock-app.com over an encrypted connection.
| Feature | What is sent |
|---|---|
| Keyword popularity, difficulty, combinations and variants | The keywords you enter, plus the country/store |
| App and keyword ranking | Your app’s identifier, the keywords, the country/store |
| Screenshot analysis | The screenshot image, plus the app’s name, subtitle and description, the platform and the locale |
| AI screenshot content generation | The app’s name, subtitle, description, your prompt, the target language |
| Translation and AI text generation | The listing text you are translating or generating, and the source/target languages |
| Review analysis | The text and star rating of the reviews being analysed — never the reviewer’s name or any other reviewer identifier |
| App Intelligence and competitor research | The search terms and app identifiers you look up, and the country/store |
The first time you use one of these features, Dock asks for your permission and tells you what that particular feature sends and who processes it. Nothing leaves your Mac until you allow it, and you can withdraw the permission at any time in Settings ▸ Privacy, which turns these features off.
These requests are authenticated with a key shared by every copy of Dock. They do not carry your account, your email or your analytics identifier, so what arrives at our servers is not linked to your identity. As with any internet request, our servers do see the originating IP address, which is used for rate limiting and abuse prevention.
3.1 AI processing
These features are powered by two AI providers, which process the content listed above on our behalf as data processors:
| Feature | Provider | Model family |
|---|---|---|
| Screenshot analysis | Anthropic, PBC | Claude Sonnet |
| Translation, AI text generation, keyword generation, keyword and phrase suggestions, review analysis | OpenAI, L.L.C. | GPT-4o |
Both providers process this content under their commercial API terms, which state that data submitted through the API is not used to train their models. See Anthropic’s privacy policy and OpenAI’s privacy policy.
We do not keep what you send. Screenshots and text submitted for AI processing are held only for as long as it takes to build the request and return the answer to your Mac. They are not written to our database and are not saved as files on our servers, and they are not written to our logs. If a request fails, a short truncated fragment of the response may be recorded in our error logs to let us diagnose the fault; those logs rotate and are deleted after 14 days.
3.2 What we never do with it
We do not sell this data, we do not share it with advertisers or data brokers, we do not use it to profile you, and we do not use your listings, screenshots or reviews to train our own models.
4. Web Presence
The Web Presence section analyses the websites associated with your apps.
- Dock discovers candidate website addresses from the support and marketing URLs already published in your store listings.
- It then requests those pages directly from your Mac, the same way a browser would, identifying itself with a Dock user agent. It reads the returned HTML, HTTP headers, TLS certificate details and the deep-link association files (
apple-app-site-association,assetlinks.json). - No part of this goes through our servers. We never receive the addresses of your websites or their content.
- If you connect Google Search Console, search performance data is fetched directly from Google, as described in section 2.3.
Results are stored locally on your Mac.
4.1 Google results tracking
Web Presence can also show you who holds Google’s top results for a keyword, and where your own
site and store pages land. This part is optional and off until you set it up, because it is
not powered by us: it needs an account of your own with DataForSEO, a third-party search data
provider, and every reading is charged to that account.
- Your DataForSEO API login and password are stored in your Mac’s keychain and are sent to
api.dataforseo.comand nowhere else. We never receive them. - When you follow or re-read a keyword, Dock sends DataForSEO the keyword, the country and
whether to read the page as a desktop or a phone. For the competitor keyword list it sends
a domain or a page address you have chosen. - None of this passes through our servers. The requests go straight from your Mac to
DataForSEO with your own credentials. We do not receive the keywords you follow, the pages you
look at, or the results. - DataForSEO is your provider, not our subprocessor. What it does with the requests made on your
account is governed by your agreement with them and their
privacy policy. - If you turn on automatic updates, Dock re-sends the keywords you follow to DataForSEO on a
schedule, at most once a day and only for the ones that are due. It is off unless you enable
it, and it stops at the monthly spending limit you set. - Articles that list apps like yours are fetched directly from your Mac, exactly as described
above for your own sites, so Dock can tell you whether your app is named on them.
The results, the positions and what you have spent are stored locally on your Mac.
5. Usage analytics
To understand how Dock is used and where to spend development effort, the app sends product analytics to our own analytics service at tracker.dimix.it. We do not use Google Analytics, Firebase, or any advertising or attribution SDK.
What is collected:
- a random identifier generated on first launch, stored in your iCloud key-value store so it stays stable across your Macs;
- screens opened and features used inside the app;
- app launches and session timing;
- Mac platform, macOS version, Dock version, country and language derived from your system locale;
- whether you currently have an active subscription;
- purchase events, as described in section 6.
What is not collected: your name, your email address, your App Store Connect or Google credentials, your app names, your listings, your keywords, your reviews, your sales figures, or the contents of your screen.
This identifier is pseudonymous, not anonymous: it is not tied to your name or email, but it is stable over time and across your devices, so under the GDPR we treat the resulting data as personal data and give you all the rights described in section 11.
Analytics is not collected in development builds.
If you would rather not be included in product analytics, email info@dock-app.com from the address you want us to act on and we will exclude you and delete the data associated with your identifier.
6. Purchases and subscriptions
Which version of Dock you have decides who sells you the subscription, so this section has two halves. If you installed Dock from the Mac App Store, 6.1 applies and the app never contacts Lemon Squeezy. If you downloaded it from dock-app.com, 6.2 applies and Apple is not involved in your purchase at all.
6.1 The Mac App Store version
Dock’s paid features are sold as In-App Purchases through Apple. Apple processes the payment. We never see or receive your payment card, your billing address or your Apple Account details.
When a purchase or renewal succeeds, StoreKit reports it to the app and we record, against the analytics identifier described in section 5: the product purchased, its price and currency, the subscription period, whether it is a trial, an introductory offer or a renewal, and the Apple transaction identifier. We use this to measure conversion and revenue.
Apple also gives us aggregate, anonymised reports about downloads, purchases and app usage, in the App Store Connect dashboards available to every developer.
6.2 The version downloaded from dock-app.com
This version is sold through Lemon Squeezy, the merchant of record: it runs the checkout, takes the payment, charges the tax and issues the invoice. As with Apple, we never see or receive your payment card or your billing address, and your purchase is visible to you at any time in your own Lemon Squeezy account, at https://dock-app.com/licence.
The subscription is unlocked by a licence key. Dock talks to Lemon Squeezy’s licence API — and to no other part of their service — in exactly three moments: when you activate a Mac, when it checks at launch that the activation still stands, and when you unlink a Mac. Those requests carry two things and nothing else:
| What is sent | Why |
|---|---|
| Your licence key | It is the thing being checked |
| The name of your Mac, as macOS reports it | So that the activations listed in your Lemon Squeezy account are ones you can tell apart, and you know which Mac you are unlinking. On a personal Mac that name usually contains your own name, so we treat it as personal data: it is sent because a list you cannot read is of no use to you |
Your Mac’s hardware identifier (IOPlatformUUID) is never sent to anyone. Dock reads it only to tie the local activation receipt to this computer, and that receipt stays in your macOS keychain (section 1.1). This is the difference between an app that binds a licence to your Mac and an app that hands a hardware identifier to a third party: Dock does the first and not the second.
The licence key and its receipt are removed from your keychain when you unlink the Mac.
Two further requests belong only to this version and carry nothing about you: when it shows prices, Dock fetches the price list (GET api.dock-app.com/api/price.json) so that what is on screen is what Lemon Squeezy will actually charge, and at launch it fetches the update feed (GET api.dock-app.com/api/appcast.xml) to see whether a newer version has been published. Both are ordinary requests with no payload; our server logs them as it logs any request, and those logs are kept for 14 days (section 10).
6.3 The Web App, and the one subscription that covers both
Web App subscriptions are not sold through Apple either; they go through Lemon Squeezy, as described in the Web App part below. It is the same subscription: one purchase covers the Mac app downloaded from dock-app.com and the Web App at app.dock-app.com, whichever of the two you bought from. (The Mac App Store version is not part of this — see 6.1.)
Because a purchase made inside the Mac app has no Web App account behind it, linking the two is something you do: on the Web App you paste your licence key once, and we ask Lemon Squeezy whether it is good — the same question the Mac app asks, at the same address. The key you paste is used to check the purchase and is not stored on our servers; what we keep is the identifier of the subscription it belongs to, so that renewals and cancellations keep your access in step.
7. Diagnostics and logs
Diagnostic files and system logs are generated only when you ask for them, to troubleshoot a problem. They stay on your Mac unless you choose to send them to us, and we use them only to investigate the issue you reported.
Dock does not install an automatic crash reporter and does not send crash reports in the background.
8. Services we rely on
| Service | Provider | What it is used for |
|---|---|---|
| App Store Connect API | Apple Inc. | Reading and writing your Apple store data (called from your Mac) |
| iTunes Search / lookup API | Apple Inc. | Public store information about apps |
| Google Play Developer API | Google LLC | Reading and writing your Google Play store data (called from your Mac) |
| Google Play Developer Reporting API | Google LLC | Listing the apps in your account (called from your Mac) |
| Google Search Console API | Google LLC | Search performance for your websites (called from your Mac) |
api.dock-app.com | dimix.it di Dimitri Giani | Keywords, rankings, App Intelligence and the AI features in section 3; the price list and the update feed of the version downloaded from dock-app.com (section 6.2) |
tracker.dimix.it | dimix.it di Dimitri Giani | Product analytics (section 5) |
| Frankfurter API | Frankfurter (open source project) | Currency exchange rates — no personal data is sent |
| CurrencyFreaks | CurrencyFreaks | Currency exchange rates, as a fallback — no personal data is sent |
| In-App Purchases (Mac App Store version) | Apple Inc. | Payment processing |
| Subscriptions (the version downloaded from dock-app.com, and the Web App) | Lemon Squeezy | Merchant of record: checkout, billing and tax; and, for the downloaded version, checking that a licence key is still valid (section 6.2) |
| Default avatars (Web App) | ui-avatars.com | Generating the initials avatar from your name |
| AI — screenshot analysis | Anthropic, PBC | Reading the screenshot and returning the analysis |
| AI — text, translation, keywords, reviews | OpenAI, L.L.C. | Generating the requested text or analysis |
| Server hosting | Hostinger International Ltd. | Running api.dock-app.com |
9. Legal bases for processing (GDPR)
| Purpose | Legal basis |
|---|---|
| Running the app’s core features, and the online services you invoke | Performance of a contract (Art. 6(1)(b)) |
| Handling purchases and subscriptions | Performance of a contract (Art. 6(1)(b)) |
| Product analytics to improve Dock | Legitimate interest (Art. 6(1)(f)) — you may object at any time, see section 5 |
| Security, abuse prevention and rate limiting | Legitimate interest (Art. 6(1)(f)) |
| Support and diagnostics you send us | Consent (Art. 6(1)(a)) and legitimate interest |
| Complying with tax and accounting law | Legal obligation (Art. 6(1)(c)) |
10. How long we keep data
| Data | Retention |
|---|---|
| Everything stored on your Mac (credentials, licence key and activation receipt, cached store data, drafts, Web Presence results) | Until you delete it or uninstall the app — it is under your control, not ours |
| Content sent for AI processing | Not retained — processed and discarded once the answer is returned |
| Server request logs | 14 days, then rotated out and deleted |
| Product analytics events | 24 months, then deleted or irreversibly aggregated |
| Web App account, connected store credentials and synced store data | Until you delete the connected account or your whole account, then removed |
| Web App session records (IP, user agent) | Until the session expires or you revoke it |
| Your subscription record on our side (the Lemon Squeezy identifier of the subscription, its status and its dates) | While the subscription is live, and until you delete your account. It is not a fiscal document and we do not keep it as one |
| The invoice for your purchase | Lemon Squeezy is the merchant of record: it sells Dock to you, issues the invoice and keeps it, under its own retention policy. Ours are the accounting records of what Lemon Squeezy pays us, which Italian law requires any business to keep for 10 years — those record the payment, not you |
| Support correspondence | 24 months from the last message |
11. Your rights
If you are in the EEA or the UK, you have the right to access your data, correct it, erase it, restrict or object to its processing, receive it in a portable format, and withdraw consent where processing is based on consent.
If you are in California, you have the right to know what personal information we collect, to have it deleted, to correct it, and to opt out of its sale or sharing. We do not sell or share personal information as those terms are defined by the CCPA/CPRA, and we do not process it for cross-context behavioural advertising. We will never discriminate against you for exercising these rights.
To exercise any of them, write to info@dock-app.com. We reply within 30 days. To help us find your records, tell us your Apple Account email if your request concerns a purchase.
Note that most of the Mac app’s data is on your own Mac, where you can inspect and delete it yourself at any time without asking us. If you use the Web App, you can delete your account, and everything attached to it, directly from its settings.
If you believe we have handled your data improperly, you may complain to your local supervisory authority. In Italy this is the Garante per la protezione dei dati personali.
12. International transfers
We are based in Italy. Our servers are operated for us by Hostinger International Ltd., on infrastructure located in the European Union.
Some of the providers listed in section 8 process data outside the EEA, including in the United States: in particular Anthropic and OpenAI, which run the AI features described in section 3.1, Lemon Squeezy, which processes payments for the Web App and for the version of the Mac app downloaded from dock-app.com, and Apple and Google for the store APIs. Where that happens, the transfer is covered by the European Commission’s Standard Contractual Clauses or an equivalent safeguard under Chapter V of the GDPR.
13. Security
We use encrypted connections (HTTPS/TLS) for every request Dock makes to our servers and to Apple’s and Google’s APIs. On your Mac, your credentials live in the macOS keychain and the rest of your data is protected by the standard macOS protections for your user account. On our side, the smallest practical amount of data is kept: the content you send for AI processing is not stored at all, and no store credential of yours ever reaches our servers.
No system is perfectly secure, but if a breach affects your personal data we will notify you and the competent supervisory authority as required by law.
14. Reviews and other people’s data
When you use Dock to read, analyse or reply to user reviews, you are handling personal data belonging to your users. In that processing you are the data controller and we act as your processor: we process review content only to give you the analysis or translation you asked for, on your instructions, and for no other purpose. Making sure your own privacy notice covers this is your responsibility as the app’s publisher.
15. Children
Dock is a professional tool for app developers and publishers. It is not directed at children, and we do not knowingly collect personal data from anyone under 16. If you believe a child has provided us with personal data, write to info@dock-app.com and we will delete it.
Dock Web App
The Dock Web App at app.dock-app.com is the browser version of Dock. It differs from the Mac app in the one way that matters most for your privacy: it runs on our servers, so the data it works with — including your store credentials — is stored there instead of on your computer. If you only use the Mac app, nothing in this part applies to you.
Your account
To use the Web App you create an account. We store your name, your email address and your password, the last of which is hashed — we never see or store the password itself. If you turn on two-factor authentication, we also store its secret and your recovery codes.
We do not host profile photos. The avatar shown next to your name is generated from your initials by ui-avatars.com, which receives your name as part of the image request.
Each active login is recorded as a session, with the IP address, the browser user agent and the time of last activity. This is what lets you review and revoke your other sessions, and it is how we detect suspicious access.
Store credentials on our servers
This is the real difference from the Mac app. When you connect a store account to the Web App:
| Credential | How it is stored |
|---|---|
| App Store Connect Issuer ID and Key ID | In our database |
App Store Connect .p8 private key | In our database, encrypted |
| Google Play OAuth access and refresh tokens | In our database, encrypted |
| The Google account’s email, display name and picture URL | In our database |
The encrypted fields are protected with AES-256 using a key that lives in the server configuration rather than in the database, and they are excluded from every serialisation, so they are never sent to your browser or returned by an API response.
We use these credentials only to make the App Store Connect and Google Play API calls that the features you are using require. You can delete a connected account at any time from the Web App, which deletes its credentials from our database. If you want the key to stop existing altogether, also revoke it from App Store Connect or from the Google Cloud Console.
Your store data
So it can show your data without calling Apple and Google on every page load, the Web App keeps a copy of what it syncs: your apps, versions and their localizations, screenshots, keywords, rankings and ranking history, App Store events, Google Play listings and release notes, user reviews and their analyses, and any drafts you have not published yet.
This copy lives in our database and file storage for as long as your account does.
Payments
Web App subscriptions are sold through Lemon Squeezy, which acts as merchant of record. You enter your payment details on their systems, never on ours, and they handle the charge and the tax. We receive and store the resulting order and subscription records — product, amounts, currency, tax, status, renewal and trial dates, receipt URL — along with your card brand and its last four digits. We never receive or store your full card number.
AI features
The Web App uses the same online services described in section 3 and sends them the same content. The providers and the no-retention rule in section 3.1 apply unchanged.
Deleting your account
You can delete your account from the Web App’s settings at any time. Deleting it removes your profile, your connected store accounts and their credentials, and the store data synced under them. Billing records are kept for as long as tax law requires, as set out in section 10.
Dock ASO MCP Extension
This section describes how the Dock — ASO Tracker MCP extension handles your data. It is a companion to the policy above: the extension is a thin bridge to the Dock macOS app and inherits its data handling for everything except the MCP transport layer described here.
What the extension is
The extension is a desktop extension (.mcpb) for Claude Desktop and other MCP-compatible clients. It packages a small stdio bridge (DockMCP) that translates MCP tool calls into HTTP requests sent to the Dock macOS app running on the same machine, at http://127.0.0.1:8765.
The extension does not open any network connections to the public internet. It contains no analytics, no telemetry, no crash reporting and no third-party SDK. The extension and the Dock app are versioned independently.
What data is processed
When you invoke one of the extension’s 28 tools from Claude:
- Claude sends the tool name and its arguments to the extension over stdio.
- The extension forwards the call to the Dock app on your machine.
- Dock reads from its local database and, when needed, calls the relevant API (App Store Connect, Google Play, or Google Search Console for the Web Presence keyword research tool) using the credentials you configured inside Dock.
- The response travels back to Claude through the same stdio channel.
The data crossing the MCP boundary is therefore the same data you can already see inside Dock: localized listings, screenshots, keyword and ranking analysis, app evolution history, public App Intelligence research on other apps in the store, user reviews, sales and finance summaries, metadata about your apps and their twins, and — through the Web Presence tools — your site’s technical audit, the search phrases you are researching together with their Search Console impressions, your positions on Google for the keywords you follow, and the list of third-party pages worth asking for a link.
That last one deserves naming plainly: a link building target carries the address, title and public contact email address of a page belonging to somebody else, read from that page when it was checked or recorded by you. Those addresses reach the model along with the rest of the answer.
No additional data category is collected by the extension itself.
Credentials
App Store Connect API keys and Google OAuth tokens are stored and used exclusively by the Dock app on your Mac. They are never transmitted through the MCP extension, and the extension cannot read or export them.
What is shared with Claude
Anything a tool returns is sent back to Claude as part of the MCP response, and is therefore visible to the model. This may include your localized store metadata, keyword data, user reviews, sales figures and other content you manage with Dock. How Claude processes that content is governed by Anthropic’s privacy policy: https://www.anthropic.com/privacy. If you use a different MCP client, that client’s own policy applies instead.
You can limit what is exposed by:
- enabling the MCP server in Dock only while you are using it;
- choosing which apps, languages and time periods you ask Claude about;
- reviewing the confirmation prompt your MCP client shows before any
update_*call.
The local server
Dock’s MCP server runs inside the Dock app and listens on TCP port 8765 for as long as you leave it enabled in Settings. It is bound to the loopback interface only, so it is not reachable from your local network or from the internet: only software running on your own Mac can connect to it, and requests coming from a web page are refused. As a matter of good practice, we still recommend enabling it only while you are actually using it.
Write operations
Five of the twenty-nine tools change something, and they fall into two groups.
update_app_aso_content and update_google_app_aso_content edit your store listings. Both are annotated destructiveHint: true, which MCP clients such as Claude Desktop render as an explicit confirmation prompt. Edits are saved as local drafts inside Dock. They are not pushed to App Store Connect or Google Play until you publish them yourself from Dock’s interface.
The nine Web Presence tools require an active Dock subscription; the twenty others do not. add_research_keywords, follow_keywords and update_link_building_target only add to lists inside Dock — a phrase to research, a keyword to track, a note about a page you wrote to. Nothing is overwritten, so they are annotated destructiveHint: false and your client may not prompt for them.
None of the five spends money on your behalf, and no tool sends email. Search data is bought with your own DataForSEO key, from inside Dock, where the price is on screen: the tools report what something would cost and leave the decision with you. Following a keyword is free in itself, but a followed keyword is read on a schedule, so it does commit future spending — bounded by the monthly ceiling you set in Settings › Web Data, which the updater stops at.
Logging
The extension writes diagnostic messages to standard error, which your MCP client captures into its local extension logs. These messages include the tool name and the URL of the local HTTP request (http://127.0.0.1:8765/...), and never include credentials or argument values. The logs stay on your Mac.
Children
The extension is intended for professional use by app developers and is not directed at anyone under 16.
Changes to this section
If we materially change how the extension handles data, the updated policy will be published at https://dock-app.com/privacy-policy/ with a new “Last updated” date. The extension itself does not check for policy updates; review the latest version at the link above at any time.
The dock-app.com website
The public site at dock-app.com is a WordPress site. It sets only the functional cookies WordPress needs to serve pages and remember what you type in a form. It does not run Google Analytics, advertising pixels, or any third-party tracker.
If you write to us through the contact form, we receive the name, email address and message you enter, and use them only to reply to you.
Two pages exist for the version sold outside the Mac App Store, and neither of them asks you for anything. /download lays out the three ways to use Dock — the Mac App Store, the disk image, and the Web App — and reads the version and size of the disk image straight from the update feed described in section 6.2. /licence explains where your licence key and your subscription live and sends you to your own Lemon Squeezy account. We deliberately did not build a form here that looks up a licence from an email address: such a form has to answer, and an answer that differs for an address that has bought is a way of finding out who our customers are.
Changes to this policy
We may update this Privacy Policy. When we do, we will change the “Last updated” date at the top of this page, and for material changes we will also notify you inside the app. Changes take effect when they are posted here. We encourage you to review this page from time to time.
Contact
dimix.it di Dimitri Giani
Italy
For any question about this policy, or to exercise any of the rights described in section 11: info@dock-app.com