Skip to content
RocketASO
GuidesPricingFree auditSign inStart free
Start free
Menu
GuidesPricingFree auditSign inStart free

Privacy

What RocketASO keeps, and why

RocketASO reads your own store data to show your listing's numbers. This page says what it collects, what it reads, who else touches it, and how to remove it.

Updated 2026-11-20

Who is responsible

RocketASO is run by Aviad Katani, trading as Katani Labs, Tel Aviv, Israel, who decides how the personal data on this page is used (the data controller). Write to hello@rocketaso.app with Privacy in the subject about anything here.

What you give us

  • Your name and email, and a password stored only as a scrypt hash. If you sign in with Google or Apple, we keep the account id that provider returns.
  • The workspaces you create and the teammates you invite by email.
  • The store keys you upload: an App Store Connect API key, a Google Play service account, an Apple Search Ads key. Each is encrypted at rest with AES-256-GCM.
  • Settings you choose: webhook addresses, goals, reply templates, drafts of listing copy and screenshots.
  • When you buy a plan, you pay on Paddle's checkout. Paddle tells us your billing name, email and country, the plan, and whether the payment went through; it never sends us your card details.

What we read from the stores

With your keys, RocketASO reads your listing copy and media, ratings and reviews, App Store Connect analytics reports (subscription and trial figures among them) and the daily sales summary when you give your vendor number, Google Play reviews and vitals, the Play Console report export if you point us at it, and Apple Search Ads campaigns, search terms and popularity.

Without a key, it reads public pages only: App Store and Google Play listings, store search results and top charts for the apps you audit or watch.

How we use it

  • To show your numbers, run audits, rank checks and the weekly report, and to price each fix from your own reports.
  • To send alerts and the Monday brief to the email or channels you choose.
  • To draft review replies, listing rewrites, translations and screenshot captions when you ask for one; the next listing change on its own after a store read, for you to approve, unless you turn off "Draft the next listing change" in Settings (it is on by default); and thank-you replies to 5★ reviews when you turn that rule on.
  • We do not sell your data or show it to other customers. The one advertising use is measuring our own Facebook and Instagram ads with Meta, only while you allow it, as “Cookies and browser storage” below describes; your apps' store data, reviews and keys are never part of it.

Why we may use it

  • To provide the service you signed up for: your account, your store reports and the alerts you chose (our contract with you).
  • To keep RocketASO secure and working, and to fix and improve it (our legitimate interest in running a reliable service).
  • To keep billing and tax records (a legal obligation).
  • To measure our Facebook and Instagram advertising with Meta: with your consent where your browser's time zone is in Europe, and elsewhere unless you turn it off. “Cookie settings” in the footer changes it at any time.
  • Anything else only with your consent, which you can withdraw at any time.

Who else processes it

Each of these is used only when the service is switched on for this installation, and gets only what its job needs.

  • Hetzner Online hosts the servers and the database, in Germany.
  • Cloudflare stores the daily backup copies of the database, encrypted at rest, in the EU, and deletes each one 35 days after it is made.
  • Resend delivers email: your address and the message.
  • xAI, with its Grok model, writes drafts when model drafting is on, and gets what each draft needs, sent with that request: for a review reply, the review (the reviewer's store name, rating, title and text), your earlier replies and your product notes; for a listing rewrite or translation, the listing text with the App Store keyword field, your tracked searches and their ranks, the topics of recent low-star reviews, rival app names and your product notes; for screenshot captions, the screenshots themselves with the listing text, your tracked searches and what recent good reviews praise; and when you ask for a fix to be analysed, the evidence behind it (search terms, ranks and report figures).
  • Paddle.com, our online reseller, is the Merchant of Record for all our orders: it takes the payment, adds sales tax or VAT where it applies, and issues receipts, invoices and refunds. It handles your billing details under its own privacy policy, and card details never reach RocketASO. Paddle's checkout script loads only when you start a checkout in Billing or open a Paddle payment link (the /pay page, which Paddle's checkout links and failed-renewal emails open), and Paddle's Retain service gets your Paddle customer id, not your RocketASO account.
  • Google and Apple, when you choose to sign in with them.
  • Meta Platforms (Facebook and Instagram), only while you allow advertising measurement: its pixel in your browser and our server tell it which public pages you open and when you finish a free audit, create an account, open a checkout, start a trial or first pay (with the amount charged), with Meta's cookie identifiers, your IP address and browser details, and a hash of your account's email address. Meta handles this under its own privacy policy. “Cookies and browser storage” below has the details.
  • Webhooks you add, such as Slack or Discord, receive the alerts and briefs you send them.

