In short
We read subject / sender / date / snippet of unread threads in the window you pick — never full message bodies beyond the snippet Gmail already gives us.
That metadata is sent to Anthropic's Claude API to generate summaries and draft replies, then discarded — we don't keep a copy.
We never send replies or take actions in your inbox. Drafts are copy-paste only.
We don't sell data, run ads, or use your email content to train models.
Server-side, we keep only your email address and billing counters — free uses left, credits, subscription status.
Payment is handled entirely by Stripe. We never see or store your card details.
01What we read from Gmail
When you click Catch me up, the extension asks Gmail (via Google's own sign-in, chrome.identity) for the unread threads inside the time window you selected — 24 hours, 3 days, or 7 days. For each thread, it reads:
| Field | What it is |
|---|---|
| subject | The thread's subject line |
| from | Sender name/address |
| date | When the last message arrived |
| snippet | Gmail's own short preview text, not the full message body |
| messageCount | How many messages are in the thread |
This uses Gmail's format=metadata mode — a deliberately narrow read that avoids pulling full message content unless it's already surfaced in the snippet.
02How that data is used
The thread metadata above is sent, over HTTPS, to a small backend we run (a Cloudflare Worker), which forwards it to Anthropic's Claude API with one instruction: read these threads and return a priority ranking, a short summary per thread, and — for the higher-priority ones — a draft reply. The result is sent straight back to your browser and shown in the popup. Nothing about this step writes to your inbox or sends anything on your behalf.
Catch Up's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
03What we store
Two different places hold data, and they hold very different things:
On our server
Billing record
Keyed to your email: free catch-ups used this month, purchased credits, subscription status, and a Stripe customer ID. That's the entire row — no thread subjects, senders, summaries, or draft replies are ever written to this database.
On your device
Last result cache
The most recent catch-up result is cached in chrome.storage.local so it's still there if you close and reopen the popup. It lives only in your browser, is never uploaded anywhere by us, and clears when you remove the extension.
05Retention & deletion
- Thread content (subjects, snippets, summaries, drafts) is never persisted server-side — it exists only for the seconds it takes to generate your digest.
- Your billing record is kept for as long as you use the extension, so your free allowance and credits carry over correctly month to month.
- You can ask us to delete your billing record at any time — email george@gezerlis.gr. Once deleted, any unused credits or subscription can't be restored, so we'll confirm before removing anything tied to an active subscription.
- Uninstalling the extension clears the on-device cache immediately.
06Your rights
If you're in the EU/EEA or UK, you have rights under GDPR to access, correct, or delete the data we hold about you, and to object to or restrict its processing. Since the only personal data we hold is your email address and billing counters, most requests are quick to fulfill — email george@gezerlis.gr and we'll respond within a reasonable time. Our legal basis for processing is performance of the service you've asked for (providing catch-ups, tracking your paid entitlements) and our legitimate interest in preventing abuse of free usage. If you're not satisfied with how we handle a request, you also have the right to lodge a complaint with your local data protection authority.
International transfers. Google, Anthropic, Stripe, and Cloudflare each process data outside the EEA (primarily the United States) as part of providing their services to us. We rely on the safeguards each of them offers — Standard Contractual Clauses and/or their own certified compliance programs — rather than transferring data ourselves outside those relationships.
07Security
Requests are authenticated using your real Google identity, not a client-supplied claim. Payment webhooks are verified against Stripe's signature before anything is credited to an account, and each spend is applied atomically so concurrent requests can't double-spend the same credit. All traffic runs over HTTPS.
08Children
Catch Up is not directed at children and isn't intended for use by anyone under 16. We don't knowingly collect data from children.
09Changes to this policy
If this policy changes in a material way, we'll update the effective date above and note the change in the extension's release notes. Continuing to use Catch Up after an update means you accept the revised policy.