Privacy Policy

Last updated 27 October 2026. This page is the official privacy policy for dayclue.com.

Who we are

Dayclue is a browser app at https://dayclue.com that helps you search Google Calendar events you already have access to. It is operated by the publisher of this site.

What Dayclue does

When you choose Continue with Google, Dayclue asks Google for read-only access to your calendars and for your basic profile (name, email, and photo if Google provides them). Searches run in your browser against the Google Calendar API. Dayclue does not copy your events onto a Dayclue database.

Data we process

• Google account profile. Name, email, and avatar are requested so the app can show who is signed in. They are kept in this browser’s local storage until you sign out.
• Calendar metadata you select. Calendar names, IDs, and your include/exclude choices stay in local storage so the next visit can restore your scope.
• Search text and preferences. Recent queries, time range, theme, language, and display options stay in local storage on this device.
• Calendar event contents. Titles, times, locations, notes, and links are requested from Google only to show search results in this browser. They are not uploaded to Dayclue.
• Access tokens. Google access tokens are held in memory for the tab session. They are not written to cookies or local storage.
• Dayclue account record. When you sign in, Dayclue keeps a small account record on its server: your Google account ID, your email, and your plan or subscription status (with a Stripe customer ID if you subscribe). It holds no calendar data, searches, or Google access tokens.

How we protect your data

We treat your Google user data, and especially your calendar contents, as sensitive data. These are the safeguards Dayclue uses:

• Minimum access. Dayclue asks Google only for read-only calendar access and your basic profile. It cannot create, change, or delete your events.
• Calendar data never leaves your browser. Event contents go straight from Google to your browser to show results. They are not sent to, stored on, or logged by Dayclue’s servers or any third party.
• Encryption in transit. Every connection, between your browser and Dayclue, Google, and our service providers, uses HTTPS (TLS) encryption.
• Encryption at rest. The small account record described above is stored in Cloudflare D1, which encrypts stored data at rest. Diagnostics and support data are held by PostHog EU Cloud, which also encrypts data at rest.
• Short-lived tokens, kept in memory only. Google access tokens live only in the open tab’s memory, expire automatically, are never written to disk or sent to Dayclue’s servers, and are revoked with Google when you sign out.
• Verified sign-in and protected sessions. Dayclue’s server checks Google’s cryptographic signature on every sign-in. Your Dayclue session is a signed cookie marked HttpOnly, Secure, and SameSite, so page scripts cannot read it and other sites cannot reuse it. Sessions expire after 30 days of inactivity.
• Payments handled by Stripe. Card details are entered with Stripe and never reach Dayclue. Messages from Stripe are accepted only when their signature checks out.
• Secrets kept out of the code. Server keys are stored as encrypted secrets in Cloudflare, not in the app’s source code or the browser.
• Browser hardening. The site sends a strict Content Security Policy and other security headers that limit which servers the page can talk to and block it from being embedded by other sites.
• Data minimization in diagnostics. Diagnostics use an allowlist and redaction, as described below, so calendar data, search words, and tokens are never sent.
• Restricted access. Only Dayclue’s operator can access the hosting, database, and diagnostics accounts, and only to run, secure, and support the service. No one at Dayclue reads your calendar data.
• If something goes wrong. If we learn of a security incident affecting your data, we will act to contain it and notify affected users and authorities as the law requires.

What we do not collect or sell

Dayclue has no server-side calendar store and does not sell, rent, or disclose personal data for advertising. We do not use calendar contents, diagnostics, or support messages to train machine-learning models. Dayclue does not use Google Workspace API data, including Google Calendar data, to develop, improve, or train generalized AI and/or ML models. We do not send Google Calendar data, search words, Google profile data, access tokens, or Google API responses to PostHog.

Privacy-protected diagnostics

Dayclue uses privacy-protected diagnostics through PostHog Cloud EU to improve reliability. They are enabled by default and can be turned off any time in Privacy controls; a browser’s Do Not Track setting is also respected.

