Privacy Policy

Stand / Last updated: 2026-10-21

This is a courtesy translation. Only the German Datenschutzerklärung is legally binding.

1. Controller

Sprint Zero UG (haftungsbeschränkt)
Wienburgstraße 23, 48147 Münster, Germany
represented by its managing directors Niklas Alexander Feldmann and Thomas Johannes Kraaibeek
Email: thomas@cronloom.io
Phone: +49 1590 6269275
Further details in the imprint.

We are not legally required to appoint a data protection officer and have not done so. Please direct all privacy questions to the address above.

2. Processing activities

2.1 Visiting the website

Our server processes technically necessary connection data (IP address, date and time, resource requested, volume transferred, status code, referrer, browser and operating system). Purpose: delivering the page, stability and security. Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in secure, trouble-free operation. Retention: the IP address can only appear in our reverse proxy's error log. We clear that log every week, so the address stays there for at most 7 days. The log files of our services contain neither the IP address nor the referrer. They rotate by size: each service keeps at most five files of 10 MB, the oldest entries are overwritten first, and a service's log files start over when we deploy a new version of it. How long an entry stays therefore depends on traffic and on our releases; at today's traffic it can be several months.

2.2 Account and use of the Service

For an account we process your name and email address and, depending on how you sign in, a password (stored only as a hash) or the identifier of your Google or GitHub account. In use, we process the content you enter: time entries, clients, projects, rates, budgets and settings. Purpose: performing the contract. Legal basis: Art. 6(1)(b) GDPR. Retention: until you delete your account, then erased within 30 days unless a statutory retention duty applies.

Providing this data is necessary to conclude the contract. Without an email address we cannot create an account.

2.3 Sign-in with Google or GitHub

If you sign in via Google or GitHub we receive your email address, name and a user identifier. Google and GitHub are independent controllers for the processing on their side. Legal basis: Art. 6(1)(b) GDPR.

2.4 Google Calendar connection (optional)

You can voluntarily connect your Google Calendar to turn appointments into time entries. We request read-only access to your calendars and store the access and refresh tokens issued by Google in order to maintain the connection. Legal basis: Art. 6(1)(a) GDPR (consent, given by granting access). Retention: until you disconnect it in the settings or delete your account. You may withdraw consent at any time with effect for the future; this does not affect the lawfulness of processing carried out beforehand.

Limited Use of Google user data: CronLoom’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: we use your calendar data solely to provide the features you asked for in CronLoom. We do not transfer it to third parties except as necessary to provide the service, for security purposes, or to comply with applicable law. We do not use it for advertising, and we do not allow humans to read it unless you have given explicit consent, it is necessary for security or to resolve a technical problem, or the law requires it. Calendar data is not used to train generalised AI models.

2.5 Email

Via the provider Scaleway (Transactional Email, Paris) we send the email about your account and contract: address verification, password resets, the welcome email with the contract confirmation, trial-ending notices, running-timer reminders, weekly summaries and budget alerts. Legal basis: Art. 6(1)(b) GDPR; for the contract confirmation Art. 6(1)(c) GDPR with § 312f(2) BGB; for timer reminders, summaries and alerts also Art. 6(1)(f) GDPR — our legitimate interest in keeping you informed about your tracking. These three contain an unsubscribe link, and the preferences can be changed in your account at any time.

If you join the waiting list, we store your email address, the language of the page and the place on the site you signed up from. We confirm the address with a confirmation email (double opt-in) and then write to you when CronLoom opens and at most once a month when something important about CronLoom changes. These emails, the confirmation included, are also sent via Scaleway (Transactional Email, Paris). Legal basis: your consent, Art. 6(1)(a) GDPR. Every email contains an unsubscribe link; after unsubscribing we send nothing more, not even a new confirmation, and keep the address only as a note that it is unsubscribed.

