calendar_monthNotionCal
How it worksPricing
Log in / Sign up
Terms of ServiceRefund Policy

Privacy Policy

Last updated: 2026-08-02

NotionCal ("the Service") turns a Notion database into a CalDAV feed and a browser calendar view. This page explains what data we collect and how we use it.

What we collect

  • Account: the email address from your login (via our self-hosted Keycloak identity provider) — used only to identify your account.
  • Notion access: when you connect your Notion workspace, we store the OAuth access token Notion issues us, along with your workspace id/name and integration bot id. This token is what lets the Service read and write the specific pages you granted access to.
  • Calendar configuration: for each Notion database you choose to sync, we store its database id, the date property used for scheduling, and a display name.
  • CalDAV credentials: we generate a random username/password per calendar so you can subscribe from Apple/Google Calendar or any CalDAV client. Only a salted hash (Argon2) of the password is stored — the plaintext is shown to you once, at creation time, and never again.

Payment data

Paddle.com is our payment provider and the merchant of record for every purchase. Your card details are entered on Paddle's checkout and are never sent to us or stored by us — we never see them. What we keep is what Paddle tells us afterwards: the customer and subscription identifiers it assigns you, your subscription status, and the date your free period started. That is enough to know whether your account is paid, and nothing more.

Paddle processes this data as its own controller under its privacy policy.

What we don't collect

  • No card numbers, bank details, or billing addresses — those stay with Paddle.
  • No analytics or advertising trackers.
  • No data is sold or shared with third parties for marketing.

How we use it

Solely to operate the Service: fetching events from your Notion database, converting them to CalDAV/iCalendar format, keeping them in sync (via periodic polling and Notion's webhook events), and rendering the calendar webview so you can view and edit events yourself.

Where it's stored

All data lives in a private PostgreSQL database we operate, not exposed to the public internet, reachable only by the Service itself. We do not use third-party data processors beyond Notion's own API (needed to read/write your workspace) and the infrastructure hosting our servers.

Your controls

  • You can revoke the Service's access at any time from Notion's own "Connections" settings in your workspace — this immediately invalidates the access token we hold.
  • To delete your account and all associated data (connections, calendars, credentials), email us at the address below.

Contact

Questions about this policy: [email protected]

NotionCal
Setup GuidePrivacy PolicyTerms of ServiceRefund Policy