Back to Dayglide

Dayglide · The details

Your life. Your information.

Privacy notice · Updated November 6, 2026

Dayglide, provided by Badger House Productions, LLC (operated by Kevin Gary), helps you plan and manage Tasks, Efforts & Events, Habits, Goals, and Areas. This page explains how the web and native apps use the information you choose to bring into them.

What Dayglide collects, why, and who receives it

This is the plain summary. The sections after it give the details for each part.

What we collect, and how

  • Your account: your name, your email address and your sign-in identifier. You give us these when you sign up, directly or through Apple or Google.
  • What you put in Dayglide: your tasks, schedule, habits, goals, Areas, notes, reviews and Memory, your conversations with Glider and your quick updates. We collect these as you type or say them.
  • Calendars you choose: the names, titles, times and details of events on the calendars you connect or select on your iPhone. Dayglide only reads them.
  • Speech, if you talk to Glider: on the iPhone, Apple's speech recognition turns your voice into words, and Dayglide receives only the words. On the web and in the Mac app, once you allow it, your speech goes straight to Deepgram to be turned into words.
  • Purchases: your plan, its renewal status, and transaction references and amounts from Apple or Stripe. We never receive your full card number.
  • Device and app details: your time zone, the app version, a push token if you allow notifications, and error reports. Product analytics are collected only under the choices described below.

How we use it

To run your account and keep your devices in step. To have Glider answer you and plan with you. To send the reminders and emails described below. To take payments and unlock your plan. To give support, keep Dayglide secure and fix what breaks. And, under the choices described below, to measure how Dayglide is used and, on the website only, which ads bring people to it.

AI: what goes to Anthropic, and when

Anthropic runs the AI behind Glider. When you ask Glider something, Dayglide sends your words through its own server to Anthropic, with past messages in the conversation and the parts of your account the answer needs: tasks, schedule, habits, goals, Areas, notes, Memory, recent quick updates, and the titles and times of your calendar events. Anthropic returns the answer. This covers Glider's conversations, quick updates, Design your week and setup, refining a day plan, and reflecting in Review.

In the iPhone and Mac apps, nothing goes to Anthropic without your permission. A screen names Anthropic and says what is sent before anything leaves your device. Dayglide is built around Glider and requires this permission to continue. If you choose Not now or withdraw permission, setup and the workspace stay paused. You can review permission again, manage your account and subscription, export or request your data, sign out, or delete your account. That permission belongs to your account on that device, so a new device or a fresh install asks again. You can withdraw it at any time: in Settings → Glider on the iPhone, and in Settings → Privacy on the Mac. On the web, you start each request by sending it, and you can turn cloud AI off in Settings → Privacy. Dayglide sends nothing to Anthropic on its own: no AI writes our emails, and nothing runs in the background.

If you connect another AI app to your account in Settings → Connectors, such as Claude, ChatGPT or Gemini, that app reads and changes your tasks, schedule, habits, goals, Areas and Memory as you authorize it, under its own terms. You start that in the other app, and sign in and allow it there. Dayglide never connects one on its own. You can disconnect it in Settings → Connectors at any time, and turning cloud AI off in Settings → Privacy, on the web or the Mac, stops every connected app from reading or changing your account until you turn it back on.

Voice: what goes to Deepgram, and when

On the web and in the Mac app, talking to Glider sends what you say while the mic is on straight from your device to Deepgram, which turns it into words as you talk. Your Area names go with it, so it hears them correctly.

Nothing goes to Deepgram without your permission. The first time you press the mic on a device, a screen names Deepgram and says what is sent. If you choose Not now, nothing is sent, you can type instead, and the next press asks again. Your computer may then ask for the microphone too. Turning cloud AI off in Settings → Privacy stops the mic and withdraws this permission, so turning it back on asks again. If Deepgram can't connect, the speech service built into your browser listens instead, which may send your voice to its maker: Apple, in the Mac app.

