Privacy Policy

Last updated: September 2026 — this revision adds the section on PRO subscriptions and payments via Stripe.

Overview

ASOApp is a privacy-friendly App Store Optimization tool. Most features work without an account — keyword research, keyword discovery, the metadata builder, the top charts and the single-keyword check — and if you use it that way we ask for no personal information at all: your work stays in your own browser.

Four features do require an account, which is free: rank tracking, competitor teardowns, the listing audit and App Discovery. The account stores your email address and lets your saved work follow you between devices, and it is the only part of the service that involves personal data in the ordinary sense. You are never asked for payment details by us: if you subscribe to PRO, Stripe collects and holds them on their own pages and we only ever see your subscription's status. Free accounts are never asked for a card at all.

This policy explains what is processed, why, on what legal basis, and the rights you have under the EU General Data Protection Regulation (GDPR).

Controller

The controller responsible for the processing described here is jungspree (sole proprietorship), Felix Brix, Berlin, Germany. The full postal address and contact details are in the imprint; by email you can reach us at hello@jungspree.com.

Accounts (optional)

If you choose to create an account we store:

• your email address,
• a hash of your password (never the password itself) — not applicable if you only sign in with Google,
• an optional display name,
• the date you registered, and
• whether your email address has been confirmed.

We send you a confirmation email when you register, and password-reset emails if you ask for one. We do not send marketing email and there is no newsletter. You can additionally ask us to email you a summary of your keyword rankings — that is off unless you switch it on, and is described under Email notifications below.

Legal basis: Art. 6(1)(b) GDPR — processing necessary to provide the account service you requested. Confirming the address also serves our legitimate interest in preventing someone from registering an address that is not theirs (Art. 6(1)(f)).

You can delete your account yourself at any time, under Account settings → Delete account. That immediately and permanently removes your email address, password hash, any Google connection and your synced workspace. Any feedback you sent is kept but stripped of its link to you (see Feedback you send us). The work saved in your browser is deliberately left untouched, so deleting the account does not delete your work.

Sign in with Google

You can register or sign in using a Google account. If you do:

• Your browser contacts Google (Google Ireland Limited, and Google LLC in the USA) to display the sign-in prompt. Google receives technical data including your IP address and the fact that you are visiting ASOApp, and may read or set cookies of its own on Google's domains. This happens under Google's own privacy policy, over which we have no control: https://policies.google.com/privacy.
• If you complete the sign-in, we receive your email address, your Google user id, and whether Google has verified that address. We do not receive your password, and we do not request access to any other Google data.
• We store the Google user id so we can recognise you on your next sign-in.

Google LLC is based in the USA. Transfers are covered by Google's participation in the EU–US Data Privacy Framework and by the European Commission's standard contractual clauses.

Legal basis: Art. 6(1)(b) GDPR (providing the sign-in you requested). Where Google's own cookies are involved, § 25(1) TDDDG requires your consent, which is why the Google sign-in prompt is only loaded once you choose to use it.

PRO subscription and payments (optional)

Only relevant if you subscribe to PRO. Free accounts are never asked for payment details, and nothing in this section applies to them.

Payments are handled entirely by Stripe. We do not operate a checkout, and card numbers, bank details and billing addresses never reach our servers — you enter them on Stripe's own hosted pages, under Stripe's privacy policy.

What we send to Stripe. When you start a subscription we create a customer record at Stripe containing your email address, the display name on your account if you set one, and an internal reference to your account (your user ID). That reference is what lets an incoming payment event be matched back to the right account.

What we store here. After Stripe confirms a subscription we keep a small mirror of it so that "is this account allowed to use this feature" is a local lookup rather than an API call on every request. That mirror is:

• the Stripe customer ID and subscription ID;
• the subscription status (for example active, past due, canceled);
• the price identifier — i.e. whether you are on the monthly or yearly plan;
• the date the current period ends, and whether a cancellation is pending;
• the timestamp of the last payment event we applied, which is only used to ignore events that reach us out of order.

That is the whole of it. We hold no card data, no card fingerprint, no bank details and no billing address.

PRO granted by hand. Separately from any payment, we can switch an account to PRO ourselves — a free period, a goodwill gesture, an account whose payment is being sorted out. That is stored as a single date on your account until which PRO applies, and nothing else. No Stripe customer is created, no payment is involved, and no data leaves us. It lapses on its own when the date passes.

