Privacy

Your event details

The links are built in your browser. Your event title, times, location and description are never sent to this site's server when you generate a link, and they are never written to a database. They travel inside the link itself, which is why the link works forever and why there is nothing here to delete.

One consequence worth understanding: anyone with the link can read the event details, since they are encoded in the URL. The encoding is for URL safety, not secrecy. Do not put confidential information in an event you are about to share as a link.

Cookies

None. No analytics script, no tag manager, no third-party pixel, no consent banner.

If you turn on click counting

When a tracked link is used, one row is written:

• The event key, a short hash of the event details
• Which calendar was chosen
• The timestamp
• A two-letter country code from the edge network
• The host of the referring page, without the path or query string

Deliberately not stored: IP addresses, user agents, cookies, device identifiers, anything that identifies a person.

On the first tracked click, the event title, start and timezone are stored once so the dashboard has something to label the numbers with.

Who can see the numbers

Anyone with the dashboard URL. It is unlisted, not protected, and those pages are marked noindex so search engines skip them. Treat the link as you would an unlisted video.

Hosting

The site runs on Cloudflare's edge network. Cloudflare processes request metadata to serve and protect the site, as any host does. Server access logs are not retained by this project.

The .ics endpoint

Requesting an .ics file sends the encoded event to the server, because the file has to be generated somewhere. It is not logged or stored, and the response is cached by content. When tracking is off, the browser can build the file locally instead, and this tool does that by default.

GDPR

No personal data is collected, so there is no processing to consent to and no data subject request to fulfil. If you use tracked links with your own audience, you are not adding a processor to your own privacy notice either, though check with whoever owns that document.

Contact

Questions or a correction: hello@makecalendarlink.com. The code is public, so you can verify all of the above rather than take it on trust.