Who receives your data, and what for

  • Anthropic runs Glider's AI: your words and the account context above, with your permission as described above.
  • Deepgram turns dictated speech into words on the web and in the Mac app, with your permission as described above. The iPhone app doesn't use it.
  • Apple processes purchases in the iPhone and Mac apps, delivers push notifications, handles Sign in with Apple, and recognizes speech on the iPhone, and in the Mac app when Deepgram can't connect.
  • Stripe processes payments on the web.
  • Clerk manages sign-in and account authentication.
  • Vercel hosts the website and the API that your data passes through.
  • Neon hosts the database that stores your account.
  • PostHog receives product analytics, under your choice, and anonymous error reports.
  • Resend delivers emails to you and feedback to our support inbox.
  • Google, Microsoft, Apple iCloud and other calendar providers supply the calendars you connect, and receive your request to read them.
  • Meta, Reddit and TikTok receive advertising measurement from our website under the choices described below, never from the iPhone or Mac app.
  • AI apps you connect, such as Claude, ChatGPT or Gemini, receive what you authorize them to read, as described above.

We give each provider only what its role needs, and only so it can do that job. Anthropic's commercial terms and data processing addendum bar it from training its models on what Dayglide sends and require it to keep that data confidential. Dayglide opts every dictation out of Deepgram's model-improvement program, which Deepgram's terms allow, so it isn't used to train Deepgram's models and Deepgram keeps the audio only as long as it takes to transcribe it. The other providers handle your data under their own business terms. We rely on these terms and settings to give your data the same protection this notice describes. AI apps you connect and calendar providers you choose follow their own terms, not this notice.

Optional analytics and advertising

Product analytics shows us how Dayglide is used, so we can see which parts help and fix what gets in the way. It is first-party: PostHog processes it only for Dayglide, and we don't use it for advertising or sell it. When it is on, PostHog keeps a random identifier in a Dayglide cookie in your browser and receives a pseudonymous account identifier, the surface and version you use, normalized screen names, setup progress, saved-action categories, AI and calendar operation outcomes and timings, quick update outcomes (such as saved, needs your decision, or no change made) and whether an update was typed or spoken, dictation outcomes (such as finished, denied, or unavailable), and broad acquisition categories (such as Google or Instagram). This includes the trial offer shown, signup steps and fixed error categories, and checkout returns; it never includes anything entered in a signup or payment form. For signed-in accounts with analytics on, this also includes trial/beta starts, verified purchase amounts and currency, refunds, renewal status, and content-free AI usage costs. It does not receive your task or calendar titles, planning text, the words of a quick update, dictated text or audio, AI conversations, credentials, or full page URLs. Automatic capture of workspace interactions is disabled. A separate, optional usability recording pilot is described below.

Optional masked usability recording pilot

Invited web users can separately agree to masked recordings of setup, Home, Schedule and Settings. PostHog processes the screen structure, clicks and scrolling for Dayglide's team, linked to the signed-in account. Text and inputs are masked and images are blocked before upload; planning content, calendar titles, conversations, audio, network bodies and console logs are not collected by this pilot. Recording pauses in hidden tabs and stops after twenty minutes per page session. Recordings are retained for up to 30 days. Product analytics and advertising choices do not enroll anyone. Stop future recording through the visible recording control or Settings. Request deletion of existing recordings at support@dayglide.ai. Native apps and the Mac host are not included in this web pilot.

