Tide is a fast, keyboard-first calendar client for Google Calendar, available at tide.naklitechie.com. This policy explains what data Tide accesses, where it goes, and what it does not do. Tide is deliberately minimal: it keeps as little of your data as possible, and most of your data never touches Tide's servers at all.
When you connect a Google account, Tide requests only the scopes it needs to be a calendar client:
calendar.events, calendar.readonly): to show your calendars
and events and to let you create or edit events.openid, email): your email,
name, and profile picture, used to label the connected account and to associate your
Tide notes and preferences with you.You can connect more than one Google account; each is requested with the same scopes.
Your Google sign-in tokens stay in your browser. Sign-in uses Google's standard OAuth flow. The one-time exchange of the sign-in code for tokens is performed by Tide's server so that Google's application secret is never exposed to your browser — but the resulting access and refresh tokens are returned to your browser and stored only there (in your browser's local IndexedDB storage). Tide's server does not retain them.
Your calendar contents never touch Tide's servers. Calendar and event data is fetched directly between your browser and Google's API. Tide's servers do not receive, process, or store your events, attendees, or calendar contents.
Notes and preferences are stored by Tide. Notes you write inside Tide (the scratchpad, per-day notes, and private notes you add to events) and your display preferences (calendar colours, which calendars are shown) are stored in Cloudflare Workers KV, associated with your Google account identifier so that they are available to you across your devices. These are the only user data Tide stores on its servers. Notes on events you can edit in Google are also written into the Google event itself, at your action.
Tide's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Tide uses Google user data only to provide and improve the calendar features you see, and does not transfer or use it for advertising, credit, or any purpose beyond those user-facing features.
All traffic is served over HTTPS. Sign-in tokens are kept in your browser rather than on Tide's servers, and stored notes and preferences are isolated per Google account so that one user cannot access another's data.
If this policy changes, the "last updated" date above will change. Material changes will be reflected here before they take effect.
Questions, or a request to delete your data: use our contact form, or email support@naklitechie.com.