Short version: Meetwisely does not require an account. Participant names and availability are stored on our server so participants can coordinate; event details and a local copy of responses are saved in your browser. Automatic deletion after 60 days is not currently implemented.
What information we do not collect
- Scheduling does not require your email, phone number, or an account. If you use the contact form, we ask for your name, email address, subject, and message.
- We do not attach your real-world identity to events. The "name" you enter is just a label for other participants to recognize you.
- We do not sell or share personal information.
What is stored, and where
When you create an event or mark availability, the following data is saved:
- On your device (in your browser's
localStorage): the events you've interacted with, so you can return to them without re-sharing the link. - On our server (Netlify Blobs storage): participant names and availability selections, keyed by the event ID. This is what lets you and your friends see each other's responses.
Stored data includes the event definition (dates, times, timezone) in the link and browser; participant names, availability slots, and update metadata on the server. A random browser identifier and edit sequence help prevent delayed saves from replacing newer edits. No email, IP, or account data is attached to stored event data.
A compact representation of the event is also encoded into the shareable URL. Anyone with that URL can open the event, read its data, and add or modify availability under any participant name. Participant names are not password-protected. Treat the URL like a password: only share it with people you want to see and contribute to the event.
How long we keep data
There is currently no automatic expiry for server-stored responses. To request removal, contact us with the event URL. Browser data remains until you clear the site data. This corrects an earlier statement that events were automatically deleted after 60 days.
To limit rapid updates, we also store request timestamps under a hash derived from the network address and event ID. Raw IP addresses are not stored in those rate-limit records.
Server logs
Meetwisely is hosted on Netlify. Netlify, as the infrastructure provider, processes standard request logs (IP address, user agent, requested URL, timestamp) for operational purposes such as detecting abuse, rate-limiting, and scaling. These logs are handled under Netlify's own privacy policy and are separate from the event data described above.
Analytics
We use Cloudflare Web Analytics to understand aggregate usage (such as how many people visit and which pages they use). Cloudflare Web Analytics does not use cookies, does not fingerprint visitors, and does not collect personal information.
Advertising
We may introduce advertising in the future to help keep Meetwisely free. If we do, advertising partners may set their own cookies or collect technical information through their ad code, subject to their own privacy policies. We will update this page with details before any advertising is introduced, and we will not sell personal information to advertisers.
Cookies
Meetwisely itself does not set tracking cookies. Third-party services we use (such as hosting, analytics, or future advertising) may set cookies for their own purposes, governed by their privacy policies. Your browser lets you manage or block cookies at any time through its settings.
Children
Meetwisely is a general-purpose scheduling tool and is not directed at children under 13. We do not knowingly collect any personal information from children.
Your rights
To remove data stored in your own browser, use your browser's "Clear site data" option for meetwisely.com. To request deletion of an event you created on our server, contact us with the event URL and we will remove it.
Contact
Questions about this policy? Write to our contact page.
Changes to this policy
If we meaningfully change how data is handled, we will update the "Last updated" date at the top and, if the change is material, add a note describing what changed.