Privacy & data handling

What we collect, where it goes, how long it stays. Covers the AgentDrive web app, API, MCP server, and the AgentDrive SnipIt browser extension. AgentDrive is in beta — this page is updated as the data flow changes. Last updated 2026-06-13.

What you put in your drive

Artifacts you (or your agents) upload are stored on Google Cloud infrastructure in the United States. Artifact metadata (path, size, content type, visibility, your supplied metadata dict) is held in our database, also in the United States. Artifacts marked private are gated by your bearer token or your signed-in session cookie — they are not reachable by URL without one of those.

Agent & MCP connector access

AgentDrive exposes your drive to AI agents over an MCP server — usable as a connector in Claude and other MCP clients — and over the REST API. Every connection is scoped to a single drive by an OAuth grant or bearer token you authorize, and can be revoked at any time from /settings.

• We store only what your agent writes. AgentDrive holds the artifacts and metadata an agent uploads through the API or MCP. We collect no data from your AI client's context beyond the arguments of the tool calls you invoke — only what is necessary to perform the requested operation.
• We never read your AI client's session. AgentDrive does not query, extract, or store your Claude (or other client's) chat history, conversation memory, conversation summaries, or any user-generated or uploaded files held inside your AI client. Conversation content is never collected, including for logging.
• Reads return only to your client. When your agent calls a read tool (e.g. read, find, list), the requested artifact contents are returned to the MCP client you connected — for example Claude — so the agent can use them. They are not shared with any other party.

What gets sent to third parties

• WorkOS (sign-in). All sign-in goes through WorkOS, which handles email/password, Google and Microsoft OAuth, and passkeys on our behalf. WorkOS sees your email address and the identity-provider response. WorkOS's privacy policy applies to that exchange. We never see, store, or have access to your identity-provider password.
• Google Gemini (LLM indexing). By default, when you upload a text-extractable artifact, AgentDrive sends up to the first 120,000 characters of its extracted text to Gemini 2.0 Flash via the Google AI API to build a per-drive wiki of entities + concepts. Per Google's terms, prompts sent via this API are not used to train Google's models. You can turn this off at /settings → Privacy → LLM indexing. With indexing off, your artifact contents stay in AgentDrive and Google Cloud and are never sent to Gemini.
• Resend (feedback delivery). When you submit the contact form at /feedback, the message body and your email address are delivered to us via Resend. Resend is not involved in any other email flow, including sign-in. Resend's privacy policy applies to delivery and bounce processing.
• No analytics, no tracking pixels, no third-party JS. AgentDrive does not run Google Analytics, Segment, Mixpanel, Sentry, or any session-replay tool. We do not embed third-party fonts or scripts.

Logs & retention

• Application logs (errors, indexer activity) and access logs (request method, path, status, latency, source IP) are retained for 30 days by default.
• Sign-in failure logs use a redacted form of your address (***@domain.tld); the local-part is never logged.
• Database backups are kept for 7 days for disaster-recovery. A deleted drive is removed from the live database immediately, but it may remain in a backup snapshot until that snapshot ages out (up to 7 days).
• Object versioning is not enabled on file storage. Deleted file bytes are removed within seconds of the delete request.

Account deletion

Deleting your account from /settings/danger triggers, in order:

1. Your drive record is deleted from our database (immediate).
2. All artifact records cascade-deleted (immediate, same transaction).
3. All your uploaded file bytes are deleted from storage (best-effort, leaks logged).
4. Your account record may persist in database backup snapshots for up to 7 days.

Your data, your access

• Read everything. Use the API (GET /v0/artifacts, GET /v0/artifacts/<path>) or MCP (list_artifacts, read) to enumerate and download every artifact in your drive.
• Delete anything. DELETE /v0/artifacts/<path> or MCP delete. Removes both the record and the file bytes.
• Delete the wiki. Browse with the show _wiki/ toggle on the dashboard and delete individual pages, or turn off indexing to stop new pages from being written.
• Delete the whole drive. /settings/danger.

EU & UK users — your rights under the GDPR

AgentDrive is operated by Mnexa ("we"), the data controller for your account data and the artifacts you store. If you are in the European Economic Area, the United Kingdom, or Switzerland, the GDPR / UK GDPR gives you the rights below. We honour them for all users regardless of location.

Legal bases for processing

• Contract. Storing and serving the artifacts you upload, and authenticating you, is processing necessary to provide the service you asked for.
• Legitimate interests. Security logging, abuse prevention, and operating the service — balanced against your rights.
• Consent. Optional LLM indexing (the per-drive wiki) is opt-in/opt-out at /settings → Privacy. You can withdraw consent at any time; withdrawal does not affect prior processing.

Your rights

You may exercise the rights of access, rectification, erasure, restriction, portability, and objection, and you may lodge a complaint with your local supervisory authority:

• Access & portability. Export every artifact in a machine-readable form via the API/MCP (see "Your data, your access").
• Rectification. Edit or re-upload any artifact.
• Erasure. Delete any artifact, or your whole account, from /settings/danger — live data is removed immediately and ages out of backups within 7 days.
• Restriction / objection. Email us (below) to restrict or object to a specific processing activity.