If we invite you to create your account before CronLoom opens, we also store when and by whom the invitation was sent, when it expires and, once you have created your account, when that was. The link in the invitation contains a random code of which we store only a hash; it is valid for 14 days and only for your address. Unsubscribing also voids the invitation. Legal basis: for the invitation your consent, Art. 6(1)(a) GDPR; for creating the account Art. 6(1)(b) GDPR.

For every email we send via Scaleway, including those in sections 2.11 and 2.12: Scaleway receives the recipient's address, the subject and the content. Depending on the email, that includes your name in the greeting and, in summaries and alerts, project and client names, hours and amounts. Scaleway deletes the content once the email is delivered or finally undeliverable, after 15 days at most, and encrypted backups of it after 7 days. The delivery records (sender, recipient, subject, timestamps and delivery status) are kept as long as our sending domain is set up there. Subjects name no project, client, hours or person; besides fixed wording they hold at most a number, such as the days left in a trial or the code for a shared report, which expires after 10 minutes. The delivery records let us show that and when an email was delivered, for example a confirmation the law requires. Legal basis for this is Art. 6(1)(f) GDPR. On request we have your delivery records deleted at Scaleway (section 6).

2.6 Reach measurement with Plausible

On our website we measure reach using Plausible Analytics, which we run on our own server in Falkenstein, Germany (pulse.cronloom.io); no data is transmitted to the vendor or any third party. We record the page requested, the referrer, an approximate country-level location, and coarse device and browser information. No cookies are set and no cross-device identifiers are created. To recognise repeat visits within a single day, a hash of IP address and browser signature is generated server-side; it rotates daily and cannot be reversed, and the IP address itself is not stored. In addition, we count a few interactions as events: completing a calculator (with the calculator's name and, for the calculator at the top of the homepage, the floor rate it computed), a click on a button that leads to the waiting list or to sign-up (with that button's place on the page), and a completed sign-up for the waiting list (with that place). These events contain no text you typed and no email address. Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in privacy-preserving reach measurement without profiling. Retention: aggregated statistics only, no individual profiles.

2.7 In-app product analytics

Inside the signed-in application we measure product use with PostHog (EU cloud, Frankfurt). This runs on two paths with two different legal bases: the analytics SDK in your browser, and a short list of events our server records when you perform them.

In your browser: the PostHog SDK only runs after you have consented in the application. A notice asks separately; you can allow or decline with equal weight and change your decision any time under Settings → Product analytics. Your decision is kept with your account, with the date and the version of this notice it answered. That way it applies wherever you sign in, never to someone else who signs in on the same browser, and we can show that you consented. If what it covers changes, the application asks again before measuring anything. Without consent the SDK is not even loaded, so nothing is measured or sent. It is cookieless (memory-only persistence), does not record sessions, and does not autocapture clicks. Legal basis: Art. 6(1)(a) GDPR — your consent, which you can withdraw at any time with effect for the future.

On our server: when you create an account, a time entry, a client or a project, set a floor rate, run an export, share a report, or change your plan, we record that it happened. These events carry your user id and the event name. Account creation may also carry the landing CTA that sent you here: a short placement label such as "hero", never a URL or page content. They never carry work content, and they neither read nor write anything on your device, so § 25 TDDDG does not apply to them. They are therefore not covered by the in-app consent decision. Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in understanding which parts of the product are used, without profiling for advertising. You can object as described in section 6.

Events on both paths are linked to your user id, which makes them pseudonymous rather than anonymous. Page paths that contain access tokens — such as shared client reports — are stripped before anything is sent. We do not send email addresses or other account content with these events. Landing-page reach measurement stays with self-hosted Plausible (section 2.6) and is separate.

2.8 Error reports

Crashes and server errors in the application and API are sent to Sentry (EU cloud, Frankfurt) so we can fix faults. Request bodies and user profiles are not sent. Tokens in URLs are stripped as in section 2.7. Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in keeping the service reliable.

2.9 Operational logs

The API writes operational logs (severity, message, NestJS context) to Better Stack in the EU so we can diagnose outages. We also run an uptime check against the public health endpoint. These logs are not used for product analytics or advertising. Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in operating and restoring the service.

2.10 AI quick add (optional)

