Privacy Policy

Last updated: September 2026

Summary

Read-only. Catnap reads your Google Calendar to work out how much of your time is work. It never creates, edits, or deletes anything in your calendar.
Never sold, never advertised, never used for training. Your calendar data, and everything Catnap works out from it, is used only to show you your own work report. It is not sold, not used for advertising, and never used to train any AI or machine learning model.
One outside AI service, and you can turn it off. To classify events as work or not work, Catnap sends a minimized part of each event to OpenAI, which does not use it for training. Every other analysis runs on Catnap's own servers, and you can turn the OpenAI step off entirely.
Protected everywhere it goes. Your data is encrypted in transit and at rest, kept on a private network, and limited to your own account. Calendar content, personal details and credentials are redacted from Catnap's logs and error reports.
Yours to remove. You can disconnect Google, delete everything Catnap has imported, or delete your account at any time from Settings.

The sections below give the full details.

What Catnap accesses

When you sign in with Google, Catnap requests read-only access to your Google Calendar: your calendar list, your events, and your calendar time zone setting. Catnap never requests write access to your Google Calendar, and never creates, edits, or deletes anything there.

What Catnap stores

Your calendar data. Event titles, times, locations, and attendee/organizer information, largely as Google returns it - this is what Catnap needs to build your work report.
What Catnap works out from it. Whether an event looks like work, and who or what it relates to (a client, employer, or job site).
Your corrections. Anything you explicitly correct always overrides what Catnap worked out, and is kept separately so it survives future re-imports.
Your Google authorization. The access credential that lets Catnap read your calendar on your behalf, stored encrypted.

How Catnap uses your data

Catnap uses your data only to show you your own work report and the events behind it. It is not used for advertising, not sold, not used to profile you for anyone else, and not combined with anyone else's data.

Who else receives your data

Your data is shared only with the services below, and only for the purpose described.

Google. Catnap communicates with Google's Calendar API to read your calendar, using the authorization you grant during sign-in.
OpenAI, for work/not-work classification only. Catnap sends a minimized part of your calendar data directly to OpenAI's API (api.openai.com) to help decide whether each event looks like work: event titles, timing, calendar names, basic event status fields, and attendee/organizer email domains (for example "example.com", never full email addresses). Event descriptions, locations, and full email addresses are never sent. You can turn this off, when choosing your calendars or later in Settings, and nothing is sent at all. See "AI and machine learning" below for how this data is handled.
Hosting. Catnap runs on Amazon Web Services, which hosts the application, its database, and its logs on Catnap's behalf.
Error monitoring. When something goes wrong, Catnap sends a technical error report to an error-monitoring service. These reports are redacted before they leave Catnap - see "Logs and error reports" below.

AI and machine learning

Catnap uses machine learning models only to interpret your own calendar for you. Google user data is never used to create, train, or improve Catnap's models or any foundational or general-purpose AI or machine learning model, whether as raw, aggregated, anonymized, or derived data.

Third-party AI provider (OpenAI). The work/not-work classification step described above calls OpenAI's API directly - not through an aggregator, gateway, or model hub. Under OpenAI's API terms, data sent through its API is not used to train OpenAI's models. Catnap sends each request with response storage turned off (store: false), so OpenAI does not keep the conversation for later use; OpenAI may still retain API traffic for a limited period (currently up to 30 days) solely for abuse and misuse monitoring, after which it is deleted.
Self-hosted models. Recognizing names in event text and deciding whether they refer to a client, employer, or job site uses open-source models (published on Hugging Face) that Catnap runs itself, offline, on its own servers. The model files are built into Catnap's software; your data is processed locally and is never sent to the models' authors, Hugging Face, or anyone else, for training or for any other purpose.
Your corrections stay yours. When you correct a classification, Catnap may include a few of your own recent corrections as examples in your own future classification requests. They are never used for anyone else and never used to train a model.

How Catnap protects your data

Everything derived from your calendar is treated as sensitive

Catnap applies the same protections to what it works out from your calendar - whether an event is work, who it relates to, your corrections, and your totals over time - as to the calendar itself. Patterns across many events can reveal things no single event says, such as an employer, a job search, or a medical routine, so none of this is treated as safe to log, analyze, or show to anyone merely because Catnap produced it rather than Google.

Limited to your own account. Every request for your data is limited to your own account, so one user cannot read another's data.
Minimal operator access. Catnap's diagnostic tools are built to show account and sync status rather than calendar content, and are restricted to named, individually authenticated staff, with every access logged. There is no way for staff to sign in as you or act on your behalf.
Calendar content is handled as untrusted. Events can be created by other people, so Catnap treats their text as potentially hostile wherever it is displayed or sent to an AI model, and never lets it run as code in your browser.
Least privilege and minimization. Catnap requests read-only calendar access, and sends outside services only the fields described in this policy.

Logs and error reports

Application logs. Catnap's log messages record identifiers and outcomes, not calendar content. Request details are filtered before they are written: calendar content, names, email addresses, search terms, and credentials are replaced with a redaction marker, and every log line is checked for Google credentials as a final safeguard. Logs are kept within Catnap's own hosting account for 180 days.
Error reports. Error reports never include request contents, cookies, or query strings, and pass through the same redaction as the logs before they are sent. They carry the technical details needed to fix a problem, not your calendar content.

Encryption and infrastructure

Encryption in transit. All connections to Catnap use HTTPS (TLS 1.2 or 1.3 only, with HSTS). Connections from Catnap to its database, to Google, and to OpenAI are also encrypted with TLS.
Encryption at rest. Catnap's database, server disks, and database backups are encrypted at rest (AES-256, managed by Amazon Web Services). Your Google access and refresh tokens are additionally encrypted within the application (AES-256-GCM) before they are stored.
Network isolation. The database sits on a private network and cannot be reached from the internet; it accepts only encrypted connections from Catnap's own servers.
Deletion that sticks. When you delete your data or your account, Catnap records the deletion separately from its backups, so that restoring a backup does not bring deleted data back.

How long Catnap keeps your data

Your data is kept for as long as your account is active. Disconnecting Google (see below) stops Catnap from reading your calendar further, but does not by itself delete anything already imported - that data is kept until you separately delete your imported data or delete your account, whichever you choose. Catnap does not currently apply a separate automatic expiration to calendar content beyond those actions.

Your controls

Catnap gives you several independent options, each doing exactly what it says:

Stop importing a specific calendar while keeping what's already imported.
Exclude a specific calendar from your reported work totals while still importing it for context.
Turn off work classification - nothing is sent to the AI provider, and you classify events yourself.
Disconnect Google entirely - revokes Catnap's access to your Google account, without deleting anything already imported.
Delete all imported data - removes everything Catnap has imported or derived, while keeping your Google connection and account active.
Delete your account - revokes Google access and permanently deletes everything, including your account itself.

These are available from your Settings page once signed in.

Google API Services User Data Policy

Catnap's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Because Catnap reads Google Calendar, a Google Workspace API, it also adheres to the Google Workspace User Data and Developer Policy.

Questions

If you have questions about this policy or your data, contact us at privacy@catnap.work.