Privacy Policy

Effective Date: November 7, 2026

Easy Email Filters ("we," "us," or "our") helps you see, name, create and delete your Gmail filters. This policy explains exactly what data the service at easyemailfilters.com (the "Service") reads from your Google account, what it stores, who it is shared with, and how to delete it. If you do not agree with it, please do not use the Service.

1. What we access from your Google account

When you sign in with Google you are asked to grant these permissions (OAuth scopes). We request only what each feature needs:

• Sign-in (openid, email, profile) — your Google account ID, email address, name and profile picture, used to sign you in and show which account is connected.
• Filters (gmail.settings.basic) — list, create and delete your Gmail filters. This is the core of the Service. We never change other Gmail settings such as forwarding, vacation responder or signatures.
• Labels (gmail.labels) — list your labels so you can pick them by name, create a label when a new filter needs one, delete labels you choose to remove, and read per-label message and unread counts.
• Read-only mail access (gmail.readonly) — used for two things only. (a) To show how many messages each filter matches, we run the filter's own criteria as a Gmail search and read only the result count. (b) When you open the Suggestions page and ask for suggestions, we sample recent messages you chose and read their headers (From, To, Subject, Date, List-Id, List-Unsubscribe), their labels and Gmail's short snippet. We do not read message bodies or attachments, and we never send, modify, archive or delete email.

Gmail remains the source of truth for your filters and labels. The Service reads them live from Google each time you open a page.

2. What we store

We store the minimum needed to make the Service work between visits, in a database hosted on Cloudflare:

• Account record: your Google account ID, email, name, picture, the scopes you granted and your settings (such as assistant thoroughness).
• OAuth tokens: the access and refresh tokens Google issues so the Service can act for you, including a once-a-day background snapshot (see section 4). Tokens are stored server-side and are never shown in the browser.
• Session: a random session ID in a secure, HTTP-only cookie, valid for 30 days.
• Filter names and descriptions: the plain-language names you (or the assistant) give each filter. Gmail cannot store these, so we keep them keyed to the filter's Gmail ID.
• Counts and history: daily totals for your mailbox (messages, unread, inbox, spam) and per label, plus cached "how many messages match" counts per filter. These are numbers only; no message content.
• Suggestions: the filter suggestions the assistant produced for you, along with the search parameters you chose and summary statistics. Suggestions describe senders, subjects and patterns, so they can include email addresses and subject fragments from the sampled headers.
• Prompt customisations: any edits you make to the assistant's prompts in Settings.

We do not store copies of your email messages, message bodies or attachments.

3. How we use the assistant (AI)

Two features use a large language model: writing a filter from a sentence you type, and generating suggestions. For suggestions, the sampled message headers and snippets described in section 1 are sent to the model provider (Anthropic or OpenAI) through Cloudflare AI Gateway, together with your label names and your prompt settings. The model's answer is validated and stored as your suggestions. These providers process the data only to return a response to us; under their API terms it is not used to train their models. Model requests are not made in the background — only when you use these features.

4. Background processing

Once a day the Service uses your stored tokens to record the mailbox and label counts described in section 2 so the history charts keep filling in. This job reads counts only. It can also assign names to filters that still lack one. You can stop all background processing at any time by disconnecting (section 7).

5. Google API Services User Data Policy (Limited Use)

Easy Email Filters' 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. In particular:

• We use Google user data only to provide and improve the user-facing features described above.
• We do not transfer Google user data to others except as needed to provide those features (the infrastructure and AI providers in section 6), to comply with law, or as part of a merger or acquisition with notice to you.
• We do not use Google user data for advertising, and we do not sell it.
• No human reads your Google user data unless you give explicit permission for a specific support request, it is required for security or legal reasons, or it has been aggregated and anonymised.
• We do not use Google user data to develop, improve or train generalised artificial intelligence or machine learning models.

6. Who else processes your data

• Google — the Gmail and sign-in APIs, under Google's Privacy Policy.
• Cloudflare — hosts the application, database and AI Gateway. Data is encrypted in transit (HTTPS) and at rest.
• Anthropic and OpenAI — language-model providers for the assistant features, receiving only the data described in section 3.

We do not sell, rent or trade your personal information, and we do not share it with advertisers or data brokers. We may disclose data if required by law or to protect the rights, property or safety of the Service, our users or the public.

7. Retention and deletion

• Your data is kept while your account is connected.
• Disconnect & erase in Settings revokes our access with Google and permanently deletes your account record, tokens, sessions, filter names, counts, history, suggestions and prompt edits. This happens immediately.
• Individual suggestions can be deleted from the Suggestions page at any time.
• You can also revoke access from your Google Account permissions page. The Service will then be unable to read anything further; email privacy@easyemailfilters.com and we will delete the remaining stored data within 30 days.
• Sessions expire after 30 days of inactivity.

8. Security

All traffic uses HTTPS. OAuth uses PKCE and signed state tokens. Session cookies are HTTP-only, Secure and SameSite. Access to the production database is limited to the operator of the Service. No method of transmission or storage is perfectly secure, so we cannot guarantee absolute security, and you remain responsible for keeping your Google account credentials safe.

9. Your rights

Depending on where you live you may have rights to access, correct, export or delete your personal data, or to object to or restrict its processing. Most of these you can exercise yourself: everything we hold is visible in the app, and Disconnect & erase deletes it. For anything else, email privacy@easyemailfilters.com.

10. Children

The Service is not directed to children under 13 (or the age of digital consent where you live) and we do not knowingly collect their data. If you believe a child has connected an account, contact us and we will delete it.

11. Changes to this policy

We may update this policy as the Service changes. We will update the effective date above when we do. Continued use after a change means you accept the updated policy.

12. Contact

Easy Email Filters
United States
Privacy questions: privacy@easyemailfilters.com
Support: support@easyemailfilters.com