The quick add turns a sentence like “yesterday 2.5h Acme website” into a proposed time entry. To do that we send the text you typed or dictated, together with the names of your projects, clients and tags, to Anthropic, PBC (USA). No other account content, email addresses or rates are transmitted. Under our contract Anthropic does not use this data to train its models and retains it only briefly for abuse prevention. A proposal is only booked once you confirm it. Legal basis: Art. 6(1)(a) GDPR — your consent, which we ask for separately before first use. You can withdraw it at any time under Settings → AI quick add with effect for the future; the feature switches off immediately.

Dictation: In the iOS app, speech is converted to text entirely on your device; audio never leaves it. In the browser, dictation uses your browser’s speech recognition. Where your browser supports local recognition (current Chrome versions), the audio stays in the browser; otherwise your browser’s vendor (Google or Apple) processes the audio under its own privacy terms — that happens through your browser, not on our behalf. The app tells you which case applies while you dictate.

2.11 Cancellation and withdrawal forms

On the pages Verträge hier kündigen (cancel a contract) and Vertrag widerrufen (withdraw from a contract) you can cancel or withdraw without signing in. We store every declaration sent there before any email goes out: whether it is a cancellation or a withdrawal, the email address for the confirmation, and what you enter in the form. For a cancellation that is your name, the name of the contract, the kind of cancellation (ordinary or extraordinary) and, if you give them, the reason for an extraordinary cancellation, a customer, contract or invoice number, and the date the contract should end. For a withdrawal it is your name and the contract you withdraw from. We also store the date and time of receipt to the millisecond, a hash of the content that tells us when the same declaration arrives twice, and the delivery status of both emails: whether and when each was sent, how many attempts it took, and the last delivery error. We do not store your IP address with the declaration. To keep the form from being flooded, the API counts in memory only how many requests came from one IP address in the past hour; that count lapses after the hour.

Purpose: receiving your declaration, confirming its content and the date and time of receipt to you by email as § 312k(4) and § 356a(4) BGB require, and being able to show that and when it arrived. Legal basis: Art. 6(1)(c) GDPR in conjunction with § 312k and § 356a BGB for receiving and confirming it, and with § 257(1) no. 2 and (4) HGB and § 147(1) no. 2 and (3) AO for keeping it. For the proof of receipt also Art. 6(1)(f) GDPR; our legitimate interest is being able to show what arrived and when if a cancellation or withdrawal is ever disputed. Recipients: the confirmation to you and the notification to our own mailbox, which carries a copy of what you entered, are sent via Scaleway (Transactional Email, Paris). Retention: each declaration is kept for six years from the end of the calendar year in which it arrived, then deleted automatically. This does not depend on your account and holds even if you delete it. The copy in our mailbox is deleted after the same period. A deleted declaration is gone from the database backups no later than 30 days after that (section 5).

2.12 Shared client reports

A CronLoom user can share a report on the time tracked for a client through a link and decide which email addresses may open it. When you open such a report, you enter your email address. If it is on the list, we send you an eight-digit code. For this we store your address, a hash of the code, when it expires, how often it was entered wrongly and how many codes went to the address in the past hour. When you enter the right code, we set a cookie that works for this one report only (section 8), and store a hash of it and when the device last opened the report. We record every opening with the address and the time; the person who shared the report sees this list. The page says so before you enter the code. We do not store your IP address for the share; for loading the page itself, section 2.1 applies.

Who is responsible: we process the list of addresses, the sending of the code, the verification of your device and the record of openings on behalf of the person who shared the report (Art. 28 GDPR, section 7). They are the controller for it and rely on their own legal basis, usually their contract with you or your company; send questions and requests about a shared report to them. We are the controller only for protecting our service against abuse: for this the API counts in memory how many requests came from one IP address in the past minute, and forgets it after that minute. Legal basis for that is Art. 6(1)(f) GDPR; our legitimate interest is keeping out unauthorised access (Recital 49 GDPR). Recipients: the code is sent via Scaleway (Transactional Email, Paris). Retention: a code is valid for ten minutes; we delete its record within a day after that. A device stays verified as long as the report is shared and your address is on the list. If it does not open the report for 180 days, the verification ends and we delete it. We delete the record of who opened the report and when after twelve months. Your address stays on the list until the person removes it, stops sharing or deletes their account. When they stop sharing, we delete everything that belongs to that share at once. If a link merely expires, it opens nothing any more and the periods above keep running. You can end the verification on your device yourself at any time ("End access on this device").

