Skip to main content
Slashy handles your email, calendar, and contacts. Security is the foundation, not a feature.
Slashy security overview showing SOC 2, encryption, and privacy certifications

Certifications

Security documentation: slashy.com/security

AI and Your Data

Does the AI train on my emails? No. Every AI provider is contractually bound to a zero-training agreement. Your data is processed to generate a response and then discarded. Only the minimum necessary context (email thread, memories, calendar if relevant) is sent to providers.

Prompt Injection Protection

Malicious emails can contain hidden instructions to trick AI assistants. Slashy sanitizes and isolates incoming email content from system instructions before it reaches any model. The agent cannot take unauthorized actions and flags suspicious content.

What Data Slashy Stores

  • Email metadata and content — cached for fast access
  • Calendar events — synced from Google Calendar
  • Agent conversations — your AI sidebar chat history
  • Memories — preferences, contacts, writing style
  • Automation logs — what ran and when
  • Usage analytics — anonymous, via PostHog
All stored data: AES-256 at rest, TLS 1.2+ in transit. To stop senders from tracking when you open their email, turn on Private reading.

OAuth Access Model

  • Slashy never sees or stores your Google password
  • You grant specific permissions you can revoke anytime at myaccount.google.com/permissions
  • OAuth tokens stored encrypted, refreshed automatically
  • Same model applies to optional integrations (Zoom, Granola)

Data Deletion Timeline

Delete your account yourself from Settings > Account > Delete Account on web, desktop, or mobile. Slashy asks an optional “Why are you leaving?” question, then asks you to type your account email to confirm.

Requesting security documents

Security reviews usually need paperwork. Email privacy@slashy.com from your work address, say which documents you need and what your review process is, and the team will send them. For vulnerability reports, email security@slashy.com. More detail is on slashy.com/security.

Trust at a Glance

SOC 2 Type II

Audited annually by an independent firm

Zero-Training Guarantee

No AI provider trains on your data

AES-256 Encryption

Data encrypted at rest and in transit

Common Security Questions

Encrypted servers in the United States, hosted on AWS with SOC 2 compliance. All data encrypted with AES-256 at rest and TLS 1.2+ in transit.
No. Employee access to production data is restricted, logged, and auditable. No one reads your email unless you explicitly share it for debugging.
Yes. Email privacy@slashy.com to request the SOC 2 report, the pen test summary, and other security documents. See Requesting security documents above.
A Business Associate Agreement (BAA) and a Data Processing Agreement (DPA) are both available on request. Email privacy@slashy.com. The standard DPA is also published at slashy.com/dpa.
Yes. Email founders@slashy.com with details. We respond within 24 hours.
Yes. Slashy is built for professionals handling sensitive email. SOC 2 Type II audited, pen-tested monthly by an independent firm, and all AI providers contractually prohibited from training on your data. Many VC firms, startups, and enterprise teams use Slashy for confidential communications.
Slashy maintains an incident response plan tested quarterly. In the event of a breach, affected users are notified within 72 hours per GDPR requirements. Encrypted data at rest means raw email content is not exposed even if infrastructure is compromised.
Yes. Slashy uses standard Google OAuth 2.0 with scoped permissions. Your Workspace admin can approve Slashy as a trusted app and control which users can connect. See Connecting Gmail for permission details.

AI Privacy

How AI providers handle your data

Data Storage

What Slashy stores and your controls

Connecting Gmail

OAuth permissions and what Slashy accesses

Does the AI send on its own?

How sending and Read Mode work

Subprocessors

Full list of infrastructure providers