Privacy Policy

Last updated 8 September 2026

Pensova schedules your work into your Google Calendar. To do that it has to read your calendars and write events to them. This page says exactly what it reads, what it keeps, and how to make it stop.

What Pensova asks Google for

Two Calendar permissions, and nothing else:

calendar.readonly: Lists the calendars you are subscribed to and reads the times you are busy. Needed because free time is not just about your primary calendar — a shared work calendar and a public-holiday calendar both occupy real time, and without this permission Pensova would book over them.
calendar.events: Creates, moves and deletes the events Pensova itself places. It only ever modifies events it created.

It does not ask for access to Gmail, contacts, Drive, or anything outside Calendar. Google shows you the full list before you approve it, and you can revoke it at any time from your Google account permissions page.

What is stored, and where

Your account: Email address and Google account id, so the app knows whose tasks are whose.
Your tasks: Whatever you type: title, how long it takes, deadline, priority, status, whether it repeats.
Scheduled blocks: The times Pensova chose and the id of the calendar event it created for each, so it can move or remove them later.
Drafts: Tasks proposed from your plain-words capture or pasted meeting notes, until you accept or dismiss them.
Your settings: Working hours and days, and which calendars count as conflicts.
Google access tokens: Needed to act on your calendar between visits. These live in a database table with row-level security enabled and no access policies at all, which means no signed-in user — including you — can read them through the application. Only the server itself can.

Your calendar events are not copied into our database. Pensova reads your availability from Google each time it plans, and forgets it. What it stores about your calendar is the busy pattern reduced to a short fingerprint, so a background job can tell whether anything changed since it last looked without re-reading everything. That fingerprint cannot be turned back into your events.

Data is held in Postgres at Supabase (United States) and the application runs on Vercel.

Plain-words capture and meeting notes

If you type a task in plain words — “deck for the board by Thursday, about two hours” — or paste meeting notes, that text is sent to Anthropic’s Claude API to be turned into structured drafts you then review. Only the text you typed or pasted is sent, together with your name and email so the model can tell which items are yours; your calendar is not. Anthropic does not train on API inputs.

The notes themselves are processed in memory and discarded: they are not stored, logged, or kept in any job queue. What is stored is the drafts that come back, until you accept or dismiss them. If you never use these features, nothing is ever sent.

Billing

Payment is handled by Stripe. Your card number and billing address go to Stripe and never touch Pensova’s servers. Pensova stores a copy of the subscription itself — plan, status, trial and renewal dates, and Stripe’s customer and subscription ids — so the app knows what you are entitled to without asking Stripe on every page.

Google user data, specifically

Pensova’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Concretely, Google Calendar data is used only to provide the scheduling you can see in the app. It is not used for advertising, not sold, not transferred to anyone else except as needed to run the service, and not read by a human except where you have asked for support in writing, or where the law requires it.

What is never done with it

It is not sold, rented, or licensed to anyone.
It is not used to target advertising.
It is not used to train machine-learning models.
It is not shared with third parties beyond the infrastructure named above, which processes it only to run the service.

Getting rid of it

Disconnecting Pensova in your Google account permissions revokes its access immediately; it can no longer read or change anything on your calendar. Events it already created stay on your calendar and are yours to keep or delete.

To delete the account itself and everything stored with it, email privacy@pensova.com from the address you signed up with. Deletion is permanent, covers tasks, blocks, drafts, settings, tokens and the subscription record, and is done within 30 days. This is currently a manual request rather than a button in the app — that is a gap, and it will become a button.

How long things are kept

Tasks, blocks and settings are kept until you delete them or the account. Access tokens are replaced each time they are refreshed and deleted outright when Google tells us the grant is gone. Server logs, which record request paths and errors but not calendar contents, are kept for up to 30 days by the providers above.

Changes, and getting in touch

Material changes to this policy will be reflected in the date at the top of this page, and anyone with an account will be emailed before they take effect. Questions go to privacy@pensova.com.