Cookie Policy
A clear, plain-language explanation of how cookies and local storage are used on FreeTimeline—and exactly what that means for you.
Last updated: May 11, 2026 · Effective: May 11, 2026
How consent actually works here: every visitor sees the cookie consent banner on first visit—we do not detect your region and do not vary the banner by country. No advertising script is loaded and no ad cookie is set until you press Accept all. If you press Reject all (or never respond), Google AdSense is never loaded on your visit, so no ads—personalised or otherwise—are shown. You can review or change your choice at any time using the control in the footer of every page.
1. Introduction
This Cookie Policy explains what cookies are, how FreeTimeline uses them, and how you can control them. It should be read alongside our Privacy Policy, which provides broader context about how we handle your information.
FreeTimeline is designed with privacy as a core value. Our own tools use localStorage rather than traditional cookies to store your timeline data. However, as a site that displays advertising through Google AdSense, third-party cookies are set in your browser by Google. This page explains everything in full.
2. What Are Cookies?
Cookies are small text files placed on your device by websites you visit. They are widely used to make websites work, to work more efficiently, and to provide information to website owners.
First-party vs. third-party cookies
First-party cookies are set directly by freetimeline.pt. Third-party cookies are set by a different domain—on FreeTimeline, these come from Google AdSense.
Session vs. persistent cookies
Session cookies are deleted automatically when you close your browser. Persistent cookies remain until they expire or you manually delete them.
3. localStorage vs. Cookies — An Important Distinction
FreeTimeline does not use traditional cookies to store your timeline data. We use your browser's localStorage instead—a technology that keeps data entirely on your device and never transmits it to any server.
- Cookies — automatically sent to the web server with every browser request. Servers can read, write, and track cookie data.
- localStorage — stored locally in your browser, never sent to any server. Only JavaScript running on freetimeline.pt can access it. It is sandboxed per domain—no other website can read FreeTimeline's localStorage.
FreeTimeline stores one consent record: a localStorage key called ft_cookie_consent which records whether you have accepted your cookie preferences, so that the consent banner is not shown on every visit.
4. What FreeTimeline Actually Stores (localStorage, not cookies)
4a. App data & preferences
This is the complete, verified list of browser localStorage keys FreeTimeline's own code writes. None of these are cookies—none are sent to any server; they never leave your device.
| Name | Type | Purpose | Duration |
|---|---|---|---|
ft_cookie_consent | localStorage | Records your cookie-banner choice (accepted or rejected) so the banner isn't shown again | Until manually deleted |
inf_universe_v4 | localStorage | Saves all Universe Timeline data: universes, events, characters, categories, connections | Until manually deleted |
inf_biography_v1 | localStorage | Saves all Biography Timeline data: life tracks, events, people, categories, connections | Until manually deleted |
ft_uni_view_v1 / ft_bio_view_v1 | localStorage | Remembers the last pan and zoom position on each timeline canvas | Until manually deleted |
ft_range_* | localStorage | Remembers the min/max year range of the active filter, per timeline | Until manually deleted |
ft_uni_history_v1 | localStorage | Stores autosave snapshots of the Universe Timeline so you can undo across sessions | Until manually deleted |
ft_uni_universes_v1 | localStorage | The list of named universes you've created in the Universe app | Until manually deleted |
ft_bio_settings_v1 | localStorage | Biography app settings, such as your saved birth date for age calculations | Until manually deleted |
ft_uni_onboarded / ft_bio_onboarded | localStorage | Remembers that you've dismissed the first-run onboarding card | Until manually deleted |
ft_touch_hint_seen_v1 | localStorage | Remembers that you've dismissed the one-time touch/mobile usage hint | Until manually deleted |
ft_tb_hint_v1 | localStorage | Remembers that you've dismissed the toolbar Save/Load coachmark | Until manually deleted |
uni-reading-mode / bio-reading-mode | localStorage | Remembers whether Reading Mode (distraction-free view) is switched on | Until manually deleted |
uni_minimap_collapsed_v1 / bio_minimap_collapsed_v1 | localStorage | Remembers whether the mini-map panel is collapsed | Until manually deleted |
4b. Advertising Cookies (Google AdSense)
FreeTimeline uses Google AdSense to display advertisements, but only after you press Accept all on the consent banner—the AdSense script is not loaded before that. Once loaded, Google (not FreeTimeline) sets its own cookies in your browser to serve and measure ads. We do not control which cookies Google sets, their exact names, or their durations—those are determined by Google and can change without notice on our part. Historically, Google's advertising cookies for AdSense/DoubleClick have included things like NID, IDE, ANID, __gads, and DSID, but treat this as illustrative, not a guarantee of what is currently set in your browser. For the authoritative, up-to-date list, see Google's Cookie Policy.
4c. Analytics Cookies
FreeTimeline does not currently use Google Analytics or any other analytics platform. No analytics cookies are set by FreeTimeline. If this changes, this policy will be updated and users will be notified via the consent banner.
5. How Google AdSense & DoubleClick Cookies Work
When you visit FreeTimeline, Google's ad-serving technology reads existing Google cookies, sets new ones if not already present, analyses your browsing history and device signals to select relevant ads, displays those ads in the designated slots on FreeTimeline pages, and records whether you viewed or clicked on them.
The DoubleClick DART cookie (stored under doubleclick.net) contains a unique, randomly generated identifier tied to your browser—not to your name, email, or any directly identifying information. This identifier is used across millions of websites in Google's advertising network to build an interest profile, which Google uses to show you more relevant ads wherever you browse.
6. Your Cookie Choices & How to Opt Out
Google Ad personalisation opt-out
Opt out of personalised advertising by Google at: google.com/settings/ads
Industry-wide opt-out tools
7. Managing Cookies in Your Browser
Google Chrome
Settings → Privacy and security → Cookies and other site data. To clear localStorage: Settings → Privacy and security → Site settings → View permissions and data stored across sites → search for freetimeline.pt → Delete.
Mozilla Firefox
Settings → Privacy & Security → Cookies and Site Data → Manage Data. You can remove cookies for specific sites or clear all cookies and site data.
Apple Safari
Preferences → Privacy → Manage Website Data. Safari also has a "Prevent cross-site tracking" option that blocks many third-party cookies automatically.
Microsoft Edge
Settings → Cookies and site permissions → Cookies and site data. Edge also offers tracking prevention levels (Basic, Balanced, Strict) under Privacy, search, and services.
Please note: Blocking all cookies may affect the functionality of other websites. On FreeTimeline specifically, if you reject or ignore the consent banner, no advertising cookies are set and no ads are loaded at all—there is no separate "non-personalised ads" mode on this site.
8. Third-Party Cookie Resources
9. Changes to This Cookie Policy
We may update this Cookie Policy from time to time. When we make material changes, we will update the "Last updated" date at the top of this page and display a notice on the site. We encourage you to review this page periodically.
10. Contact
- Email: privacy@freetimeline.pt
- Contact form: Contact Us