Privacy & data

Exactly what we store, and where

Plain language, no surprises. Last updated November 19, 2026.

On our servers: nothing about your events

Wentely has no database. Our server only sends the app's code to your browser. Event titles, names and availability never reach it, and there are no accounts. Like any website host, our hosting provider may keep standard request logs (such as IP address and the page path); the part of an event link after the # is never part of a request, so it can't appear in them.

One exception: if you turn on calendar sync (Booked), a small Wentely server function passes your busy times from your calendar provider to your browser, in memory only. See Calendar sync below. It still never receives your events or answers.

In your browser (this device only)

  • The events you created or opened, with every answer you've received, in IndexedDB.
  • Private signing keys: one per answer you wrote (so only you can change it) and one per event you organize (so only you can rename it or hide answers). They never leave this browser unless you export a backup.
  • Small preferences in localStorage: the time zone you chose to view, whether you dismissed the first-run notice, a count of how many links you have created in this browser (for the 25 free links; it never leaves your device), and, if you subscribe to Booked, your Stripe customer id with the last-known plan status.

We ask the browser to treat this storage as persistent, so it isn't cleared to free space. Clearing site data still removes it, so export a backup if it matters. This device keeps up to 200 events. Near that limit we warn you, and we always ask before removing anything. Pinned events are never removed automatically.

In the links you send

A share or reply link carries the event and its answers after the #, compressed. Anyone holding the link can read the names and times in it, so send it only to the people it's for. Every answer is signed by its author and the event by its organizer, and Wentely checks those signatures before using a link or a backup, so a link can't quietly change someone else's answers.

In your own cloud (only if you turn it on)

The app can keep a copy of your event list in Google Drive (a hidden app-data folder, scope drive.appdata); OneDrive is planned. This is part of Booked. Files go straight from your browser to your provider; we never see them or your tokens. These options are switched off in this version until their app registrations are in place.

What we don't do

  • No ads, no ad networks, no analytics or tracking scripts, no third-party cookies.
  • No accounts, no email collection, no selling or sharing data.

Booked subscriptions

Booked is sold through Stripe, which collects your card and email; Wentely never sees them. After checkout, a small server route (/api/pro/status) asks Stripe whether your trial or subscription is active, using a read-only key, and returns only the plan status and its dates. Your browser keeps your Stripe customer id and that status so Booked can be recognised without an account. There is no Wentely database.

Calendar import (Booked)

Calendar files you import are read in your browser to mark free slots. The file is never uploaded.

Calendar sync (Booked)

Calendar sync is part of Booked, and always optional. You connect one calendar, and Wentely shows when you're busy on your own grid. Where each calendar stands today:

  • Apple Calendar (iCloud): live.
  • Google Calendar: available in early access. Wentely's Google app is still being reviewed by Google, so until that review is finished only Google accounts we have approved as testers can connect (anyone else will see a Google warning screen or be unable to continue). Everything below applies to those accounts.
  • Outlook / Microsoft 365: not available. It isn't offered and nothing connects to Microsoft. If that changes, this page will be updated first.

What we read: when you're busy, nothing else

Wentely asks for your busy and free times only. We never keep event titles, descriptions, attendees or locations. What each connection lets us request:

  • Google: the permission https://www.googleapis.com/auth/calendar.freebusy (“View your availability in your calendars”). Google's free/busy service returns only blocks of busy time, never event titles. We also ask for your email address, only to show which account is connected.
  • Apple (iCloud): Apple has no sign-in for apps like this, so you create an app-specific password in your Apple Account and paste it in. Apple's calendar service sends whole events. Our server reads them in memory, keeps only the start and end times of the busy ones, and throws the rest away. We only read; we never change or delete anything in your calendar. Never enter your normal Apple password.

What it's used for

Only to show your own busy times on your own grid, as a hatched pattern, so you can see where you're free while you answer. It never changes your answer for you, and it is never shown to an organizer or anyone else.

Not stored on a server

Wentely still has no database. When you open an event, your browser asks a small Wentely server function for your busy times. The function asks your calendar provider, reduces the answer to start and end times, and passes it back to your browser. It is held in that function's memory only while it handles the request (and for about half a minute in case you refresh), then it is gone. Busy times are never written to disk on our side, never put in a share or reply link, never included in a backup or export, and never saved with your events: they exist only in the open page, and they refresh when you open the page or press Refresh (not in real time). Like any website host, our hosting provider may keep standard request logs (such as your IP address, the page path and the time range requested). We don't log your calendar data, and our own logs hold only codes and counts.

Because calendar sync is part of Booked, the same server function also asks Stripe, with a read-only key, whether your Booked subscription is active. It sends Stripe your customer id (which your browser holds) and gets back only whether you are subscribed.

What stays in your browser

To keep you connected without an account, your Google login token (or your Apple ID and app-specific password) is kept in a cookie in this browser. It is encrypted (AES-256-GCM) with a key only our server holds, and it is marked HttpOnly and Secure, so scripts on the page can't read it. It can only be used while our server handles a request from your browser.

How long things are kept

  • Busy times: in the open page only. Closing or reloading the tab discards them, and we stop showing them if they are more than an hour old.
  • Login token or app password: in the encrypted cookie for up to 30 days after you last used calendar sync, and at most 90 days in total. Then you reconnect.
  • Short-lived access tokens: in server memory only until they expire (up to about an hour). Never written down.

You're in control: disconnect any time

  • Press Disconnect in Wentely (under your grid, or in “Your data”). That deletes the cookie, and for Google it also revokes the permission at Google right away.
  • Apple can't be revoked by us: to finish, delete the “Wentely” app-specific password at account.apple.com under Sign-In and Security, App-Specific Passwords. For Google you can also remove access at myaccount.google.com/permissions.
  • Clearing this site's cookies has the same effect on our side.

Google users: Limited Use

Wentely'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. In plain words: we use your Google calendar data only to show your busy times to you, inside Wentely. We don't sell it, share it or use it for ads, and no one at Wentely reads it, except where needed for security or to comply with the law.

Back to Wentely