A: I hear you. Seeing third-party requests fire when you embed a booking page can be really concerning, especially for GDPR requirements.

At the moment, TidyCal’s booking page is hosted and rendered from tidycal.com (including when embedded), and there isn’t a setting in TidyCal to “self-host” assets (like fonts) or selectively disable third-party resources that the booking page may load.

What you can do today (depending on your use case) is avoid embedding (recommended for strict privacy setups).

* Instead of an iframe embed, share your TidyCal booking link as a normal link/button that opens in a new tab.

* This won’t remove third-party requests from the booking page itself, but it keeps your site from embedding that content directly.