Privacy Policy

What we collect

Your email address — collected when you sign up through Clerk, our authentication provider. We use it to identify your account.

Google OAuth tokens (Gmail and Calendar) — when you connect a Google account, Google gives us a scoped access token (not your password). We encrypt this token and store it in Databunker, a dedicated encrypted vault. Our main database never holds your credentials — only a reference ID pointing to the vault.

Pending drafts (Gmail and Calendar write actions) — when your AI tool tries to send an email or create a calendar event, we hold the draft in a pending-events queue until you explicitly approve it from your dashboard. Unapproved drafts are auto-deleted after 24 hours. We never send an email or create an event without your explicit approval.

Audit logs — we log every request an AI agent makes: what it asked for, whether it was allowed, and what data was returned. These logs exist so you can see exactly what your agents are doing.

What we don't do

• We don't sell your data. To anyone. Ever.
• We don't share your data with third parties (other than passing it through to the AI tool you've explicitly authorized).
• We don't use your Google data (emails, calendar events) to train AI models, including our own.
• We don't use Google user data for advertising or advertising-related profiling.
• Humans at Datafense don't read your Gmail messages or calendar event contents. Server processes fetch data from Google, apply your permission filters, and pass results to your AI tool — no human is in the loop.
• We don't store the contents of your emails or calendar events. Data is fetched on-demand from Google, filtered per your rules, and returned to your AI tool. Nothing is cached on our servers — the only Google data we briefly hold is unapproved outgoing drafts (auto-deleted after 24 hours).

How we protect your data

• OAuth tokens are encrypted in Databunker, which runs in an isolated network — it's not accessible from the internet.
• Agent API keys are hashed with SHA-256 before storage. We can't read them.
• All connections use TLS encryption.
• AI agents never see your credentials. They only receive the data your permission rules allow, filtered through our content filters.

Third-party services

We use these services to run Datafense:

• Clerk — handles sign-up and sign-in. Their privacy policy.
• Google — we use Google OAuth to connect your Gmail and Calendar. The scopes we request are listed in the "Google user data — Limited Use" section below. We do not access any Google data beyond what those scopes grant. Google's privacy policy.
• Railway — hosts our servers. Their privacy policy.

Google user data — Limited Use

Datafense's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Scopes we request and why:

• gmail.readonly — used to read messages on your behalf when your AI agent calls the check_email or search_email tools, filtered by the permission rules you set.
• gmail.send — used only to deliver outgoing drafts that you have explicitly approved in the Datafense dashboard. Your AI tool cannot send email autonomously.
• calendar.readonly — used to read calendar events on your behalf when your AI agent calls the get_calendar or get_calendar_details tools, filtered by the permission rules you set.
• calendar.events — used only to create calendar events that you have explicitly approved in the Datafense dashboard. Your AI tool cannot create or modify events autonomously.

How we comply with Limited Use:

• We use Google user data only to provide the user-facing features described above (reading email/calendar via your AI agent, sending emails or creating events that you personally approve).
• We do not transfer Google user data to others except as necessary to provide or improve these features (which in practice means passing data through to the AI tool that you have explicitly authorized), in response to a valid legal request, or in connection with a corporate sale or merger that is bound by the same restrictions.
• We do not use Google user data for advertising or advertising-related profiling, ever.
• We do not allow humans at Datafense to read Google user data, except where you give us explicit affirmative consent (for example, when you forward us a support email containing a specific message), or where required by law, or necessary for security investigations to address an abuse or security violation.
• We do not use Google user data to develop, improve, or train generalized AI models. We do not feed Gmail or Calendar content into any third-party AI training corpus.

You can revoke Datafense's access to your Google data at any time from your Datafense accounts page (one click revokes the OAuth token) or directly at myaccount.google.com/permissions.

Deleting your data

You can disconnect any account from your dashboard at any time — this immediately deletes the OAuth token from our vault and revokes access.

To delete your entire account and all associated data (credentials, agents, permissions, audit logs), email us at vaultagent.dev@gmail.com. We'll delete everything.

Your rights

Depending on where you live, you may have additional rights under laws like the GDPR (EU) or CCPA (California). These include:

• Access — request a copy of the personal data we hold about you.
• Correction — ask us to correct inaccurate data.
• Deletion — ask us to delete your data (see "Deleting your data" above).
• Portability — request your data in a machine-readable format.
• Objection — object to certain processing of your data.

To exercise any of these rights, email vaultagent.dev@gmail.com. We'll respond within 30 days.

Data retention

We keep your data only as long as your account is active. When you delete your account, we delete everything — credentials, agents, permissions, and audit logs. We don't keep backups of deleted data beyond a 30-day rolling window for disaster recovery.

Legal basis for processing (GDPR)

If you're in the EU, our legal bases for processing your data are:

• Contract — processing your email address and OAuth tokens is necessary to provide the service you signed up for.
• Legitimate interest — audit logging to ensure security and prevent abuse.

Children

Datafense is not for children under 13 (or under 16 in the EU). If you believe a child has created an account, contact us and we'll delete it.

Changes

If we change this policy, we'll update the date at the top and notify you by email for any significant changes.

Contact

Questions? Email vaultagent.dev@gmail.com