In place since April 2026 · Last updated: 22 October 2026
Royalti is operated by AJL Technologies Ltd, a company registered in England and Wales ("Royalti", "we", "our", "us"). This policy explains what data we collect, how we use it, how long we keep it, and what rights you have. If anything is unclear, email support@royaltiapp.com.
When you create an account: your name, email address, and role (artist or manager). Authentication is handled by Clerk; we never see or store your password. If you sign in with Apple or Google, we receive only your name and email.
The core of the product. This includes:
Statement files you add on the Statements page are read in your browser where possible; PDFs and other files the browser can't read, and statements forwarded by email, are read on our servers. Either way, what Royalti stores is a per-song summary: song titles, industry codes (ISWC, ISRC, tunecodes), writer and publisher names, ownership shares, amounts, the statement period, and your society member / CAE number. On Royalti Business, an encrypted copy of each statement file is also kept so it can be downloaded later or shared as proof (Keep original files: on by default, and turning it off deletes the copies). On other plans the file itself is not kept.
Song and release details you add, or that we fill in for you: titles, industry codes, credits and splits, versions, release and label details, links and notes. Contacts you add to a song (names, roles, companies, email addresses and phone numbers). Documents you upload (contracts, split sheets, agreements) and media files (masters, stems, artwork, press photos and video).
If the app hits an error, a technical report (the error, the screen it happened on, browser/device type and app version) is sent to Sentry so we can fix it. Collection of personal data is switched off: reports don't include your email, royalty figures or login tokens.
Whether you have an active subscription or trial. iPhone subscriptions come from Apple's StoreKit, refreshed on each app open; Royalti Business is billed through Stripe. We never see your full card details: Apple or Stripe handles payment.
We collect anonymous usage events (e.g. "a user opened the app", "a user confirmed a statement"). These events contain no user identifier; they are stored as aggregate counters only. They cannot be linked back to your account.
We apply automatic expiry timers to anything sensitive that isn't part of your active product data. After the timer runs out, the data is permanently deleted by our database; we do not need to take any action for this to happen.
| Data | Retention |
|---|---|
| Source PDFs / images / raw email bodies | 30 days, then auto-deleted (unless kept as originals, below) |
| Statement originals, portal records and payer PDFs (Royalti Business, Keep original files on) | Until you turn the setting off, delete the statement, or close your account |
| Statement fingerprints (one-way hashes only, for timestamps) | Until you close your account |
| Read but unconfirmed statements | 90 days, then auto-deleted |
| Confirmed deals (your dashboard) and contracts | Until you delete them or close your account |
| Catalogue song summaries | Until you remove the import or close your account |
| Vault details, documents and media | Until you delete them or close your account |
| Saved statement layouts (column headings and file name only, no rows or amounts) | 365 days |
| Song lookup and artwork caches | 3 to 30 days |
| Crash reports | Up to 90 days |
| Bank link tokens | Until you disconnect the bank |
| Subscription state | 90 days, refreshed on each app open |
| Anonymous aggregate counters | Indefinite (no identity attached) |
We compute industry-level statistics, for example the median payment from a major royalty source, or the distribution of deal types across users. This dataset is built from fully anonymised counters stored in a separate database namespace that has never seen and never will see a user identifier. It cannot be reverse-engineered to reveal individual users or accounts.
These insights are only ever reported at a level that can't identify an artist, a label, a deal or a company, and we may use them in industry reports or partnerships. If you'd prefer your account, or for Royalti Business your company's whole roster, not to contribute at all, email us: we'll exclude it and confirm in writing.
We use these vendors to operate the product. Each receives only the minimum data needed for its role.
The Royalti Statement Fetch extension for desktop Chrome reads your statements from the royalty portals you sign into yourself (listed below), and statements a payer shares with you as a Google Drive folder (for example Roc Nation Publishing). For a Drive folder it reads only the folder you open and the folders inside it, using your own Google sign-in, and downloads only the statement files and summaries it needs. It never reads the rest of your Drive or changes anything in it. It uses your own logged-in browser session (including, where a portal needs them, the request headers the portal's own page uses) only inside that portal's tab, to list your statements, read the balances the portal shows for them (advances, recoupment and payments, so Royalti can tell money earned from money paid), and download the statement files the portal already offers you. It reads those files in your browser and sends summaries to your own Royalti account. Your portal session never leaves your browser. On Royalti Business, each statement file is also kept as an encrypted copy in the artist's Royalti account (Keep original files), encrypted in the browser, so it can be downloaded later or shared as proof. Only the artist and their team can open it. It can be turned off at any time on the Statements page, which deletes the copies. On other plans, statement files stay in your browser. The extension doesn't change anything in your portal account, with these exceptions. The Orchard only builds a new month's statement file when you press its own Generate button. As part of pulling the statements you connected, the extension presses The Orchard's Generate button for you, only for new months whose file hasn't been built yet, and at most 3 per pull. Platoon only sends song-level statement files by email, when you ask for them. With your OK, the extension presses Platoon's own Download statements button for you, only for months that don't have a file yet and at most 12 months per request: while your history is being filled in, as many requests as it takes in one sync; after that, no more than once every 30 days. Platoon then emails you a link to the files. Nothing else on your account changes. To stop it, disconnect the extension on Royalti's Sources page, or remove the extension. Some other portals only produce older statements when you ask for them, and some only hand out newer statements through their own Download button (the extension presses it in a hidden tab and reads the file instead of saving it to your computer; it never touches your other downloads). For those, the extension asks your permission once, and only after you agree does it press that portal's own "generate report" or "Download" option for you. You can withdraw that permission at any time in the extension's settings. It never accepts terms, changes settings, or touches payments or payout details on your behalf.
The extension can only open these websites, and uses each one only to download your own statements from a portal you are already signed in to, with your own session:
It never stores your password for any of these portals, and what it reads from your statements is sent only to your own Royalti account.
The extension stores only these items, and only in your browser's local storage: your Royalti link token, an activity log of what it has done, sync progress (including reports it asked a portal to build), the portal member each of your Royalti accounts is linked to, any portal permissions you have granted, and your extension settings. On Royalti's own website it runs a small script so the Statements page can show its status and start a sync; that script never receives your link token.
The extension never reads or stores your portal passwords, never tracks your browsing outside the portals it syncs and Royalti's own site, and sends no data to anyone other than your own Royalti account.
Proof records (Royalti Business). When "Keep original files" is on, Royalti also keeps, encrypted like your statement files: for portals that show figures without a downloadable file, an exact copy of the figures the portal returned (a "portal record"); and the payer's own PDFs that come with a statement (for example remittance, self-billing and VAT documents). To show when each statement was received, Royalti adds a fingerprint of it (a one-way hash, from which nothing about the statement can be read) to a log and, once a day, sends a single combined fingerprint to an independent timestamping service (DigiCert, or FreeTSA if DigiCert is unavailable). No statement contents, names, amounts or account details are ever sent.
We do not sell, rent, or trade your personal information. We do not share your individual royalty figures with labels, publishers, PROs, distributors, or any third party.
Data flows only to:
All connections to Royalti are encrypted in transit (HTTPS / TLS). API endpoints require authenticated sessions, are rate-limited per user, and validate every input. Bank credentials are never transmitted to or stored on our servers: Plaid and Yapily handle authentication directly via OAuth flows. Internal admin access is restricted by an explicit email allow-list. UK bank connections are made through Yapily Connect Ltd, authorised by the FCA (FRN 827001), with Royalti acting as its registered agent (FRN 1060782).
Contracts and Vault documents are encrypted (AES-256) before they are stored. Vault media files are encrypted in your browser before upload. The keys for all of these are held by Royalti, themselves encrypted under a master key, so that you and the people you share with (such as your manager) can open them on any device. This means files are not end-to-end encrypted: we decrypt them only to show them to you or people you've shared with, when you ask Rex to read one, or if compelled by valid legal process.
Regardless of where you live, you can:
Users in the EU, UK, or California have additional rights under GDPR / UK-GDPR / CCPA, including the right to data portability and to lodge a complaint with a supervisory authority. We honour all such requests.
Royalti is not directed at and not intended for use by anyone under 18. We do not knowingly collect data from minors.
We will update this page if our data practices change. The "Last updated" date at the top will reflect the latest revision. Material changes will be communicated in-app.
Questions, requests, complaints: support@royaltiapp.com. We aim to respond within 7 days.