Privacy

Signing in. TimeSeek uses Google Sign-In to identify your account. It receives your name, email address and profile picture, and never sees your password.

Your calendars. Connecting Google Calendar is a separate, optional step — everything else works without it. With it connected, TimeSeek reads the list of your calendars so you can map each one to an area of life, and reads the events in them so they can appear alongside your day. Events are fetched when a page needs them and held briefly in memory; they are never written into TimeSeek's database.

Google data is used only to show you your own information inside your own dashboard. It is never sold, never shared, never used for advertising, and never used to train a model. You can disconnect at any time from Settings, which deletes the stored credentials immediately, or revoke access from your Google account permissions.

Your account. When you sign in with Google, TimeSeek stores the email address, name and profile picture URL Google returns, and creates a session. It never sees or stores your Google password.

What you put in it. Tasks, projects, areas, notes, habits and their check-ins, deadlines, people and the interactions you log, conversations with Helper, and any files you attach.

Calendar data, if you connect it. Connecting Google Calendar is a separate, optional step. TimeSeek stores the list of your calendars and which life area you map each one to. Events themselves are fetched when a page needs them and held in memory for five minutes — they are never written to the database.

Credentials, encrypted. Google Calendar tokens and your OpenRouter API key, if you add one, are encrypted before they are stored and are only ever decrypted on the server. They are never sent to your browser and never appear in an API response.

Running the product for you, and nothing else: showing your day, computing streaks, answering Helper questions about your own data. No profiling, no advertising, no third-party analytics.

TimeSeek runs on Vercel (hosting), stores data in a Neon PostgreSQL database, and keeps attached files in Vercel Blob storage. Those providers process data on TimeSeek's behalf in order to run it.

Google is used for sign-in, and for reading your calendars if you connect them. TimeSeek's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is used only to show your events inside your own dashboard; it is never transferred to anyone else, used for advertising, or read by a human.

Helper is optional. If you use it, the messages you send and the relevant parts of your data are sent to OpenRouter and on to the model you have chosen, in order to produce a reply. If you never open Helper, nothing leaves for a model provider.

Your data stays until you delete it. Deleting something in the app deletes the record; disconnecting Google Calendar deletes the stored tokens and calendar mappings immediately.

You can ask for your whole account and everything in it to be deleted by writing to jawilliams88@gmail.com. You can also revoke TimeSeek's access at any time from your Google account permissions, which stops any further calendar access straight away.

Sessions are HTTP-only cookies checked against the database on every request, so access can be revoked server-side. Every record is scoped to its owner, and stored credentials are encrypted with keys held only on the server. No system is perfect, and this one is small and personally run — please do not store anything you could not bear to lose.

If this policy changes in a way that affects what is collected or who it is shared with, the date at the top changes with it. Questions of any kind: jawilliams88@gmail.com.