Legal
Privacy Policy
Last updated October 23, 2026
1. Who is responsible for your data
The data controller for all personal data processed by Recl is the Recl operator, reachable at hello@recl.app. We respond to all privacy requests within 30 days.
2. Data we collect
| Category | Examples | Source | Why |
|---|---|---|---|
| Account data | Email address, display name, avatar URL, Google/Apple account ID | Google or Apple sign-in (OAuth) | Create and authenticate your account |
| Saved content | YouTube URLs, page URLs, notes, quotes, transcripts, AI summaries, quiz answers, recall reviews, folders, topics | You (saving content) | Provide the core product: your personal knowledge library |
| Push notification tokens | Mobile push token | Your devices (when you enable notifications) | Deliver recall nudges to your device |
| Device & session data | Session tokens, extension tokens, mobile push tokens, IP-derived coarse region, user-agent | Your devices | Authentication, security, abuse prevention |
| Usage & diagnostics | Feature usage counters, error logs, crash reports (stack trace, device model, OS and app version), performance metrics, feed interaction signals (likes, reads, dwell time) | Automatic | Reliability, quota enforcement, and ranking your own feed |
| Billing data | Subscription state, plan, billing interval, store transaction ID, payment provider customer ID | Payment providers (Dodo Payments on the web, Google Play, the Apple App Store) and RevenueCat | Operate paid plans. Card numbers never touch Recl servers. |
| Support chat | Messages, photos and voice messages you send in the in-app chat, plus basic device and app details | You (only when you open Chat with us) | Answer your support questions |
| Instagram DM data | Page-scoped user ID (PSID), message content (reel/post URLs, attachments), email address provided for account linking | Your Instagram DMs to @reco.save | Save-to-library: link your DM identity to your Recl account and save shared reels/posts |
We do not collect: precise location, contacts, advertising identifiers, or data from third-party data brokers. The camera, photo library and microphone are used only when you choose to: to take or pick a photo to save, or to send a photo or voice message in support chat.
3. Why we process your data (legal bases)
| Purpose | Legal basis (GDPR) |
|---|---|
| Providing the service you signed up for — saving, summarizing, searching, graphing, and recalling your content | Contract (Art. 6(1)(b)) |
| Generating AI summaries and quizzes from content you save | Contract (Art. 6(1)(b)) |
| Sending recall nudges as push notifications you explicitly enabled | Contract / Consent (Art. 6(1)(a)–(b)) — disconnect any time |
| Security, fraud and abuse prevention, rate limiting | Legitimate interest (Art. 6(1)(f)) |
| Billing, invoicing, accounting records | Legal obligation (Art. 6(1)(c)) |
| Service diagnostics and reliability monitoring | Legitimate interest (Art. 6(1)(f)) |
4. How AI processing works
- When you save content, the transcript or text is sent to our AI provider (OpenRouter) to generate summaries, topics, quiz questions, and category labels.
- AI requests are scoped to the single piece of content being processed. Your library as a whole is never used to train AI models — neither by us nor, per their terms, by our AI provider.
- We create vector embeddings of your saved videos and nuggets, stored in our own database and scoped to your account. They power search by meaning in the Chrome extension and the similarity links in your knowledge graph.
- AI outputs can be wrong. They are labeled as generated content and are never represented as professional advice.
5. Where your data lives
- Primary database and application servers: an Amazon Web Services (AWS) EC2 server in the Mumbai region (ap-south-1).
- Encrypted backups and uploaded images: Cloudflare R2 object storage.
- All traffic is encrypted in transit (TLS 1.2+). Backups of secrets are GPG-encrypted at rest.
- Access to production systems is limited to the operator, via key-based SSH.
7. How long we keep data
Retention periods per data category are documented on the Data retention page. In short: your content stays as long as your account exists; deleting your account deletes your content; operational logs rotate within weeks; billing records are kept as long as tax law requires.
8. Your rights
Depending on where you live (GDPR in the EU/EEA/UK, CCPA/CPRA in California, and similar laws elsewhere), you have the right to:
- Access — get a copy of the personal data we hold about you.
- Rectification — correct inaccurate data (most profile data is editable in Settings).
- Erasure — delete your account and all associated content (self-serve in the app under Profile → Settings → Delete account, on the web under Settings → Danger zone, or by email).
- Portability — receive your saved content in a machine-readable format.
- Restriction & objection — limit or object to specific processing.
- Withdraw consent — disable push notifications at any time.
- Complain — lodge a complaint with your local data-protection authority.
To exercise any right that isn't self-serve, email hello@recl.app. We verify requests against your signed-in account email and respond within 30 days. See GDPR & EU users for the full process.
9. Children
Recl is not directed at children under 16 and we do not knowingly collect data from them. If you believe a child has created an account, contact us and we will delete it.
11. Changes to this policy
We will update this page when our practices change and revise the “Last updated” date above. For material changes affecting your rights we will notify you in-app or by email before they take effect.
12. Instagram DMs via @reco.save
@reco.save is a mascot/sub-brand Instagram account operated by Recl (not the official recl.app Instagram). When you DM it, we process your Page-scoped user ID (PSID), the message content (reel/post links and attachments), and the email address you provide to link your Recl account — solely to save shared content to your library and send save receipts. Retention: DM link rows are kept 90 days after deletion/unlink; webhook event records are kept 90 days. Deletion: reply DELETE in-DM at any time, use the Meta data-deletion callback, or email hello@recl.app. Subprocessors for this flow are Cloudflare (edge delivery), Resend (one-time-code email), Supadata (content fetch), and OpenRouter (AI summaries) — see the Subprocessors page for details.
13. Contact
Privacy questions and requests: hello@recl.app.