Diagnostics use a small allowlisted set of anonymous product signals and redacted browser errors. We do not send full URLs, search words, calendar names or IDs, event contents, account details, tokens, or user-entered text. Dayclue does not call PostHog’s identify() function or create a PostHog person profile for you.

Privacy-protected diagnostics can also help us understand technical issues in the app. Calendar content and form values remain protected, and diagnostics never start from a support request.

Support requests

Before opening the support form, Dayclue explains that the message is handled in its PostHog EU project. A request contains only what you deliberately provide in the form: a category, message, and optional reply email. You can separately choose to include limited technical context: app release, browser family, language, and the current Dayclue screen. Calendar data, searches, Google identity, tokens, and request bodies are not attached.

Please do not include calendar events, attendee lists, access tokens, or other sensitive information in a support request. PostHog Surveys are an intake channel, not a customer-support portal: they do not provide a public ticket-status page, attachments, or a guaranteed response time. Dayclue will not enable support intake in production until its 90-day support-retention process is verified. Once enabled, requests are intended to be deleted within 90 days after resolution unless a longer period is required for a legal claim, security investigation, or accounting record.

Where processing happens

The app is a static site hosted on Cloudflare. Cloudflare may process standard request data (such as IP address, user agent, and the page URL) to deliver the site and protect it. That is hosting traffic for the web app, not a copy of your calendar.

When diagnostics are enabled or you submit a support request, the relevant data is sent to PostHog’s EU Cloud service as a processor for Dayclue. Dayclue configures its PostHog project to anonymize IP addresses. Access to support responses and diagnostics is limited to people who need it to operate and support Dayclue.

Google processes sign-in and Calendar API requests under Google’s Privacy Policy. Dayclue’s use of Google user data is limited to providing calendar search in your browser and complies with the Google API Services User Data Policy, including Limited Use requirements: we do not transfer Google user data to third parties (except as needed to provide or improve the user-facing features, as required by law, or as part of a merger or acquisition with notice), we do not use it for advertising, and we do not allow humans to read it unless you give us permission for support, it is necessary for security, or we are required to by law.

Cookies and local storage

Dayclue does not set advertising cookies. Preferences, including your optional-diagnostics choice, use browser local storage keys prefixed with dayclue-. PostHog is loaded only after a relevant choice or an explicit request to open support, and Dayclue configures it for memory-only operation rather than a persistent analytics cookie. Clearing site data for dayclue.com removes local preferences; it does not erase a support request or already-submitted optional diagnostic data held by PostHog.

How long data stays

Profile, calendar choices, and search history remain on your device until you sign out, change them, or clear the site. Your Dayclue account record is kept while you use Dayclue; you can ask us to delete it through Help & support, and subscription records may be kept longer where accounting law requires. Tokens expire with the Google session or when you close the tab. Privacy-protected diagnostics are retained for no longer than 30 days where applicable. Dayclue will publish the confirmed retention schedule for analytics, sanitized error events, and support requests here once it has been verified with PostHog; Cloudflare request logs follow Cloudflare’s retention for the Worker.

Your choices

• Sign out in Dayclue to drop the in-memory token and the stored profile hint.
• Revoke access at any time in your Google Account permissions.
• Use Privacy controls to turn diagnostics off or change them at any time. Withdrawal stops future PostHog capture immediately in this browser.
• Clear this site’s data in your browser to delete local history and preferences.
• For an access, deletion, or objection request about diagnostics or a support message, use Help & support and choose the privacy category. Include the same optional reply email if you previously gave one so we can locate the request.

Children

Dayclue follows Google’s own age rule. It is not directed at children under 13, or under the minimum age to have your own Google account in your country if that is higher. Do not use it with a Google account managed for a child. If we learn that we hold an account record for a child below that age, we will delete it.

Changes

If this policy changes in a material way, we will update the date at the top of this page. Continued use after an update means you accept the revised policy.