Privacy Policy

Ledger is an internal revenue-reporting tool operated by Version Systems Private Limited("we"). It shows our own team the daily revenue, advertising earnings, advertising spend and active users of the mobile apps we publish. Ledger is not offered to the public: only team members we approve can sign in. This policy explains what data Ledger accesses, including data from Google, and how it is handled.

Data Ledger accesses from Google

When an authorised team member connects a Google account on Ledger's Integrations page, they grant Ledger read-only access through Google's OAuth consent screen. Depending on the account connected, Ledger requests:

• AdMob reports (read-only) — admob.readonly: the estimated earnings of our own apps per day, used to show each app's advertising income.
• Google Analytics (read-only) — analytics.readonly: the number of daily active users of our own apps.
• Google Cloud Storage (read-only) — devstorage.read_only: the sales and earnings report files that Google Play Console places in our own developer account's reports bucket, used to calculate daily subscription revenue.
• Basic account information — openid and email: the email address of the connected account, used only to label the connection on the Integrations page.

Ledger only reads these sources; it never creates, changes or deletes anything in AdMob, Google Analytics, Google Play or Cloud Storage.

How the data is used

• Figures read from Google are reduced to daily totals per app (for example, "ad earnings on 28 September") and shown to our authorised team members on the dashboard and in internal reports.
• Individual Play order rows are processed in memory to calculate those totals and are not stored.
• The data is used only to provide Ledger's reporting features. It is not sold, not used for advertising, and not used to train artificial-intelligence or machine-learning models.
• We do not share data obtained from Google with any third party.

Limited Use disclosure

Ledger's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Storage and security

• Ledger runs on Google Cloud (Firebase App Hosting) and stores its data in Google Cloud Firestore. All traffic uses HTTPS.
• The access granted when an account is connected (an OAuth refresh token) is encrypted with AES-256-GCM before it is stored, using a key held only by the server. It is never shown in the browser.
• Access to Ledger requires a team account; database access from browsers is blocked.

Retention and deletion

• A connected Google account can be disconnected at any time on the Integrations page; this deletes its stored access immediately.
• Access can also be revoked from the Google side at myaccount.google.com/permissions.
• Daily totals are kept for as long as they are needed for our internal reporting. To request deletion of any data, email digitalm@factohr.com.

Team member accounts

To sign in, team members use an email address and password managed with Firebase Authentication. We use this only to control access to Ledger and to record who saved or changed a figure.

Changes and contact

If this policy changes, the updated version will be published on this page with a new date. Questions about this policy or about data handled by Ledger can be sent to digitalm@factohr.com.