Where it is stored

The live database is in Germany, in the EU, and its backup copies are in the EU too. RocketASO is run from Israel, which the European Commission recognises as protecting personal data adequately. Resend, xAI, Paddle and Meta may process data in the United States, the United Kingdom or elsewhere, under the European Commission's standard contractual clauses or an equivalent safeguard.

Cookies and browser storage

RocketASO keeps your sign-in in an httpOnly cookie, or in your browser's local storage where that cookie cannot reach our server. While you are signed in, local storage also keeps a marker that you are, with your account's id, name and email address. It also keeps small preferences, such as the colour theme and the app you last opened. RocketASO advertises on Facebook and Instagram, and measures those ads with Meta's pixel in your browser and Meta's Conversions API from our server. It is the only advertising tracker and the only third-party measurement on this site, and it follows your choice. If your browser's time zone is in Europe, or cannot be read, nothing is loaded from Meta and nothing about you is sent to it unless you press Accept on the banner. Elsewhere it is on from your first page, and the banner offers Turn off; that default never replaces a Decline or Turn off you pressed. A browser that sends a Global Privacy Control signal counts as having declined, everywhere. Your choice and its time are kept in your browser's local storage, and “Cookie settings” in the footer of every public page opens the banner again so you can change it. While it is allowed, Meta's script (from connect.facebook.net) runs on the public pages and the sign-in page, and in the signed-in app only to report a new account or an opened checkout. It sets Meta's cookies _fbp and _fbc (a browser identifier, and the fbclid identifier of the Meta ad you clicked), and tells Meta which of those pages you open and when you finish a free audit, create an account or open a checkout, together with what a browser sends any site it contacts: your IP address, your browser's details and the page's address. Meta's script is kept off any page whose address holds more than campaign tags, such as a password-reset or invite link, a shared report, an audited app or a workspace, so Meta is not told those addresses; a step taken on such a page is reported from the next page instead. Our server sends Meta the same three steps, and a trial starting and a first payment with the amount charged and its currency, each with those two identifiers and your browser's user agent, your IP address when your browser made the request, and, once you have an account, a SHA-256 hash of your email address, never the address itself. For the steps that arrive later from our payment provider, your account keeps your choice and its time, the two identifiers and your browser's user agent; they are shown to no one and are deleted with the account. Meta uses what it receives under its own privacy policy to measure and deliver ads. Turning it off removes Meta's cookies from this site and loads no Meta script on later pages. If you are signed in when you turn it off, our server stops sending anything more for your account at once. If you are signed out, your account keeps its earlier choice until this browser next signs in, or opens a page of the site while signed in, so a trial or payment reported before then is still sent. What Meta has already received stays with Meta. RocketASO measures, on its own server, how visitors become customers. Free audits are counted as daily totals of how many were started and finished, by site section (for an article, comparison, shortlist, free tool, definition or diagnosis, the page itself), the kind of site the visit came from, and its channel and campaign, with no account and no IP address. For each account it keeps one record per step the account reaches (account created, first app tracked, store connected, first recommendation seen with a store connected, checkout opened, trial started, first payment, subscription ended, these last four for each workspace), with the account, its workspace and the time. The checkout, the first payment and the end of a subscription also keep the plan, billing interval and quantity, and the first payment its price and currency. It also stores which section of the site you first opened, or which of those guide pages, the website name you came from (not the full address), any campaign tags in the link (utm_source, utm_medium, utm_campaign, utm_term, utm_content), whether the link came from a Google, Microsoft or Reddit ad and which, and the kind of source they add up to. RocketASO's own measurement reads only whether the link has one of those ads' click identifiers, and never stores or sends the identifier itself; Meta's fbclid is used only as described above, and never for this. These records are deleted with the account. The acquisition report also adds up each paying workspace's charges and refunds from its billing records, which are kept with the workspace, and whether it is still subscribed. Before you have an account, and unless advertising measurement is allowed, this measurement writes nothing about where you came from to your browser's storage or cookies: the open page holds your first page in memory only, so a reload, a new tab or closing the tab forgets it, and so does signing in. While advertising measurement is allowed, those same details (never a click identifier itself) are also kept in your browser's local storage for 30 days, so a sign-up on a later visit is still credited to the first one; turning it off, or signing in, removes them. As on any website, the address you open, with any campaign tags and an ad's click identifier, stays in your browser history, and the site's page framework keeps a copy of it with that history entry, even after the page tidies the address. Neither is used for this measurement. A sign-up link opened in a new tab or copied, and “Track this app free”, put those details in the sign-up page's address, so they appear there too, and a Google or Apple sign-in hands them, with your advertising choice, to our server, which holds them for at most 10 minutes, until the sign-in returns, and keeps them only if it creates an account. RocketASO's own measurement is sent only to RocketASO. Separately, like any website, our web servers' access logs record each address requested, which can include campaign tags, an ad's click identifier and those sign-up page details; those logs are kept for a limited time and are not used for this measurement.