Invoices. Invoices are created and stored by Stripe, not by us. When you open the invoice list or the manage subscription link in your account settings, we ask Stripe for them at that moment and pass them through — we keep no copy. Where sales tax applies, Stripe determines it and processes the location data needed to do so. Stripe also processes payment and device data on its own account for fraud prevention and to meet the obligations placed on a payment institution.

Roles. For the payment itself Stripe acts as an independent controller, not as our processor: it is subject to its own regulatory duties (payment supervision, anti-money-laundering, tax) that we cannot direct. For the customer and subscription records it keeps on our behalf it acts as a processor within the meaning of Art. 28 GDPR.

Where the data goes. Our contracting entity is Stripe Payments Europe, Limited (Ireland). Stripe's group includes Stripe, Inc. in the United States, so a transfer to a third country takes place. It is covered by Stripe's certification under the EU-US Data Privacy Framework and by the European Commission's standard contractual clauses.

Legal basis: Art. 6(1)(b) GDPR — performance of the subscription contract you entered into. For the retention of billing records, Art. 6(1)(c) GDPR (compliance with statutory commercial and tax retention obligations). Stripe's own fraud prevention rests on its legitimate interests, Art. 6(1)(f) GDPR.

Cancelling and deleting. You can cancel at any time from your account settings, which opens Stripe's billing portal. Deleting your ASOApp account removes the local subscription mirror with it. It does not delete the customer and invoice records at Stripe: those are accounting documents both Stripe and we are legally required to retain (see Storage periods). If you want to know what Stripe holds about you, or to exercise your rights against Stripe directly, their privacy policy at stripe.com/privacy explains how.

Workspace sync (account holders only)

When you are signed in, the work you would otherwise keep only in your browser — your tracked apps and keywords, competitor lookups, audit and keyword-check history, and the related notes and settings — is also stored on our server and linked to your account, so you can reach it from another device. We store it as a single opaque document and do not analyse its contents.

If you are not signed in, none of this is sent to us; it stays in your browser.

Legal basis: Art. 6(1)(b) GDPR — this is the function the account exists to provide.

Rank tracking

So a background job can keep your tracked rankings up to date automatically, the apps and keywords you track, and their rank history, are stored on our server. This is anonymous — it is keyed to public App Store identifiers (app id, keyword, country), is tied to no account, and is not linked to your identity or IP address. Your private notes and view preferences stay in your browser's localStorage and are not sent to us.

Legal basis: our legitimate interest in providing the rank-tracking feature (Art. 6(1)(f) GDPR).

Email notifications (optional)

If you switch it on, we email you a summary of the rankings of the keywords you track — which moved up, which slipped, which newly entered or left the ranking. This is off by default; no account ever receives it without turning it on.

To provide it we store, linked to your account:

