Cookie Policy
Last updated: 7 September 2026
This Cookie Policy explains how Time to Go uses cookies and similar technologies.
It should be read together with the Privacy Policy.
1. What cookies and similar technologies are
Cookies are small pieces of information stored by a browser. Websites and third-party services may also use technologies such as local storage, web beacons or similar identifiers.
Some storage is necessary for a site's technical operation or to remember privacy choices. Other storage can support advertising, measurement and personalization.
2. Categories used on Time to Go
A. Strictly necessary storage
This category may be used for functions that are necessary to provide requested functionality, security or privacy choices.
Examples may include the storage used by the consent-management platform to remember whether you accepted, rejected or customized advertising/privacy purposes.
Strictly necessary storage is not used by Time to Go to build a behavioural profile of your calendar activity.
B. Advertising and advertising-measurement technologies
Time to Go uses Google AdSense.
Google and authorized advertising providers may use cookies or similar technologies in connection with:
- serving advertisements;
- selecting non-personalized or personalized ads according to applicable choices;
- frequency capping;
- fraud and abuse prevention;
- ad delivery;
- reporting and advertising measurement.
Third-party vendors, including Google, may use cookies to serve ads based on a user's previous visits to Time to Go or other websites.
Google's use of advertising cookies enables it and its partners to serve ads based on visits to this site and/or other websites.
Users can manage Google ad personalization through Google's Ads Settings, as well as through the Time to Go consent/privacy interface where applicable.
3. Consent in the EEA, UK and Switzerland
Time to Go uses Google Privacy & messaging as its consent-management platform.
For AdSense traffic in the EEA, UK and Switzerland, the production CMP must be Google-certified and integrated with the IAB Europe Transparency & Consent Framework where required by Google.
The consent interface must offer clear controls including:
- Accept all
- Reject all
- Manage options
Rejecting non-essential advertising purposes must be as straightforward as accepting them.
Where consent is required, non-essential advertising cookies or similar storage must not be used before the relevant consent signal.
A permanent Privacy / Cookie settings control allows choices to be reviewed or withdrawn later.
4. Current cookie/vendor list
Advertising vendors and individual cookie names can vary by:
- visitor region;
- consent state;
- browser;
- AdSense configuration;
- Google's and vendors' current technology.
For that reason, Time to Go does not pretend that a hard-coded list in this document is permanently exhaustive.
The live CMP vendor and purpose list is the authoritative interface for optional advertising technologies in the current configuration.
The implementation should nevertheless document any Time to Go first-party storage accurately.
First-party / consent storage
Codex must replace the table below with the exact production values after the CMP is configured.
| Name | Provider | Type | Purpose | Duration |
|---|---|---|---|---|
FCNEC |
Google LLC (Funding Choices) | cookie | remember consent and privacy choices | 1 year |
Do not publish unresolved placeholders.
5. The Time to Go date tools
Dates placed in the query string of a shareable general visualization are URL parameters, not cookies.
However, a requested URL can be visible to the website's delivery infrastructure and, once advertising services are loaded according to applicable consent/settings, third-party services may receive the page URL as part of normal web/ad requests.
Do not place confidential information in a shareable URL.
The Life Calendar is designed differently: the birth date must not be written to the URL, cookies, consent storage, localStorage or advertising parameters by Time to Go.
6. No site-owner behavioural analytics
Time to Go does not use Google Analytics or another behavioural analytics module selected by the site owner.
This does not mean that advertising services perform no measurement. AdSense advertising measurement is governed by the advertising configuration, CMP signals and provider policies.
7. Netlify
Time to Go is hosted on Netlify.
Hosting/CDN infrastructure processes technical web requests to deliver and secure the site. That infrastructure-level processing is not itself the same as Time to Go using an analytics or advertising cookie.
This Policy does not claim that Netlify sets a particular visitor cookie unless the current production implementation verifies that it does.
8. Changing or withdrawing choices
Use the persistent Privacy / Cookie settings link on Time to Go to reopen the CMP.
You can use it to review or change available advertising/privacy choices.
You may also delete cookies or local storage using browser controls. Doing so can cause the consent interface to be shown again.
9. Google advertising controls
Google provides additional advertising controls through its Ads Settings.
Depending on your region, other industry opt-out tools may also be available.
These external controls are separate from Time to Go's CMP.
10. Changes to this Cookie Policy
Cookie names, providers and advertising technology can change.
Time to Go should update this Policy when its own implementation, CMP or advertising configuration materially changes.
11. Contact
Questions about this Cookie Policy:
info@timetogo.fyi
Advertising data: Google partner-sites data-use information · Google Ads Settings · Privacy / Cookie settings.