๐Ÿ“„ Legal

Privacy Policy

We built PageRecall so that even we can't read your data. This policy explains exactly how that works โ€” in plain English.

๐Ÿ• Last updated: March 2, 2026
๐Ÿ”’The short version: Your browsing data is AES-256 encrypted in your browser before it reaches us. We store only ciphertext. Your secret key never leaves your device. Even if compelled, we cannot read your data.
๐Ÿ”

Overview

PageRecall is built on a simple promise: your browsing history belongs to you, and only you. Every architectural decision โ€” from client-side encryption to zero plaintext storage โ€” exists to make that promise technically enforceable, not just a policy claim. This Privacy Policy explains what data we collect, why we collect it, how it is protected, and your rights over it. It applies to the PageRecall Chrome extension and the web application at pagerecall-webapp.vercel.app.

๐Ÿ“ฆ

Data We Collect

Personally Identifiable InformationCollected
  • Google account email address โ€” used as your account identifier in our database.
  • Google display name and profile photo โ€” used only within the app UI.
Authentication InformationCollected
  • Google OAuth token โ€” used to authenticate you with our backend. Never stored permanently on our servers.
  • Your AES-256 secret encryption key โ€” generated once in your browser, shown to you once, and never transmitted to or stored by PageRecall. We have zero access to this key.
Web HistoryCollected & Encrypted
  • Page titles and URLs of pages you visit.
  • Domain names.
  • Time of visit and time spent on each page.
  • All web history data is AES-256 encrypted in your browser before it leaves your device. We store only ciphertext โ€” unreadable without your secret key.
Website Content (SEO Metadata)Collected & Encrypted
  • Meta description tags.
  • Open Graph tags (og:title, og:image, og:description).
  • Canonical URLs.
  • Page headings (H1, H2).
  • All website content data is encrypted client-side alongside your web history. We never process or read this data.
Data We Do NOT CollectNever
  • Passwords or form inputs of any kind.
  • Health or medical information.
  • Financial or payment details (handled entirely by Stripe).
  • Personal communications โ€” emails, messages, or chats.
  • GPS location or IP-based location.
  • Mouse movements, clicks, scroll position, or keystrokes.
  • Microphone, camera, or any device sensor data.
๐Ÿ”’

How Encryption Works

PageRecall uses AES-256-GCM encryption โ€” the same standard used by banks and governments โ€” applied entirely within your browser before any data is uploaded. Here is the exact flow: 1. When you first sign in, your browser generates a unique 256-bit secret key. 2. This key is shown to you once. You must save it โ€” we do not store it. 3. Every session is encrypted in your browser using this key before upload. 4. Our servers receive only encrypted blobs (ciphertext + IV). The plaintext is mathematically inaccessible to us. 5. When you open your dashboard, your browser fetches the ciphertext and decrypts it locally using your key. This means: even if our database were breached, even if we were subpoenaed, even if a PageRecall employee wanted to โ€” nobody can read your browsing data without your secret key.

๐Ÿ—„๏ธ

Data Storage & Retention

Encrypted session data is stored in MongoDB Atlas (cloud-hosted), indexed by your Google account ID. Free plan users: encrypted data is retained for 14 days. Pro plan users: encrypted data is retained indefinitely until you delete it. Your Google account information (email, display name) is stored in our database to associate your encrypted data with your account. This is the only plaintext data we store about you. You can permanently delete all your data at any time from Settings โ†’ Delete My Data. Deletion is immediate and irreversible.

๐Ÿค

Third Parties

Google OAuthAuthentication only
  • Used solely to authenticate you. We receive your email, name, and profile photo from Google.
  • We do not share any of your browsing data with Google.
MongoDB AtlasEncrypted storage
  • Hosts our database. Receives only encrypted ciphertext โ€” no plaintext browsing data.
  • MongoDB cannot read your data. Only you can, with your secret key.
StripePayments only
  • Handles all payment processing for Pro subscriptions.
  • We never receive or store your credit card number. Stripe is PCI-DSS compliant.
  • Stripe receives no browsing data of any kind.
VercelHosting
  • Hosts our web application. Standard server access logs (IP address, request path, timestamp) may be retained by Vercel per their own privacy policy.
  • Vercel does not receive or process your browsing data.
๐Ÿšซ

We Do Not Sell Your Data

PageRecall does not sell, rent, trade, or transfer your personal data or browsing history to any third party for any purpose โ€” advertising, analytics, data brokering, or otherwise. Our business model is simple and transparent: paid Pro subscriptions. Your data is not our product. You are not our product. We do not use your browsing data to show you ads. We do not allow advertisers to target you based on your PageRecall data. We do not share data with data brokers or marketing platforms.

โš–๏ธ

Your Rights

You have the following rights over your data at all times: Access โ€” You can view all your stored data through your PageRecall dashboard. Export โ€” Pro users can export their full history as CSV or JSON at any time from Settings. Deletion โ€” You can delete all your data instantly from Settings โ†’ Delete My Data. This permanently removes your encrypted data from our database. Because we don't hold your decryption key, deleted data is unrecoverable. Account closure โ€” You can uninstall the extension and close your account at any time. Uninstalling stops all data collection immediately. If you are in the EU or UK, you have additional rights under GDPR/UK GDPR including the right to rectification, restriction of processing, and to lodge a complaint with your supervisory authority.

๐Ÿงฉ

Chrome Extension Permissions

PageRecall requests the following Chrome permissions, each strictly necessary for its single purpose: storage โ€” Saves encrypted session data locally before cloud sync. tabs โ€” Reads page titles, URLs, and navigation timing. Required to record your browsing sessions. alarms โ€” Schedules periodic background sync of encrypted data to the cloud. scripting โ€” Injects a content script to read SEO metadata (meta tags, headings, canonical URLs) from pages you visit. host_permissions (<all_urls>) โ€” Required for the scripting permission to operate across all websites. No data is collected from pages without user interaction. PageRecall does not use remote code. All extension JavaScript is bundled within the installed package.

๐Ÿ‘ถ

Children's Privacy

PageRecall is not intended for users under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal data, please contact us and we will delete it promptly.

๐Ÿ“

Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page and notify you via the PageRecall extension popup if the changes are material. Continued use of PageRecall after changes are posted constitutes your acceptance of the updated policy.

โœ‰๏ธ

Contact

If you have any questions, concerns, or requests regarding this Privacy Policy or your data, please contact us at: privacy@pagerecall.com We aim to respond to all privacy-related requests within 48 hours.

โœ‰๏ธ

Questions about your privacy?

We take privacy questions seriously and respond within 48 hours.

privacy@pagerecall.com