Privacy Policy

Last updated October 5, 2026

This policy explains what personal data Timescrolly collects, why, who we share it with, how long we keep it, and what rights you have. It covers the Timescrolly website, apps and API (together, "the service"). Our Cookie policy explains what we store in your browser in more detail.

Who we are

Inquibit runs Timescrolly and is the controller of your personal data, as defined in the EU General Data Protection Regulation (GDPR).

Inquibit
KVK 42167196 · VAT ID NL005551738B04

For anything about your personal data, email [email protected].

One exception: when you pay for a plan, Stripe sells the plan to you as merchant of record and is the controller of the payment data it collects (see "Billing" below).

What we collect

Your account

Name and email address, which you give us when you sign up or sign in with a code. We use your email address to verify your account and let you sign in, and for messages about the service.
Your handle, the short name in your profile and timeline addresses.
Your plan and account settings, and the date your email address was verified.

Signing in with Google or Apple

If you sign in with Google or Apple, we receive your name, email address and an account identifier from them, and from Google also your profile picture. We don't receive your Google or Apple password. What Google and Apple themselves collect when you sign in with them is covered by their own privacy policies.

When you sign in we create a session. With it we store the IP address and browser (user agent) you signed in from, and when the session was last used. This is how we keep you signed in and spot misuse of an account. When you ask for a one-time sign-in code, a verification link or a password reset link, we store a hashed copy of it until it expires.

Your content

Everything you put into timelines: titles, dates, rich text, sources and citations, locations, tags, collections, images, audio and video files, PDF documents and voice memos. Voice memos are recorded in your browser with your microphone, and only when you start a recording. When you upload an image, we remove its embedded metadata, including any GPS position, before we store it. Audio, video and PDF files are stored as you upload them.

Your content may include personal data about you or about other people. You decide what goes in, and who can see it (see the Terms).

Teams, collaboration and activity

Your memberships and roles in teams, and the timelines you collaborate on.
Invitations: the email address an invitation was sent to, who sent it, and whether it was accepted.
Transfers of timelines and teams between people, and their outcome.
Change history: who changed what in a timeline, and when. Editors of that timeline can see it.
Recently viewed: which timelines you opened and when, so we can show you your recent timelines.
Notifications we send you in the app and by email, and whether they were delivered.
Timeline assistant usage: for each message you send the assistant, and for each part of a document it reads for an AI import, who sent it, on which timeline, when, how many tokens the model processed and how many credits it used. We don't keep the messages or the answers. Owners and admins of a team see how many credits each member used from the team's pool.
Help assistant usage: the help assistant on the help pages is free and works without an account. Your question, the conversation so far and your interface language are sent to Google Cloud (Vertex AI, in the EU) to write the answer. Our servers keep neither your questions nor the answers. To enforce daily limits and track the daily cost, we keep one record for each message: the day (UTC), a keyed hash of that day and your account id (if you are signed in) or your IP address (if you are not), the model, the tokens it processed and the credits it used. Never the IP address or the account id itself. What the chats keep in your browser is listed in our Cookie policy.
AI imports: when you import items from a document, the files you upload, your instruction, the drafts made from them with the quotes they came from, and a record of the import (the file names and sizes, the credits it used and its outcome). Only you can see an import and its drafts until you add them to the timeline.

People you work with see your name and handle. Team owners and admins, and the people who manage a timeline, see the email addresses of people they have invited.

Views

We count views of timelines.

Views are counted, including those from readers without an account.
If you are signed in, the view is tied to your account. That is what powers your recently viewed timelines.
If you are not signed in, nothing about you is stored with the view.
When a timeline is opened in an embed on another website, the view stores the name of that site, for example moodle.example.edu, and nothing about the reader.
Embedded timelines set no cookies, write nothing to your browser's storage and send no analytics.

Billing

When you buy a plan, the payment is handled by Stripe, which acts as the seller (merchant of record). Stripe collects your payment details, billing address and tax information, and processes them under its own privacy policy. We never receive or store your full card number. From Stripe we get your customer and subscription identifiers, your plan, billing interval, subscription status, renewal date, and the invoices we show you in your dashboard.

Messages you send us

When you use the contact form we store your name, email address, message, and your account id if you were signed in. When you email us, we keep the email and our reply.

Analytics

We use Mixpanel to understand how people use Timescrolly, so we can improve it. Your browser sends Mixpanel:

