Oct 28, 2026
ThinkStream reads your email, calendar, documents, and messages so protecting that data is the job. This page describes the controls we run today. We've adopted NIST SP 800-53 as the framework we're building toward. We don't yet hold a formal certification such as SOC 2 or ISO 27001, and we'll say so plainly until we do.
Infrastructure and where your data lives
ThinkStream runs on Google Cloud Platform, in a single region in the United States. Our Google Cloud application infrastructure is in the US. Outside providers process data in the locations listed on our Subprocessors page.
Component | What it does | How it's run |
|---|---|---|
Application services (API, sign-in, background workers, scheduler) | Run ThinkStream | Containers on Google Kubernetes Engine |
Main database | Stores accounts, Content and Derived Data | Google Cloud SQL (managed PostgreSQL) |
Search, cache and relationship stores | Power search, speed and connections between items | Run inside our private cluster |
File storage | Holds model files | Google Cloud Storage |
Secrets | Holds keys and credentials | Google Secret Manager |
We use a small number of outside vendors to run the service. Our Subprocessors list View subprocessors policy names each one and the data it handles.
Encryption
- In transit. Every connection to ThinkStream uses HTTPS with TLS 1.3. Plain HTTP requests are redirected to HTTPS.
- At rest. Our database and file storage are encrypted with AES-256.
- Connected Account credentials. The tokens that let us read your Gmail or Calendar get an extra layer of field-level encryption in the database.
- Secrets. API keys and passwords live in Google Secret Manager, never in our code. Our deploy pipeline signs into Google Cloud with short-lived credentials, not stored keys.
Signing in
You can sign in with Google, Apple, or an email and password. We store passwords only in hashed form. Two-factor authentication with an authenticator app is available, and we recommend it.
Connected Accounts
- Permission you grant. We connect to Gmail, Google Calendar and other providers through their official sign-in (OAuth). The provider's consent screen lists exactly what we ask for. We ask only for what our features need.
- Disconnecting. When you disconnect an account in ThinkStream, we delete its access tokens right away and ask the provider to revoke our access. For belt-and-braces, you can also remove ThinkStream in your provider's security settings, such as myaccount.google.com/permissions.
Keeping accounts and Data Spaces separate
Every record we store carries the ID of the ThinkStream Login it belongs to. Before returning any data, our service checks that the person asking owns it. Each record also carries its Data Space label, so Personal and Business data stay separate as the Account Ownership policy promises.
Who at ThinkStream can see your data
Only a few team members have production access, controlled by role. Admin actions, such as deleting an account or changing a plan, are logged. We look at customer data only for the reasons in our Terms of Service: a support request you approve, fixing a stuck process, security work, or a legal requirement.
AI processing
To create summaries, priorities and drafts, we sometimes send AI providers only the content each request needs. Our agreements with them bar them from training their models on your data. The providers are named on our Subprocessors list.
Backups and deletion
- Backups. Google Cloud backs up our main database automatically. Backups are retained for 30 days.
- Deletion. When you disconnect an account or cancel, we delete its data from active systems within 30 days and from backups within 60 days, as our Account Ownership and Cancellation policies describe.
Monitoring
We log every request to our service, every sign-in and every admin action, and send the logs to a central system where we can search them. We track error rates and background-job health, and get alerts when something fails.
How we ship changes
- Every change goes through a pull request and must pass automated checks before it merges.
- Production releases are started by hand and need an explicit confirmation step.
- Automated tools flag outdated software libraries every week so we can update them.
Our team
Everyone with access to production signs a confidentiality agreement and gets only the access their role needs. We remove access the day someone leaves.
If something goes wrong
We follow a written incident response plan. If we confirm a breach that affects your data, we'll tell you within 72 hours, and in any case within the time the law requires.
Report a security problem
Found a vulnerability or think your account is under attack? See our Security Response page or email security@thinkstream.ai.
Still in progress
We're a young company and we're constantly upping our security game. We regularly review our security practices and improve our safeguards.