Privacy Policy
Last updated .
This policy explains what personal data AsoBeast collects, why, who receives it, how long it is kept and what you can do about it. It covers:
- the website at asobeast.com and the documentation at docs.asobeast.com,
- the hosted AsoBeast service at app.asobeast.com, including its REST API and MCP server,
- the emails the service sends and any message you send us.
It does not cover a copy of AsoBeast you run on your own server. That case is described in Self-hosted installations.
Who we are
AsoBeast is operated by Adex77, an independent developer based in Poland, who is the data controller for the processing described here. In this policy “AsoBeast”, “we” and “us” mean Adex77.
For anything about your personal data, write to support@asobeast.com. We have not appointed a data protection officer, because Article 37 of the GDPR does not require one for the processing we do.
The short version
- We collect what is needed to run your account, bill you and track the apps and keywords you choose.
- We use Google Analytics on asobeast.com, only after you accept analytics cookies. The app does not use it.
- We use Sentry to catch errors, with account details, cookies, headers and request bodies stripped out.
- Payments are handled by Link, a Stripe affiliate, which uses your checkout details under its own privacy policy. We never see or store your card number.
- We read public store pages. The only data about your app’s users we handle is what they publish in store reviews, and the totals Apple and Google report if you connect a store console.
- We do not sell personal data or use it for advertising.
- You can export everything and delete your workspace at any time.
What we collect
When you visit the website or the docs
- Usage data on asobeast.com, if you accept analytics cookies: pages viewed, how you arrived (referrer and campaign parameters), approximate location derived from your IP address, device, browser and language. This is collected by Google Analytics.
- Usage data on docs.asobeast.com: pages viewed and searches, collected by Mintlify, which hosts the documentation.
- Technical data that any web server receives: IP address, browser and the page requested. Our hosting providers use it to serve the page and protect the site from abuse.
- Nothing from the free tools. The keyword rank tracker and the listing audit run in your browser, which sends the app ID, keywords and country you enter straight to Apple’s iTunes Search API. The keyword field checker sends what you enter nowhere. None of it reaches our servers, and Apple handles its requests under its own privacy policy.
When you use the hosted service
Account data you give us
- Email address and a hash of your password. We never store the password itself.
- Your display name, if you set one.
- The names and emails of teammates you invite.
You need an email address and a password to create an account, and a card and billing details to start a trial or buy a plan. Everything else is optional.
Workspace data you give us
- Store URLs and identifiers of the apps you track, your competitors, groups and the top charts you follow.
- Keyword phrases and the markets you track them in, including keyword files you import from other tools.
- Notes you add, such as named events on a rank chart.
- Alert settings, email recipients and webhook URLs, including the chat tools you send alerts to.
- The iOS keyword field, if you paste it in or import it from App Store Connect.
- Review replies you write or draft, and the guidelines you set for them.
- Personal API tokens, which we store only as a hash.
Store console connections
If the workspace owner connects App Store Connect or Google Play Console, we store the key’s identifiers and fingerprint and, encrypted, the private key or Google sign-in token. With it we download the totals Apple and Google report for your apps, such as impressions, downloads and conversion, which do not identify anyone. We also import the keyword field if you turn that on and post the review replies you confirm, looking up the review at the store to do so. Disconnecting deletes the key. More detail is in Store console credentials.
Data we derive for you
Rankings, search results, listing snapshots, category ranks, top chart positions, public reviews of the apps you track, audits, keyword scores and recommendations. All of it comes from publicly visible App Store and Google Play pages, except the funnel figures above.
Billing data
Your plan and subscription status, and the details you enter at checkout: billing name, email and address, and a tax ID if you add one. Link needs them to charge you, calculate tax and issue your invoice, and shares the order details with us so we can attach the plan to your workspace. Card details are entered in Link’s own checkout, embedded in the app or on its own page, and never reach our servers. When you start a trial, Stripe gives us the card’s fingerprint, a code that identifies the card without revealing its number, which we use only for the trial record below.
Usage and technical data
- Server logs with the IP address, request URL and query, workspace and correlation identifiers, timing and, in some events, an email address. Secrets are removed before a line is written.
- Error reports sent to Sentry, described in Who receives your data.
- A record of each AI call: which feature you ran, for which app, when, the model and the number of tokens. It counts your monthly AI allowance and never holds the prompt or the answer.
- A trial record: a keyed hash of the email address and of the card fingerprint that started a trial, so each mailbox and each card gets one trial. It holds neither the address nor any card data, and points to no account.
- A log of each time we access your workspace to help you, with the operator, the action and the reason.
Messages
What you write to us by email or through support, and our replies.
People who appear in public store data
Some of what AsoBeast collects from the App Store and Google Play is about people who are not our customers:
- Reviewers. Each public review carries the reviewer’s public nickname, the rating, the text, the date and the storefront.
- Developers who publish under their own name. A store listing shows the developer’s name, and sometimes a support email or website.
Apple and Google are the source. AsoBeast stores this data so the workspaces that track an app can read, analyse and answer it, and shows it to no one else. If you appear in it and want it removed from AsoBeast, or want to object, write to us.
What we never collect
AsoBeast has no SDK or tracking pixel, so it cannot receive data about the people who use your app beyond what is described above. We run no advertising cookies and do not use your data for ads.
Why we use it and our legal basis
Where the GDPR applies, each use rests on one of these legal bases:
| What we do | Legal basis |
|---|---|
| Create and secure your account, run the daily tracking, send alerts | Performance of our contract with you |
| Connect a store console, read its reports and post the review replies you confirm | Performance of our contract with you |
| Manage your subscription and keep accounting records | Contract, and our legal obligations under tax and accounting law |
| Send service emails: confirmation, alerts, trial and billing notices | Performance of our contract with you |
| Measure how the website is used with Google Analytics | Your consent, which you can withdraw at any time |
| Find and fix errors with Sentry, keep server logs, prevent abuse | Our legitimate interest in a working and secure service |
| Keep a trial record so each mailbox and card gets one trial | Our legitimate interest in preventing abuse of the free trial |
| Log our own access to your workspace | Our legitimate interest in accountability and security |
| Store public reviews and listings, with the names they show, for the workspaces that track the app | Our and our customers’ legitimate interest in reading and answering feedback and studying the market |
| Count AI calls against your plan’s monthly allowance | Performance of our contract with you |
| Answer your messages and handle complaints | Contract, or our legitimate interest in answering you |
| Send product news | Your consent. We send none without it |
| Respond to lawful requests and defend legal claims | Legal obligation, or our legitimate interest in establishing or defending one |
We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.
Cookies
We use as few cookies and as little browser storage as the service needs, plus analytics cookies only when you accept them.
asobeast_session, set by the app. Keeps you signed in. Strictly necessary. Kept for 7 days.sidebar_state,asobeast_collapsed,asobeast_alerts_seenand the app’s browser storage entries, set by the app. Remember display preferences and carry no identifier. Cookies are kept for up to 1 year, and storage entries until you clear them.asobeast-cookie-consent, kept in your browser’s storage by asobeast.com. Remembers whether you accepted or rejected analytics cookies. Kept for 180 days._gaand_ga_*, set by Google Analytics. Count visits to asobeast.com and tell returning visitors from new ones. Kept for up to 2 years.- Stripe and Link cookies, set on the checkout and billing pages and on link.com for payment security, fraud prevention and, if you choose to save your details with Link, faster checkout, under their own policies.
Under Article 399 of the Polish Electronic Communications Law, strictly necessary cookies and the storage entries that only remember your settings do not need consent. Google Analytics cookies are set only after you accept them in the cookie banner. The banner asks again after 180 days. You can change your choice at any time from the cookie settings link in the footer, which also removes the Google Analytics cookies when you reject them.
Who receives your data
We use service providers that process data on our behalf, under data processing terms that bind them to our instructions. They are:
- Cloudflare hosts asobeast.com and the app, its database and queue, sends our emails and stores our offsite backups. It receives everything the service stores, the IP address and technical data of each request, the recipient and body of each email, which can name your apps and keywords, and backup archives that are encrypted before they leave our control, so Cloudflare cannot read them.
- Mintlify hosts docs.asobeast.com. It receives the technical data of each request and the usage data described above.
- Google Analytics (Google) measures website usage, with your consent. It receives pages viewed, events, device and browser, and approximate location. Google Analytics 4 does not log or store IP addresses.
- Sentry (Functional Software, Inc.) monitors errors. It receives the error type, a message and stack trace, with secrets removed from server errors, workspace and correlation identifiers, and the request path with identifiers masked. It never receives your account details, cookies, headers, query strings or request bodies.
- Webshare carries requests to the App Store and Google Play. It receives the store request itself, a keyword phrase and a storefront, and no account data.
- OpenAI powers the optional AI features, described in AI features.
Some recipients act on your instructions rather than ours, and use the data under their own terms:
- Apple and Google, when you connect a store console. We call their APIs with your key to read your reports and to publish the review replies you confirm, which then appear publicly under your developer name.
- The chat tools and endpoints you add as webhooks, such as Slack, Discord, Microsoft Teams, Telegram or Google Chat. They receive the alert reports you set up, with app names, icons, keywords and review text.
Stripe and Link
When you start a trial or buy a plan, Sold through Link, LLC, an affiliate of Stripe, processes the payment as the merchant of record. Stripe and Link run the checkout, the payment, tax collection, receipts, invoices, the billing portal, payment support, refunds and disputes. They process your name, email, billing address, tax ID, payment details and order details as independent controllers, not under our instructions, as described in the Link privacy policy and Stripe’s privacy policy. We pass them your email and a workspace identifier when you start a checkout, and they share the order details and the card fingerprint with us. If you ask Link to delete your data, it also cancels your subscription.
We may also disclose data when the law requires it, to protect our rights or the safety of others, or to a buyer of the service if AsoBeast is ever sold, in which case this policy continues to apply to your data.
We do not sell or rent personal data, and we do not use one customer’s keywords to serve another.
AI features
AI features are optional. A request goes to OpenAI only when you invoke one, never on a schedule or without you starting it. Depending on the feature it carries the listing metadata, icon, screenshots and tracked keywords of the app you ran it on, competitor icons and titles, or the evidence behind a recommendation. A review translation carries the review’s title and text. A reply draft also carries the reviewer’s public nickname, the rating, your guidelines and instructions, and your earlier replies. On the hosted service those requests use our OpenAI account and are processed under OpenAI’s API terms, which do not allow OpenAI to train its models on them. A store console key is never sent. If you do not want this, do not use the AI features.
International transfers
We are based in the European Union. Some providers above, including Cloudflare, Google, Mintlify, Sentry, Webshare and OpenAI, may process data in the United States or other countries outside the European Economic Area. Where they do, the transfer is covered by the EU-US Data Privacy Framework for certified companies, which remains valid while an appeal against it is pending before the Court of Justice of the EU, by the European Commission’s Standard Contractual Clauses, or by another safeguard recognised under Chapter V of the GDPR. You can ask us for a copy of the relevant safeguard.
Stripe and Link process checkout data in the European Union and the United States, where Sold through Link, LLC is based. They transfer the data they control under the safeguards described in their own privacy policies.
How long we keep it
| Data | Kept for |
|---|---|
| Account and workspace data, including store funnel figures | While your account exists, then deleted as described below. Raw store report files are kept for 35 days |
| Keyword rankings, category ranks and top chart positions | 365 days |
| Search results | 90 days for the top 10, 30 days below it |
| Listing snapshots and closed action items | 180 days, and the newest snapshot of each app and market is always kept |
| Reviews, listing changes, audit scores | While you track the app |
| Alert delivery log and server logs | 30 days |
| Billing events stored by the app and error reports | At most 90 days |
| AI call records | 400 days, and the current month is always kept for the allowance |
| Google Analytics data | At most 14 months |
| Backups | 56 days, encrypted |
| Trial record (hashes only) and the log of our access to your workspace | Indefinitely, so a deleted account cannot start a new trial with the same mailbox or card, and so our access stays accountable |
| Receipts, invoices and accounting records | Link keeps receipts and invoices as merchant of record. We keep our own records as long as Polish tax law requires, normally five years from the end of the year they concern |
| Support messages | As long as needed to resolve your request and any follow-up |
Export and deletion
You can export your workspace’s data at any time, from the app as CSV or JSON, or as an archive through the API. The export leaves out credentials and account-recovery state, raw store report files, stored billing events, the log of our access and shared search results. Ask us for any personal data held in those. Export keeps working after paid access ends and while a deletion is pending.
The workspace owner can delete the workspace from Settings. Deletion waits seven days so it can be cancelled, then removes the workspace and everything it owns, deletes its Stripe customer and cancels any subscription. These limits apply:
- Backups still hold the deleted data until they rotate out, at most 56 days later.
- Stripe and Link keep their own payment records under their legal obligations. Link keeps your receipts and invoices as the merchant of record, so ask Link directly about those.
- Keyword phrases and top chart captures are shared and carry no owner. Phrases are not deleted, and captures stay for up to 365 days.
- Stored billing events stay, unlinked from the workspace, for up to 90 days.
- The trial record and the log of our access stay, as described above.
The full detail is in Data export, deletion and retention.
Your rights
Under the GDPR and similar laws you have the right to:
- access the personal data we hold about you and get a copy,
- correct data that is wrong,
- delete your data,
- restrict how we use it,
- port it to another service in a machine-readable format,
- object to processing based on our legitimate interests, including the storage of a review or listing that names you,
- withdraw consent at any time, which does not affect processing that happened before.
Most of this you can do yourself in the app. For the rest, write to support@asobeast.com. We answer within one month, which the law allows us to extend by two further months for complex requests, and we may ask you to confirm your identity first.
You can also complain to a data protection authority. Ours is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stanisława Moniuszki 1A, 00-014 Warszawa, Poland (uodo.gov.pl), and you can also go to the authority in the country where you live or work.
If you live in the United States, we do not sell or share personal information as the California Consumer Privacy Act and similar state laws define those terms, and we do not use it for cross-context behavioural advertising or to infer characteristics about you. Wherever you live, you can use the rights above by writing to us, and you will not be treated differently for doing so.
Security
Passwords are hashed with Argon2, API tokens are stored only as hashes, store console keys are sealed with AES-256-GCM, traffic is encrypted in transit and backups are encrypted before they leave the server. Access to production data is limited and every support access through our admin tools is logged. No system is perfectly secure. If a breach puts your rights at risk we will notify the supervisory authority within 72 hours and tell you without undue delay where the law requires it.
To report a vulnerability, follow the security policy.
Children
AsoBeast is a professional tool for people aged 18 and over. We do not knowingly collect data from children. If you believe a child has given us personal data, write to us and we will delete it.
Self-hosted installations
AsoBeast is open source under AGPL-3.0. If you run it on your own server, we receive nothing from it: the software sends no telemetry and contacts no service of ours. Every outbound integration, such as email, webhooks, AI, a proxy or a store console, stays off until you configure it. You are the controller for everything your installation holds, and this policy does not apply to it.
Changes to this policy
We will post changes on this page and update the date at the top. If a change materially affects how we use your data, we will tell you by email or in the app before it takes effect.
Contact
Adex77, Poland. Email: support@asobeast.com
See also the Terms of Service.