In the United States, product analytics is on by default on dayglide.ai and in the web app. You can turn it off at any time in Settings → Privacy in the web app or with Your Privacy Choices at the bottom of the website, and it stops at once. A Global Privacy Control or Do Not Track signal from your browser turns the default off; that browser is measured only if you turn analytics on yourself. Everywhere else, including the EU, UK, EEA, Switzerland and Canada, and whenever we can't tell where you are, product analytics is off unless you turn it on. The iPhone app (Share product analytics in its Settings) and the Mac app ask first, everywhere. We use your approximate country, which our host Vercel derives from your IP address on each request, only to apply this default, and don't store it for this purpose. For a signed-in account that hasn't chosen, the default also covers the account reports above (such as trial starts and purchases) from its next visit in a US browser; never anything from before, and they stop when you turn analytics off or visit with Global Privacy Control. Your own choice, on or off, always wins over the default. The signed-in product analytics choice applies across your Dayglide devices; advertising choices remain separate and stay in the browser where you made them. If you decline analytics on the website, that choice also applies to an undecided account you use in the same browser. If you accept it on the website and sign up or sign in in the same browser within a day, it applies to that account too, and the app tells you so. Turning analytics off for your account also turns it off for the website in that browser. Enabling analytics does not export your earlier account or payment history. Required account, payment, tax and credit records are maintained separately to operate the service, regardless of this choice.

Reddit advertising measurement

When advertising measurement is allowed, our server tells Reddit about a new web account, completed setup, a card-confirmed trial and the first paid subscription. It shares a hashed account identifier, event time and unique event identifier, IP address, browser type and, when available, the Reddit ad-click identifier. Payments include their amount and currency. A trial is not counted as a payment. Reddit may connect this information with activity on Reddit to measure and optimize ads. The same advertising choices and opt-out signals described below apply. We never send names, emails, plans, calendar content or AI conversations to Reddit, and no Reddit script runs in the workspace or native apps. A first-party cookie keeps the ad-click identifier for up to 30 days across our website and sign-up. Checkout context is retained for at most 40 days; delivery retries retain only the permitted event, erase its payload after receipt and stop after seven days. Turning advertising off clears pending Reddit measurement in the signed-in account.

TikTok advertising measurement

When advertising measurement is allowed, our server tells TikTok about a new web account, completed setup, a card-confirmed trial and the first paid subscription. It shares a hashed account identifier, event time and unique event identifier, IP address, browser type and, when available, the TikTok ad-click identifier. Payments include their amount and currency. A trial is not counted as a payment. TikTok may connect this information with activity on TikTok to measure and optimize ads. The same advertising choices and opt-out signals described below apply. We never send names, emails, plans, calendar content or AI conversations to TikTok, and no TikTok script runs in the workspace or native apps. A first-party cookie keeps the ad-click identifier for up to 30 days across our website and sign-up. Checkout context is retained for at most 40 days; delivery retries retain only the permitted event, erase its payload after receipt and stop after seven days. Turning advertising off clears pending TikTok measurement in the signed-in account.

Advertising measurement (Meta)

What we share: visits to our public pages (dayglide.ai and join.dayglide.ai), a successful waitlist signup, and a new web account, together with your IP address, browser type, Meta cookies and ad-click identifiers, and for a new account a hashed account identifier. We send these from your browser (Meta Pixel) and from our server, with the same event identifier so each is counted once. For an account created on the web, our server alone also tells Meta when it finishes setup, when it starts a free week (a free trial), and when it makes its first payment, with that payment's amount and currency, the same hashed account identifier, and the network and browser details above. Each one follows the advertising choice you had in place at that moment: when you finished setup, or when you tapped to start your free week, for the free week and its first payment, even if you then paid in another browser. We save that choice, with your IP address, browser type and Meta cookies, only until the first payment's event is sent, and for no more than 40 days. Purchases in the iPhone and Mac apps are never sent to Meta. Why: to see which ads bring people to Dayglide and which of them go on to use it and pay. Meta may connect it with your Facebook or Instagram activity. Under some US state privacy laws this counts as sharing personal information for targeted advertising. We never send your name, email address, task or calendar content, prompts or responses, and Meta's script never runs inside your private workspace, sign-in pages or the native app. No advertising identifier or Meta tracking SDK is enabled in the native app.

