How we handle your data.
Quarters is a founder-led CRM that threads your email, iMessage, and Slack conversations together so you can keep relationships warm across channels. To do that, we have to handle some sensitive data — your inbox content, your contacts, your conversations. This page explains exactly what we collect, why, who we share it with, and what control you have.
1. Who we are
"Quarters" is the service operated by AskHumans, Inc. ("we", "us", "our"). You can reach us at hello@usequarters.com.
2. What we collect
2.1 Account information
When you sign up, we collect your name, email address, password (stored as a salted hash, never plaintext), and the workspace name you provide. If you sign in with Google, we also receive your Google email and profile name from Google's OAuth flow.
2.2 Mailbox content
If you connect a Gmail account, we receive email metadata (sender, recipient, subject, timestamps) and message bodies for the threads we ingest. We use this to build your unified inbox and surface conversations that need follow-up. We store ingested messages in our database so the app stays fast and works offline-ish.
2.3 iMessage content (if you install the Mac helper)
If you install the optional Quarters Agent Mac app (or its Terminal-install equivalent) for iMessage sync, it reads your local Messages database and POSTs new messages to our server. This requires Full Disk Access on your Mac, is opt-in, and is uninstalled by dragging the app to the Trash. We store iMessage content the same way as email content.
2.4 Contacts and deals
Everything you create in the app — contacts, accounts, deals, cadence settings, notes — is stored in our database, scoped to your workspace.
2.5 Slack support channels (if connected)
If you wire up a Slack channel to a customer account, we receive messages posted to that channel and store them as part of the customer's conversation history.
2.6 Usage data
We use PostHog (a product-analytics tool) to track how you use the app — which pages you visit, which features you click, when you encounter errors. This is aggregated and used to improve the product. You can opt out via the in-app settings.
2.7 Payment data
When you subscribe, payment information (card number, expiration, billing address) is collected directly by Stripe. We never see or store your card number — we only receive a customer ID and subscription status from Stripe.
3. How we use it
- To provide the service: threading conversations, computing cadences, sending notifications, generating AI draft replies and reports.
- To improve the product: aggregate analytics on which features get used, what causes errors. We use Sentry for error tracking and PostHog for product analytics.
- To bill you: via Stripe.
- To support you: if you email us, we read the email and reply. If you connect a Slack channel for support, we read the messages and reply.
4. What we don't do
- We don't sell your data. To anyone. Ever.
- We don't train AI models on your data. When the app makes an AI call (cadence drafts, lookalike reports, etc.), it goes to Anthropic's Claude API. Anthropic's API terms specify that customer inputs are not used to train models. We don't run our own model training pipeline.
- We don't share your inbox content with advertisers. Or anyone else outside the sub-processors listed below.
- We don't show ads. The product is paid; that's the business model.
Optional advisor text messages
If you request SMS access, we store your mobile number, account and workspace identifiers, the consent disclosure version, and the time you consent or withdraw. SMS is optional. Delivery remains disabled until registration and phone verification are complete. When enabled, Twilio and mobile carriers process phone numbers, message content and delivery information to provide this service.
We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. We do not share mobile information with affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent are not shared with third parties except providers needed to operate the messaging service. You can withdraw your request in Advisor settings; once messaging is active, reply STOP to stop texts or HELP for help. See our SMS terms and signup instructions.
5. Sub-processors
We use a handful of third-party services to operate the product. Each one only sees the data it needs to do its specific job:
| Service | What they see | Why |
|---|---|---|
| Supabase | All your account, mailbox, contact, and deal data | Database + Edge Function hosting |
| AWS Amplify | Static frontend files (no customer data) | Web hosting + CDN |
| Anthropic (Claude API) | The specific prompt for each AI call (e.g., a few recent messages + a question) | AI cadence drafts, reports, classification |
| Twilio (optional advisor SMS) | Verified phone numbers, SMS content and delivery metadata when texting is enabled | Deliver and receive advisor texts; honor opt-outs |
| Stripe | Your name, email, billing address, card details | Payment processing |
| Resend | Your email address + transactional message content (password resets, receipts) | Outbound transactional email |
| PostHog | Anonymized usage events (page views, button clicks) | Product analytics |
| Sentry | Error stack traces, browser metadata, session replays of error sessions only | Error monitoring + debugging |
| Google (OAuth + Gmail API) | Your Google email and the inbox content you authorize us to read | Sign-in + Gmail sync |
| Slack (Events API) | Messages posted to channels you've connected to Quarters | Slack support drawer |
6. Google user data and Limited Use
When you connect a Google account, Quarters accesses your Gmail and (optionally) Google Calendar data through Google's APIs using OAuth scopes you explicitly grant. Quarters'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. Specifically:
- We use Google user data only to provide and improve the user-facing features described above — your unified inbox, conversation threading, cadence, coaching, and reports — never for any unrelated purpose.
- We do not transfer or sell Google user data to third parties, except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger or acquisition with appropriate notice.
- We do not use Google user data for advertising, and we do not let humans read it — except with your explicit consent (e.g. to debug an issue you report), where required for security or to comply with law, or where the data has been aggregated and anonymized.
- We do not use Google user data to train generalized AI / ML models. Per-feature AI calls (e.g. a draft reply) send only the minimum context required to Anthropic's Claude API, which does not train on it.
- Quarters requests only the narrowest scopes it needs: read and send for Gmail (to surface and reply to your threads), and read-only for Google Calendar (to enrich relationships — Quarters never creates, edits, or deletes calendar events).
- You can revoke Quarters's access at any time from your Google Account permissions, or by disconnecting the account in Settings.
7. Data retention
We retain your data for as long as your account is active. If you delete your account, we delete the associated data within 30 days. Some data may persist longer in backups for up to 90 days, after which it's purged.
8. Your rights
You can:
- Export your data at any time from Settings → Data → Export. We provide a JSON dump of contacts, deals, conversations, and notes.
- Delete your account at any time from Settings → Account → Delete. This triggers the 30-day purge described above.
- Disconnect Gmail / Slack / Stripe at any time without deleting your account.
- Request a copy of all data we hold on you by emailing hello@usequarters.com. We'll respond within 30 days.
- Object to processing by emailing the same address. We'll work with you in good faith.
If you're in the EU or UK, you also have rights under GDPR / UK GDPR — right to access, rectification, erasure, restriction, portability, and to lodge a complaint with a supervisory authority. The above mechanisms cover those rights; email us if you need anything more formal.
9. Security
We take security seriously but we're a small team, so let's be specific about what that means:
- Data is encrypted in transit (TLS 1.2+) and at rest (Supabase Postgres uses AES-256).
- Database access is enforced via row-level security and a service-role key that never leaves our server.
- Passwords are stored as scrypt hashes, not plaintext.
- Session cookies are HttpOnly + Secure + SameSite=None.
- OAuth tokens for Gmail/Slack are stored encrypted at the database level.
- No bug-bounty program yet — if you find something, email hello@usequarters.com.
10. Children
Quarters is a B2B sales tool. We don't knowingly collect data from anyone under 18. If you believe we have, email us and we'll delete it.
11. International transfers
Our infrastructure is hosted in the United States (Supabase + AWS, both US-East). If you use Quarters from outside the US, your data is transferred to the US for processing. We rely on the Standard Contractual Clauses where applicable.
12. Changes to this policy
If we change this policy in a meaningful way, we'll email you and update the "Last updated" date at the top of this page. Substantive changes (new sub-processors, new data categories) will be flagged at least 30 days in advance.
13. Contact
Email hello@usequarters.com for anything privacy-related. We aim to respond within 5 business days.