Privacy Policy
Last updated: November 1, 2026
Calendar Clarity (formerly Calendar Color) is a Chrome extension that helps you focus on and organize your Google Calendar. It is operated by Human Quest (humanquest.net), which is the data controller for the purposes of this policy. The extension is built to be private by default: your settings live in your own browser, we do not run user accounts or a database of your calendar or settings, and the extension only talks to an outside service when you turn on a feature that needs one. If you choose to submit product feedback, we keep that submission privately as described below. This policy explains exactly what happens.
The short version
- Your settings are stored in your browser (and, if you use Chrome Sync, synced by Google under your own account). We never receive them.
- The extension does not track you, show ads, run analytics on your calendar, or sell or share your data.
- Two features reach the internet, and each is off until you use it: Event Actions, which talk to the Google Calendar API, and opening Spotify for focus music.
- Colors, Event Visibility, check-offs and the focus timer work inside the open Google Calendar tab and need no sign-in. Nothing from them is sent to us.
- When you use a Google Calendar feature, the extension talks to Google directly from your browser — those requests never pass through our servers.
- Our marketing website (this site) uses a privacy-friendly analytics tool to count visits; the extension itself does not.
- If you submit feedback, only the fields you review and send are stored; Calendar Clarity never attaches calendar contents automatically.
- Everything that leaves your browser travels over encrypted HTTPS, and there is no central database of your calendar or settings.
1. What we store, and where
Everything you configure — your color categories, color assignments, event visibility rules, saved workflows, focus-timer history, which events you've ticked done, and any resumable cross-calendar batch — is stored on your device using the browser's extension storage. If you enable Chrome Sync, Google syncs that data across your devices under your own Google account; if sync is off, it stays in local storage on that machine.
- We do not have a server that stores your settings, and we cannot read them.
- Uninstalling the extension removes its local data from that browser.
- You can clear your settings at any time from the extension.
2. Data security
The strongest protection for your calendar data is that we don't hold it. Calendar Clarity has no user accounts and no server that stores your calendar or settings, so there is no central database of that information for anyone to breach. Voluntary feedback is stored separately with restricted server-side access.
- Your settings stay in your own browser's extension storage, and — if you use Chrome Sync — in your own Google account. We never receive them.
- Whenever an opt-in feature does reach the internet, it does so over an encrypted HTTPS (TLS) connection: Google Calendar requests go directly from your browser to Google.
- Access to your Google Calendar uses a token you grant through Google's own sign-in screen. In Google Chrome, Chrome's identity system manages that token; in other browsers, the extension keeps it in its own session storage, which the browser clears when it closes, and the token expires after about an hour. It is never sent to or stored by us, and you can revoke it at any time at myaccount.google.com/permissions.
- We never store or log your calendar contents or settings on our side. A feedback submission contains only the fields you explicitly review and send.
3. Optional features that use the internet
These features are the only ones that send anything outside your browser. Each is opt-in: the extension asks for the relevant permission the first time you use it, and nothing is sent until you take an action.
Google Calendar Event Actions
- If you enable Event Actions (duplicate, split, spread, postpone, reschedule, extend), the extension uses the Google Calendar API with an access token you grant through Google's own sign-in screen. These features create, modify, and move real events in your Google Calendar, including the color an action sets on an event, only when you run them.
- For Multi-calendar destinations, the extension passively reads the exact source-calendar ID already rendered on the selected event and the calendar names, exact destination IDs, colors, visibility, and sections already rendered in the open Google Calendar tab's sidebar. It uses this information in your browser to route the requested event operation and show destination choices; it does not request separate Calendar List access. Known read-only system calendars are excluded, and Google's existing Events API checks a shared calendar's write access only when you confirm a copy.
- For a cross-calendar batch, the extension keeps a short-lived local checkpoint containing the source event ID, selected dates and destination IDs, action options, successes, and failures so you can resume interrupted work. Checkpoints are retained on that device for up to seven days. A bounded local audit keeps counts, status, generic safety warnings, and number of calendars; it excludes event titles and event IDs.
- These requests go directly from your browser to Google. They do not pass through, and are not logged by, our servers.
- In browsers other than Google Chrome (such as Edge, Brave or Vivaldi), Google's sign-in window returns to a page on this website,
calendarclarity.app/oauth/extension.html, which immediately hands the result to the extension inside your browser. The access token travels in the part of the address that browsers never send to a server, so our servers never see it, and that page runs no analytics. The extension also remembers, on your device only, which Google account you signed in with, so it can renew access without asking again. Turning Event Actions off deletes that record and any stored token. - We request Google Calendar access only when you first turn on Event Actions, and we ask only for permission to view and edit your events. The extension does not request access to your calendar settings.
- You can revoke this access at any time at myaccount.google.com/permissions.
Spotify
- If you choose to play focus music, the extension opens
open.spotify.comin a new browser tab. That is an ordinary link — the same as clicking through to Spotify yourself. - We do not embed a Spotify player, connect to your Spotify account, or send Spotify any of your data. Once you are on Spotify, Spotify's own privacy policy applies.
Colors (no sign-in needed)
- Colors are Google Calendar's own color labels. You create them in Google's Labels dialog, and the extension applies them through Google Calendar's own color menu in the open tab. Coloring needs no sign-in and no extra permission, and nothing goes anywhere except through Google Calendar itself, exactly as if you had picked the color by hand.
- The names, groups and order you give your colors, and settings such as hiding the calendar-color strip on colored events, are stored in your browser's extension storage like your other settings.
Focus and ambient sounds that play inside the extension are bundled files that run locally — they involve no network request.
4. Our website and voluntary feedback
This marketing website (the pages you are reading now) uses a privacy-friendly product-analytics tool, PostHog, to count page views and understand which pages are useful. This is standard website analytics and is entirely separate from the extension — it does not see your calendar, your settings, or anything inside the extension.
- We use it only in aggregate, to improve the site.
- The extension itself runs no analytics and sends us nothing about how you use it.
Feedback center
- The extension can prepare a feedback draft in the URL fragment of an ordinary link to this website. A fragment is not included in the initial web request; the page reads it locally, removes it from the address bar, and does not submit it until you click Send feedback.
- A submission may contain the feedback type, feature area, title, description, extension version, submission time and status, an optional email address when you consent to contact, and optional diagnostics you explicitly include.
- The diagnostic preview is limited to compatibility anchors, module states, action/auth result categories, counts and timestamps. It excludes event titles, guests, calendar IDs, URLs, account identifiers, OAuth tokens and raw error messages.
- Feedback is stored privately in Google Cloud Firestore. Browser clients cannot read the feedback collection; access is restricted to authorized Human Quest administrators using server-side credentials and the Firebase console.
- When enabled, optional screenshots, screen recordings, and voice notes are captured only after you choose them. Your browser may ask for one-time screen or microphone access; this does not change the extension's Google Calendar permissions. Captures can contain anything visible or audible in the source you choose, so review and remove sensitive details before sending.
- Captures remain in page memory until you send them, and are not saved to local storage. If you edit an image, only the finished image is uploaded. Uploaded captures use private Google Cloud storage accessible to authorized team members, with automatic deletion after 30 days (cloud deletion processing can take additional time). Unsubmitted uploads from interrupted submissions follow the same limit.
- When the private GitHub integration is enabled, your reviewed report text and references to private attachments may be copied to the team's private issue tracker. Access to an issue does not grant access to its attachments. Your contact email is not copied into the issue. Issue-tracker records may remain as part of development history; contact us to request deletion of a report.
- When the enhanced submission service is enabled, Cloudflare Turnstile checks for automated abuse. The check is verified by our server before accepting a submission. We do not send your feedback text, email, or captures to that check.
- The extension offers an optional “Keep my draft on this device” setting. It saves only the thought and selected feedback fields locally. Turning it off removes that quick draft, without changing other extension settings.
- The form is excluded from website autocapture, and the feedback body is not sent to PostHog. Pageview analytics use only the page path and query string, not the draft fragment.
- We retain a feedback submission for up to 12 months so we can triage, deduplicate and verify improvements, then delete it. A daily rotating one-way request fingerprint and count may be retained for up to two days solely to rate-limit spam; it is not attached to the feedback record.
- You can omit your email and submit anonymously. If you include an email, it is stored and used only when you check the box allowing us to contact you about that submission.
5. Google API Limited Use
Calendar Clarity's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, information obtained from your Google Calendar is used only to provide and improve the features you enable; it is never sold, never used for advertising, and never used to develop, improve, or train generalized or standalone AI or machine-learning models.
6. What we do not do
- No tracking, tracking pixels, or behavioral profiling in the extension.
- No advertising.
- No selling, renting, or sharing of your data with third parties for their own use.
- No user accounts and no central database of your calendar or settings. Only voluntary feedback is stored by us.
7. Permissions we request, and why
- Storage — to save your settings on your device and, optionally, via Chrome Sync.
- Access to the open Google Calendar tab — to apply your colors, visibility rules, check-offs and focus mode in the page. The extension runs only on
calendar.google.com. - Identity and Google Calendar access (optional) — requested only if you enable Event Actions, so the extension can act on your events through the Google Calendar API on your behalf. Multi-calendar routing uses the already-rendered selected event and Calendar sidebar and does not request another Google scope.
8. Third-party services
Depending on which features you use and how you reach us, your activity may involve these services, each governed by its own privacy policy:
- Google (Chrome Sync and the Google Calendar API) — policies.google.com/privacy.
- Spotify, if you open it — spotify.com/legal/privacy-policy.
- PostHog, which provides analytics for this website — posthog.com/privacy.
- Google Cloud / Firebase, which privately stores voluntary feedback and rate-limit metadata — policies.google.com/privacy.
9. Your rights, choices and data retention
Because we don't hold accounts or a database of your settings, most control sits with you directly:
- Uninstall the extension to remove its local data from that browser.
- Turn Chrome Sync off, or clear synced data, from your Google account.
- Revoke the extension's Google Calendar access at myaccount.google.com/permissions.
- Simply leave Event Actions off if you prefer nothing to leave your browser at all.
- Do not submit the feedback form if you do not want a feedback record stored. If you supplied an email, you can use it to ask us to locate, correct or delete that feedback.
- Depending on where you live, you may have rights to access, correct, or delete personal data we hold about you (for example, GDPR or CCPA rights). The opt-in features rely on your consent, which you can withdraw at any time by not using them. To make a request, email us at the address below and we'll respond within a reasonable time.
10. Children's privacy
Calendar Clarity is a general-audience productivity tool and is not directed to children under 13. We do not knowingly collect personal information from children.
11. Updates to this policy
We may update this policy to reflect changes to the extension or for legal or operational reasons. Material changes will be noted here with a new “Last updated” date and, where appropriate, on the Chrome Web Store listing.
12. Contact
Questions about this policy or your data? Reach us at:
- Email: info@humanquest.net