In the United States this measurement is on by default. You can turn it off at any time with Your Privacy Choices at the bottom of dayglide.ai and join.dayglide.ai, or in Settings → Privacy in the app; it stops at once in that browser, for both browser and server reports. A Global Privacy Control or Do Not Track signal from your browser turns it off automatically. Everywhere else, including the EU, UK, EEA, Switzerland and Canada, and whenever we can't tell where you are, nothing is measured until you choose Allow. Your own choice, on or off, always wins over the default. We use your approximate country, which our host Vercel derives from your IP address on each request, to apply this default; advertising measurement doesn't store it. Advertising choices stay in the browser where you make them. Declining measurement never prevents signup or use. Turning off a choice stops future collection; information already received by a provider is subject to its retention and deletion practices.

Error diagnostics

So we can find and fix problems, when the website, the web app or our server hits an error, Dayglide sends an anonymous error report to PostHog. A report contains the type of error, its message with quoted text, addresses, numbers and identifiers removed, where in Dayglide's code it happened, the screen name, the app version, your browser and operating system, and for a failed request its route type, status, failure stage, duration, a fixed operation category and a request reference that lets us match it with our application or hosting platform logs. A rendering error may include up to twelve locations in our compiled app code, without component names or screen content. Calendar parsing failures use fixed categories, without calendar or event content. Where available, a fixed trial-offer label helps distinguish signup failures. Reports carry no account, device or advertising identifier, set no cookies, store nothing in your browser, and PostHog discards the IP address they arrive from. They never include your task or calendar titles, notes, planning text, the words of a quick update, AI conversations, email addresses, credentials or full page URLs. These operational reports are sent whether or not you enable product analytics.

To resolve Apple purchase problems, we separately keep a private support record linking the request reference to your Dayglide account, Apple's verified transaction reference, test or live payment environment, and a fixed verification result. It also records the app build and whether the app reports running on a simulator, iPhone or Mac. This record contains no signed receipt, account token or payment-card details. Account and transaction references are not sent to PostHog. Support records are removed when you delete your account and by our scheduled cleanup after 30 days; financial receipts follow the separate payment-record retention policy.

How you found Dayglide

So we know which of our own campaigns and pages bring people to Dayglide, we keep a short first-party note of how a new account arrived: the campaign labels in the link you followed (such as utm_source or utm_campaign), whether the ad was aimed at mobile or desktop, the device category used when your new account first reports its arrival, the website that referred you, which of our pages you landed on, and your approximate country when you signed up. A first-party cookie holds the labels for up to 90 days so they carry from dayglide.ai to sign-up; it contains no identifier. This note stays in our own records, is never shared with advertisers or analytics providers, does not depend on the choices above, and is deleted with your account.

Signup offer assignment

When a signup offer experiment is enabled, we store an opaque first-party cookie for up to 180 days to keep the offered trial consistent. We record the offer shown and, after signup, link the assignment to your account so we can honor its terms and compare signup and verified payment outcomes. We also compare the timing of saved organizer actions, without reading their text, to understand whether each offer leads to useful app use. The assignment record contains no card information or workspace content. Anonymous assignments are removed after 180 days; account deletion removes the linked offer record. Optional analytics remains subject to your separate analytics choice.

Feedback you send

When you send feedback, answer the check-in, or tell us why you are leaving (in the app or in the billing page when you cancel), we keep your words, any screenshot you attach, and the small context the form names: the screen you were on, the app version, your browser, window size and theme, your plan, and a reference to a recent error if there was one. It is stored with your account and sent to our support inbox through Resend so we can read it and reply, and we use it only to improve Dayglide. It never includes your tasks, calendar or plans unless you write them in yourself, is not shared with advertisers or analytics providers. The feedback copy in Dayglide is deleted with your account. For web cancellations, we also send your selected reasons and explanation to Stripe as cancellation details. One cancellation category stays with the payment records we keep for reconciliation.

We also count how many visits reach each step of the sign-up and sign-in pages, and whether they come from an app’s built-in browser (such as Instagram’s) and which kind of device. These are totals only: nothing that identifies you, your device or your account is sent or kept with them. If you use our link to open Dayglide in Safari or Chrome from an app’s browser, the link carries the same campaign labels, so your sign-up is still credited to the campaign, and, if you turned advertising measurement off there, that choice too.

