Privacy Policy
Last updated: April 7, 2026
This Privacy Policy describes how Swell ("we," "us," or "our") collects, uses, and protects information when you use the Swell meeting follow-up application (the "Service"). Please read this policy carefully before connecting your Google Account.
1. Google API Limited Use Disclosure
The app's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
The full Google API Services User Data Policy can be found at: https://developers.google.com/terms/api-services-user-data-policy
2. Google Permissions We Request
When you sign in with Google, we request the following OAuth scopes. We request only the permissions strictly necessary to provide the Service.
| Scope | Classification | Purpose |
|---|---|---|
https://www.googleapis.com/auth/gmail.readonly | Restricted | Read your sent email threads to understand your writing style and retrieve prior email context with a prospect before drafting a follow-up. |
https://www.googleapis.com/auth/gmail.compose | Sensitive | Place a completed follow-up draft (with no recipient address pre-filled) in your Gmail Drafts folder, and send a "draft ready" notification to your own email address only. |
https://www.googleapis.com/auth/calendar.readonly | Sensitive | Read your calendar events to identify meeting attendees, meeting titles, and meeting times so the draft can be correctly addressed and dated. |
https://www.googleapis.com/auth/userinfo.email | Standard | Identify your Google account email address to associate your tokens with your account. |
https://www.googleapis.com/auth/userinfo.profile | Standard | Display your name within the application. |
3. How We Use Google Data
We use the data accessed through Google APIs solely to provide you with the Service — generating a personalized follow-up email draft after your sales calls. Specifically:
- Gmail (read): We retrieve your sent-mail threads and email history with the prospect to (a) analyze your writing style and (b) give the AI context about prior conversations with the contact.
- Gmail (compose): We create a Gmail Draft in your Drafts folder with no "To" field pre-populated. The draft cannot be sent automatically — you must open it, add the recipient(s), and send it yourself. We also send a notification email to your own email address only to alert you that a draft is ready.
- Google Calendar (read): We read your calendar events to identify the attendees of the meeting you just had and to accurately date and address the draft.
We do not:
- Read your inbox or emails you have received (only your sent mail and threads with the identified prospect are accessed).
- Send email to any address other than your own verified Google account address.
- Pre-populate the "To" field in any draft we create.
- Store the raw content of your Gmail threads or calendar events beyond what is necessary to complete a single draft generation job.
- Share your Google data with any third party other than as described in Section 4 below.
- Use your Google data for advertising, analytics unrelated to the Service, or any purpose other than drafting follow-up emails for you.
4. AI Processing — Anthropic Claude
To generate a draft follow-up email, we transmit relevant context — including excerpts from your email threads with the prospect, calendar event details (attendee names, meeting title, date), and a representation of your writing style — to Anthropic's Claude API (Anthropic PBC, San Francisco, CA).
This data is used exclusively to produce a draft email suggestion for your review. We do not use this data to train models, and Anthropic's API usage policies govern how Anthropic handles API inputs. See Anthropic's privacy policy at https://www.anthropic.com/privacy for details.
5. Human-in-the-Loop — No Automatic Sending
Swell never sends email to any prospect, customer, or third party on your behalf.
Every draft produced by the Service is placed in your Gmail Drafts folder with no recipient address. You are solely responsible for:
- Reviewing and editing the draft before sending.
- Adding the correct recipient(s).
- Deciding whether to send, discard, or modify the draft.
The Service only sends email to your own verified Google account email address (a "draft ready" notification). This is enforced at the code level — our application will throw a hard error and abort if the destination address differs from the Google-verified address associated with your OAuth token.
6. Data Storage and Retention
We store the following data in our database (Supabase, hosted on AWS):
- Your Google OAuth access and refresh tokens (encrypted at rest), used to make API calls on your behalf.
- Your email address, display name, and account preferences.
- Meeting metadata (title, attendee email addresses, meeting date/time) used to generate drafts.
- The generated draft subject and body, so you can review it in the app.
We do not store the full content of your Gmail messages or raw calendar event bodies persistently. Email content fetched during draft generation is processed in memory and discarded after the draft is produced.
You may request deletion of all your data by contacting us at the address in Section 9.
7. Revoking Google Permissions
You may revoke Swell's access to your Google Account at any time by visiting your Google Account permissions page:
https://myaccount.google.com/permissions
Find "Swell" (or "meeting-follow-up") in the list and click Remove Access. Revoking access will prevent the Service from functioning until you sign in again and re-grant permissions.
8. Children's Privacy
The Service is intended for use by business professionals and is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13.
9. Contact Us
If you have questions about this Privacy Policy, your data, or to request data deletion, please contact us at:
Email: kai.jarmon@gmail.com
10. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be communicated by updating the "Last updated" date at the top of this document and, where required, by notifying you by email. Continued use of the Service after changes take effect constitutes your acceptance of the updated policy.