What we collect.
And what we don't.

Effective: 2026-05-21 · Last updated: 2026-07-03

The 30-second version

Your calendars are read and merged on your device, not in our cloud; the only network call a paid plan makes to us is a license check. Your events are stored on your device, not sent to our servers, not shared with anyone, and we have no way to read them.
We don't run analytics. No Google Analytics, no Mixpanel, no PostHog, no Segment, no tracking pixels of any kind on the marketing site or inside the extension.
We don't sell anything to anyone. Not your data, not your email, not aggregate statistics. We're funded by the price you pay, not by selling you out.
The only things we receive are the email and payment info you give us to subscribe, and license and trial checks that carry your account email and license status. No calendar data attached. The free tier with no account makes zero requests to us.
Tab Sync happens 100% in your browser. The events read from your Outlook / Google / corporate calendar tab stay on your computer, not in our cloud.
Want the deep dive? The security page shows exactly what crosses the network, what every permission does, and how to verify all of it yourself in DevTools.

1. What we collect

1.1 Account & payment

If you sign in to start a trial or subscribe to a paid plan, we collect:

Your email address (so we can deliver receipts and recover your license)
Your payment method, stored and processed by Stripe - we never see your full card number
The plan you're on (Pro, Premium, or Team, billed monthly or annually) and renewal dates

That's it. We do not collect your name, address, phone number, employer, or any other personal information unless you voluntarily provide it (for example, by emailing us for support). We do not store IP addresses; see Section 5 for what our hosting providers may log in transit.

1.2 License and trial checks

On the free tier with no account, the extension makes no requests to our servers at all. If you start a trial or subscribe, the extension periodically makes an HTTPS request to our license server to verify your subscription or trial is active. This request contains your account email and your license status: no calendar data, no event titles, no tab URLs, no browser fingerprint. The server's response is your license validity and tier. Like any web request, it passes through our hosting infrastructure, which may log standard request metadata (IP, user-agent, timestamps) in transit. The security page documents every network call the extension can make.

1.3 Crash & error reports

We do not collect crash reports automatically. If you choose to email us a bug report, you may voluntarily include screenshots, console logs, or stack traces - we only see what you choose to send.

1.4 What we explicitly do NOT collect

Your calendar events (titles, times, attendees, locations, descriptions)
Which websites you visit
Which browser tabs you have open
Which calendars you've added to the extension
How often you use the extension or which features
Your IP address or geographic location. We do not collect or store these; Cloudflare, which serves our website, and Supabase, which serves the license-check API, may log standard request metadata in transit, as covered in Section 5.
Browser fingerprints, device IDs, or any other identifier beyond your license key

2. How browser Tab Sync works

Tab Sync is the killer feature, and it's worth explaining carefully so you know exactly what it does and does not do.

When you point the extension at a browser tab (for example, your Outlook Web Access tab), it reads the visible event data from the page's accessibility tree - the same data your screen reader sees - entirely on your local machine. The events are stored on your device in chrome.storage.local and localStorage. They are not transmitted anywhere.

If you close the tab, the extension can briefly reopen the same URL in a background tab, read the events, and close it. This still happens 100% locally. The extension only ever opens URLs you added yourself. Your calendar provider sees a normal page load from your browser (the same thing it sees when you open the tab) and that's the only network signal generated.

We do not automate logging in for you, we do not store or transmit credentials, and we do not maintain server-side sessions. If your tab's login session expires, you'll see a "Needs sign-in" status indicator and a button to re-authenticate yourself.

3. Local storage

Everything the extension knows about you lives on your physical device, in your browser's extension storage (chrome.storage.local) and localStorage:

The list of calendars you've added (names, colors, feed URLs)
Events fetched from ICS feeds or synced from browser tabs
Manual events you've created
Your theme and privacy-mode preferences
Multi-timezone clock settings

This data persists across browser restarts but is tied to your specific browser profile on your specific device. Uninstalling the extension deletes it. Clearing the extension's stored data from your browser's settings also deletes it.

4. End-to-end encrypted sync (planned, not yet shipped)

When device sync ships, your calendar data will be encrypted on your device before upload using AES-256-GCM with a key derived from a sync passphrase you generate. The encryption key is never transmitted to us. Our servers receive only opaque ciphertext blobs that we are mathematically incapable of decrypting.

This is the same architecture used by 1Password, Bitwarden, Standard Notes, and Obsidian Sync. If you lose your sync passphrase, your synced data is unrecoverable - we cannot reset it for you because we don't have it.

5. Third-party services

We use the minimum third-party services required to operate:

Stripe - processes payments. Stripe sees your card info; we don't. Stripe's privacy policy.
Supabase - runs our backend: sign-in, license and trial records, and the license-check API (Edge Functions). It processes your account email and license status, nothing else. No calendar data reaches it. Supabase's privacy policy.
Resend - delivers the license email when you purchase. It sees your account email only. Resend's privacy policy.
Cloudflare - hosts our website. Cloudflare may log standard HTTP request metadata (IP, user-agent, timestamps) in transit as part of normal CDN operation. Cloudflare's privacy policy.

That is the entire third-party list: Stripe, Supabase, Resend, and Cloudflare. Fonts are self-hosted, so the site makes no font request to Google or any other server. No advertising networks, no remarketing, no behavioral profiling.

6. Your rights (GDPR / CCPA)

You have the right to:

Access - request a copy of any data we have about you (email, subscription info)
Correct - update your email or subscription details
Delete - we'll erase your account and all associated subscription records on request
Port - export your subscription data in JSON
Object - we don't use your data for marketing automation, but if you ever want us to stop emailing you, we will

To exercise any of these rights, email [email protected] from the address tied to your account.

7. Data retention

We retain your account information for as long as your subscription is active, plus 12 months after cancellation for billing reconciliation. After that, the data is permanently deleted.

8. Changes to this policy

If we materially change this policy, we'll email you at the address tied to your account at least 30 days in advance. We won't expand what we collect without your explicit opt-in.

9. Contact

Questions, concerns, or rights requests: [email protected]

For general support: [email protected]