Chrome Extension Privacy

Effective: April 22, 2026

This page explains what the REPS Chrome extension collects, what it doesn't, and how the data it does handle is used. It covers the extension specifically — for how REPS as a whole handles your information, see our main Privacy Policy.

Short version: the extension only acts when you explicitly invoke it (toolbar click, right-click menu, or keyboard shortcut). It does not read pages you haven't saved, does not track your browsing, does not run background scripts, and does not include any analytics or third-party trackers.

1. What the Extension Collects

(a) The pairing token

When you pair the extension with your REPS account, the REPS backend issues a device token — an opaque identifier tied to your account. The token is stored locally in chrome.storage.local on your device so the extension stays signed in across browser restarts. It is never shared beyond the REPS ingest pipeline and never used to identify you to third parties.

(b) URLs and page titles you explicitly save

When you click the extension icon, press the keyboard shortcut, or otherwise trigger a "save" action on a page, the extension reads the URL and title of that tab and sends them to your REPS account. No other pages, tabs, or browsing activity are collected.

(c) Text selections you explicitly save

When you highlight text on a page and choose "Save selection to REPS" from the right-click menu, the highlighted excerpt is sent to your REPS account along with the source URL (so you can see where it came from later). Only the selected text is captured — not the rest of the page.

2. What the Extension Does NOT Collect

Your browsing history. The extension has no visibility into pages you visit unless you explicitly save them.
Page content you haven't saved. The extension never reads or scrapes page bodies in the background. When you save a URL, the extension sends only the URL and title — REPS's server-side pipeline fetches the page content via trusted extraction providers.
Keystrokes, mouse movements, or form data. The extension does not observe user activity at all.
Analytics or telemetry. The extension does not include Google Analytics, PostHog, Mixpanel, error-reporting SDKs, or any other third-party measurement tools.
Personal information. Name, email, age, location, payment information — none of this is requested, read, or collected by the extension. Your name and email live in your paired REPS account and are governed by our main Privacy Policy.

3. How Saved Content Is Used

The URLs, page titles, and text selections you save are sent over HTTPS to the REPS ingest pipeline (getreps.app.n8n.cloud) and stored in your REPS account. From there, they go through the same spaced-repetition processing pipeline as anything you add through the mobile app: extraction (for URLs and videos), concept generation, and rep creation.

Saved content is used solely to power your learning experience inside your own REPS account. It is not sold, not shared with advertisers, and not used to train AI models outside the normal processing pipeline described in the main Privacy Policy.

4. Where Data Is Stored

Saved content and the device token's hashed form are stored in REPS's backend database (Supabase). REPS and its service providers operate in the United States and other countries; by using the extension you consent to the cross-border transfer of the content you save, under the same terms as our main Privacy Policy.

Retention follows the same rules as your REPS account. When you remove content in the REPS app, it is archived per the main policy's section on archived content. If you request account deletion (see "Your Control" below), the content you've saved through the extension is deleted or anonymised alongside the rest of your account data.

5. Third Parties

Content you save through the extension flows through the same service providers described in the main Privacy Policy. Relevant to the extension:

Supabase — hosts your REPS account database (used by the extension to redeem the one-time pairing code during setup).
n8n — orchestrates REPS's content processing pipeline (the ingest endpoint the extension POSTs to).
Content extraction providers (such as Firecrawl and Jina) — fetch the text of URLs you save so they can be processed into learning content. Only the URL is sent to these providers.
Anthropic (Claude) — generates concepts and reps from the saved content. Anthropic does not use API inputs to train their models.

The extension does not communicate with any advertising networks, analytics platforms, or other third parties beyond the REPS infrastructure listed above.

6. Your Control

Disconnect this browser from local access by uninstalling the extension from chrome://extensions or by clearing the extension's local storage. This removes the device token from this browser.
Server-side token revocation (centrally invalidating a paired browser from your REPS account) is not yet available in this version of the extension. It will ship in a future release. For now, if you lose access to a browser and need its pairing revoked before that release lands, contact privacy@getreps.io.
Archive content you've saved inside the REPS mobile app — the same archive controls apply to content from any ingest source, including the Chrome extension. Archived content is excluded from your training sessions and is no longer visible to you. For permanent deletion of specific content, contact privacy@getreps.io.
Request account deletion by emailing privacy@getreps.io, as described in our main Privacy Policy. We will delete or anonymise your personal information within 30 days of your request, including everything you've saved through the extension.

7. Remote Code

The extension executes no remote code. All JavaScript is bundled into the extension at build time and ships inside the Chrome Web Store package. There are no runtime imports, no eval calls, and no dynamic script loading from any origin. Every response the extension receives over the network is treated as data, not code.

8. Changes to This Policy

We may update this Chrome Extension Privacy page as the extension adds capabilities. Material changes will be reflected in the effective date at the top of the page and announced through the main REPS Privacy Policy. Continued use of the extension after changes are posted constitutes your acceptance of the revised policy.

9. Contact

Questions about how the Chrome extension handles your data?

Email: privacy@getreps.io

Main privacy policy: getreps.io/privacy