3. Recipients and processors

Beyond this we disclose personal data only with your consent or where legally required. We do not sell data and use no advertising networks.

4. Transfers to third countries

Personal data leaves the European Union in one case only: if you use the AI quick add (section 2.10), Anthropic, PBC (USA) processes the text you entered for it together with your project, client and tag names. This transfer rests on the EU Commission’s Standard Contractual Clauses (Art. 46(2)(c) GDPR); you can obtain a copy via the contact details in the imprint. Without your consent this transfer does not happen. All other processing stays in the EU: hosting (Hetzner, Germany), encrypted backups (Hetzner, Finland), email delivery (Scaleway, France), our mailbox (All-Inkl, Germany), in-app product analytics (PostHog, Frankfurt), error reports (Sentry, Frankfurt) and API logs (Better Stack, EU).

5. Retention

We keep personal data only as long as necessary for the purposes described. Account and content data are deleted within 30 days of the contract ending. The delivery records of your email at Scaleway are the exception; section 2.5 says how long they stay there. Declarations you send through the cancellation or withdrawal forms are kept as received business letters for six years (§ 257(4) HGB, § 147(3) AO), counted from the end of the calendar year in which they arrived, and then deleted automatically (section 2.11). How long we keep data on shared client reports is set out in section 2.12. We back up the database every night, encrypted, to Hetzner storage in Finland. Each backup is kept for at most 22 days, and the storage snapshots hold it for at most 7 days longer, so deleted data is gone from every backup no later than 30 days after its deletion. Once we issue invoices, the relevant records become subject to statutory retention periods — accounting records are kept for eight years under German tax law, running from the end of the calendar year in which the record arose. During that period processing is restricted to storage.

6. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20), and to withdraw consent with effect for the future (Art. 7(3)).

Right to object under Art. 21 GDPR: You have the right to object at any time, on grounds relating to your particular situation, to processing of your personal data based on Art. 6(1)(f) GDPR. This applies in particular to reach measurement and product analytics. We will then stop processing unless we can demonstrate compelling legitimate grounds that override your interests. An informal message, for example by email to thomas@cronloom.io, is sufficient.

You can also export and delete your data yourself under Settings → Privacy & data.

You further have the right to lodge a complaint with a supervisory authority. The authority responsible for us is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen, Kavalleriestr. 2–4, 40213 Düsseldorf, Germany.

7. Processing on behalf of our users

When you record data about your own clients in CronLoom, you are the controller and we act as processor under Art. 28 GDPR. This includes shared client reports: the addresses you allow to open a report, the codes sent to them and the record of who opened it when (section 2.12). Informing your clients about this is up to you as the controller. We provide a data processing agreement free of charge on request at thomas@cronloom.io.

8. Cookies and local storage

Signing in sets strictly necessary cookies: your session, and short-lived values that carry a Google or GitHub sign-in through to the end. They are essential for the service you requested and therefore require no consent. The same holds for the cookie with which a verified device opens a shared client report without a new code (section 2.12): we set it only after you enter the code, it holds nothing but a random identifier, works for that report only and expires 180 days after the last opening. We set no advertising or tracking cookies. Beyond that, the application keeps a few entries in your browser's local storage so it works the way you left it: your product analytics decision (which is also kept with your account, section 2.7), your theme and language, the project and description your last timer used, and, if you arrived from one of our calculators, the rate you entered there. These entries stay in your browser and are not read on our servers.

9. Changes to this policy

We update this policy when our processing or the legal situation changes. The version published on this page applies.