When3Meet Privacy Policy

When3Meet is a scheduling tool. You create an event, share a link, and people mark when they're available. That's the core of it. There's also an optional Google Calendar overlay so you can see your existing commitments while filling out availability, and a comments section for coordinating details.

We only collect what the app needs to function:

• Account data — if you sign up: your name, email address, and a hashed password. We never store your password in plain text.
• Event data — the name, dates, time window, timezone, and other settings you configure when creating an event.
• Availability data — the display name you enter and the time slots you select when responding to an event.
• Comments — any notes you post on an event page, including your name and the time posted.
• Session data — stored in a cookie to keep you signed in and remember your participant identity between page loads.

Connecting Google Calendar is optional. If you do, When3Meet requests read-only access to your calendars so it can show your existing events as busy blocks on the scheduling grid. We do not create, edit, or delete anything in your Google Calendar.

Your Google access credentials are stored in your session and cleared when you sign out. You can also revoke access at any time from your Google account settings. Google Calendar data is only used to render the overlay in the app — it is not written to our database or shared with anyone.

When3Meet's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising or share it with third parties.

We use what we collect to run the service: showing events, saving availability responses, displaying comments, and keeping you signed in. We do not sell your data, use it for advertising, or share it with anyone beyond what's needed to operate the app (hosting infrastructure, database provider, Google APIs when you opt in).

Events are unlisted by default — they're accessible to anyone with the link, but not publicly listed or indexed. Don't put sensitive information in event names or comments if you're sharing the link widely.

We use a single session cookie to keep the app working. It stores things like your signed-in user ID, your participant name for an event, and your Google Calendar session. It expires automatically or clears when you sign out.

You can use When3Meet without an account — just enter a name when filling out availability. Connecting Google Calendar is entirely optional. If you want to disconnect it, sign out to clear the session or revoke access from your Google account settings.

We use standard security practices like hashed passwords and signed cookies. That said, no internet service can guarantee absolute security, and this is a student-built project.

If this policy changes, the updated version will be posted here with a new effective date.