Research beta (ended)

An invitation-only research beta, a separate explicit choice, ran until October 2026. It has ended: Dayglide no longer collects research copies of AI messages or app activity, and the research copies it held have been deleted. Content-free records of reviewer access are kept for up to one year.

Emails about your account

When you create an account, our support inbox receives an operational signup notice through Resend with your name, email, sign-in method and assigned trial offer. This is separate from optional analytics. If the trial offer has not yet been confirmed, temporary signup details wait for confirmation for up to seven days before being cleared. Notification counters are aggregate operational records and do not represent completed card checkouts or payments.

Dayglide emails your sign-in address, through Resend, to help you finish setup and get started, and about your trial: a welcome when you finish setup; a few reminders while setup is unfinished (about an hour after you sign up, then weekly for up to four weeks); if you designed your week and have not started your free week, a few notes over the next week, and if you tapped Start my free week and checkout did not open, one note about 15 minutes later (these, and the reminders while Design your week is unfinished, carry a sign-in link that works once, for 48 hours, and only for your account); help getting started if you have not used Dayglide yet; during your trial, a morning summary of your own plan for the day on days after one you did not use Dayglide; for a free week, a reminder 2 days before your first charge with its date and amount; once you have designed your week, a daily brief each morning that has something planned, at the hour your day starts; once you are set up, a weekly email the evening your week ends, with the week you had (what you marked done, habits logged, tasks finished, time by Area) and the week ahead; notes on your trial's progress and when it ends; and, after you have used the app beyond setup, one short feedback request. You can turn the daily brief and the weekly email off in Settings, under Notifications. You get at most one of these a day, except that the weekly email can arrive on the same day as that morning's daily brief, and the reminder before a first charge always goes out. To write them we read, at the moment of sending and only for that email, your time zone and week settings, the titles and times of your own blocks, tasks, habits, Areas and goals, and counts of what you did in Dayglide (such as tasks finished and requests to Glider). We never use your Memory, your conversations with Glider, events from connected calendars or anything about another person, and no AI writes these emails. Nothing from an email's content is stored; we keep a send receipt (which email, which day, when) to avoid duplicates and to count, without content, whether Dayglide was used in the two days after an email. Every email except the setup welcome and the reminder before a first charge has a one-click unsubscribe link, or write to support@dayglide.ai to stop them. When you open one of their links while signed in, we note that the email was used, only to count which emails help. Our email provider, Resend, also records whether an email was opened, using a small image in the email, and which of its links were clicked, by sending the links through links.dayglide.ai on the way to their destination. We use these counts only to check that emails arrive and to see which ones help. Some mail apps load images automatically, so a recorded open is not always a read; blocking remote images in your mail app stops open recording. We also note whether you started setup on a phone or a computer, when you finish the phone part, and when you next use Dayglide on a computer (from your browser type), to choose the right reminders and to see where setup gets stuck. These notes are deleted with your account.

Information you save

Dayglide stores your account identity, the objects and notes you create, Habit entries, preferences, and change history so your workspace can load again and your changes can sync. Each quick update is kept as a record of your words, what was saved or not changed, and Glider's answer, so its receipt and Undo work on every device. When you sign in to the same Clerk account, the web, iPhone, and Mac apps use a shared server-side workspace. The apps also keep local preferences and cached data.

Calendar connections are optional and read-only

Connecting Google Calendar, Outlook/Microsoft 365, iCloud, CalDAV, or an iCalendar subscription lets Dayglide read your calendar list and events from the calendars you select. This includes calendar names and identifiers, event titles, start and end times, all-day and busy/free status, locations, and links to the original events. Dayglide displays these commitments alongside your plan and protects busy time when suggesting where work can fit.

Dayglide does not create, edit, RSVP to, or delete connected calendar events. It stores your calendar selections, account identifier, sync time, and encrypted authorization tokens, app-specific passwords, or private subscription links on its server. Event results are fetched for the requested period and kept temporarily in the active browser session; they are not copied into the saved Task or Block tables.