To exercise any right, email hello@mnexa.ai. We respond within 30 days. We do not sell personal data and do not use it for advertising or automated decision-making with legal effects.

International data transfers

Our infrastructure and sub-processors are in the United States, so your data is transferred to and stored in the US. Where that involves EEA/UK personal data, the transfer relies on the EU-U.S. / UK Data Privacy Framework certifications of our sub-processors and/or the European Commission's Standard Contractual Clauses.

Sub-processors

We use the following processors to run AgentDrive. Each is bound by a data processing agreement and processes data only on our instructions.

• Google Cloud (US) — artifact storage and database hosting.
• WorkOS (US) — authentication (sign-in, OAuth, passkeys).
• Google (Gemini API) (US) — optional LLM indexing of text you choose to index; disabled when you turn indexing off.
• Resend (US) — transactional delivery of the feedback / contact form.

Business customers who need a signed Data Processing Agreement can request one at hello@mnexa.ai.

AgentDrive SnipIt (browser extension)

AgentDrive SnipIt is an optional Chrome extension that captures a region of the current tab, lets you annotate it, and uploads the image to your AgentDrive with a shareable link. The extension is a front door to the same data flow described above — anything SnipIt saves is just an artifact in your drive, governed by the same storage, retention, and deletion rules.

Single purpose

SnipIt has one purpose: capture, annotate, and upload screenshots to your AgentDrive. The extension does nothing else. It does not read pages you don't trigger it on, does not monitor browsing activity, does not inject ads, and does not modify pages you visit beyond the on-demand region-select overlay you opt into.

What the extension collects

• Screenshots you capture. Only the region or viewport you explicitly select. Capture is gesture-initiated (toolbar button or keyboard shortcut) — there is no background or scheduled capture.
• Annotations you draw. Arrows, redaction blurs, text, and crops you apply in the editor — flattened into the uploaded image. Redaction is irreversible (solid-ink overdraw, not a CSS effect).
• Your sign-in tokens. A short-lived access token plus refresh token are stored in chrome.storage.local so you don't have to sign in on every capture. They are readable only by the SnipIt extension on your device. We do not have access to the local storage of your browser.
• In-flight capture state. A pending screenshot blob and editor session metadata live in chrome.storage.session while you're editing. This slot is cleared when you close the editor tab or restart Chrome.

What the extension sends, and to whom

• To api.agentdrive.run (us): the annotated PNG bytes, the destination path (default screenshots/YYYY-MM-DD/<slug>.png), and your bearer token. This is the upload itself. Stored in your drive under the storage and database scheme described above.
• To WorkOS (sign-in): during initial sign-in only, the standard OAuth round-trip carries your email/identity provider response. SnipIt reuses the same WorkOS flow as the web app; no extra identity data is captured by the extension.
• No third parties. SnipIt sends no telemetry, no analytics, no crash pings, no usage events to anyone — not to Google, not to us. The extension contains no analytics SDK, no Sentry, no PostHog, no Segment.

Chrome permissions, and why each is needed

• activeTab — capture the visible area of the tab you explicitly invoke SnipIt on. Granted per-gesture; no background tab access.
• scripting — inject the region-select overlay so you can drag a rectangle to capture. Only injected on user gesture, only into the current tab.
• storage — persist your sign-in tokens (so you don't sign in on every capture) and your editor draft state. See "What the extension collects" above for the exact contents.
• notifications — show a one-line confirmation (with the share URL) after a capture uploads, so you know it's done. No badging, no background notifications.
• offscreen — required by Chrome MV3 to use canvas APIs from a service worker context (image processing, annotation flattening). No network or DOM access from the offscreen document.
• Host permissions for https://api.agentdrive.run/* and https://agentdrive.run/* — the only endpoints the extension talks to. SnipIt does not have host access to any other domain.

No remote code, no model training

SnipIt ships all its code in the extension package. It does not fetch and execute remote JavaScript or WebAssembly at runtime. The image bytes you upload are stored in your drive — they are not used to train any machine-learning model, ours or anyone else's. If you later turn on LLM indexing for your drive (see the third-party section above), text-extractable artifacts may be sent to Google Gemini; screenshot PNGs from SnipIt are not text-extractable and are not part of that flow.

Limited use compliance

Per Chrome Web Store's limited-use requirements, we affirm that data accessed by AgentDrive SnipIt:

• is used only to provide the user-facing feature (capture + upload),
• is not sold to third parties,
• is not transferred for advertising, credit-scoring, or any other unrelated purpose,
• is not read by humans except (a) with your explicit consent, (b) for security or to comply with applicable law, or (c) in aggregated, anonymized form for internal operations.

Removing the extension

Uninstalling SnipIt clears all extension-local storage (tokens, drafts) from your browser. It does not delete screenshots already uploaded to your drive — those follow the standard deletion path (see "Your data, your access" above).

Cookies

AgentDrive uses one cookie: ad_session, a signed session cookie that holds your drive id and a CSRF token. It is HttpOnly, SameSite=Lax, and (in production) Secure. We use no advertising or analytics cookies.

Contact

Questions, data-export requests, deletion verifications, or anything else privacy-related: hello@mnexa.ai.