1. Introduction
This Privacy Policy explains how Persona ("we," "us," "our") collects, uses, and protects your information when you use our web application at personadraft.com and our Google Chrome browser extension (collectively, the "Service"). We are committed to protecting your privacy and handling your data transparently.
By using the Service, you agree to the collection and use of information as described in this policy.
2. What Persona does
Persona is an AI-powered email writing assistant. You describe what you want to say, choose a writing persona, and the Service generates a professionally crafted email using large language models (LLMs). The Service operates as a web application and as a Chrome extension that integrates with Gmail.
3. Information we collect
3.1 Account information
When you create an account, we collect your email address and display name through Google OAuth. We store a user profile containing your subscription plan, usage statistics, and preferences.
3.2 Email content you provide
When you use Persona, you provide the following information:
- User intent: The description of what you want your email to say (e.g., "tell them I agree with the proposal but need more time").
- Extra instructions: Optional additional guidance you type (e.g., "mention Q3 deadline, keep under 3 sentences").
- Thread context (web app): If you paste an email thread into the web app for context-aware replies, that text is processed for tone analysis.
- Thread context (Chrome extension): If you are replying to an email in Gmail, the extension reads the currently visible email thread from the Gmail page to analyze the conversation tone.
3.3 My Voice writing samples
If you use the My Voice feature, you provide writing samples by copying and pasting your own sent emails into a text field within Persona. Persona processes that text to compute a statistical writing fingerprint — numerical values representing your writing patterns (such as sentence length distribution, formality level, vocabulary frequency, and contraction ratio). The raw email text is not sent to or stored on our servers. Only the resulting numerical fingerprint is saved.
3.4 Generated emails and drafts
When you generate an email, the output text is displayed in the Service. If you are a paying subscriber, generated emails may be saved as drafts in your account for later reference. Drafts are stored in our database and are accessible only to you.
3.5 Payment information
If you subscribe to a paid plan, payment processing is handled entirely by Stripe, Inc. We do not receive, process, or store your credit card number, bank account details, or other financial information. We receive only a customer identifier, subscription status, and invoice history from Stripe.
3.6 Device fingerprint (anonymous users only)
For users who are not signed in, we compute a browser fingerprint using publicly available browser signals (screen resolution, timezone, language, and similar non-identifying technical attributes). This fingerprint is used solely to enforce a fair-use limit on anonymous email generation (2 free emails per device). We store a hashed version of this fingerprint — it cannot be reversed to identify you personally.
3.7 Automatically collected technical data
We automatically collect standard server logs including IP address, browser type, operating system, referring URL, pages visited, and timestamps. This data is used for security monitoring, abuse prevention, and service reliability.
4. How we process email content — PII sanitization
This is the most important section of this policy. We take extraordinary measures to protect the personal information contained in email threads.
4.1 Before any email thread text leaves your browser
When the Chrome extension reads an email thread or when you paste a thread in the web app, the following personally identifiable information (PII) is automatically detected and replaced with anonymous placeholders before the text is transmitted to our servers:
- Names (e.g., "Sarah Chen" → "PERSON_1")
- Email addresses (e.g., "sarah@company.com" → "EMAIL_1")
- Phone numbers (e.g., "+1 (415) 555-0172" → "PHONE_1")
- Social Security Numbers (e.g., "123-45-6789" → "SSN_1")
- Account and card numbers (e.g., "Account #4521" → "ACCOUNT_1")
This sanitization happens in your browser (client-side), before any network request is made. Our servers never receive the original names, email addresses, phone numbers, or account numbers from email threads.
4.2 After the email is generated
When the AI-generated email is returned from our server, the anonymous placeholders are replaced back with the original values in your browser (client-side). The re-insertion happens locally — our servers never see the real names in the generated output.
4.3 What our servers receive
Our servers receive only the PII-sanitized version of the email thread (e.g., "PERSON_1 reached out to PERSON_2 about the upcoming deadline"). This sanitized text is used for real-time tone analysis and is not stored after processing is complete.
5. How we use your information
| Data | Purpose | Stored? | Duration |
|---|---|---|---|
| Account email and name | Authentication, account management | Yes | Until account deletion |
| User intent and instructions | Generate the email you requested | No | Processed in real-time, discarded |
| PII-sanitized thread text | Tone analysis for context-aware replies | No | Processed in real-time, discarded |
| Generated email text (drafts) | Allow you to revisit past emails | Yes (subscribers only) | 7–90 days depending on plan, or until deletion |
| Voice fingerprint (numerical values) | Reproduce your writing style | Yes | Until you delete the profile |
| Subscription and billing status | Manage your plan and access | Yes | Until account deletion |
| Device fingerprint hash | Enforce anonymous usage limits | Yes | 90 days |
| Server logs (IP, browser) | Security, abuse prevention | Yes | 30 days |
6. Third-party service providers
We use the following third-party services to operate Persona:
6.1 AI model providers
To generate emails, we send your user intent and PII-sanitized thread context to one or more of the following large language model providers:
- Anthropic (Claude) — anthropic.com/privacy
- OpenAI (GPT) — openai.com/privacy
- Google (Gemini) — ai.google/privacy
These providers process the text to generate a response and return it to us. They receive only PII-sanitized text — never raw names, emails, or phone numbers from your email threads. We use API-tier access, which means these providers do not use your data to train their models.
6.2 Supabase (authentication and database)
User accounts, profiles, drafts, and voice fingerprints are stored in a PostgreSQL database hosted by Supabase. Supabase's privacy policy: supabase.com/privacy.
6.3 Stripe (payment processing)
Subscription payments are processed by Stripe. We never receive or store your payment card details. Stripe's privacy policy: stripe.com/privacy.
6.4 Vercel (web hosting)
The web application is hosted on Vercel. Vercel's privacy policy: vercel.com/legal/privacy-policy.
7. Data sharing
We do not sell, rent, or trade your personal information to any third party.
We share data with third parties only in the following circumstances:
- AI model providers receive PII-sanitized text for email generation (as described in Section 6.1).
- Stripe receives your email address to create a payment customer record.
- Law enforcement may receive data if we are required to comply with a valid legal process (subpoena, court order, or applicable law).
8. Chrome extension — specific disclosures
The Persona Chrome extension operates within Gmail (mail.google.com). The following disclosures apply specifically to the extension:
8.1 What the extension accesses
- The currently visible email thread: When you open a reply in Gmail, the extension reads the email messages visible on screen to analyze the conversation tone. It does NOT access your email archive, contacts, or any emails you have not opened.
- The compose field: The extension reads the text you are typing in the Gmail compose box (your intent for the reply).
- Recipient count: The extension detects how many recipients are in the To and CC fields (count only — not the email addresses).
8.2 What the extension does NOT access
- Your Gmail inbox, sent folder, or email archive — Persona only reads the reply thread you have open
- Your Google contacts
- Your Google Drive, Calendar, or any other Google service
- Any browser tab other than the active Gmail tab
- Your browsing history or bookmarks
8.3 Data transmission
All data read by the extension is PII-sanitized in your browser before transmission to our servers (see Section 4). The extension communicates exclusively with Persona's API servers over HTTPS.
8.4 Permissions used
- activeTab: Access the current Gmail tab when you click the extension icon.
- sidePanel: Render the Persona interface in a side panel alongside Gmail.
- storage: Store your authentication session and preferences locally in the browser.
- host_permissions (mail.google.com): Inject a content script into Gmail to read the visible thread and insert generated emails into the compose field.
9. Data security
We implement the following security measures:
- All data in transit is encrypted using TLS 1.2 or higher (HTTPS).
- Authentication uses industry-standard OAuth 2.0 via Google.
- Database access is restricted to authenticated API endpoints.
- PII sanitization occurs client-side before any data leaves the browser.
- Server logs are retained for 30 days and automatically purged.
- We do not store raw email content on our servers.
10. Your rights
You have the right to:
- Access your data by viewing your profile, drafts, and voice profiles within the Service.
- Delete your account and all associated data by contacting us at privacy@personadraft.com. Upon account deletion, we remove your profile, drafts, voice fingerprints, and any other stored data within 30 days.
- Revoke extension access at any time by uninstalling the Chrome extension. This immediately stops all data access from Gmail.
- Export your drafts by copying them from the Service.
- Opt out of My Voice by deleting your voice profile within the Service.
If you are a resident of the European Economic Area (EEA), United Kingdom, or California, you may have additional rights under GDPR, UK GDPR, or CCPA respectively. Contact us to exercise these rights.
11. Data retention
| Data type | Retention period |
|---|---|
| Account profile | Until you delete your account |
| Generated email drafts | 7–90 days (depends on plan), or until you delete them |
| Voice fingerprint | Until you delete the voice profile |
| Device fingerprint (anonymous) | 90 days |
| Server logs | 30 days |
| Stripe billing records | As required by applicable tax and accounting laws |
Email thread text processed for tone analysis is never stored — it is processed in server memory and discarded immediately after the response is generated.
12. Children's privacy
Persona is not intended for use by individuals under the age of 16. We do not knowingly collect personal information from children. If you believe a child under 16 has provided us with personal information, please contact us and we will promptly delete it.
13. International data transfers
Our servers are located in the United States. If you access the Service from outside the United States, your data may be transferred to and processed in the United States. By using the Service, you consent to this transfer.
14. Changes to this policy
We may update this Privacy Policy from time to time. When we make material changes, we will notify you by posting a notice in the Service or sending an email to your registered address. The "Last updated" date at the top of this policy indicates when it was last revised.
15. Contact us
If you have questions about this Privacy Policy or your data, contact us at:
Email: privacy@personadraft.com
16. Organization and business users
If you use Persona through a business organization account, your organization's administrator may have access to your usage statistics (email count, plan status). Your administrators do not have access to the content of your generated emails or drafts.
Organization administrators may configure compliance features (firewall, knowledge base) that affect how the Service processes emails for members of their organization. Firewall audit logs may record that a compliance rule was triggered, along with a brief description — but they do not contain the full email text.