Revenue Sensor Security and Privacy for Your Marketing Data
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 and never returned through the API.
- 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 Paddle, 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 is used read-only. Revenue Sensor never changes a bid, pauses a campaign, edits a store listing or moves money. You can revoke access from the provider's own settings at any time. Disconnecting in the console removes the stored credential and deletes the data that connection imported; reconnecting later starts a fresh import.
Signing in
Sign-in is passwordless: you enter your email and receive a six-digit code that expires after 10 minutes. One session covers every ScaleSensor product, it ends after 72 hours without activity, and signing in on a new device signs out the previous one.
Data retention
What you can read is limited to the history window your plan includes. There is no self-serve account deletion: 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.