Privacy policy
RevenueOverview is a dashboard that shows app and game developers their own revenue from the App Store, Google Play, AdMob and Steam. This policy explains which personal data we process, why, and what your rights are. We wrote it to match exactly what the service does: no advertising, no third party tracking and no selling of data.
1. Who we are
RevenueOverview is operated by Corbata Webdevelopment, Adriatische Zee 1a, 3825WZ, Amersfoort, Netherlands, registered with the Dutch Chamber of Commerce (KvK) under number 39079294. We are the controller for the personal data described in this policy. You can reach us at info@revenueoverview.com.
2. What we process
Account data
- Your email address and, if you set one, a display name.
- Your password, stored only as an Argon2id hash. We can never see your password.
- If you turn on two-factor authentication, the secret of your authenticator app, stored encrypted.
- If you add passkeys: the name you gave each passkey, its public key and a usage counter. The private key never leaves your device or password manager, and no biometric data (such as your fingerprint or face) is ever sent to us.
- Preferences such as your display currency, and technical account data such as the time of your last sign in and failed sign in attempts.
Purchases
When you buy a plan in one of our apps, the payment is handled by Apple or Google. We never receive your payment details, your name or your billing address. We receive and store the purchase record the store sends us: which plan you bought, the transaction number, the start and end date, and whether it renews or was refunded. We use it only to give your account access to the plan.
Store credentials
To read your revenue, you give us credentials for the stores you connect: an App Store Connect API key, a Google Cloud service account key, a Google (AdMob) sign in or a Steamworks Financial API key. These are encrypted with XChaCha20-Poly1305 before they are stored, are never shown again after saving and are only used to request your own reports.
Revenue data
We import the names of your apps, games and products and your revenue per day, per product and per type (sales, subscriptions, ads), with the number of units and the amounts in the original currency and in euros. Next to that we store per day, product and buyer country the number of downloads (App Store), purchases, refunds and ad impressions and the revenue, and per day and product the number of Steam wishlist additions, removals, purchases and gifts. The reports we download from the stores can contain details about individual transactions, such as an order number or the buyer's state or postal code. We do not keep those details: only daily totals per product and country are stored, which do not identify a buyer.
Security and usage logs
- A security log of events such as sign ins, failed sign in attempts, changes to credentials and API tokens, with the IP address and browser (user agent) involved.
- For API tokens used by the mobile apps: the name you gave the token, when it was last used and from which IP address. The token itself is never stored, only a keyed hash of it.
- A log of each synchronisation with a store (time, result and number of records).
- Our web server keeps standard access logs (IP address, time, requested page, browser) for security and troubleshooting.
Website statistics
To see how the website is used, we count visits with CorbaCount, our own analytics service, hosted on servers in Germany. For each page view it records:
- the page address and title, the referring website and any campaign (UTM) tags in the address;
- the browser, operating system and device type (derived from the user agent, which itself is not stored), screen resolution and preferred language;
- the country and network operator, derived from your IP address;
- page speed measurements (Core Web Vitals) that your browser reports;
- a random visitor identifier from the
_cc_vidcookie (see section 6) and a device hash made in your browser from your time zone, language, screen size, colour depth, platform and number of processor cores, used to recognise returning visitors when the cookie is missing.
Your IP address is only used to look up the country and network and to filter out traffic from data centers. It is never stored with the page view, not even as a hash, and is deleted within 24 hours at the latest. The statistics contain no name or email address, are not linked to your RevenueOverview account, are not used to build profiles across websites and are never shared with advertisers.
3. Why we process it and on which legal basis
- To provide the service (account, store connections, importing and showing your revenue, the mobile API): necessary for the performance of our agreement with you (Article 6(1)(b) GDPR).
- To keep the service and your account secure (security log, rate limiting, account locking, access logs): our legitimate interest in protecting the service and your data (Article 6(1)(f) GDPR).
- To understand how the website is used and improve it (website statistics): our legitimate interest in running and improving our website, with minimal impact on your privacy because the statistics are first-party only, store no IP addresses and are not used for profiling or advertising (Article 6(1)(f) GDPR).
- To meet legal obligations, for example tax administration if you pay for the service (Article 6(1)(c) GDPR).
We do not use your data for advertising, profiling or automated decision making, and we do not sell it.
4. Google user data (AdMob)
If you connect AdMob, you sign in with Google and grant RevenueOverview read only access to your AdMob reports (the admob.readonly scope). We store only an encrypted refresh token and use it to request your network report: estimated earnings, impressions and ad requests per app, country, ad format and day. We do not access any other Google data.
RevenueOverview's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, data from Google APIs is only used to show you your own revenue, is not transferred to others except as necessary to provide the service, to comply with the law or as part of a merger or acquisition, is not used for advertising, and is not read by humans unless you ask us to (for example for support), it is needed for security or to comply with the law.
You can revoke access at any time by deleting the AdMob connection in RevenueOverview or at myaccount.google.com/permissions.
5. Who receives data
- The stores you connect (Apple, Google and Valve): we send them your credentials only to request your own reports, as their APIs require.
- Our hosting provider, which stores the data on our behalf on a server in Germany, under a data processing agreement. The data is processed under the GDPR and the German Federal Data Protection Act (BDSG).
- Apple and Google as payment providers: when you buy a plan, the store receives a random identifier of your account with the purchase, so the purchase can be linked to your account. It contains no personal data.
- Our email provider, only to deliver the confirmation email when you sign up.
- CorbaCount, our own analytics service (see "Website statistics" above). For its live visitor view it uses the Pusher Channels service, which receives only the random visitor identifier and minimal page view details.
- Authorities, only when we are legally required to.
Exchange rates are fetched from the European Central Bank and an open currency dataset. Those requests contain no personal data. Apart from the CorbaCount statistics script, the website loads no external scripts, fonts or trackers, and no data is shared with advertising or analytics companies.
The stores you connect are based partly outside the European Economic Area. Your data is exchanged with them because you instruct us to connect to them, and they process it under their own privacy policies and safeguards, such as the EU-US Data Privacy Framework.
6. Cookies
We only use cookies that are needed for the service to work:
revenueoverview_sessionkeeps you signed in and protects forms against cross site request forgery. It is deleted when you sign out or after a period of inactivity.revenueoverview_rememberis only set when you tick "Keep me signed in for 30 days". It is deleted when you sign out, and expires 30 days after your last visit.sidebar_collapsedremembers whether you minimized the navigation bar. It contains no personal data.
For the website statistics we also use one analytics cookie:
_cc_vidcontains a random identifier, so the statistics can group page views into visits and tell new visitors from returning ones. It is set on this website only (first-party), is never used on other websites and expires 365 days after your first visit.
This cookie has only minor consequences for your privacy and is used only to measure how our own website is used, which Dutch law (article 11.7a of the Telecommunicatiewet) allows without consent. We do not use advertising or third party tracking cookies. You can delete or block cookies in your browser at any time; the website keeps working without them.
7. How long we keep data
- Account data, revenue data and logs are kept as long as your account exists.
- Website statistics are kept as long as we use them for this website. IP addresses used for the country lookup and bot filtering are deleted within 24 hours, and page views marked as bot traffic after 30 days.
- When you delete a store connection, its credentials and all revenue imported through it are deleted immediately.
- API tokens expire after 90 days without use and can be revoked at any time.
- You can delete your account yourself under Settings. Your account and all related data (connections, credentials, revenue, API tokens and your security log) are deleted immediately and permanently, and AdMob access is revoked at Google. Backups containing the data are overwritten within 30 days.
- Data we must keep by law, such as invoices, is kept for the legal period (in the Netherlands 7 years).
8. Security
We protect your data with, among other things, encryption of all credentials and two-factor secrets, HTTPS only, hashed passwords and API tokens, optional two-factor authentication, rate limiting and account locking, a strict content security policy and separate storage of encryption keys and backups. No system is perfectly secure. If a data breach affects you, we will inform you and the Dutch Data Protection Authority as required by law.
9. Your rights
You have the right to access, correct and delete your personal data, to restrict or object to its processing and to receive it in a portable format. You can change most data yourself under Settings and Sources, and delete your account under Settings. For other requests, email info@revenueoverview.com. We respond within one month.
You also have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) or the supervisory authority in your own country.
10. Children
RevenueOverview is meant for developers and businesses and is not intended for anyone under 16. We do not knowingly process data of children.
11. Changes
We may update this policy when the service changes. The date at the top shows the current version. If a change matters for you, we will let you know by email or in the dashboard before it takes effect.
12. Contact
Corbata Webdevelopment
Adriatische Zee 1a, 3825WZ, Amersfoort, Netherlands
info@revenueoverview.com