Scrubbr connects to your email, chat and calendar with your permission. Where a control is still being rolled out, we say so.
7 days free·Cancel anytime
Scrubbr connects to Gmail, Google Calendar, Google Chat, Slack and, if you choose, Outlook and Teams, with your permission.
Nothing is sent to another person without your explicit action: a click, or a voice command you confirm.
Some actions that affect only your own account happen automatically or on a single voice request. Scrubbr applies its own labels in Gmail. The voice assistant can mark messages read and create, move or cancel events on your own calendar when you ask.
We do not use your content to train AI models. Every model request is routed only to providers whose data policies prohibit training on it.
Scrubbr records only an attachment's filename, type and size. Attachment content is never sent to an AI model.
CASA Tier 2 verified
SOC 2 Type I · LOE upon request
Effective 4 October 2026 · version 1.6
This page explains where your data lives, who can see it and how we protect it.
Application data and customer data are stored in Supabase (managed Postgres on AWS) in a US region (us-west-2).
Application servers run on AWS in the same region, behind Cloudflare.
Backups are encrypted and managed by Supabase.
AI processing is performed in the United States by Anthropic, OpenAI, and Google. If you are located outside the United States, your data is transferred to and stored in the United States under appropriate safeguards.
Data is encrypted in transit (TLS 1.2 or higher) and at rest (AES-256 with provider-managed keys).
OAuth tokens carry a second, application-layer AES-256-GCM encryption layer. Its key is held outside the database.
Production access is limited to our two founders and granted at the smallest scope needed.
We have not built any internal tool for reading customer messages.
Message metadata (sender, recipient, subject, timestamps, labels) and message body content. Processed for prioritization, summarization, and drafting.
Message metadata and message body content from channels and direct messages your account has access to. Processed for prioritization, summarization, and drafting.
Scrubbr uses your personal Slack user token, not a bot token.
Messages you send through Scrubbr appear in Slack under your name, indistinguishable from a message you typed in Slack itself. There is no scrubbr-bot installed in your channels.
Event metadata (titles, attendees, times, locations, descriptions). Processed for triage context and meeting prep. Future events are kept; past events follow the retention window.
Space, channel and direct-message metadata, and message text from the spaces and chats your account belongs to. Processed for prioritization, summarization, and drafting.
Replies are sent only when you approve them. Scrubbr creates a direct-message space or changes space membership only when you take an explicit action.
Never stored.
Scrubbr records only an attachment's filename, type and size. When you open an attachment, we fetch it from the source system and hand it straight to your browser without keeping a copy. Attachments you add when composing stream straight through to Gmail, Outlook or Slack without being persisted.
The one exception: small images embedded inline in an email's body are stored as part of that message.
Scrubbr never sees your card. Payment is handled directly by Stripe; we receive only a customer ID and subscription status.
Production access is limited to our two founders and granted at the smallest scope needed. Access reviews are targeted quarterly; the most recent completed review was in June 2026.
We access the contents of your messages only with your explicit approval, except where we must act on a security incident or a legal obligation.
That is typically when you have asked us to investigate something. For Gmail, Calendar, and Chat data, it means your affirmative agreement to view the specific messages concerned. We do not browse customer data.
For Gmail, Calendar, and Chat data, Google's API Services User Data Policy binds us to the same limit.
We have not built any internal tool for reading customer messages. Administrative tools return account and usage metadata only, and there is no “view as user” feature.
An append-only audit log records sign-ins, integration changes, messages sent and calendar changes made through Scrubbr, administrative actions and deletions. It is kept for 365 days.
If we discover a security incident affecting customer data, we contain it, investigate, and notify affected customers without undue delay and in any event within 72 hours of confirmation.
Report a suspected incident to security@scrubbr.ai.
The providers below help us run Scrubbr. Each is engaged under written terms to handle data only for the purposes of running Scrubbr.
We give at least 30 days' notice before a new sub-processor handles customer data, by updating this page and emailing account holders.
Scrubbr has completed Google's CASA Tier 2 security assessment for restricted Gmail scopes, with the accredited assessor's Letter of Validation issued in August 2026.
AlignedScrubbr's security program is aligned to NIST SP 800-171 Rev. 2.
Audit engagedScrubbr is not yet SOC 2-attested.
A SOC 2 Type I audit is engaged with TAC Security, and the letter of engagement is available on request. When the report is issued, this page will be updated and the report will be available under NDA.
If your team needs these commitments in a contract and not on a page, we will sign one. A data processing agreement covering processing scope, sub-processors, security measures, breach notification, and deletion is available on request from privacy@scrubbr.ai.
For questionnaires or vendor reviews from your infosec team, send them to security@scrubbr.ai with your due-diligence document and we'll respond promptly.
Security: security@scrubbr.ai · Privacy: privacy@scrubbr.ai
Legal text lives on its own pages: Privacy notice · Terms
No. Scrubbr does not use your content to train AI models. Every model request is routed only to providers whose data policies prohibit training on it.
Not yet. Scrubbr is not yet SOC 2-attested. A SOC 2 Type I audit is engaged with TAC Security, and the letter of engagement is available on request. Scrubbr has completed Google's CASA Tier 2 security assessment for restricted Gmail scopes, with the accredited assessor's Letter of Validation issued in August 2026, and its security program is aligned to NIST SP 800-171 Rev. 2. When the SOC 2 report is issued, this page will be updated and the report will be available under NDA.
Nothing is sent to another person without your explicit action: a click, or a voice command you confirm. Some actions that affect only your own account happen automatically or on a single voice request: Scrubbr applies its own labels in Gmail, and the voice assistant can mark messages read and create, move or cancel events on your own calendar when you ask.
We access the contents of your messages only with your explicit approval, except where we must act on a security incident or a legal obligation. We have not built any internal tool for reading customer messages. The database itself can be reached by our two founders, for incident response and approved repairs. That limit is enforced by policy, not yet by encryption, and reads made directly in the database console are not individually logged today.
No. Scrubbr uses your personal Slack user token, not a bot token. Messages you send through Scrubbr appear in Slack under your name, indistinguishable from a message you typed in Slack itself. There is no scrubbr-bot installed in your channels.
You can delete your account from Settings at any time; deletion is immediate. Verified deletion requests by email, and deletion after a contract ends, are completed within 30 days, except where retention is required by law. You can also set a shorter retention window in Settings, from 30 days to 10 years. Audit log entries (never message content) are kept for up to 365 days as security evidence.
Email security@scrubbr.ai. If we discover a security incident affecting customer data, we contain it, investigate, and notify affected customers without undue delay and in any event within 72 hours of confirmation.