Privacy Policy

Timeliner collects and stores the following categories of data:

• Content you create or paste — the raw text you paste or type, and the structured events extracted from it (titles, descriptions, dates, people, locations, tags, recurrence rules, and any links/attachments you add).
• Photos you upload — image files you attach to events.
• A randomly generated device identifier — used only to scope your data if cloud sync is enabled (see below). It is not linked to your name, email, or any other identity.
• App settings — view preferences, dark mode, sidebar state, custom tags, and similar UI preferences.
• Search history and a location lookup cache — stored locally to make repeat searches and map lookups faster.
• Basic request metadata — Timeliner's serverless API endpoints read the requesting IP address transiently, in memory, to enforce rate limits. It is not written to a database or logged with your content.

Timeliner has no user accounts, login, or signup — there is nothing to register, and no name, email address, or password is collected by the app itself.

• Your pasted text and photos are used only to build the timeline you asked for.
• The device identifier exists solely so that, if you turn on cloud sync, your data can be matched back to you across sessions/devices without requiring an account.
• Settings and caches exist to make the app faster and remember your preferences.
• The IP address is used only to prevent abuse of the AI and sharing endpoints.

• Your browser (default, always on): events, timelines, custom tags, and photo files are stored locally using IndexedDB; lightweight settings are stored in localStorage. This data never leaves your device unless you explicitly use a feature described below.
• Cloud sync (optional, only if the app is configured to use it): when a Supabase backend is configured, your timelines, events, and photos can also be stored in Supabase (database + file storage) so they're available across devices/sessions. Photo files are stored in a private storage bucket, scoped to your device identifier, and are not publicly accessible — the app reads them back using short-lived signed URLs rather than public links.

• Events, timelines, and photos are kept for as long as you keep them in the app — Timeliner does not automatically delete your own timeline content or uploaded photos after any fixed period.
• Deleting an event, timeline, or photo in the app removes it from your local storage and, if cloud sync is enabled, from the cloud copy as well.
• Deleted events go through a brief (a few seconds) "undo" window before the cloud copy is actually removed, so an accidental delete can be reversed.
• You can remove all locally stored data at any time by clearing your browser's site data/storage for Timeliner. Note that if cloud sync was enabled, this clears your device identifier too — if you need Timeliner-side cloud records erased after that point (i.e. you can no longer reach them from the app), use the contact method below.
• Shared timeline links: if you generate a public share link, a copy of that timeline's events is stored separately and is reachable by anyone with the link until it expires (you choose 30, 90, or 365 days at creation). Once expired, the link stops working immediately; the underlying record is deleted the next time the expired link is visited. A share link that is never visited again after expiring may remain in storage longer than its stated expiry.

When you ask Timeliner to extract events from text, or to generate timeline insights, the relevant text (or a stripped-down summary of your events) is sent from Timeliner's own server-side API to Anthropic's Claude API for processing. Photo files themselves are not sent to the AI — only photo filenames, so the AI can suggest matches.

This processing happens on each request to generate a result; Timeliner does not use your content to train its own models. Anthropic processes this data under its own terms and privacy policy as the AI provider — see Anthropic's privacy policy for how they handle data submitted to their API.

Depending on which features you use, the following third parties may process data:

• Anthropic (Claude API) — processes text/event data you submit for AI extraction and insights, as described above.
• Supabase — hosts the optional cloud database and file storage used for cross-device sync and for public share links, when configured.
• Vercel — hosts the application and its serverless API endpoints, and provides Vercel Analytics, which collects aggregated, anonymized page-view metrics (Timeliner does not use cookie-based tracking or ad/marketing pixels).
• OpenStreetMap (map tiles) and Nominatim (place search) — if you view the Map view or type a location, the location text you enter may be sent to OpenStreetMap's Nominatim service to look up coordinates, and map tiles are loaded from OpenStreetMap/CARTO.
• Google Fonts — used to load the app's typefaces.

Timeliner does not sell your data, and does not share it with third parties for advertising purposes.

Timeliner does not use cookies for tracking or advertising. It uses browser localStorage/IndexedDB to store your data and preferences on your own device, and Vercel Analytics for anonymized, aggregate usage metrics (page views), which does not use cookies or persistent identifiers to track you across sites.

Data in transit to Timeliner's API and to Supabase is sent over HTTPS. Cloud-stored photos are kept in a private storage bucket (not publicly listable or readable) and served only via short-lived signed URLs; database access is scoped by your device identifier. No method of storage or transmission is perfectly secure, and Timeliner cannot guarantee absolute security of data you choose to sync to the cloud.

• You can use Timeliner entirely offline/locally without ever syncing to the cloud.
• You can export your data (CSV, JSON, Markdown, plain text, or PDF) at any time from within the app.
• You can delete individual events, timelines, or photos at any time in the app.
• You can clear all local data via your browser's site data settings, or request removal of any cloud-stored data using the contact method below.

Depending on where you live, you may have additional legal rights over your personal data (for example, under GDPR or CCPA/CPRA). Timeliner is a small, independently operated project; if you have questions about your rights in your jurisdiction, please reach out using the contact method below.

For privacy questions or to request deletion of any data Timeliner holds on your behalf, reach out via the links in the app footer/sidebar (developer website or GitHub).

If Timeliner's data practices change, this page will be updated to reflect them.