What we collect, and why.

The booking calendar on this site is ours. It is run by MOD.fyi from internal.mod.fyi, and it asks for:

Name

So we know who we are meeting.

Email

For the confirmation, the calendar invite, and anything we need to send you before the call.

Notes

Optional. Whatever you want us to know beforehand.

Additional guests

Optional. Email addresses of colleagues to invite.

• We also record the time you picked and your time zone, and, if you arrived from an ad or a tagged link, how you got here (see below).
• Booking creates an event with a Google Meet link in our Google Calendar, which invites you and any guests you added. Confirmations are sent by our email provider.

The contact, support and fit-analysis forms collect what you type into them, usually your name, email, company and message, and we use it to answer you.

To stop the booking calendar and the forms being abused, your IP address is used briefly to limit how often they can be submitted.

The site is hosted on Vercel. We use Vercel Web Analytics to count page views and Vercel Speed Insights to measure how fast pages load. Neither sets cookies. According to Vercel, Web Analytics identifies a visit by a hash of the request that is discarded after 24 hours, so it cannot follow you across sites or from one day to the next.

• Vercel Analytics privacy and compliance ↗

We advertise on Google. Our pages load Google's tag (gtag.js) so we can tell whether an ad led to a booked discovery call.

• When you arrive from one of our ads, Google adds a click identifier (gclid) to the address, and the tag keeps it in cookies on mod.fyi, such as _gcl_aw and _gcl_au, for about 90 days.
• When you book a discovery call, the page tells Google that a booking happened, with the booking's reference number so that one booking is counted once. It does not send your name, your email, your notes or anything else you typed.
• Like any website request, Google also receives the page address, your IP address and your browser details, and it may set or read its own cookies under its own privacy policy.
• Customer-success bookings are never reported to Google, and our internal presentation pages do not load the tag.

• Google Privacy Policy ↗
• How Google uses information from sites that use its services ↗
• My Ad Center: turn off personalised ads ↗

If you arrive with a Google Ads click identifier or campaign tags (utm_source, utm_medium, utm_campaign, utm_term, utm_content) in the address, we remember the first ones, and the page you landed on, in your browser's session storage. It is not a cookie, and it is cleared when you close the tab.

If you book a call, it is saved with the booking so we can see which campaign brought you to us. Nothing else from the address is kept.

Apart from Google's cookies above, the site sets one cookie of its own: mod_cs_access, after an existing customer enters the access code on the customer-success page, so they don't have to type it again. It holds the code and nothing about you, and lasts about four months. Staff using our internal presentation tool get a sign-in cookie of their own.

You can block or delete cookies in your browser. The site works without them, booking included; we just can't tell which ad brought you.

We don't sell or rent personal data. We share it only with the services that run this site and our calendar for us (our hosting, database and email providers, and Google for calendar invites and the ad measurement above), and only so they can do that work.

We keep booking and contact details for as long as we need them to work with you, and delete them when you ask.

Write to we@mod.fyi to see what we hold about you, to correct it, or to have it deleted.

If we change what we collect, we will update this page and the date at the top.