Privacy
Effective November 5, 2026. Reclipd is in private beta. This page says what the product does today, in plain words. If something changes, we update this page and the date above.
The short version
Your context belongs to you. Reclipd stores the clips you save so you can use them in any AI chat. The extension only acts when you press the hotkey or use its right-click menu. It does not read your chats in the background. Nothing is sent to an AI assistant until you press send yourself. We do not sell your data and we do not use it to train AI models. We cannot speak for the AI services you use: what you send to them follows their own terms.
What we store
- Your account: your email address and your password. The password is stored only as a salted hash (scrypt). We can not read it. If you sign in with Google or GitHub, Reclipd gets only your account number there and your verified email address. It never sees your Google or GitHub password, and it does not keep their sign-in token.
- Your devices: each browser you sign in on gets its own sign-in token. We store only a hash of it, with a label such as "Chrome on Mac" and when it was last used.
- Your Vault: the clips you create, import or capture: title, text, binders, type, source, dates, and whether a clip is locked.
- Images and files: images and documents you attach to clips or add to your Media library, with the name, description and summary you give them, stored with your Vault. Only you can open or download them. Text pulled out of a PDF, Word or Excel file is read in your browser, not on our server. Your plan sets how much you can store.
- Your use log: each time you insert clips from the picker or through a connected assistant, we keep one line: the date, which clips and binders, their size, and the name of the assistant or app they went to (for example "ChatGPT" or "Claude"). A rewrite adds one line too: the date, the site or app, the style you used and the size. Never the text. Reclipd also remembers which style you last used on each site, so it can start there next time. This powers the Insights page in your Vault. It never includes what you typed or what the assistant answered.
- Invite requests: if you request an invite, your email, the assistants you picked and the note you wrote.
Locked clips are encrypted on your device. When you set a passphrase (Vault, Settings, Security), the text of every locked clip is encrypted in your browser before it is saved. Reclipd stores only the encrypted text and a copy of the key that your passphrase or your recovery code can open, so Reclipd cannot read locked clips. Titles stay readable. AI features and connectors leave locked clips out. If you lose both the passphrase and the recovery code, nobody can open them. Older saved versions of a clip are deleted when it is encrypted.
What the extension reads, and when
- When you press the hotkey or click the Reclipd icon: it opens the picker on that one tab. To place your clips, it looks at the chat box on that page. That text stays in your browser. It is not saved or sent anywhere.
- When you capture: if you highlight text and press the hotkey, or choose "Clip to Reclipd", it reads the highlighted text, the page title and the page address, so it can fill in the new clip. Nothing is saved until you press Save.
- Never in the background: it has no access to pages you have not acted on. It asks Chrome for the "active tab" permission only, not access to all sites.
- On reclipd.com only: on the Reclipd setup and Vault pages, a small bridge lets the page check that the extension is installed and connect it to your account with a one-time code, so you do not sign in twice. It runs on no other site.
- Where it sends data: only to reclipd.com, to load and save your clips. It does not send your data to any other company.
The extension stores your sign-in token and your picker settings (such as dark or light theme) in your browser's extension storage.
GitHub live copy (only if you turn it on)
If you connect GitHub in Export and connect, Reclipd copies your clips into a folder named reclipd/ in the one repo you choose. Images and files from Media are copied too unless you turn that off. Locked clips are not copied unless you turn that on.
- Access goes through the Reclipd app that you install on GitHub. You choose which repos it can reach, on GitHub's own page. Reclipd never sees your GitHub password.
- When you connect, Reclipd checks with GitHub that the install belongs to you, then discards that sign-in. For each copy it asks GitHub for a short-lived token for that one repo, keeps it only in memory (at most an hour), and never writes it down.
- Reclipd only writes inside
reclipd/. It lists the repo's file names to find that folder, but does not open or change any other file. The copy is one way: edits made on GitHub are replaced on the next copy. - Use a private repo. In a public repo, anyone could read your clips.
- Disconnect any time in Export and connect. Files already in your repo stay there. To remove Reclipd's access completely, uninstall the app on GitHub.
AI providers
Reclipd only sends something to an AI provider when you ask it to, in three places:
- Summarize with AI sends that one image or that document's text (with the name and description you gave it), and nothing else.
- Screenshot, Summarize (⌥S or Alt+S) sends only the area you selected, the page title and site name, and your note, for that one summary. If you do not save it, the image is not kept.
- Keep: each clip, file and screenshot has a Keep time (for example 1 year). If you do not use it in that time, it is archived: it leaves your binders and the apps, stays restorable in your Vault (Account, Archives) for 30 days, then is deleted for good. Using an item resets its time. If you keep a GitHub live copy, archived items stay in its
reclipd/archives/folder. - Binder archives: archiving a binder keeps it as a zip you can download, restore or delete in the Vault. It counts toward your storage. Apps never show archives.
- Optimize for this chat (⌥Enter or Alt+Enter in the picker) sends the clips and file summaries you picked, and your question, to the AI for that one call. Nothing is stored unless you click Save as clip.
- Short versions (⌥R or Alt+R when you edit a clip) send that clip's text to the AI for that one call. The short version you keep is saved with the clip.
- Screenshot, Save to Vault stores the image in your Media library with a small preview, and your text as a clip, with the date, page title, page address, image size and device. It counts toward your storage.
- Build a prompt (the Prompt Engine) sends what you typed plus the title, type and the first few lines of each of your unlocked clips, so the AI can pick the ones that fit. Locked clips are never sent to it.
- Rewrite (Alt+Shift+W, or "Try it" in the Rewrite tab) sends the text you selected, the style you picked, your unlocked clips of type style (unless that style turns them off) and any one-off instruction you typed. The text you selected is used for that one rewrite and is not stored by Reclipd. It can be an email or a work message, so only rewrite what you are allowed to share with an AI service.
Summaries and prompt builds share one monthly allowance on your plan; rewrites have their own.
- By default these are written by Anthropic's Claude, using Reclipd's account. Anthropic processes them under its commercial terms. Anthropic says it does not use inputs or outputs from its commercial products to train its models by default (Anthropic: Is my data used for model training?). That is Anthropic's policy, not something Reclipd controls. If Reclipd adds other labs' models to its own account, they will be named here before you can pick them.
- If you add your own API keys (Anthropic, OpenAI, Google Gemini or OpenRouter), you choose which of your models runs each task, and the content goes to that provider under your own agreement with them. Your keys are stored encrypted on reclipd.com and used only for your own requests. Each request still passes through Reclipd's server on its way to your provider; Reclipd does not keep the content.
- To show the list of models your key can use, Reclipd asks your provider for that list with your key and keeps the model names, refreshing them after a day.
- Insights (Generate insights on the Graph page) sends counts from your Vault and your insert history, binder names and goals, and the titles of some clips. It never sends the text of a clip, and never anything from a locked clip. The result is saved in your Vault so you can read it again.
- Locked clips are never summarized unless you open them and click Summarize yourself.
When you use a clip in a chat, you send it to that assistant yourself, under that assistant's own privacy terms. Connected assistants (for example Claude or ChatGPT through the Reclipd connector) can see the clips you pick, including their images. A connector is read only unless you allow it to save when you connect it. You can turn saving on or off any time in the Vault, under Settings, Security, Signed-in devices.
What we do not do
- We do not sell or rent your data.
- We do not use your data for advertising.
- We do not use your clips to train AI models. This covers Reclipd only. Each AI service you use, including through your own API keys, has its own training policy; check theirs.
- We do not read your chats.
Chrome Web Store: Limited Use
The use of information received from Google APIs and Chrome will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data the extension handles is used only to provide Reclipd's single purpose: saving your context and inserting it into AI chats when you ask. It is not transferred to third parties, used for advertising, or used to determine creditworthiness.
Export and delete
- Export: on the Vault page, Export CSV downloads every clip, with every field. You can import the same file back.
- Archive: archiving a clip removes it from every binder. Archived clips are kept on the server so you can change your mind.
- Delete your account: on the Vault page, Your data, Delete my account. It deletes your Vault, your archived clips and your account, and signs out every device and connector, right away. A GitHub copy stays in your own repository until you delete it there.
- Sign out a device: on the Vault page, Settings, Security, Signed-in devices.
Where it runs and how it is protected
Reclipd runs on shared web hosting from Spaceship. All traffic uses HTTPS. Sign-in attempts are rate limited. Each account's Vault is kept in its own folder, and every request is checked against your sign-in token.
Who else handles your data
Only these services touch your data, and only for the job named:
- Spaceship (web hosting, United States): stores your Vault and runs reclipd.com.
- Resend (email): gets your email address and the message when Reclipd emails you (invites, password resets, sign-in notices).
- Anthropic (AI): gets the text for an AI feature you start, such as Summarize, Rewrite or the Prompt writer, when you use Reclipd's included AI.
- Your own AI providers: if you add your own key, the text for the AI feature you start goes to that provider instead.
- GitHub: only if you turn on the GitHub copy (to your own private repository), or sign in with GitHub.
- Google: only if you sign in with Google. Reclipd asks Google for your email address and nothing else.
Report a security problem to privacy@reclipd.com. We answer within a few days.
Children
Reclipd is not meant for children under 13, and we do not knowingly collect their data.
Contact
Questions or deletion requests: privacy@reclipd.com.