[ yourtime /// privacy policy ]

Privacy Policy

Last updated: July 6, 2026

yourtime is a calendar that shows you where your time actually goes. Doing that well means handling some genuinely personal data — your schedule, your screen activity, and (if you turn it on) transcripts of your meetings. This page explains exactly what we collect, why, and what we never do with it.

What we collect

Account. When you sign in with Google we receive your name, email address, and profile picture. We use these to identify your account and nothing else.

Calendar data. Events you create in yourtime, and — if you connect Google Calendar — the events we import on your behalf (titles, times, attendees, locations). Your ratings, tags, feelings, and written reflections are stored alongside them.

Screen activity. If you connect a computer or iPhone, the sync agent uploads spans of app usage: the app name, the window title, and the start and end time. No screenshots, no keystrokes, no content of what you were working on. Time when you are away from the keyboard or your screen is locked is excluded before anything leaves your device.

Meeting transcripts. If you install the recorder, audio from your meetings is transcribed in ~30-second chunks and the resulting text is attached to the calendar event. Audio is processed for transcription and is not stored; only the text transcript is kept. You are responsible for telling participants they are being recorded — consent laws apply where you live.

Bookings. When a guest books time with you, we store the name and (optional) email they enter, and the slot they picked.

Todos. If you connect a todo service (e.g. Todoist), we access your tasks to show them beside your calendar. We don't copy your task history to our servers beyond what's needed to display and sync them.

What we never do

We do not sell your data. We do not use it for advertising. We do not train AI models on it. No human at yourtime reads your calendar, activity, or transcripts except with your explicit permission to debug a problem you've reported.

Where it lives

Your data is stored in a Supabase (PostgreSQL) database hosted in Sydney, Australia, encrypted in transit and at rest. Access is enforced row-by-row at the database level: your data is readable only by your signed-in account. Availability you explicitly publish for booking (free/busy shape only — never event titles or attendees) is the single exception, since guests need it to book you.

A copy of your workspace also lives in your own browser (localStorage) so the app opens instantly and works offline.

Processors we rely on

We use a small number of infrastructure providers to run the service: Supabase (database, authentication), Google (sign-in and calendar sync, at your request), and a transcription provider (Groq or OpenRouter, only if you use the meeting recorder — audio chunks are sent for transcription and not retained by us). If you connect Todoist, your tasks flow through their API under their terms.

Google user data

yourtime's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Calendar data is used only to display and sync your calendar inside yourtime — never for advertising, never sold, never used to train models.

Your controls

You can disconnect Google Calendar, screen-time tracking, the recorder, or your todo service at any time from the app menu — each stops the corresponding data flow immediately. To delete your account and all synced data, email us and we'll remove it within 30 days. Local data can be cleared by clearing your browser storage.

Changes

If this policy changes in a way that matters, we'll say so in the app before the change takes effect.

Contact

Questions or deletion requests: hello@timegarden.ai