# Trust & Security You’re always in control of what your assistant can do. Town treats trust and security as core to the product, not as an afterthought — your data stays protected, and nothing happens on your behalf until you’ve approved it. This page answers the most common questions about how Town handles your data and your permission. For the mechanics of how you grant and limit that permission, see the sub-pages below. ## In this section - [Modes & Approvals](/content/docs/safety/modes-approvals/index.html) - [Security](/content/docs/safety/security/index.html) ## Will Town email, schedule meetings, or message people without my permission? **No — never without your permission.** By default, Town asks first and waits for your go-ahead before any email, message, or calendar invite goes out. Nothing is sent or scheduled behind your back. You stay fully in control: Town can draft replies, suggest messages, and prepare invites for you, and by default nothing is sent until you review and approve it. Think of Town as preparing the work and handing it to you for the final say. Some advanced features let you grant that permission ahead of time. For example, you can set up a [trusted contacts](/content/docs/using-town/email#let-your-assistant-send-email-directly/index.html) list so your assistant can email specific people or domains directly, without approving each message. Features like this are always opt-in and off by default — you choose exactly who they cover, and you can change or remove them anytime — so it’s still your permission, just granted in advance rather than message by message. The exact way you grant that approval — per-session permission levels, per-routine modes, and per-tool controls — is covered in [Modes & Approvals](/content/docs/safety/modes-approvals/index.html). ## Does Town train its AI on my data? - Using your data for AI training is off by default, and we configure our [AI model providers](/content/ai-model-providers/index.html) so your inputs and outputs aren’t used to train their models either. If you ever want to help improve Town, there’s a training toggle in your settings where you can opt in. (Go to Account → Settings → Privacy.) - Google data is fully off-limits for training. Anything from Gmail, Google Calendar, or Google Drive is never used to train machine-learning models — a requirement of Google’s API Services User Data Policy, and a commitment Town stands behind. - We never sell your data. ## Who at Town can see my data, emails, or messages? Access is tightly restricted by design. - **No Town team member has production database access.** Full stop. - **No one at Town can access your data by default** — it’s encrypted at rest and in transit. Access only happens two ways: you approve it for support, or our CEO/CPO authorizes a one-time look at a single session during a security incident (very rare). - **Your Townie only touches the data needed to do what you’ve asked.** For email, it accesses only what’s required to act — organizing your inbox, drafting a reply, surfacing what matters — and never browses your inbox for any other purpose. ## How is my data encrypted, and where is it hosted? **Encrypted everywhere.** All your data is encrypted in transit (HTTPS/TLS) and at rest (AES-256). On top of that, especially sensitive items — like the access tokens for your connected accounts — get an extra layer of application-level AES-256 encryption. **US-hosted.** Your data is hosted in the United States on Convex and AWS. One honest note: this isn’t “zero-knowledge” encryption. Town’s systems work with your data to actually do tasks for you, so the service can process your content during normal operation. What we promise is that it’s encrypted, access is tightly controlled, and it’s only ever used to help you. ## How long do you keep my data if I delete it or my account? You can delete your account anytime from **Settings**. - **We soft-delete immediately.** The moment you delete, your account is deactivated, your routines stop, and your Town sessions are revoked. - **Everything is permanently removed within 30 days.** - The only exceptions are narrow ones — for example, if there’s an active legal hold, or a small set of security/audit records we’re required to retain. **Want to step back without deleting everything?** You can disconnect any integration anytime from your settings — or revoke Town’s access directly from your Google, Slack, or Notion security settings. ## Do you have SOC 2, a DPA, or compliance docs? Security is built into how Town works, not bolted on. Here’s where things stand: - **SOC 2 Type 2 — completed.** Town has completed SOC 2 Type 2 certification for independently audited assurance of its security controls. - **CASA — completed.** Town has completed a Cloud Application Security Assessment, validated by an independent third party against the OWASP ASVS standard. - **Google API Limited Use — compliant.** Google user data is used only to provide Town’s services to you — never shared, sold, or used for advertising. **Bringing Town to a team with specific security requirements?** We’re happy to talk — email [support@corp.town.com](mailto:support@corp.town.com) and we’ll walk you through the details. ### Where to find our security & privacy documentation Doing a security review? These are the canonical resources: - **Trust Center** — [trust.town.com](https://trust.town.com/) for our controls, certifications, and to request documents. - **Security overview** — [town.com/features/security](/content/features/security/index.html). - **Data Processing Addendum (DPA)** — [town.com/dpa](/content/dpa/index.html). - **Subprocessors** — [town.com/subprocessors](/content/subprocessors/index.html) (includes Convex). - **AI model providers & no-training** — [town.com/ai-model-providers](/content/ai-model-providers/index.html). ## Encryption specifics - **In transit:** TLS 1.2 / 1.3. - **At rest:** AES-256-GCM, with an extra application-level layer of AES-256 encryption on especially sensitive items like your connected-account access tokens. ## Data residency & transfers Town is **US-hosted** (Convex and AWS). We don’t offer EU data residency today. International data transfers are covered by the Standard Contractual Clauses (SCCs) in our [DPA](/content/dpa/index.html). ## Enterprise: SSO, SCIM, HIPAA, GDPR For teams evaluating Town against enterprise requirements, here’s where things honestly stand today: - **SSO / SAML** — on the enterprise roadmap; no committed date yet. For Microsoft 365 tenants, admins can already manage access via [Microsoft Entra](/content/docs/admin-setup/microsoft-entra/index.html). - **SCIM (automated user provisioning)** — not supported and not currently planned. - **HIPAA / BAA** — not available today. - **GDPR** — not available today. If any of these are requirements for your organization, reach out to [support@corp.town.com](mailto:support@corp.town.com) or via the [Trust Center](https://trust.town.com/) so we can talk through your needs and timeline. ## Built-in protections Beyond the controls you set, Town includes security measures that apply automatically: - **Smart safeguards** — When a routine has access to private data, untrusted input, and external communication tools, extra protections kick in automatically. - **Input validation** — Blocks known manipulation patterns in incoming content. - **Output validation** — Checks tool arguments before executing actions. - **Account isolation** — Routines can only access accounts you’ve connected. Learn more in [Security](/content/docs/safety/security/index.html). ## Does Town have a privacy policy? Yes. You can read it anytime at [town.com/privacy-policy](/content/privacy-policy/index.html). It explains exactly what information Town collects, how it’s used, and the safeguards in place to keep your data protected. Last updated on August 8, 2026.