Privacy Policy
Last updated: 5 October 2026
The short version: Drift has no server and no account. Your recordings stay on your computer. The only time data leaves your browser is when you add your own OpenAI or Anthropic API key and Drift sends your narration and selected screenshots to that provider to turn them into an issue report. We never receive, see, or sell your data.
1. Who we are
Drift is a Chrome extension that lets you narrate bugs while you browse and turns the recording into a structured folder of issues, screenshots, transcript, clicks and logs. This policy covers the Drift extension and this website. Contact: nechalmaggon@gmail.com.
2. What Drift collects
Drift only collects data while you have started a recording, and only on your device. During a recording it captures:
- Screen video of the tab, window or screen you choose to share, and microphone audio of your narration.
- Clicks: timestamp, page URL, a CSS selector, a short preview of the element's visible text, and position.
- Sustained hovers (an element hovered for 250 ms or longer).
- Console output: warnings and errors always;
console.log/infoonly if you turn that on in Settings. - Network requests: method, URL, type, status and duration. If you opt in to "Capture network response bodies" in Settings, Drift also stores the first ~8 KB of the response for failed requests only.
- Viewport and device info: window size, pixel ratio and user agent.
Because this data comes from the pages you visit during a recording, it can include page URLs, on-screen content, and text in requests or responses. Please be mindful of what is on screen when you record, and avoid recording pages containing information you are not comfortable processing.
Drift does not collect anything when you are not recording. It has no analytics, no advertising, no tracking pixels, and no user accounts.
3. Where your data is stored
| Data | Location |
|---|---|
| Recordings, transcripts, issues, logs | Your browser's IndexedDB, on your device only |
| Settings and your API keys | chrome.storage.local, on your device only |
| Backups | A .zip saved to your Downloads folder (automatic backup, on by default, can be turned off in Settings) and any folder you choose via "Save Full Recording" |
None of this is uploaded to us. You can delete any recording from the Library, use "Free Up Browser Storage", or remove the extension to delete all data held in the browser. Backup files in your Downloads folder or other folders you chose are yours to manage and delete.
4. Third-party AI providers (your own API keys)
Drift's AI processing runs directly from your browser to the provider, using the API key you supply in Settings. We are not in the middle. When a recording is processed, Drift sends:
- to OpenAI (
api.openai.com): your microphone audio, for transcription (Whisper). If you choose OpenAI as your reasoning provider, the transcript, selected screenshots, and the relevant clicks, console and network excerpts are also sent there. - to Anthropic (
api.anthropic.com), if you choose Claude as your reasoning provider: the transcript, selected video frames, and the relevant clicks, console and network excerpts for each issue.
Drift also makes a lightweight request to the chosen provider to check that your API key is valid. Your key is sent only to that provider and is never sent to us.
Once data reaches OpenAI or Anthropic, it is governed by their terms and privacy policies, including their retention and training practices for API data. Review them at openai.com/policies and anthropic.com/legal/privacy. If you do not want data sent to a provider, do not add a key; recording and local backup still work, but AI processing will not.
5. Sharing and exports
Drift's "Copy prompt", "Download issues" and "Save Full Recording" features write files or text to your clipboard and disk. Where that content goes next (for example, into a ticket or an LLM chat) is your choice. Drift does not upload it anywhere itself.
6. Why Drift needs its browser permissions
- Access to all sites and content scripts: so it can record clicks, hovers and console output on whatever site you choose to test. These scripts only record while a recording is active.
- webRequest: to log network request metadata during a recording.
- debugger: used only if you enable "Capture network response bodies"; Chrome shows its own "debugging this tab" banner while it is active.
- tabs, scripting: to find the tab being recorded and attach capture to it.
- offscreen: to run the screen and audio recorder in the background.
- storage: to save your settings and API keys locally.
- downloads: to write backup and export files to your Downloads folder.
7. What we do not do
- We do not sell or rent your data, or transfer it to third parties other than the AI providers you choose to use as described above.
- We do not use your data for advertising, credit or lending decisions, or any purpose unrelated to Drift's single purpose of producing bug reports from your recordings.
- We do not load or execute remotely hosted code in the extension.
Drift's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
8. This website
This site is a static page hosted on Cloudflare Pages. It sets no cookies and runs no analytics of our own. Fonts are loaded from Google Fonts, and Cloudflare may process standard server logs (such as IP address) as part of hosting.
9. Children
Drift is a developer tool and is not directed at children under 13.
10. Changes to this policy
If we change how Drift handles data, we will update this page and the "Last updated" date above. Material changes will also be noted in the extension's release notes.
11. Contact
Questions or requests about privacy: nechalmaggon@gmail.com.