Last updated 9 October 2026
ASA Condor manages Apple Search Ads campaigns on your behalf. To do that it has to hold a narrow set of things about you and your apps. This page says exactly which, why, and who else sees them. It describes what the product actually does today, not what it might do.
ASA Condor is operated by Manuel Couto (Portugal). For questions about your data, or to exercise any of the rights below, write to coutocf@gmail.com.
| Data | Why | Basis |
|---|---|---|
| Your email address and Apple sign-in identifier | To sign you in and to keep your account separate from everyone else's. | Performing our contract with you |
| An access token for your Apple Ads account | To read your campaigns and make the changes you approve. Stored encrypted; we never see or hold your Apple ID password. | Performing our contract with you |
| Your campaign, keyword and search-term performance | This is the raw material of the analysis. It comes from Apple, not from your users. | Performing our contract with you |
| A RevenueCat API key, if you choose to connect one | To read aggregate revenue for your app and work out what an install is worth to you. Stored encrypted. Optional — the product works without it. | Your consent, withdrawable at any time by removing the connection |
| A record of every change the agent makes | So you can see what was done to your account and what it cost or saved. | Performing our contract with you |
| An email address you enter on the waiting list | To tell you when the product opens. Nothing else. | Your consent |
What is not held. ASA Condor never receives data about your app's users. It reads aggregate figures from Apple and RevenueCat — installs, spend, revenue totals — and nothing that identifies an individual person who installed your app. It also never receives your Apple ID password: the connection is made through Apple's own sign-in, and can be revoked from your Apple account at any time.
These are the only third parties involved, and each sees only what its job requires:
| Service | What it sees | Where |
|---|---|---|
| Clerk | Your email address and sign-in identity | United States |
| Apple (Search Ads API) | Your campaigns, and the changes you approve | United States |
| Google (Gemini API) | Your app's public App Store name, category and description, when generating keyword ideas. No account or revenue data is sent. | United States |
| RevenueCat | Only if you connect it, and only aggregate revenue is read back | United States |
| Hetzner | Hosts the server your data sits on | Germany |
| Cloudflare | Serves this website and stores waiting-list emails | Global network |
Transfers outside the EU rely on the European Commission's Standard Contractual Clauses, which these providers offer as part of their terms.
If you connect ASA Condor to Claude (or another MCP client), you choose to share with that assistant what its requests return: your apps, campaigns, keywords, search terms, recommendations, activity log, revenue figures and prices. That data then becomes part of your conversation, and is handled under your own agreement with that assistant's provider — for Claude, Anthropic.
Under the GDPR you can ask for a copy of your data, ask for it to be corrected or deleted, object to how it is used, or ask for it in a portable form. Write to coutocf@gmail.com and you will get an answer within 30 days. You can also complain to your national data protection authority; in Portugal that is the CNPD.
Credentials — your Apple access token and any RevenueCat key — are encrypted at rest with AES-256-GCM, using a key held separately from the data itself. Traffic runs over HTTPS. Backups are taken daily and are subject to the same retention as above.
This is a small operation, honestly described: it is one developer, one server, and the measures above. It is not an enterprise security programme, and this page will be updated rather than quietly outgrown if that changes.
This website sets no analytics or advertising cookies. The application sets what Clerk needs to keep you signed in, and nothing else.
Both the website and the application count how many people reach each step — how many landed here, how many pressed play, how many reached the pricing, how many finished setting up a campaign. It is how we find the screen that is losing people.
What is stored is a number against a step, per day. For example:
| Day | Step | Count |
|---|---|---|
| 2026-09-18 | Landed on the home page | 120 |
| 2026-09-18 | Saw the plans | 9 |
There is no identifier of any kind. No cookie, no visitor ID, no fingerprint. Your IP address, your browser and the page you came from are not stored, not even briefly. Nothing recorded here can be connected to you, to your account, or to a second visit — including by us, and including later.
Your browser does keep one thing, in sessionStorage: the list of steps already
counted in that tab, so a refresh is not counted as a second person. It never leaves your
browser, it is deleted when you close the tab, and it contains no identifier.
There is no consent banner on this site because there is nothing here to consent to.
Settings has a box for telling us what is wrong. Unlike the counting above, that one is not anonymous, and the screen says so before you type: your message is stored with your account, so that it can be answered. If you fill in the reply address, that is stored with it too.
It is read by one person — there is one of us — and used to answer you and to fix what you described. It is not added to a mailing list, not passed to anybody else, and nothing about your campaigns or your figures is attached to it. Ask, and your messages are deleted.
If this policy changes in a way that affects you, you will be told by email before it takes effect. The date at the top always reflects the current version.