Privacy Policy
How Data Requiem collects, uses, and protects your information.
Caton Analytics LLC d/b/a Data Requiem
Effective date: October 28, 2026.
Caton Analytics LLC d/b/a Data Requiem ("we", "us") operates requiem.com and our public services on its subdomains, including app.requiem.com and filings.requiem.com, and the Requiem Filings mobile app for iOS and Android. This policy explains what personal information we collect, why we collect it, and what you can ask us to do about it. It covers those sites, the app and the services on them, including our as-filed SEC data products and the CUSIP lookup tool.
1. Information We Collect
We collect the categories of information below.
| Category | What it is | Why we have it | Who else receives it | How long we keep it |
|---|---|---|---|---|
| Google account email | The email address on your Google account, sent to us by Google when you sign in | To establish your signed-in session | No one | We don't keep it. It is held, encrypted, in a cookie in your own browser for up to 30 days |
| Account Identifier | An opaque Google account ID, not your email address | The identifier our servers use on every request, and the key to your fair-use limits | Stripe, as the key linking you to your payment record | Held by Stripe as part of your payment record, for as long as that record exists. Also held in a rate-limiting record that expires about a minute after your last request, and in our access logs as above. See Your Rights. |
| Access Log Data | Your IP address and the address of each request you make, including any search terms in it. In the mobile app, also the app's anonymous sign-in identifier (see the mobile app rows below) | To keep the service available, and to detect automated harvesting and abuse | Amazon Web Services; Datadog | 30 days in our own infrastructure; 15 days with Datadog |
| Error Tracking Data | An automatic report when something breaks: the error, together with your IP address and browser | To find and fix faults in the service | Datadog | 15 days, with Datadog |
| Analytics Data | Pages visited, the time and date of your visit, your browser and device, approximate location derived from your IP address, and analytics cookie identifiers | To understand how our sites and app are used and improve them | Deleted by Google after 2 months | |
| Mobile App Installation Identifiers (mobile app only) | Two random identifiers created when you install the app: a Firebase installation ID, and an anonymous Firebase sign-in ID that the app presents to our servers. Neither contains your name, email address or a hardware identifier such as your phone's serial number or advertising ID | To count installations, to connect usage data and crash reports from the same installation, and, for the sign-in ID, to recognise the app on each request and apply fair-use limits | Google (Firebase). The sign-in ID also appears in our access logs, as above | Installation ID: until you uninstall the app or clear its data. Sign-in ID: 30 days after last use, once Firebase's automatic clean-up is turned on; in our access logs for 30 days (15 days with Datadog) |
| Mobile App Usage Data (mobile app only) | Which screens and features you use, the app version, your device model and operating system, your language, and your approximate location (city) derived from your IP address. Search terms are never included | To understand how the app is used and improve it | Google (Google Analytics for Firebase) | Deleted by Google after 2 months |
| Mobile App Crash Reports (mobile app only) | If the app crashes, a report of the app's state at that moment: the screen you were on, the error, and your device model and operating system version | To find and fix crashes | Google (Firebase Crashlytics) | 2 months, with Google |
| Payment Data (if you choose traditional card payment via Stripe) | Your card details, and the record of your payment | To take payment for what you buy | Stripe. Card details are entered on Stripe's own payment page and never reach our servers | Held by Stripe to meet its own financial-recordkeeping obligations |
| Digital Wallet Address (when you sign in with a digital wallet) | The public address of the crypto wallet you connect — a long string of letters and numbers that identifies your wallet on the blockchain. It is not a bank account number and does not contain your name. | How we recognise you when you sign in, and the key to your fair-use limits | Your wallet provider, the service that connects it to us, and the blockchain node that reads the network on your behalf. The node also sees your IP address. | In a cookie in your browser until you disconnect your wallet or clear your cookies; in a rate-limiting record that expires about a minute after your last request; and in our access logs as above |
| On-Chain Payment Data (when you pay on-chain) | The amount, the plan you chose, and your wallet address, written to the public Base network | To take payment on-chain | Anyone — the blockchain is public | Permanent. Neither we nor you can alter or remove it |
Card payments and wallet sign-in are not currently available. Those rows describe what we will collect when they are.
1.1 What this means in practice
We do not store your email address on our servers — it lives only in the session cookie in your own browser, and signing out or clearing your cookies removes it. We have no mailing list and send no marketing email.
Card details are entered on Stripe's own payment page and never reach our servers. When you pay on-chain, we write nothing to the blockchain beyond the payment itself: no identifiers, no reference numbers and no memo fields.
We use our access logs to keep the service running and to detect automated abuse. We do not use them to build a profile of you.
The mobile app has no account. It does not ask for your name, email address, phone number, contacts, photos or precise location, shows no advertising and uses no advertising identifiers. Your saved views and recently viewed filings are stored on your device only, and are removed when you delete them, or uninstall the app.
2. How We Use Your Information
We use your sign-in to give you access to what you have paid for, Stripe to take payment, our access logs to keep the service available and free of automated abuse, error and crash reports to fix faults, and analytics to understand how our sites and app are used. We do not sell your personal information, we do not share it for advertising, and we do not use it to train machine learning models.
3. Who Else Receives Your Information
A small number of service providers receive only what they need to do their job, and none of them may use it for their own purposes.
Google handles your sign-in and receives your analytics data. In the mobile app, Google also provides the anonymous sign-in (Firebase Authentication), usage analytics (Google Analytics for Firebase) and crash reporting (Firebase Crashlytics).
Stripe receives your card details directly, so that we never hold them.
Amazon Web Services hosts our systems and holds our access logs.
Datadog monitors our systems, and receives our access logs and browser error reports.
Vercel hosts requiem.com and sees traffic to that site.
If you use a wallet, your wallet provider, the connection service and the blockchain node each see your wallet address, and the node sees your IP address.
We also disclose information where the law compels us to.
4. Cookies
We run no advertising, marketing or social media trackers on our sites or in the mobile app. We use three kinds of cookie:
Strictly necessary: the cookie that keeps you signed in, and the short-lived cookies used during the sign-in process itself. The site cannot work without them.
Error monitoring: a cookie that groups the error reports from a single visit, so a fault can be traced.
Analytics: Google Analytics cookies, which record how the sites are used.
The mobile app sets no cookies. It uses the installation identifiers described in section 1 instead.
5. Your Rights
You can ask us what personal information we hold about you, ask us to correct it, ask us to delete it, ask for a copy, or object to how we use it. We will not treat you differently for asking.
Three limits we would rather state plainly than have you discover. First, we cannot look you up by email address, because we do not store it. Second, we cannot delete payment records held by Stripe, because Stripe must retain them by law. Third, nobody can delete a blockchain transaction. Fourth, the mobile app has no account, so we cannot look up or delete its data on request. Uninstalling the app or clearing its data removes everything on your device, and the identifiers Google holds are deleted on the schedule in section 1.
6. Security
We take reasonable measures to protect your information, though no method of transmission over the internet or electronic storage is completely secure, and we cannot guarantee absolute security. Specifically: your card details never reach our servers; your email address is never written to any file of ours; the identifier our systems see is an opaque ID rather than your email address; and your session cookie cannot be read by scripts running in your browser. The mobile app connects to our servers only over encrypted (HTTPS) connections.
7. Changes to This Privacy Policy
We may update this Privacy Policy. Any changes take effect when we post the revised policy on our website, and we will update the effective date above.
8. Contact Us
If you have any questions or concerns about this Privacy Policy or the information we collect, contact us at privacy@datarequiem.com.
This policy applies to requiem.com and our public services on its subdomains, to the Requiem Filings mobile app, and to the services on them. Our Terms of Service are at requiem.com/terms.