How long we keep it

Data stays while the account exists; store reports are kept as history so later comparisons work. Deleting the account in Settings cancels any paid plan on the workspaces only you belong to, then removes those workspaces with everything in them, and your login and signup details, from the live database at once, with every invite sent to your current email (an invite to an address you used before is not linked to your account, and stays until the workspace that sent it is deleted). A workspace you share keeps the notes, decisions and activity you left in it, which can carry your name. If you pay for a workspace's plan, shared or one you have left, that plan ends at once and the Paddle customer it was billed to is detached from the workspace: its other members see neither your card nor your invoices, and the workspace keeps only Paddle's ids for that customer and the ended subscription, so a later payment from that customer is cancelled. If another member already pays for their own plan on that same Paddle customer, the customer stays with their plan: we stop showing your payments to the workspace's members and change the customer's contact details in Paddle to theirs, but Paddle's own billing pages for that customer may still show its earlier payments and saved cards. We keep the id of each deleted workspace and when it was deleted, and nothing else, so a payment for it is cancelled. If our operator has to finish a deletion without Paddle's confirmation, we keep a receipt with the workspace and Paddle ids and the reason, without your name or email. Copies in server backups expire on the backup schedule of the deployment. Paddle keeps payment records for as long as tax law requires.

Your choices

  • Download: most tables have a CSV button.
  • Correct: change your name, email and password in Settings.
  • Revoke: Disconnect a store in Connections, and revoke the key in App Store Connect, Play Console or Apple Ads as well.
  • Delete: Settings, Account, Delete the account.
  • Advertising measurement: turn it on or off with “Cookie settings” in the footer of any public page. Your browser's Global Privacy Control signal turns it off too.
  • Ask: write to us for a copy of everything we hold about you, to correct or delete it, or to object to a use. We answer within 30 days.
  • Complain: you can also go to a data protection authority, such as Israel's Privacy Protection Authority or the one where you live.

Children

RocketASO is for adults who run apps and is not meant for anyone under 18. If a child has given us personal data, write to us and we delete it.

Changes to this policy

The new version is posted here with a new date. If a change affects how your data is used, account owners also get an email before it applies.

Contact

Email hello@rocketaso.app.

Terms of serviceRefund policySecurityContact

On this page

  1. Who is responsible
  2. What you give us
  3. What we read from the stores
  4. How we use it
  5. Why we may use it
  6. Who else processes it
  7. Where it is stored
  8. Cookies and browser storage
  9. How long we keep it
  10. Your choices
  11. Children
  12. Changes to this policy
  13. Contact
RocketASO

Names one listing fix for the week, in dollars when the reports allow, then compares installs before and after it.

Product

  • Pricing
  • Black Friday 2026
  • Public lookup
  • Audit a listing free

Company

  • Privacy policy
  • Terms of service
  • Refund policy
  • Security
  • Contact

Guides

  • How to do ASO: read, change, read again
  • Google Play ASO: no keyword field, more to test
  • App Store rankings: one list, read once
  • ASO services, software or DIY: the real costs
  • App Store keywords: fill the field nobody sees
  • All guides

Comparisons

  • vs AppTweak
  • vs Sensor Tower
  • vs AppFollow
  • vs Mobile Action
  • vs Astro
  • vs RespectASO
  • vs Appfigures
  • vs Asodesk
  • vs AppRadar
  • vs TheTool
  • vs Sonar
  • vs ASO.dev
  • All comparisons

Alternatives

  • Best ASO tools in 2026
  • Best free ASO tools
  • Best ASO tools for the App Store and Google Play
  • All alternatives

Free tools

  • App Store title character counter
  • App Store subtitle character counter
  • App Store keyword field counter
  • Google Play title character counter
  • Google Play short description counter
  • Metadata checker
  • Store test calculator
  • All free tools

Glossary

  • App Store optimization
  • Search result conversion
  • App Store title
  • App Store subtitle
  • App Store keyword field
  • Google Play short description
  • Listing audit
  • Asking for ratings
  • All definitions

Diagnose

  • Search impressions are not becoming downloads
  • The keyword is in the metadata and the store is not showing the app
  • A rival changed their listing
  • All diagnoses