• the frequency you chose (daily, weekly or monthly, or off),
• which of your apps the summary should cover, identified by their public App Store id, plus the app name as a label (each app's summary covers every storefront you track it in — we store no separate country choice),
• when the last summary was sent, so you are not emailed twice for the same period, and
• a random unsubscribe token, which is what makes the unsubscribe link in the email work without you having to sign in first.

The email itself is assembled from the anonymous rank data described under Rank tracking above; switching notifications on is what links your choice of apps to your address. Summaries are only sent to a confirmed email address.

You can turn this off at any time — with the one-click unsubscribe link at the foot of every summary, or under Account settings → Email notifications. Turning it off stops the emails immediately; deleting your account removes the settings above along with everything else.

Legal basis: Art. 6(1)(a) GDPR — your consent, given by switching the notifications on, and withdrawable at any time with effect for the future.

Keyword lookups and Apple

When you research a keyword, look up an app, or check rankings, your browser queries Apple's public iTunes Search / App Store endpoints directly. As part of that direct request, Apple receives your IP address and the search term and processes them under Apple's own privacy policy (apple.com/legal/privacy). If a direct request is blocked, it falls back to our server, which performs the same public lookup on your behalf.

The Keyword Suggest autocomplete is the exception: it always runs through our server, so for that feature Apple sees our server's IP address, not yours.

Because Apple Inc. is based in the United States, this involves your data reaching a third country. On the normal path your browser contacts Apple directly, so it is your own browser that sends the request — Apple receives the IP address and search term as an independent controller and handles them under its own privacy policy (linked above), much as if you queried Apple's service yourself. In the fallback case our server performs the lookup for you; that transfer is necessary to carry out the App Store request you made. Where Apple Inc. is certified under the EU–US Data Privacy Framework, that framework additionally covers such transfers.

Legal basis: our and your legitimate interest in retrieving the requested App Store data (Art. 6(1)(f) GDPR); any transfer to the USA is necessary to fulfil the lookup you requested (Art. 49(1)(b) GDPR) and, where applicable, is additionally covered by the EU–US Data Privacy Framework (Art. 45 GDPR).

Anonymized, aggregated usage analysis

We analyze anonymized, aggregated usage data — the keyword strings that are researched or suggested (including Keyword Suggest searches) and App Store rankings — to improve the tool and for market research. This aggregated data is not linked to your identity, IP address or an account and does not constitute personal data. We may publish aggregated keyword statistics (e.g. difficulty and demand estimates) as public report pages.

Legal basis: to the extent the underlying keyword strings are briefly processed before aggregation, our legitimate interest in improving the service and in market research (Art. 6(1)(f) GDPR).

Server logs

Our server keeps standard technical logs (which include the requesting IP address and the request path) to operate and secure the service. We do not build user profiles from them.

Legal basis: our legitimate interest in the secure, stable operation of the service (Art. 6(1)(f) GDPR).

Rating the tool

If you rate the tool with the star widget, we store your rating (1–5) together with a one-way, salted hash of your IP address. This hash is pseudonymised personal data: it exists only to keep each visitor to a single vote — it cannot be reversed back to your IP, is tied to no account, and is used for nothing else. We never store your raw IP address, and we do not use it to identify or profile you.

Legal basis: our legitimate interest in preventing duplicate or abusive votes (Art. 6(1)(f) GDPR).

Feedback you send us

Next to the star rating there is a Give feedback link. If you use it we store:

• the message you wrote, exactly as you typed it,
• the page you were on and the language you were using, as context,
• a salted hash of your IP address (never the address itself), so a flood of submissions can be traced to one source, and
• a link to your account, but only if you were signed in when you sent it.

Sending feedback is entirely optional and works without an account. Signed out, the message carries no link to you at all — the form says so before you send. Signed in, it carries your account, which is the only thing that lets us reply.

If you delete your account, the link is removed and the message stays. Deleting an account removes what identifies you; it does not un-say what you told us. We keep no separate copy of your address alongside the message, so once that link is gone there is nothing left connecting the two.

Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in learning what is wrong with the product from the people using it. You decide what to write, and you can ask us to delete a message at any time.

Cookies and local storage

We set no tracking or advertising cookies, and use no analytics service that would need one.

What we do store on your device is limited to what the tool needs to work, which under § 25(2) TDDDG does not require consent:

• localStorage — your tracked apps, keywords, history and preferences (theme, language, whether you have seen the intro). This is what lets the account-free features work at all. It never leaves your browser unless you sign in and it syncs to your account.
• sessionStorage — a single short-lived flag used to show you a message after signing out. It is discarded when you close the tab. The cookies we set, in full:

None of these are used to profile you or to follow you across sites.

Changing your mind: you can review or withdraw your consent at any time via the Cookie settings link in the site footer — withdrawal is as easy as consent (Art. 7(3) GDPR), and takes effect immediately. Withdrawing only stops the Google prompt from appearing; nothing else changes.

If you allow Google sign-in, one further cookie appears:

Google may additionally read or set cookies on its own domains (accounts.google.com) under its own privacy policy. We have no access to those and cannot list them. If you do not allow the Google category, none of this happens: our own "Continue with Google" button simply redirects you to Google when you click it, and no Google code runs on this site at all.

Stripe: the checkout and billing-portal pages run on Stripe's own domains and set their own cookies there. Nothing of Stripe's is loaded into this site, and you only ever reach those pages by clicking through to them.

Third-party cookies: none, unless you use Sign in with Google. Google's sign-in code is loaded only at the point you choose to use it, and it may then set cookies on Google's own domains — see the section above.

Recipients and processors

Apart from the direct requests to Apple described above, your data is not shared with third parties, sold, or used for advertising. To run the service we use:

• our hosting provider, Uberspace (Germany), which processes server data (including IP addresses in logs) on our behalf as a processor within the meaning of Art. 28 GDPR. All email we send — address confirmation, password resets and, if you switched them on, keyword-ranking summaries — goes through the same provider, so your email address is processed there too. No separate mail service is involved, and no email marketing platform;
• Google, but only if you choose Sign in with Google — as an independent controller, not a processor, and only for the sign-in itself;
• Stripe Payments Europe, Limited (Ireland), and within its group Stripe, Inc. (USA), but only if you subscribe to PRO — for the payment itself as an independent controller, and for the customer and subscription records as a processor. See PRO subscription and payments above.

Storage periods

• Tracked apps, keywords and rank history: kept for as long as they are tracked so the history feature works; removed when you ask us to (see below).
• Server logs: kept only as long as needed to operate and secure the service, then routinely deleted.
• Rating (score + salted IP hash): kept to prevent repeat votes; removed on request.
• Feedback messages: kept while they are still useful to act on, then deleted. Any link to your account is removed the moment you delete it; the message itself is removed on request.
• Account data (email, password hash, Google connection): kept until you delete your account, then removed immediately and permanently. Deleting is self-service under Account settings.
• Subscription mirror (Stripe customer and subscription ID, status, plan, period end, last event timestamp) and any hand-granted PRO date: kept while the account exists and deleted with it. The corresponding customer and invoice records at Stripe are billing documents and are retained under the statutory commercial and tax retention periods (§ 257 HGB, § 147 AO) — depending on the type of document, six to ten years — which a deletion request cannot shorten.
• Synced workspace: kept while your account exists; deleted with the account, and replaced each time it syncs (we keep no version history).
• Email-notification settings (frequency, chosen apps, last-sent date, unsubscribe token): kept until you turn notifications off or delete your account, whichever comes first. We keep no copy of the emails we sent you.
• The copy in your browser: when you sign out, the synced work is removed from that browser — the account already has it, and leaving it behind would expose it to the next person using a shared computer. Work that was never synced is left alone, because then your browser is the only place it exists. The same reasoning is why deleting your account does not clear it: at that point the server copy is gone and your browser holds the only one.

No automated decision-making, no profiling

We do not use your data for automated decision-making or profiling within the meaning of Art. 22 GDPR. The difficulty, traffic and opportunity scores the tool produces are calculated from Apple's public App Store data — they describe keywords and apps, not you, and no decision is made about you on that basis.

Is providing data required?

Not for most of the tool. Keyword research, keyword discovery, the metadata builder, the top charts and the single-keyword check work with no account, and nothing on the public pages asks you for personal data. Rank tracking, competitor teardowns, the listing audit and App Discovery require an account; the only data required for one is an email address, which we need in order to give you a login you can recover. There is no legal or contractual obligation to provide it — if you choose not to, you keep using the rest of the tool anonymously, with your work stored in your browser.

If you subscribe to PRO, providing payment details to Stripe is required to perform that contract — there is no other way for us to take a payment. That requirement applies only to the subscription; declining it leaves the free plan and every tool on it exactly as it was.

Data protection officer

We are not required to appoint a data protection officer (Art. 37 GDPR) and have not appointed one — the processing described here is small in scale and is not our core activity. Address any data protection question to the controller above.

Your rights

Under the GDPR you have the right to access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18) and data portability (Art. 20) of your personal data, and the right to object to processing based on our legitimate interest (Art. 21). To exercise any of these — for example to have a rating you cast removed — or for any question about your data, contact us at hello@jungspree.com or via the address in the imprint.

If you have an account, you can exercise most of these yourself without contacting us: Account settings lets you change your password, download a copy of your data (Art. 20) and delete your account outright (Art. 17).

If you do not have an account we store no name, email or identifier, so we usually cannot identify you from our data alone; to act on a request about the rating hash we may need the IP address you rated from so we can match it.

You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR) — for us that is the Berliner Beauftragte für Datenschutz und Informationsfreiheit — or the authority in your place of residence.