Privacy Policy

The short version

Whensday shows your friends when you're busy, not what you're doing. Events you keep private, and everything imported from Google Calendar or Apple Calendar, reach your friends as a block of time with no title, no notes, and no location attached. That's the default, and it only changes if you choose to share an event's details.

We don't sell your data, we don't run ads, and we don't use your calendar for anything other than showing you and your friends when you're free.

What we collect

When you sign in and use the app, we store:

• Your account: the user id and email address Sign in with Apple gives us, and your name if you chose to share it. Apple's private relay addresses work fine, and we never see your Apple password.
• Your profile: display name, an optional username, an optional photo, and a randomly generated invite code. The photo comes from your library or your camera, only when you pick one.
• Your events: title, start and end time, time zone, whether it's all day, and any location or notes you add.
• Your friends: who you've connected with. Friendships are made by sharing a link, so we never search or upload your contacts.
• A notification token for each device you sign in on, if you allow notifications, so we can tell you when a friend adds or changes a plan. It identifies the device, not you, and it's deleted when you sign out on that device.

Apple Calendar, if you connect it

Connecting Apple Calendar is optional and off until you turn it on. Unlike Google, this one runs entirely on your phone: Apple has no server-side calendar API, so there's nothing for us to connect to. Your phone reads the calendars you tick, using the calendar permission iOS asks you for, and sends us the events from them.

What reaches our server is the same as with Google, and it's stored the same way: as private time blocks. Your friends see that you're busy between 2pm and 3pm, and not the title, the notes, or the location, unless you decide to share it. You can share one event, from the event itself, or all of them at once with a setting in the app.

Events you create in Whensday are written back to a calendar called "Whensday" that we create on your device, so they show up alongside everything else. We don't write to any of your other calendars, and we don't read the ones you haven't ticked.

You can turn it off in Settings inside the app, which deletes every event we imported from it. You can also revoke calendar access entirely in the iOS Settings app, under Privacy and Security.

Google Calendar, if you connect it

Connecting Google Calendar is optional and off until you turn it on. When you do, we ask Google for access to your calendars, and we store:

• A refresh token, which is what lets us keep syncing while the app is closed. It's encrypted before it's stored, it stays on our server, and it is never sent to your phone.
• Your Google account's email address and identifier, so we can show you which account is connected.
• Your list of calendars, so you can choose which ones to sync. Holiday and birthday calendars are off by default, because importing them would mark you busy all year.
• Events from the calendars you switch on: title, description, location, start and end time, and whether you've marked yourself free or declined. We skip events you've marked Free or declined, because they aren't a reason for anyone to think you're busy.

What we do with your Google data

Two things, and nothing else. We show your Google events on your own calendar in the app, and we show the times as busy to friends you've connected with. And when you create an event inside Whensday, we write it to a calendar called "Whensday" that we create in your Google account, so it shows up alongside everything else.

Events pulled in from Google are stored as private time blocks. Your friends see that you're busy between 2pm and 3pm. They do not see the title, the notes, the location, or who else was invited. This is enforced in the database, not just in the app.

The one thing that changes it is you asking for it. You can share a single imported event with your friends, from the event itself, or switch on sharing for all of them in Settings, and then the friends you've connected with see that event's title and details. Nothing is shared with anyone else, and turning it back off makes them private again.

Whensday's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Concretely, that means we do not use Google Calendar data for advertising, we do not sell it, we do not transfer it to anyone except as described below, we do not use it to train generalised AI or machine learning models, and no human at Whensday reads it, except where you've explicitly asked us to look at something to help with a support problem, or where we're required to for security or by law.

Who can see what

People you've added as friends can see your name, your photo, and any event you've explicitly marked as visible to friends, including its title.

For everything else, private events and anything imported from Google or Apple Calendar that you haven't shared, friends see only the time you're busy.

If you've allowed notifications, your friends' phones get an alert when you add, change, or remove an event you've marked as visible to friends. Private events and imported ones never trigger one.

Nobody who isn't your friend sees any of it.

Who we share data with

We use a small number of services to run the app. They process data on our behalf and can't use it for their own purposes:

• Supabase, which hosts our database, authentication, and server code.
• Apple, which handles Sign in with Apple, and which delivers notifications to your devices.
• Google, whose Calendar API we call on your behalf when you've connected your account.
• Vercel, which hosts this website.

How it's protected

Sensitive data, which here means your calendar events and the connection to your Google account, is protected against unauthorised access, alteration, and disclosure by these measures:

• Encryption in transit. Every connection runs over HTTPS with TLS: the app talking to our server, our server calling the Google Calendar API, and you reading this page. Unencrypted connections aren't accepted.
• Encryption at rest. The database is encrypted on disk by our hosting provider. Your Google refresh token is then encrypted a second time, with AES-256-GCM, before it's written, using a key held as a server-side secret outside the database. A leaked database dump on its own doesn't give anyone access to your calendar.
• Row-level access control. The database decides who can read each row, so the rules described above are enforced by the database itself and not only by app code that could have a bug. The public key the app ships with can't read anyone's calendar data. The privileged key that can exists only in our server environment, and is never included in the app.
• Least privilege at Google. We only ever asked Google for permission to read the calendars you tick and to write to a single calendar we create ourselves. We can't change or delete events on your existing calendars, because we never requested the ability to.
• Restricted human access. Production data is reachable only by the developers who build and run Whensday, through accounts protected by two-factor authentication. Nobody reads your calendar content as part of running the service, apart from the exceptions named above: a support problem you've asked us to look into, or a legal or security obligation.
• Deletion. Disconnecting a calendar or deleting your account removes the data immediately, as described below, rather than after a retention window.

If something goes wrong

No system is perfectly secure, and we'd rather say so than imply otherwise. If we discover a breach affecting your data, we'll tell the people affected and the regulators we're required to, without waiting to be asked.

If you've found a security problem in Whensday, email dhruvchowdhary7@gmail.com and we'll answer.

Keeping and deleting your data

We keep your data while your account exists.

Disconnecting a calendar, from Settings inside the app, deletes every event we imported from it. For Google, it also tells Google to revoke our access and removes the stored connection. Events you created in Whensday stay, and so do the copies of them already in your Google or Apple calendar, which are yours to keep or delete there.

To delete your account, open Settings in the app and tap Delete account. It removes your profile, your events, your friendships, your photo, and any stored calendar connection, and it takes effect immediately rather than after a waiting period. Events already synced to your Google or Apple calendar stay there, because those are copies in your own account and ours to write, not to take back.

If you can no longer sign in, email dhruvchowdhary7@gmail.com and we'll delete it for you.

Analytics and tracking

There aren't any. The app contains no analytics SDK, no advertising SDK, and no crash reporter, and we don't track you across other apps or websites.

Children

Whensday isn't directed at children under 13, and we don't knowingly collect their data. If you believe a child has given us information, email us and we'll remove it.

Changes

If we change what we do with your data, we'll update this page and the date at the top. If the change is significant, we'll tell you in the app rather than hoping you re-read this.

Contact

Questions, requests, or concerns: dhruvchowdhary7@gmail.com.