Apple app-specific passwords can authorize access to iCloud Mail, Contacts, and Calendar; they are not calendar-only credentials. Dayglide uses the password only to read calendars. Create a dedicated password for Dayglide and revoke it in your Apple Account’s Sign-In and Security settings when you no longer need it. Disconnecting removes Dayglide’s stored copy; it does not revoke the password at Apple. See Apple’s app-specific password instructions.

The native app and Apple services

The current iPhone app keeps an account-specific copy of your workspace and unsent changes on your device. It sends those changes to your shared account when it can connect. Earlier native versions used a separate local or iCloud workspace. That older data stays separate and is not automatically uploaded or merged when you sign in. Clerk manages your account sign-in. When you use Apple or Google to sign in, the provider shares your account identifier and the profile information you choose to share.

Native AI can run on your device or use the configured cloud service, depending on your AI setting, device support, and subscription. Auto mode can fall back to cloud processing when on-device processing is unavailable. The on-device setting keeps supported native AI planning on the device; Quick update and other cloud-only features still request separate permission before cloud AI is used. Before the first cloud AI request, Dayglide asks whether it may send your message and relevant planning or selected calendar context through Dayglide to Anthropic. A decline stops the request, including its pricing quote. This permission is separate from analytics and advertising, applies to the signed-in account on that device, and can be withdrawn in Settings. A different account or fresh installation asks again.

Calendar access, microphone and speech recognition, and notifications are optional system permissions. The iPhone app reads the device calendars you select to display commitments and plan around them. Its dictation uses Apple's speech recognition, on the device when your language supports it and otherwise Apple's servers; sending the resulting message can include that text in an AI request. The Mac app's dictation goes to Deepgram with your permission, as described above, and macOS asks for the microphone the first time. Apple processes subscription purchases; Dayglide uses purchase and entitlement information to enable paid features and does not receive your payment-card details. You can manage these permissions and subscriptions in your device or Apple account settings.

AI planning and your choices

On the web, sending an AI request starts cloud processing without a separate permission dialog. Settings → Privacy names Anthropic, and you can turn cloud AI off there; that choice stops requests before their pricing estimate, and it stops dictation and connected AI apps too. The Mac app asks before its first cloud AI request, as described above. Turned off while signed in, cloud AI's off applies to your account in every browser and the Mac app; the iPhone app asks for its own permission. Analytics and advertising remain independent choices.

When you ask Dayglide to use AI, your request and relevant workspace context are sent to the configured AI service, currently Anthropic, to generate a response or proposed changes. When you ask AI to refine a day plan, that context can include the names and times of selected calendar events in the plan. When you send a quick update or plan with Glider, it can include the titles and times of your calendar events for today and tomorrow; a quick update does not store those events, and a saved answer that names one is stored without the event's name.

Quick updates save simple things you state directly (such as a task, a plan at a time you named, or time you report) right away, with Undo; bigger changes wait for your review. In Plan with Glider, proposals require your approval before they change your saved workspace.

On the web and in the Mac app, once you allow it, dictation streams your speech from your device directly to Deepgram, with your Area names, and Deepgram turns it into text as you talk. Dayglide opts out of Deepgram's model-improvement program, so Deepgram keeps the audio only as long as it takes to transcribe it. Dayglide never receives or stores your audio; it receives only the text you choose to send, and how many seconds you dictated, which count toward your Glider allowance. Where Deepgram isn't available, dictation uses the speech service built into your browser (in the Mac app, the system web view), which on some browsers sends your audio to the browser maker's servers.

Dayglide does not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Its use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

Who receives Google user data

