What Recall can see, what it stores, and what never leaves your Mac.
A plain-language register of Recall's security controls, the third parties we use, and where we stand on formal compliance. No badge on this page claims more than we can prove.
Vendors that receive your work content: none, unless you share diagnostics.
Because Recall's AI runs on your Mac, there is no cloud AI vendor in this table. No screenshots, transcriptions, or work descriptions flow to any third party, with one opt-in exception. The vendors below handle account plumbing: payments, email, hosting, crash reports, website analytics, advertising measurement. The single conditional row is diagnostics storage, which only ever holds bug reports you explicitly chose to send us: analysis traces, screenshots redacted on your device before upload, and any text you add.
| Vendor | Purpose | Data received | Work content? |
|---|---|---|---|
| Paddle | Payments, billing, and licence management (merchant of record) | Name, email address, payment details, purchase history | No |
| Cloudflare | Website hosting, account records, licence infrastructure, and the analytics records below | Email address, licence and referral records, the app's pseudonymous usage events and install records tied to a random install ID, feedback you send from the app and our replies, website-visit records, standard web logs | No |
| Resend | Transactional email (licence keys, invites, product notices) and our own alerts for new feedback messages | Email address, email contents we send you, the text of feedback you send from the app | No |
| Sentry | Crash reporting | Crash stack traces, macOS version, hardware model, a random install ID | No |
| Scaleway | EU object storage for opt-in diagnostics bundles | Bug-report bundles (analysis traces, screenshots with on-device redaction applied, and any text you add), only if you enable diagnostics sharing | Only with your opt-in, redacted |
| AppSumo | Licence-code sales for AppSumo customers | Their own customer and purchase records (AppSumo purchases only) | No |
| Apple | App notarization and macOS distribution requirements | The app binary for notarization scanning, no user data | No |
| Website analytics (Google Analytics) and app milestones sent through Google's Measurement Protocol | Page views and technical data (IP address, browser, device), campaign data, and a few pseudonymous app milestones (a purchase among them, with its amount and currency) tied to a hashed install ID, or to your website visit's client ID when the install is linked to one (never your email) | No | |
| RB2B | Company identification of website visitors (outside the EU, EEA, UK and Switzerland only) | Website visit data (pages viewed, IP address); RB2B identifies companies and, for some US visitors, individuals | No |
| Advertising measurement, while advertising is allowed (Cookie settings, Do not share my data) | Page visits from Reddit's pixel (with IP address and browser), and when a visit from a Reddit ad led to a download, a sign-up, a trial or a first purchase (its amount and currency), identified by Reddit's click ID and cookie ID, plus one-way hashed reference numbers (of your install, the download or the payment) used only so a conversion is not counted twice | No |
This list is complete as of October 2026. If we add a vendor, it appears here before it processes anything.
Where Recall gets shaped.
The subreddit is public: anyone can read and search it. The Telegram group is smaller, and the people in it see builds before they ship.
Power-user group on Telegram
A smaller group we build with directly. Tell us what broke, what you wish it did, and what you want to try first.
r/joinrecall on Reddit
The open room. Ask questions, report bugs, request features, and read how other people got their focus back. Nothing behind a login.
Open the subreddit