events, which describe what you do in Timescrolly:
- pages you view, and signing up or in;
- what you create and use: timelines, items, tags, attachments and voice memos, images, comments, exports, collections, teams, invitations, share links and embed codes, including the titles of timelines and items and the names of tags;
- how you use the timeline viewer: switching views, zooming and jumping, search terms, tag filters, items you open, the date display, and how long you spend on a timeline;
- how you arrived at a timeline, for example from Explore, a share link, or another website's address;
- asking the help assistant a question: which help page you were on and whether you are signed in, never the text of your question;
- plan and billing steps: viewing plans, starting checkout, changing or cancelling a plan (never payment details, which only Stripe sees);
- reaching a plan limit, and errors from our API.
Each event also carries your plan, language, device type (mobile or desktop) and whether you are signed in and verified;
technical details that Mixpanel collects by default: browser, operating system, device type, screen size, the page address and the page you came from.

By default this is anonymous. Nothing is stored in your browser, so each page load counts as a new visitor, events are not linked to your account, and your IP address is not passed on.

If you accept analytics, your browser also sends and stores:

a random identifier in your browser (see the Cookie policy), so Mixpanel can recognise you between visits. While you are signed in, we link it to your internal account id, but never to your name or email address. It is reset when you sign out;
a profile linked to that identifier, with your plan, account creation date, whether your email address is verified, your site role, and how many timelines and teams you have and how much storage you use, but never your name or email address.

You choose in the notice shown on your first visit, and can change it at any time with Cookie settings in the footer. Ignoring the notice counts as declining.

Before an address is sent, we remove share link tokens and email verification or password reset tokens from it. Mixpanel requests go through our own servers. We use Mixpanel's EU data residency.

If your browser sends a Do Not Track signal, no analytics are sent at all.

Timelines embedded in other websites send no analytics.

Error reports and performance

We use Sentry to find and fix bugs. When something goes wrong in the app or on our servers, an error report is sent to Sentry. It contains technical details: the error, the page address, the browser and operating system, and the steps that led to it. For a sample of page loads we also send performance measurements. We remove share link tokens and verification or reset tokens from page addresses before they are sent. We don't record your screen, and our servers don't send your IP address or other identifying request data to Sentry.

Server logs

Our servers log each request: the time, method, path (without the query string), response status, duration and a request id. Our hosting provider may also keep network-level logs, including IP addresses, for security and operations.

Why we use it and our legal bases

We use personal data only for the purposes below, each on a legal basis under the GDPR:

Providing the service (contract, Article 6(1)(b)): creating and running your account, signing you in, storing and showing your content to the people you share it with, teams and collaboration, notifications, and the billing of your plan.
Keeping the service safe (legitimate interests, Article 6(1)(f)): securing accounts and sessions, preventing fraud, spam and abuse, rate limiting, and enforcing our Terms.
Fixing and improving the service (legitimate interests, Article 6(1)(f)): error reports, performance measurements, server logs and anonymous analytics, so we can find bugs and learn which features work.
Analytics that recognise you (consent, Article 6(1)(a)): the stored identifier, the link to your account and your IP address in analytics, only if you accept. You can withdraw consent at any time.
Answering you (legitimate interests, or contract when it concerns your account): replying to contact form messages and emails, and answering the questions you ask the help assistant, including when you have no account (we send the question to Vertex AI, and keep a daily count under a hash of your account id or IP address, to limit abuse and cost).
Meeting legal obligations (Article 6(1)(c)): keeping records the law requires, and responding to lawful requests from authorities.

Where we rely on legitimate interests, we have weighed them against your rights. You can object at any time (see "Your rights" below).

We don't sell your personal data, don't use it for advertising, and don't make decisions about you that are based solely on automated processing and have legal or similarly significant effects on you.

Service providers

We use service providers (processors) that handle personal data only on our instructions and under a data processing agreement:

Hosting: Google Cloud, in European Union. Runs our servers and database.
File storage: Google Cloud, in European Union. Stores images, audio, video, documents and voice memos.
Email delivery: Postmark. Sends sign-in codes, verification and password reset emails, invitations and notifications.
Google Cloud (Vertex AI), processed in the EU: generates the answers of the timeline assistant and the help assistant, and reads the documents you upload for an AI import. For the timeline assistant it receives your message, the conversation so far and the content of the timeline you are asking about. For the help assistant it receives your question, the conversation so far and your interface language. For an import it receives the files you upload and your instruction. For the timeline assistant and for imports we keep a usage record for each message and each part of a document read (who sent it, on which timeline, when, and the tokens and credits it used) for 13 months. For the help assistant we keep a count for each message (the day, a hash of your account id or IP address, and the tokens and credits used, with no timeline) for 35 days. We never keep the messages, the answers or the documents.
Mixpanel: product analytics, as described above.
Sentry: error reports and performance measurements, as described above.

Stripe

Stripe sells our paid plans as merchant of record. We share with Stripe your email address and the details needed to set up and manage your subscription. Stripe processes payment data as an independent controller.

Services your browser contacts directly

Google and Apple, when you choose to sign in with them.
Stripe, when you open checkout or the customer portal.
OpenFreeMap, which serves the map tiles when you open a map. Your browser requests the tiles from OpenFreeMap's servers, which then see your IP address and the map area you look at. No account information is sent.

