Security and privacy
What Revenue Sensor stores, what it never touches, and how access to your accounts works.
Revenue Sensor reads business reporting data. It does not read your users' data, because it is never in a position to — there is no SDK in your app and no device-level identifier anywhere in the system.
What we store
- Aggregated daily metrics: spend, revenue, installs and related counts, by app, country and account.
- The credentials or tokens needed to keep fetching those metrics, encrypted at rest.
- Your account, workspace and team membership records.
What we never store
- End-user identifiers, advertising IDs, or device-level events.
- Payment card details — billing is handled by our payment provider and card data never reaches our servers.
- Anything from your app's own database. We have no connection to it.
Access and scopes
Every connector requests read-only scopes. Revenue Sensor cannot change a bid, pause a campaign, edit a store listing or move money. You can revoke access from the provider's own settings at any time, and disconnecting in the console removes the stored credential.
Signing in
Sign-in is passwordless: you enter your email and receive a six-digit code. Sessions are bound to one device and expire after a period of inactivity, and signing in somewhere new ends the previous session.
Data retention
Daily detail is kept for the history window your plan includes. Deleting your account removes your workspace data; the Data Deletion page explains how to request it and what the timeline is.
Processing your data
If your organisation needs a Data Processing Agreement in place, ours is published and covers the processing described above.