Earnin Tracker
Privacy & data handling
This is our own statement of how the platform handles your data: what we use, what never leaves your device, and the only outside service the app is permitted to contact. It describes the behaviour the app actually enforces.
What we hold about you
We only keep what the platform needs to track a creation and pay the creator who made it.
- Account: email address and the sign-in session issued to your device.
- Creator profile: display name, handle, discipline, country badge, biography and the public/private choices you set yourself.
- Connected accounts: the public profile links and handles you add so your work can be matched.
- Tracked earnings: detections of your work being used, the amounts held for you, claims, splits and payout events.
- Verification: the identity checks you complete, stored as a tamper-evident, append-only history.
- Device state for offline use: your update channel, install state and queued offline actions.
What stays on your device
The console is offline-first. Your dashboard snapshot — balances, ledger, tracked earnings, claims, connected accounts, alerts and leaderboards — is written to this device's own storage (IndexedDB) so the app opens and works with no connection at all, even after a full restart.
Actions you take offline (adding accounts, marking alerts read) are queued locally and replayed in order the moment you reconnect. Nothing leaves the device while you are offline.
The on-device snapshot is namespaced to the signed-in account and erased on sign-out. Clearing the app's data or uninstalling removes it entirely.
Which outside services the app contacts
A strict Content Security Policy is sent with every page, and it enumerates the only origins your browser is allowed to reach. Anything else — analytics, ad pixels, tag managers, third-party SDKs, embedded frames — is blocked by the browser, not merely avoided by convention.
- Earnin Tracker itself (this domain) — the app, its API routes, and the proxy that serves every creator photo, so your browser never contacts the source platform directly.
- Google Fonts (fonts.googleapis.com, fonts.gstatic.com) — the three brand typefaces only. Google receives the standard request metadata a font download carries (IP address, user agent, referring page). No account data, no earnings data, no identifiers are sent.
- Our own Lovable Cloud backend — the database, authentication and file storage that hold your records.
No third-party access to your data
There are no advertising, analytics or data-broker integrations, and no data sharing or selling. Everything outside sign-in is public information (the landing pages, the creator directory, topic and research pages); everything inside the console requires your session and is scoped to your account by row-level database rules.
Signed-in members can only ever change their own records. Shared discovery and index rows are read-only for members apart from the two claim fields that record that an entry is yours; that rule is enforced by column-level privileges and database triggers, not just by app code.
Staff review actions (claims, disputes, verification status) are restricted to Earnin staff roles and every change is written to an append-only audit trail.
Bluetooth and nearby device sync
Where your device supports it, updates and signed offline payloads can be passed between your own devices over Bluetooth so the app keeps working with no internet. This only happens when you start it, only between devices you control, and every package is signature-verified before it is accepted.
Your controls
You decide what appears on your public creator page — amounts, streams, country, networks, rank, payout status and rights notice are all individually switchable, and every change is recorded in your own privacy audit log.
You can export every record we hold for you from Settings, and you can request deletion of your account and its data from the same place.