These services act under their own privacy policies.

Other people

Content you make public or share with a link can be seen by anyone who has access to it (see the Terms). Your public profile shows your name, your handle and your public timelines.

Our staff

A small number of authorised people who run Timescrolly can access accounts and content when needed to provide support you asked for, to investigate reports of abuse or security issues, or when the law requires it.

Authorities and changes of ownership

We disclose personal data when the law requires it, for example in response to a valid court order. If Timescrolly is sold or merged, your data may pass to the new owner. They will be bound by this policy, and we will tell you beforehand.

International transfers

We aim to keep personal data in the European Economic Area. Some service providers, or their subprocessors, may process data outside it, for example in the United States. When that happens, we protect the transfer with the European Commission's Standard Contractual Clauses, or an adequacy decision such as the EU–US Data Privacy Framework, where available. You can ask us for a copy of the safeguards at [email protected].

How long we keep data

Your account and content: for as long as your account exists. Before we delete an account, the timelines and teams it owns are transferred to someone else or deleted; we then delete the account. Content in timelines owned by other people or teams stays with those timelines (see the Terms).
Deleted timelines and items: move to the trash, where they can be restored until the date shown there. That date is set when they are deleted, from the change-history window of the plan that funds them at that moment: currently 30 days on Free and 365 days on Pro and Team, and never less than 30 days. When the date has passed, we permanently delete them automatically, together with their images and files, normally within a few hours. The owner of a timeline can also delete them permanently straight away from the app. A single image or file that is removed from an item is deleted at once, without going to the trash.
Change history: every change is recorded. How far back you can see and restore it follows the plan that funds the timeline, as above. We may keep older entries so that they become visible again if the plan is upgraded, and we delete them after a retention period.
Timeline assistant usage: we keep the records for 13 months after the month the message was sent, then delete them automatically. If you delete your account, the records of your own credits are deleted with it, and those charged to a team's pool are kept without your name.
Help assistant usage: 35 days, then deleted automatically. If your account is deleted, the hash is erased from your records. The rest of the record is kept, linked to no one, until it is deleted after the 35 days.
AI imports: the files you upload are deleted as soon as they have been read, and at the latest when the import is discarded or expires. The drafts and their quotes are deleted when you add them to the timeline or discard the import. An import that is never finished expires, and its drafts are deleted with it: after 24 hours if it was never read, after 7 days if it is showing a sample, and after 30 days if it is waiting for your review. The record of an import (the file names and sizes, the credits it used and its outcome) is kept with the timeline's change history and deleted with it.
Sessions: they expire after 30 days without use, and when you sign out.
Sign-in codes and links: sign-in codes expire after 10 minutes, password reset links after an hour and verification links after 24 hours. We then delete them.
Unfinished uploads: an upload that was never finished is removed after 24 hours.
Billing records: we keep them as long as tax and accounting law requires. Stripe keeps its own records as the seller.
Contact messages and emails: as long as we need them to handle your request and any follow-up. Ask us if you want one deleted sooner.
Analytics and error reports: Mixpanel and Sentry keep them for the retention period set in our accounts with them. After that they are deleted.
Backups: deleted data can remain in backups for a limited time until they are overwritten.

Your rights

Under the GDPR you have the right to:

access the personal data we hold about you and get a copy of it;
rectify data that is wrong or incomplete (you can change your name yourself in your account settings);
erasure: have your account and data deleted;
restriction: ask us to limit how we use your data while a question about it is being resolved;
portability: receive the data you gave us in a structured, machine-readable format;
object to our use of your data based on legitimate interests, including analytics;
withdraw consent at any time, where we rely on your consent, without affecting what we did before.

Self-service export and account deletion are not available yet. Until they are, email [email protected] from the address on your account. We may ask you to confirm your identity. We answer within one month, and tell you if we need more time for a complex request.

You also have the right to lodge a complaint with a data protection supervisory authority, especially in the EU country where you live or work, or where you think the problem occurred. We'd appreciate the chance to address your concern first.

Children

Timescrolly is not meant for children under 16, and they may not create an account. If you believe a child under that age has given us personal data, email [email protected] and we will delete it.

Security

We protect your data with technical and organisational measures. Connections are encrypted. Passwords, sign-in codes and session tokens are stored only as hashes. Files are served through links that expire. Access to production systems is restricted. No system is completely secure, though. If we become aware of a breach that puts your rights at risk, we will tell you and the authorities as the law requires.

Changes to this policy

We will update this policy when the service or the law changes. The date at the top shows when it last changed. If a change materially affects how we use your data, we will tell you by email or in the app before it takes effect.

Contact

For questions about this policy or your data, email [email protected]. You can also use the contact form.