Dayglide shares Google user data only as needed to provide the features you use, as described below. Connecting Google Calendar does not give these providers independent access to your Google account.

  • Vercel hosts Dayglide's website and API. Its servers process Google Calendar responses, connection details, and authorization credentials so Dayglide can retrieve and display the calendars and events you select.
  • Neon hosts Dayglide's database. It stores your connected Google account identifier, calendar list and selections, connection timestamps, and encrypted OAuth credentials. Calendar event results are fetched when needed rather than copied into the saved Task or Block tables.
  • Anthropic processes cloud AI requests. When you use AI planning features, relevant selected calendar event details, including titles and times, may be sent through Dayglide's API to Anthropic as planning context. Google authorization tokens are never included in AI requests. Displaying calendars alone does not send their contents to Anthropic.
  • Clerk manages Dayglide sign-in. If you choose Sign in with Google, Clerk processes the Google account identifier and profile information shared for sign-in. Dayglide does not send connected Google Calendar events or calendar authorization tokens to Clerk.

Google calendar contents and authorization credentials are not shared with PostHog, Meta, advertisers, data brokers, or information resellers. Optional analytics receives only the content-free operation information described above. We do not sell Google user data or transfer it for advertising, credit decisions, or training general-purpose AI or machine-learning models. Service providers process it for the specific Dayglide functions described here. Human access is limited to your explicit consent for specific data, a security investigation, or compliance with applicable law, consistent with Google's Limited Use requirements.

How we protect Google user data

  • Encryption in transit: the production website and API use HTTPS. Google authorization and Calendar API requests also use HTTPS to protect data while it travels between your device, Dayglide, and Google.
  • Encrypted credentials: Google access and refresh tokens are encrypted before being stored in the database, using AES-256-GCM. The encryption key is held in the server environment separately from the stored tokens, and encrypted values are bound to the Dayglide account that owns them. Tokens are not returned to the browser or native app, or included in analytics.
  • Account access controls: the server verifies your sign-in session and scopes calendar connections and requests to your Dayglide account. Calendar OAuth uses short-lived, single-use authorization state and PKCE to protect the connection flow. Dayglide requests read-only calendar permissions.
  • Limited storage and removal: event results are held temporarily for display and planning, while connection settings and encrypted credentials remain until you disconnect or request deletion. Disconnecting deletes the stored connection and credentials and requests revocation from Google. Saved AI conversations or approved plans can retain information you used in them until you remove that information, as explained below.

Services that help run the app

Vercel hosts the web app and API; Neon provides its database; Clerk provides account authentication; Anthropic processes AI requests; Deepgram turns dictated speech into text (Dayglide doesn't store the audio); PostHog provides product and error diagnostics; Resend delivers account emails to you and feedback to our support inbox; Stripe processes web payments and keeps the payment method for a free week started on the web, and may email you its own notice before the first charge; and Apple processes purchases in the iPhone and Mac apps. Dayglide never receives your full card number. They receive information needed for their roles. Calendar authorization tokens stay on the server, encrypted at rest, and are not sent to the browser or the AI service.

Disconnect, export, or remove information

You can change the selected calendars or disconnect in Settings → Calendar. Disconnecting removes the stored connection and tokens, clears the browser's calendar session, and, for Google connections, requests revocation from Google. You can also remove the app’s access directly in your Google Account connections. For Microsoft and app-password connections, also remove the application grant or app-specific password in the provider’s account settings to revoke provider-side access. Disconnecting leaves your original calendar events intact. Previously approved plans or AI conversations remain in Dayglide until you remove them.

Settings → Data provides export and data-management controls while your plan is active; otherwise, email us for a copy of your data. Where account deletion is enabled, it removes the live workspace and connected calendar credentials, then queues provider cleanup. Payment records required for reconciliation are retained separately. Apple subscriptions must be cancelled with Apple. Unsynced browser changes and native account caches can remain on other devices until their local app or browser data is removed. For account deletion, access questions, or help removing retained information, contact support@dayglide.ai. Operational backups may retain removed information until their normal replacement cycle; Dayglide does not use those copies to repopulate your active workspace.

Changes to this notice

This page will be updated when data practices change. A change to how connected calendar data is accessed or used will be disclosed before that new use and will request consent where required.