Privacy Policy
Effective 2026-10-26
Timepoint AI ("we", "us") runs timepointai.com and app.timepointai.com. This policy says what we collect, why, and what you control.
1. What we collect
- Account: your email address and the identifier from the sign-in provider you choose (GitHub or email link).
- What you ask Timepoint to run: meetings you preview, outcomes you pin, the outcome you record afterwards, and the results.
- Calendar data, only if you connect Google Calendar: the title, time, length, description, location and attendees (names and email addresses) of the events on your primary calendar that Timepoint lists for you.
- Payments: handled by Stripe. We never see your full card number.
- Usage: pages viewed and buttons clicked (PostHog), errors, and approximate country from your IP address.
2. Meetings, pins and records are private
Everything you run about your own meetings and goals is private to your account by default. It is never published, never shown on this site, and never used as public content. Attendees are people who did not sign up, so their names never appear on any public page or share card. If you share your own route card, attendees are reduced to roles.
3. Google user data
If you connect Google Calendar, Timepoint requests read-only access to your calendar events. It never creates, changes or deletes an event. We use that data only to show you your meetings and build the private meeting previews you ask for. If you use Trajectory, Timepoint also reads your past events for the period you choose and keeps only hours-per-category totals, never event titles or attendees. We do not sell Google user data, use it for advertising, or let people read it except where you ask us to, where security requires it, or where the law requires it.
AI and machine learning. Timepoint does not use Google user data, or anything derived from it, to create, train or improve AI or machine-learning models, its own or anyone else's. To build a preview you ask for, Timepoint sends the details that preview needs to the AI model providers that run it, through OpenRouter, and uses their answers only for your preview. Timepoint asks OpenRouter to route these requests only to providers that do not collect or train on them, and never to free endpoints. What is sent depends on where you start. From the Meetings form in the app, it is the meeting as the form holds it when you run it: the title, time, length, agenda (the event's description and location) and the attendees, including any names you leave in the form. From an AI assistant or the API (preview_meeting), it is the title, time, attendee roles (never names) and at most the first 120 characters of the description. Trajectory's totals are computed by Timepoint without any model.
What we keep, and disconnecting. So that a preview can start from an event you pick, Timepoint keeps a copy of the events it lists for you: each event's Google event ID, title, start time, length and description, and its attendee display names and whether each is the organizer or you (never email addresses). The copy does not include the event's location. A copy is deleted 30 days after the last calendar read that listed it. You can disconnect at any time with Disconnect Google Calendar on the Meetings page in the app. Disconnecting there revokes Timepoint's access at Google, erases the stored access token, and deletes every saved calendar event copy and any Trajectory calendar summaries. You can also remove Timepoint at your Google Account's third-party access page (myaccount.google.com/permissions); that stops further reads, and the saved copies are then deleted by the 30-day rule. A preview you already ran keeps its own copy of that meeting with your private runs (section 9), and attendees you chose to save as contacts stay in your private contacts, with their names and email addresses, until you delete them or your account.
Limited Use. Timepoint's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
4. How we use data
- To run the simulations and walk-backs you ask for, through model providers routed by OpenRouter. Your private runs go only to the providers that run them, and Timepoint asks OpenRouter to use only providers that do not collect or train on them, never free endpoints. Google calendar data is never used to train models (section 3).
- To sign you in, meter credits and take payment.
- To keep the service working and stop abuse.
5. Sealed forecasts
When a forecast is sealed, we publish a cryptographic hash and its OpenTimestamps proof. For a private forecast, only the hash is public; its content stays private.
6. Who else handles data
Fly.io (hosting and databases), Stripe (payments), OpenRouter and the model providers it routes to (running your requests), Google (calendar, if you connect it), GitHub (sign-in, if you use it), email delivery for sign-in links, and PostHog (product analytics). We do not sell personal data or share it for advertising.
7. Cookies
This site (timepointai.com) sets no sign-in cookies. PostHog analytics may set a first-party cookie. The app at app.timepointai.com uses a session cookie to keep you signed in.
8. Your choices
You can ask for a copy of your data, or for it to be corrected or deleted, by emailing privacy@timepointai.com. Deleting your account deletes your meetings, pins and records. Residents of the EU, UK and California have the additional rights their laws give them.
9. Retention
We keep account data and private runs while your account is open, and delete them when you delete it, except billing records we must keep by law. Saved calendar event copies are deleted 30 days after the last read that listed them, or at once when you disconnect Google Calendar in the app, which also deletes any Trajectory calendar summaries (section 3).
10. Children
Timepoint is not for children under 13, and we do not knowingly collect their data.
11. Changes and contact
We will post changes here with a new effective date. Questions: privacy@timepointai.com.
