Privacy Policy

Unfair ("Unfair", "we", "our", "us") provides a Chrome extension and supporting backend service that helps salespeople classify email threads and draft replies. This policy explains what data we access from Google services, how we use it, how long we keep it, how we protect it, and how you can delete it. It applies to all use of the Unfair extension and service.

1. Data we access

When you connect your Google account, you grant Unfair access to the following. We request the minimum scopes necessary for the features below and nothing more.

Google account email address and basic profile (name), to authenticate you and identify your company workspace.
Email thread content of the thread you are actively viewing (subject, body, participants, timestamps), read on demand to classify the thread and generate reply suggestions. We do not bulk-download, index, scan, or background-sync your mailbox. We only read a thread when you have it open and the extension is acting on it.
Google OAuth tokens (access and refresh tokens), to call the Gmail API on your behalf.

2. How we use Google user data

We use Google user data solely to provide and improve the user-facing features of Unfair:

Classifying whether an open thread is a sales conversation and summarizing it.
Generating suggested reply drafts you can edit, send, or discard. You remain in control. Unfair never sends email on your behalf without your explicit action.

We do not:

Sell, rent, or license your data to anyone.
Use your data for advertising or marketing.
Use your data to determine creditworthiness or for lending.
Use Google user data to train, fine-tune, or improve any generalized or third-party AI/ML model. Email content is sent to our AI subprocessor (Azure OpenAI) under contractual terms that prohibit training on customer data and prohibit the provider from retaining it beyond the request.
Allow any human to read your Google user data, except: (a) with your explicit prior consent (for example, when you ask us to investigate a specific issue), (b) where strictly necessary for security or to investigate abuse, (c) to comply with applicable law, or (d) where the data has been aggregated and anonymized and is used for internal operations.

3. How long we keep data (Retention)

We minimize what we retain. Specifics:

Data	Retention
Raw email thread content (subject, body, participants)	Not stored persistently. Processed in memory to fulfill your request, then discarded.
AI results cache (classification and generated suggestions for a thread)	Cached up to 24 hours for sales threads and 7 days for non-sales threads, keyed by a hash of the thread's current state. Automatically invalidated when the thread receives a new message. A scheduled job permanently deletes expired entries nightly.
Google OAuth tokens	Encrypted at rest and kept only while your account is active. Deleted immediately on disconnect or revocation, and within 30 days of account deletion.
Account records (your email address, name, mailbox connection state)	Kept while your account is active. Deleted within 30 days of account deletion.
Anonymized analytics and product-improvement data (usage metrics, suggestion feedback)	Up to 24 months. This data is irreversibly de-identified before storage (see Section 4) and contains no Google user data. It cannot be linked back to you, your messages, or your account.
Diagnostic / error logs	90 days, then permanently deleted. Error logs are scrubbed of email content and personal identifiers before storage and are used only for debugging and security.

Backups containing any personal data are encrypted, rotated, and fully purged within 35 days.

4. De-identification of analytics data

Before any thread-derived data is written to long-term analytics storage, it is irreversibly de-identified so it is no longer Google user data:

Thread and message identifiers are replaced with one-way SHA-256 hashes.
No user, account, or mailbox identifier is stored alongside analytics records.
Email addresses, phone numbers, URLs, person names, postal addresses, and company names are removed or replaced with neutral placeholders ([EMAIL], [PERSON], [COMPANY], etc.).
Records are retained only in a form that supports aggregate analysis and product improvement, and cannot be re-associated with an individual or a specific message.

Data processed this way is used to evaluate suggestion quality and improve the Unfair playbook in aggregate. It is never used to train third-party AI models.

5. How to delete your data

You can remove your data from Unfair at any time, by any of these methods. Each fully deletes your Google user data from our systems within the timeframes stated.

Disconnect in the extension. Open the Unfair popup and click "Disconnect Gmail." This immediately revokes and deletes your OAuth tokens and purges any cached classifications and suggestions for your mailbox.
Revoke access in your Google Account. Visit myaccount.google.com/permissions and remove "Unfair." We detect the revocation on the next API call and delete your tokens and cached data automatically.
Request full account deletion. Email ops@unfair.app from your registered address with the subject "Delete my account." We will delete your account record, mailbox record, OAuth tokens, and all cached data, and confirm by email.

Deletion timing:

OAuth tokens and cached email content: deleted immediately (or within 24 hours via asynchronous purge).
Account and mailbox records: deleted within 30 days.
Already-anonymized analytics contain no Google user data and cannot be linked to you, so they are not individually deletable. They age out per Section 3.

We respond to verifiable deletion and access requests within 30 days.

6. Google API Services User Data Policy, Limited Use

Unfair's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

We limit use of Google user data to providing and improving Unfair's user-facing features.
We do not transfer Google user data to others except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger or acquisition with notice to users.
We do not use Google user data for advertising.
We do not allow humans to read Google user data except in the narrow circumstances described in Section 2.

7. Subprocessors

We rely on the following subprocessors, each bound by confidentiality and data-protection obligations consistent with this policy:

Microsoft Azure (App Service, PostgreSQL, Table Storage, Key Vault), application hosting and storage.
Azure OpenAI Service, AI classification and reply generation, under terms that prohibit training on, and persistent retention of, customer data.

We do not transfer Google user data to any other third party.

8. Data security

All data is transmitted over HTTPS (TLS 1.2+).
Google OAuth tokens are encrypted at rest with AES-256, using keys held in Azure Key Vault.
Tenant data is isolated at the database level (row-level security). Every runtime query is scoped to a single company or user.
Production access is limited to a small number of authorized personnel, requires multi-factor authentication, and is logged.
We maintain an annual independent security assessment (CASA) consistent with Google's requirements for restricted scopes.

9. Children

Unfair is a business product, not directed to and not intended for anyone under 16. We do not knowingly collect data from children.

10. International users

Your data may be processed in the United States or the European Union, in the region configured for your workspace. Where required, we rely on appropriate safeguards for international transfers.

11. Changes to this policy

We will post changes here and update the "Last updated" date. We will notify active users by email of material changes affecting how we handle Google user data at least 14 days before they take effect.

12. Contact

For questions, access requests, or deletion requests, contact us at ops@unfair.app. We respond to verifiable requests within 30 days.