Privacy policy
This is a translation. The German version is legally binding; for consumers residing in the USA or in Canada, § 12 (1) of the Terms applies. The German original is available at trackplanner.io/datenschutz.
1. Controller
The controller within the meaning of the GDPR is:
Georg Wächter Prinzessinnenstraße 29 12307 Berlin Germany Phone: +49 179 5644922 Email: info@trackplanner.io
2. General
We take the protection of your personal data seriously and treat it confidentially and in accordance with the statutory provisions (GDPR, BDSG, TDDDG). This policy applies to the website trackplanner.io and equally to the web app at app.trackplanner.io (accounts, plans, payment); the app refers to this privacy policy. The app Trackplanner Kids for tablets has its own privacy policy (section 9i).
Changes to this policy. If we change this privacy policy, we publish the new version on this page; the “Last updated” date at the end of the page shows the day of the last change.
“Do Not Track”. We do not track what you do on other websites over time. We therefore do not respond differently to “Do Not Track” signals from your browser.
Third parties that collect data themselves. Some third parties may, under their own privacy policies, collect information about your activities over time and across different websites when you use our services: Google, as soon as the web app shows the “Continue with Google” button (section 9, “Sign-in with Google”), and YouTube, when you start a video (section 6a); retailers and partner programs, after you click a purchase link (section 9c).
3. Hosting
This website is hosted by Vercel Inc., 440 N Barranca Avenue #4133, Covina, CA 91723, USA. On our behalf, the provider processes, among other things, access data (see server log files). The legal basis is our legitimate interest in secure, efficient provision (Art. 6 (1) (f) GDPR). A data processing agreement (DPA) pursuant to Art. 28 GDPR is in place. A transfer to the USA is possible; Vercel Inc. is certified under the EU-US Data Privacy Framework, and standard contractual clauses are in place in addition.
4. Server log files
When the pages are accessed, information that your browser transmits is collected automatically (browser type/version, operating system, referrer URL, host name, time, IP address). This data serves the technical delivery and security and is not combined with other data. Legal basis: Art. 6 (1) (f) GDPR.
4a. Error diagnostics in the web app (Sentry)
In the web app (app.trackplanner.io), we use the service Sentry of Functional Software, Inc., 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA, for error diagnostics. The error data is stored in the EU (data center in Frankfurt am Main). Sentry is not used in embedded plan views (including on third-party sites), and on this website (trackplanner.io) only in one case: the campaign page shows the import preview of the web app as an embedded window (section 6b); there, error diagnostics run as in the web app.
No error reports in kids’ profiles and in the app Trackplanner Kids. As long as a kids’ profile is active in the web app (section 9g) or, for example directly after reloading, it is not yet clear which profile is active, the web app does not send any error reports to Sentry: it discards every error event, does not remember any recently used tools, commands and routes and does not create an entry for crash detection. In the parent profile, error diagnostics run as described here. The app Trackplanner Kids does not contain Sentry (section 9i).
Purpose is detecting and fixing technical errors (program errors, crashes, frozen views) — not analyzing your usage behavior.
Data processed: error message and stack trace; browser, operating system, device and graphics card (e.g., processor cores, memory, GPU name); app version; the visited route without parameters (e.g., “/plan/:planId”); names of the most recently used tools and commands; key figures of the open plan without its content (e.g., number of tracks, track systems used); address (host and path without parameters), method and status code of the app’s most recent network requests, and the most recently visited routes without parameters; in addition, app attributes of your session: plan tier (without account, free or Premium), unlock level for early-access features, language, the active view (2D/3D) and the display mode (browser or installed app). No storage of the IP address (it is switched off in the service) and no plan content (no coordinates, names, texts or images). From the IP address that technically arises during transmission, Sentry derives a rough location (country and city) before discarding it and stores only this.
Pseudonymous user ID: If you are signed in, an error event is linked to your internal, pseudonymous account ID (no email address, no name) so that we can recognize related errors. Your rights (section 10, in particular access and erasure) also extend to this data. Deleting your account does not delete it automatically — it expires at the latest with the storage period; on express request, we delete it earlier.
Legal basis is our legitimate interest in an app that works without errors (Art. 6 (1) (f) GDPR). A data processing agreement (DPA) pursuant to Art. 28 GDPR is in place with Sentry. Insofar as access from the USA by Functional Software, Inc. or its subcontractors is possible, the transfer takes place on the basis of the European Commission’s adequacy decision on the EU-US Data Privacy Framework (Art. 45 GDPR), under which Sentry is certified; in addition, standard contractual clauses of the European Commission have been agreed (Art. 46 (2) (c) GDPR). Storage period: at most 90 days, after which the error events are deleted automatically.
Device storage: To be able to detect crashes, the app places a small entry per browser tab in your browser’s local storage (key tp.sw.*: start time, last sign of life, app version, route without parameters, names of the most recently used commands) as well as a random tab identifier in the tab’s session storage (tp.sw.id, ends with the tab). The entry is deleted when the page is closed normally; if it remains after a crash, it is evaluated and deleted the next time the app is opened — if the crash was more than 7 days ago, it is deleted without evaluation. If you do not open the app again, the entry remains in your browser until you delete the website data; it then never leaves your device. As long as a kids’ profile is active, the app does not create this entry and removes an existing one. These entries are technically necessary for the service you use (Section 25 (2) TDDDG).
5. Cookies and storage in your browser
We do not use cookies for analytics or advertising purposes and therefore do not need a consent banner. On this website, we only place entries that are necessary for a function you have requested (Section 25 (2) no. 2 TDDDG):
- Cookie
tp-lang(language selection): is only set when you switch the language in the footer or open an address with?lang=de, and makes sure that we do not automatically redirect you to the other language again. Content:de,enorja. Duration: 1 year. The same value is also stored in your browser’s local storage (localStorage, keytp-lang). - localStorage
tp-glossar-view: remembers whether you want to view the glossary sorted alphabetically or by topic. - sessionStorage
tp-partner-hinweis(partner notice): if you come via one of our partners (address withpartner=…or its partner page), a small notice at the bottom right names it. Only once you click in it (minimise, set as your retailer, undo) does the tab remember, until it is closed, which partner that was and what state the notice is in, so that it stays that way on the next page.
These entries do not leave your device, except for the cookie tp-lang, which your browser sends to our host with every page request (section 3). You can delete them in your browser at any time; the website then falls back to automatic language detection and the alphabetical view, and the partner notice to its expanded form.
If you come here from another website or via a link with campaign parameters (utm_…), the links on this website append your origin to their address so that the web app learns it when you register (section 9e). We do not store anything in your browser for this; the information is carried as parameters in the address of the pages.
Setting a retailer in the partner notice. If you set the partner as your retailer in the notice, the links on this website into the web app then carry the addition partner_wahl=1. If you click such a link, your browser sends the web app the full address of the page you come from (referrer) instead of only https://trackplanner.io as usual. The web app uses it to check whether you made the setting on a page of trackplanner.io with the same partner (section 9b). As with every page request, the address may appear in the server log files (section 4). The legal basis is our legitimate interest in adopting a setting only if you really made it on our website (Art. 6(1)(f) GDPR). If you undo the setting in the notice, the links no longer carry the addition, and your browser again sends only https://trackplanner.io.
Prices and home page for your country. On the English home page and the English pricing page, your browser asks for the country you are visiting from. For this we only read the country code (for example “US”) that Vercel derives from your IP address, and for a visit from Canada also the province code, and use it to show you the prices, offers and payment methods for your country. If you visit from the United Kingdom and the language setting of your browser does not already show this, we also use the country code to show you a heading, text and pictures for railway modellers in the United Kingdom on the English home page. We do not store the result and store nothing in your browser for it; like every page request, the request itself is covered by section 4 (server log files). If no country code arrives, we show prices in euros and the general version of the home page. The legal basis is our legitimate interest in showing you the prices and offers that apply in your country and in adapting the home page to your country (Art. 6 (1) (f) GDPR).
Which entries the web app (app.trackplanner.io) places in your browser is described in section 9b.
6. Cookie-free audience measurement (Vercel Web Analytics)
On this website (trackplanner.io), we measure reach with Vercel Web Analytics of Vercel Inc., 440 N Barranca Avenue #4133, Covina, CA 91723, USA — the same provider that hosts the website (section 3). We do not use Vercel Web Analytics in the web app (app.trackplanner.io).
- Purpose: aggregated statistics on which pages are accessed how often and where visitors come from, in order to improve the website. We only evaluate aggregated figures, not individual visitors.
- Data processed per page view (according to Vercel): time, accessed address (URL and page pattern), referring page (referrer), filtered parameters of the address, rough location (country, region, city), operating system and browser, each with version, device type (mobile, desktop, tablet) and the version of the measurement script.
- No cookies: The measurement script is loaded from our own address (
/_vercel/insights/script.js). Vercel states that it works without third-party cookies; according to our review (version of 09/30/2026), the script does not set any cookies. When loading, it queries an entry in your browser’s local storage (__va_attribution), but only creates it if a website expressly assigns a user identifier to its visitors — we do not do that. To distinguish visitors, Vercel forms a hash value from the incoming request; this is discarded after 24 hours. Recognition across days or across other websites does not take place. - Legal basis: our legitimate interest in aggregated audience measurement to improve the website (Art. 6 (1) (f) GDPR).
- Processing on behalf and third country: Vercel processes the data on our behalf; the data processing agreement from section 3 applies. A transfer to the USA is possible; Vercel Inc. is certified under the EU-US Data Privacy Framework (adequacy decision, Art. 45 GDPR), and standard contractual clauses are in place in addition (Art. 46 (2) (c) GDPR).
- Storage period: Vercel provides the evaluation in our plan for one month but reserves the right to store the data longer; Vercel does not state a fixed deletion period.
- Objection: You can object to the measurement at any time (Art. 21 GDPR). Because we do not recognize individual visitors, the most effective way to implement the objection yourself is to block the script
/_vercel/insights/script.jsin your browser (for example with a content blocker); the website then works unchanged.
Further information: vercel.com/docs/analytics/privacy-policy.
6a. YouTube videos in tutorials
Tutorials on this website may contain a video from YouTube. It is only loaded when you click on the preview image; before that, the page does not establish any connection to YouTube (the preview image is on our own server). With the click, the page loads the player in the privacy-enhanced mode of YouTube (youtube-nocookie.com); the provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Google receives your IP address, information about your browser and the address of the page; once playback starts, YouTube may use cookies or similar technologies. The legal basis is your consent given by clicking (Art. 6 (1) (a) GDPR, Section 25 (1) TDDDG); you withdraw it by reloading the page and no longer starting the video. Google may also process data in the USA; Google LLC is certified under the EU-US Data Privacy Framework (Art. 45 GDPR). More information: policies.google.com/privacy.
6b. Content from our web app and preview images
Some pages of this website show content from our web app and from our storage without you having to click:
- Plan cards, among others in the plan gallery, on the home page, on the track system pages and on the manufacturer pages: the preview image of a plan from our storage at Supabase (hosting in the EU, Frankfurt region) and, where available, a 3D view of the plan from app.trackplanner.io. If a preview image is missing, the page asks our server at Supabase to create it.
- The photos on partner pages (section 9n), loaded from our storage at Supabase.
- The image of a plan in blog posts, loaded from app.trackplanner.io.
- The import preview on the campaign page, embedded from app.trackplanner.io. If you select an AnyRail or WinTrack file there, it is transferred to our servers at Supabase for conversion even without an account (other formats are converted by your browser itself); we do not store the file, only a log line without the file name (error class, coverage, unrecognized articles, a checksum of the file), which we delete after 180 days. To protect against abuse, we count requests via a salted hash value of the IP address (as in section 7).
- Help clips (short videos) on the help and knowledge pages, in tutorials and on the home page, partly from this website, partly from our storage at Supabase. When the page is opened, it loads the preview image and, depending on the page, the subtitles and the details of the video (such as length and format); it loads the video itself when you play it or, on the home page, when it comes into view.
app.trackplanner.io is delivered via Vercel (section 3). Vercel or Supabase technically receive your IP address and information about your browser in the process. The embedded web app may place entries in your browser’s storage (section 9b); error diagnostics also run in the import preview (section 4a). The interactive plan view in blog posts only loads after a click. The legal basis is our legitimate interest in a clear presentation of our offer (Art. 6 (1) (f) GDPR).
7. Contacting us
If you contact us by email, we process your details to handle the inquiry (Art. 6 (1) (b) or (f) GDPR). Your email is stored in the provider’s mailbox; Migadu (Switzerland) is used as the mailbox service. An adequacy decision of the European Commission exists for Switzerland. The emails are read and answered in a Gmail account of the provider, with the help of AI agents (see “How we handle messages” below). The data is deleted as soon as it is no longer required and no retention obligations prevent this.
Contact form. At trackplanner.io/kontakt (English: /en/contact, Japanese: /ja/contact; also in the website’s other languages, e.g. /fr/contact), you can write to us using a form.
- Data processed: your email address and your message (mandatory), your name (optional), the language code of the page and the time of sending. To fend off automated submissions, we also check a field invisible to humans and the time between opening the page and sending; neither is stored.
- Purpose: handling and answering your inquiry; if it contains feedback on Trackplanner, also evaluating that feedback (see “How we handle messages” below).
- Abuse protection: As with the waiting list, we count submission attempts per sender. For this, we do not store your IP address, but only a salted hash value of it (for IPv6, of the /64 prefix) together with the time window and number of attempts; a job running every hour deletes these entries again. They are stored in our database at Supabase (hosting in the EU, Frankfurt region) as processor. The legal basis is our legitimate interest in a functioning offer free of abuse (Art. 6 (1) (f) GDPR).
- Legal basis: Art. 6 (1) (b) GDPR insofar as your inquiry is aimed at a contract, otherwise our legitimate interest in answering inquiries (Art. 6 (1) (f) GDPR).
- Transfer: Your message itself is not stored in a database, but delivered directly as an email to info@trackplanner.io. Sending is handled by the email service Resend of Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA, as processor; a transfer to the USA is possible. Plus Five Five, Inc. is certified under the EU-US Data Privacy Framework (Art. 45 GDPR), and standard contractual clauses have been agreed in addition (Art. 46 (2) (c) GDPR). If Resend fails or its quota is exhausted, the email service Brevo of Brevo GmbH, Köpenicker Str. 126, 10179 Berlin, Germany, takes over sending as a substitute, as a further processor; a data processing agreement pursuant to Art. 28 GDPR is in place. Brevo also uses sub-processors outside the EU (including in the USA and in India); a transfer there is possible and takes place on the basis of standard contractual clauses of the European Commission (Art. 46 (2) (c) GDPR), and for recipients in the USA that are certified under the EU-US Data Privacy Framework, also on the basis of this adequacy decision (Art. 45 GDPR). The email is stored in the provider’s mailbox; Migadu (Switzerland) is used as the mailbox service. An adequacy decision of the European Commission exists for Switzerland. It is read and answered as described below under “How we handle messages”.
- Storage period: as described below under “How we handle messages”.
Message to the provider from the web app. In the web app (app.trackplanner.io), you can write to us directly from the editor (“Write to me”). Using the editor requires an account; the message is assigned to your account.
- Data processed: your message, an optional subject, the email address and display name of your account, the account identifier, the language code and the time of sending, as well as technical information to classify the problem: app version, browser/operating system, window size and language of your browser, your subscription tier, identifier, title and link of the plan you are currently working in, and — if an error occurred shortly before — the identifier of the associated error report (see section 4a); in addition, the tool currently active, the view (2D or 3D) and your last up to 30 working steps in the editor with how long before sending each one happened (only the kind of step, such as “track placed” or “tool changed”, no content). If it is selected in the dialog, an image of the drawing area is added, as you see it when you open the dialog (2D and/or 3D view, without the other controls); for a bug report it is preselected. For a bug report we also attach the current state of the plan as a file. The image and the plan file are sent as attachments to the email.
- You see what is sent along before you send (“What I’m sending along”), with a preview of the image. You can deselect the image; if you deselect the plan reference, neither the image nor the plan file is sent.
- Send a reference: If track pieces are missing from the track catalogue because we lack the manufacturer’s dimensions, you can use “Send a reference” to send us photos or PDF files (up to four, for example a photo of the piece next to a ruler, of its box or of a catalogue page) and a text. The track system and the list of pieces missing there are sent along, as are the email address, display name and identifier of your account, the language code, app version, browser/operating system, window size and browser language and your subscription tier; the image of the drawing area, the plan reference, the plan file, the editing steps and the identifier of an error report are not sent. The web app reduces photos in your browser before sending; the files are sent as attachments to the email, in the same way as above (Resend or, as a fallback, Brevo; mailbox at Migadu). The purpose is to determine the dimensions of the track piece for our track library and to reply to you; the legal basis is our legitimate interest in a complete and correct track library and yours in having the piece added (Art. 6(1)(f) GDPR). We only take the dimensions and do not publish your pictures; in the documentation of the library we refer to the reference without your name. We keep the email with its attachments until the piece has been added or we have discarded the reference, for at most 24 months; then we delete it. If a photo shows people or private rooms, please crop it beforehand so that only the track piece is visible.
- Purpose: handling and answering your inquiry and fixing reported errors; if it contains feedback on Trackplanner, also evaluating that feedback (see “How we handle messages” below).
- Legal basis: Art. 6 (1) (b) GDPR insofar as it concerns the functioning of the user agreement concluded with you, otherwise our legitimate interest in answering inquiries and improving the offer (Art. 6 (1) (f) GDPR).
- Transfer: Your message is not stored in a database, but delivered directly as an email to info@trackplanner.io. The same service providers as above for the contact form apply to sending and mailbox: Resend (Plus Five Five, Inc., USA) as processor (a transfer to the USA is possible, basis as above: Data Privacy Framework, in addition standard contractual clauses) or, as a substitute, Brevo (Brevo GmbH, Berlin), basis as above, and Migadu (Switzerland) as mailbox service (adequacy decision of the European Commission); it is read and answered as described below under “How we handle messages”.
- Abuse protection: We limit the number of messages per account and time window. Counting is done via a salted hash value of your account identifier in our database at Supabase (hosting in the EU, Frankfurt region); a job running every hour deletes these entries again. No IP address is processed for this — unlike with the website’s contact form, because an account exists here. The legal basis is our legitimate interest in a functioning offer free of abuse (Art. 6 (1) (f) GDPR).
- Storage period: as described below under “How we handle messages”.
Enquiries from businesses. Using the form at trackplanner.io/en/for-businesses/enquiry (German: /fuer-unternehmen/anfrage), manufacturers, retailers and service providers can enquire about a partnership.
- Data processed: role, company, country and email address (required), website, contact person, language of the reply, the optional additional questions and the message, the consents with time and version of their wording, and the status of the enquiry and our replies. To fend off automated submissions, we check a field invisible to humans and the time between loading the page and sending, and count submissions per day using a salted hash of the IP address (not the IP address itself); we delete these counters after two days.
- Confirmation: After you send the form, we send an email with a confirmation link. We only process the enquiry once it is confirmed. This way nobody can request an offer for someone else’s address.
- Purpose and legal basis: preparing a partner agreement (Art. 6 (1) (b) GDPR); the protection against misuse is based on our legitimate interest in a working service (Art. 6 (1) (f) GDPR).
- Reminders: We remind you about an answered enquiry at most twice and only if you agreed to this in the form (Art. 6 (1) (a) GDPR). You can withdraw this consent at any time using the link in the reminder or by email to info@trackplanner.io. We only send partner news after a separate confirmation.
- Storage period: We delete unconfirmed enquiries after 30 days and confirmed enquiries without a contract 24 months after the last email or change. If a partner agreement is concluded, we keep the enquiry for its duration.
- Recipients: Data is stored in our database at Supabase (hosting in the EU, Frankfurt region); emails are sent by Resend or, as a fallback, Brevo as described for the contact form above, and the mailbox is hosted by Migadu (Switzerland); the emails are read as described below under “How we handle messages”.
How we handle messages. This applies to all emails received at info@trackplanner.io: emails to us, messages sent via the contact form and from the web app, replies to our emails, enquiries from businesses and the notification emails we receive about new waitlist sign-ups and new accounts (sections 8 and 9).
- Gmail: Besides the mailbox at Migadu, the messages also reach a private Gmail account of the provider at Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). We read and answer them there, and they remain stored there until we delete them. There is no data processing agreement with Google for this account; Google processes the data under its own terms and privacy policy (policies.google.com/privacy). Google may also process data in the USA; Google LLC is certified under the EU-US Data Privacy Framework (Art. 45 GDPR).
- AI agents: AI agents working with the AI service Claude from Anthropic help us read, sort, translate and answer messages. They read the messages in full, including names, email addresses, attachments (such as the image of the canvas and the plan file from the web app) and everything you write. They look up in our database whether you have an account, since when, when you last used Trackplanner, the country of registration, scale and track system from your settings, your tier (Free or Premium, subscription, trial or unlock), the number of your plans, the summarized counters of your usage and whether you take part in test versions; they do not read the usage history from section 9e. They write draft replies; Georg Wächter sends replies to your message himself, and the agents do not send any emails from the mailbox. For this we use a Claude subscription under Anthropic’s consumer terms, not a commercial access. The contracting party is Anthropic, PBC (USA); according to Anthropic’s privacy policy, the controller for customers in the European Economic Area is Anthropic Ireland, Limited (Dublin, Ireland), which also has data processed in the USA. There is no data processing agreement with Anthropic for this; Anthropic processes the data under its own terms and privacy policy (anthropic.com/legal/privacy) and, according to that policy, bases transfers to countries without an adequacy decision on standard contractual clauses. We have not agreed any safeguards of our own under Art. 46 GDPR with Anthropic for this. In our account, the use of content to improve Anthropic’s AI models is switched off. Under its terms, Anthropic may still use content for this if it is flagged for safety review (for example for a possible breach of its usage policy) or if we send it to Anthropic as feedback.
- Inquiries in Japanese: If you write to us in Japanese, the AI agents translate your message and our answer; the previous point applies.
- Register of feedback: If a message contains feedback on Trackplanner (such as praise, criticism, an error or a wish), we record it in an internal register. This way no feedback gets lost, we can derive wishes from many pieces of feedback, and we can write to you when your wish has been implemented. The register contains the date of receipt, the type of feedback, a summary, short verbatim excerpts that say something about Trackplanner, a short history of the conversation, language, country, tier (Free or Premium), scale and track system, general details of the layout, the topics, the status of the reply, open points, details such as interest in test versions or a quote approval, the assigned wishes, references to other entries of yours, an identifier of the email thread and, if you have an account, your internal account ID. Names, email addresses, telephone numbers, postal addresses and private details do not go into the register. We also record feedback from the feedback portal there (section 9d), without verbatim excerpts, and the answers to the survey after a purchase (section 9f) in summarized form. The register is kept in a non-public repository at GitHub (GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA) as processor; GitHub’s Data Protection Agreement applies (Art. 28 GDPR). A transfer to the USA is possible; GitHub, Inc. is certified under the EU-US Data Privacy Framework (Art. 45 GDPR), and standard contractual clauses apply in addition (Art. 46 (2) (c) GDPR). The AI agents write and maintain the register.
- Quotes: We only show a sentence of yours on our website if you have agreed in writing beforehand to the exact wording (Art. 6 (1) (a) GDPR). It appears with the form of your name that you give us; if you give none, with your first name, the first letter of your surname and your country (for example “Lukas S., Germany”). We tell you this before publication. On pages in other languages we show our own translation of the sentence and mark it as a translation. You can withdraw your consent at any time; we then remove the sentence from the website.
- Legal basis: our legitimate interest in answering inquiries promptly and in your language, in not losing any feedback and in improving Trackplanner according to its users’ wishes (Art. 6 (1) (f) GDPR); where your contract is concerned, Art. 6 (1) (b) GDPR.
- Storage period: We keep the emails in the mailbox at Migadu and in the Gmail account for at most three years after your last message; we then delete them unless statutory retention obligations prevent this. For the notification emails from sections 8 and 9, the periods stated there apply if they are shorter. What the AI agents read and write is stored in the history of our Claude account at Anthropic; we delete these histories at the latest one year after the session. According to its privacy policy, Anthropic removes deleted histories from its systems within 30 days; for content flagged for safety review, Anthropic’s periods apply. We keep entries in the register as long as we need the feedback for the further development of Trackplanner, at most three years after your last message. If you request erasure or object, we remove your entries earlier. The register is kept with version control (Git): removed entries disappear from the current state but remain in full and without time limit in the version history, including in copies of the repository. After your account and your emails have been deleted, they can no longer be linked to you.
- Objection: You can object at any time to the handling by AI agents and to the entry in the register (Art. 21 GDPR); an email to info@trackplanner.io is sufficient. The objection applies to the future; we may still read the email containing the objection itself in the way described.
Contact from the error page. If the web app crashes, the error page offers a mail link. This opens your own email program with a prepared subject and the identifier of the error report; nothing is sent without your action, and no data is transmitted to us before you send the email yourself.
8. Launch waiting list (email sign-up)
On our home page, you can sign up for a waiting list with your email address in order to be notified at the launch of Trackplanner and to receive the launch benefit.
- Data processed: email address, language code, timestamps of sign-up/confirmation, of sending the launch email and of any unsubscription, and a sequential position number.
- Double opt-in: After you enter your address, we send you a confirmation email. Your sign-up only becomes effective when you click the confirmation link — this is how we make sure that the address really belongs to you.
- Purpose: notification of the launch and allocation of the founding member benefit (6 bonus months when taking out the yearly Premium, Terms § 5b). If consumers with habitual residence in Japan order via the Ordering Process for Japan (prices in yen), the benefit does not apply (Terms § 11 (5)).
- Legal basis: your consent (Art. 6 (1) (a) GDPR).
- Sending of emails: via the email service Resend (Plus Five Five, Inc., USA) as processor (address and basis of the transfer to the USA as in section 7 for the contact form: Data Privacy Framework, in addition standard contractual clauses) or, as a substitute, via Brevo, section 7.
- Storage: in our database at Supabase (hosting in the EU, Frankfurt region) as processor.
- Notification of the provider: As soon as you have confirmed your sign-up, this additionally triggers a notification email to the provider (contact address see imprint); an unconfirmed sign-up does not trigger one. It contains the email address provided, the language code, the origin of the form, your waiting list position and the time of confirmation. This email is stored in the provider’s mailbox; Migadu (Switzerland) is used as the mailbox service. An adequacy decision of the European Commission exists for Switzerland. It is read as described in section 7 under “How we handle messages”. The notifications are deleted together with the waiting list data, at the latest after the end of the launch campaign or upon your request for erasure.
- Abuse protection: To prevent mass sign-ups via the form, we count sign-up attempts per sender. For this, we do not store your IP address, but only a salted hash value of it (for IPv6, of the /64 prefix) together with the time window and number of attempts; a job running every hour deletes these entries again. The legal basis is our legitimate interest in a functioning offer free of abuse (Art. 6 (1) (f) GDPR).
- Withdrawal/erasure: You can withdraw your consent at any time with effect for the future — via the unsubscribe link in the launch email or by writing to us (an email is sufficient). An unsubscription sets a note on your entry so that we do not contact you again; the other data mentioned above initially remains stored. Upon your request for erasure, we delete your entry completely. At the latest after the end of the launch campaign, we delete the waiting list data unless there is further consent (e.g., account or newsletter).
9. Web app, accounts & payment
Registration, storage of track plans and the paid subscriptions are handled via the web app (app.trackplanner.io). Like this website, the web app is delivered by Vercel (section 3); accounts, plans and subscription data are stored in our database at Supabase (hosting in the EU, Frankfurt region) as processor. This privacy policy applies to processing in the web app. The app Trackplanner Kids for tablets has its own privacy policy (section 9i).
Account and plans.
- Data processed: email address, password (stored only as a hash value by Supabase’s auth service), display name, language and settings, the time of your last use, aggregated usage counters of your account (such as the number of plans created and tracks placed), your plans including versions, inventory lists and shares with other accounts, as well as records of imports and of your confirmations when publishing.
- Purpose and legal basis: provision of the web app under the user agreement (Art. 6 (1) (b) GDPR).
- Emails about your account: For example, to confirm your email address, reset your password, send a sign-in link or change your email address (then to the new and, where applicable, also to the previous address), we send you emails with a link. For this, we transmit your email address and the content of the email to the email service Resend or, as a substitute, Brevo, both as processors (address and basis of the transfer as in section 7 for the contact form).
- Import files: If an import fails or remains incomplete, we keep the uploaded file for up to 90 days. We use it to find the error and to write to you if the import works better later; you can unsubscribe from this in the email settings. For every import we also store a checksum of the file (SHA-256) so that we can tell whether you have already imported the same file successfully. If you delete your account, we delete the file immediately.
- Storage period: as long as your account exists. We do not delete plans on our own; a plan that you delete is kept in the trash for one year and then deleted permanently. We delete logs of file imports after 180 days and uploaded import files after 90 days. If you delete your account, we delete your private and unlisted plans; public plans are retained but detached from your account, and your display name is removed from them — likewise from copies that others have made of your plans. Such plans then appear without an author or as “by a Trackplanner user”; in caches (at our host and in visitors’ browsers), the name may still appear for a transitional period — for gallery and plan pages and the other embeddings usually within one day, for embedded plan views with a fixed version for up to one year.
Public plans and gallery. If you publish a plan (with free accounts, plans are always public, Terms § 7), the following can be accessed by anyone: title, description, the plan itself, a preview image, key figures such as dimensions, track systems and view count, and your display name as author. They appear in the gallery of the app, on trackplanner.io under “Track plans” and in embeddings on other websites. You can change the display name in the account settings; when signing in with Google, it is pre-filled with your name at Google. If you work on a plan together with others, they see your display name (or, if there is none, your email address) and your changes.
Images in plans. Images that you upload into a plan are stored in our storage at Supabase under an address that is hard to guess and contains your account ID. This address can be accessed without signing in — even for private plans, if someone knows it. Therefore, do not upload any images that nobody but you should see.
Invitations and shares. If you invite someone to a plan by email address, we store this address with the invitation and send it an invitation email (sent via Resend or, as a substitute, Brevo, section 7). The invitation is deleted as soon as the invited person creates an account; otherwise it exists until you revoke the share or the plan is permanently deleted (after the trash, section above) — even after your account is deleted, insofar as the plan is retained as a public plan. The legal basis is our legitimate interest and yours in sharing plans with others (Art. 6 (1) (f) GDPR).
Reports of public plans. If you report a public plan (“Report”), we store your account ID, the reason, your note and the processing status; we inform you about our decision by email; if we remove the plan, we also inform the author about the reasons (sent via Resend or, as a substitute, Brevo, section 7). The legal basis is the fulfillment of our obligations to handle notices (Art. 6 (1) (c) GDPR in conjunction with Art. 16, 17 Digital Services Act). A fixed deletion period for reports has not yet been set.
Payment via Stripe. Payments are processed by Stripe (Stripe Payments Europe, Limited, Ireland) as payment service provider. After completion, we send you a contract confirmation by email (sent via Resend or, as a substitute, Brevo, section 7). We transmit your email address and your internal account ID to Stripe; you enter your billing address and payment details directly at Stripe; from Stripe, we store the subscription status, the Stripe identifiers of customer and subscription, the country of the billing address and the invoice amounts, and for each payment also the product purchased (e.g., annual plan or Premium Pass) and the type of payment method (e.g., card, direct debit, Klarna), but no card or account details. If the billing address is in Canada, we check whether it is in Québec (Terms § 12 (7)): at completion and, if Stripe already has your address from an earlier order, as soon as you start the order. If your billing address is on the Isle of Man or you order from the United Kingdom without Link, we exclude the purchase (Terms § 13 (1)): we check this at completion and, if Stripe already has your address from an earlier order, as soon as you start the order. If it only turns out at completion, we end the contract and refund the amount paid. If Stripe has stored an address for you in the United Kingdom or on the Isle of Man, or if the billing address of your last purchase was there, the customer portal does not offer a change of plan. The legal basis is the performance of the contract (Art. 6 (1) (b) GDPR) and, for the invoice data, the fulfillment of statutory retention obligations (Art. 6 (1) (c) GDPR); we keep them as long as these obligations exist. We evaluate sales per payment method and product only in aggregated form, to see which payment methods are used and which ones we offer; the legal basis is our legitimate interest in improving our offer (Art. 6 (1) (f) GDPR). We keep the product and payment method as long as the invoice data. If you pay in yen or your billing address is in Japan, we also store for each payment the issuing country of your card, as reported to us by Stripe. If you order in yen or in pounds, we also store, at completion, the country from which you ordered. For this, at completion we only read the country code that our hosting provider Vercel derives from your IP address (e.g., “JP”), not the IP address itself. With this information, we document the country in which you live and, for pounds, also that the price in pounds was shown correctly. This determines where the revenue is taxable, for example whether the turnover threshold of the Japanese consumption tax has been reached. If your billing address is in the United States or in Canada, we also store for each payment the state, province or territory of the billing address; with it, we check whether we reach a threshold in that state or province, or in Canada as a whole, above which we must register for sales tax there (US sales tax, GST/HST or PST). The legal basis is the fulfillment of tax obligations (Art. 6 (1) (c) GDPR); insofar as tax obligations outside the EU are concerned, our legitimate interest in fulfilling them and being able to document this (Art. 6 (1) (f) GDPR). We keep the issuing country of your card, the country from which you ordered and the state, province or territory with the payments as long as the invoice data; the country from which you ordered is also stored with your consent record and is deleted with your account; we do not include it in the record we keep afterwards (see “Consents when purchasing”). Stripe processes payment data partly under its own responsibility; more information: stripe.com/privacy. If you choose PayPal as payment method (not available for payments in yen), you log in directly with PayPal (PayPal (Europe) S.à r.l. et Cie, S.C.A., Luxembourg); Stripe passes on to PayPal the information needed for the payment, such as the amount. PayPal processes this data under its own responsibility; more information: paypal.com/legalhub/privacy-full. The legal basis here, too, is the performance of the contract (Art. 6(1)(b) GDPR). If you choose TWINT (only for payments in Swiss francs), you confirm the payment in your TWINT app; Stripe passes on to TWINT AG (Zurich, Switzerland) the information needed for the payment, such as the amount. If you choose Klarna, Stripe passes on this information to Klarna (Klarna Bank AB (publ), Stockholm, Sweden); if you choose Amazon Pay, you log in with Amazon Pay (Amazon Payments Europe S.C.A., Luxembourg) for this, and Stripe passes on to it the information needed for the payment. TWINT, Klarna and Amazon Pay process this data under their own responsibility, as does your bank. Link is a Stripe service with which you can save your payment details at Stripe for later purchases; Stripe itself is responsible for this. For Switzerland, there is an adequacy decision of the European Commission. The legal basis here, too, is the performance of the contract (Art. 6(1)(b) GDPR).
Payment through Link (prices in pounds). If you order with prices in pounds sterling, the payment is not handled by Stripe Payments Europe but by Link (Sold through Link, LLC, USA, a Stripe group company; Terms § 14). Link processes the details you enter on the payment page (name, email address, billing address, payment details, tax number if any) as an independent controller: for payment, VAT, receipts, refunds, fraud prevention and Link’s customer support; see Link’s privacy policy (link.com/privacy). For this we pass your email address and your internal account ID to Link. Link sends us the order details (including name, billing address, country, amount, payment method type without card or account details, status of subscription and payment); we keep what is listed above under “Payment via Stripe”, plus the VAT and fee withheld by Link. The transfer to Link in the USA is necessary for the contract you want to conclude with us (Art. 49 (1) (b) GDPR); the legal basis is the performance of the contract (Art. 6 (1) (b) GDPR), and for the tax details compliance with legal obligations (Art. 6 (1) (c) GDPR). If you ask Link to delete your data, Link ends the contracts bought through Link and deletes the data at Stripe; we delete the data we hold under this section and on request (section 10).
Trackplanner Family. If you buy Trackplanner Family in the browser, payment is processed via Stripe as described above, and we send you a contract confirmation by email. For the purchase, we store on your account where the unlock comes from (purchase via Stripe, gift code, App Store or Google Play), the identifier of the purchase (at Stripe, the identifiers of the checkout session and the payment), the time of the unlock and, where applicable, its reversal with time and reason (for example after a refund or a withdrawal). If the purchase started from a hint in the app, we also store which function the hint belonged to; we evaluate this only in aggregated form, to see which functions lead to a purchase. If you redeem a gift code, we store the code only as a hash value, together with the redeeming account and the time of redemption. The legal basis is the performance of the contract (Art. 6 (1) (b) GDPR), and for the aggregated evaluation our legitimate interest in improving the offer (Art. 6 (1) (f) GDPR). The information is deleted with your account; on the code, only the fact that it has been redeemed remains noted. The retention obligations above apply to the invoice data; for the record of your consent, see “Consents when purchasing”. For purchases in the app Trackplanner Kids, see its privacy policy (section 9i).
Consents when purchasing. When ordering, we store as evidence which declarations you made (immediate start of the service, acknowledgment of Terms and privacy policy): account ID, plan, language, currency, for yen, US dollars and pounds the confirmed amount, the version of the Terms and the withdrawal policy (for orders via the Ordering Process for Japan, instead of the withdrawal policy, the version of the page “特定商取引法に基づく表記”), a check value of the wording, the time and the identifier of the payment session at Stripe — no IP address. If you order in yen, we also store with the consent the country from which you ordered (only the country code, see “Payment via Stripe”). If you order a subscription in US dollars, we also store your consent to automatic renewal. If you order in pounds, we also store that Link handles the payment and the country from which you ordered, and for a subscription also your consent to automatic renewal. If consumers with habitual residence in Japan order via the Ordering Process for Japan, there is no right of withdrawal (Terms § 11 (5)); the declaration on the immediate start of the service and the withdrawal policy only concern contracts with a right of withdrawal. The records remain stored as long as your account exists; until then, the legal basis is the fulfillment of our obligations to provide evidence (Art. 6 (1) (c) GDPR) and our legitimate interest in being able to substantiate claims (Art. 6 (1) (f) GDPR). If you delete your account, we keep the record for each order you completed, without your account ID: plan, language, currency, the confirmed amount where it is stored with the consent (for yen, US dollars and pounds), the version of the Terms and the withdrawal policy or of the page “特定商取引法に基づく表記”, the check value of the wording, the time and the identifier of the payment session at Stripe. For this purpose, an order is completed once the payment is confirmed (for a direct debit, once it has been received) or if there was nothing to pay; records of orders that have not been completed, for example after an aborted payment, are deleted with your account. We delete the record we keep three years after your consent or one year after the deletion of your account, whichever is later; when you delete your account, we end any ongoing contract. Keeping this record allows us to prove what you agreed to; for subscriptions with automatic renewal, California law requires us to keep it for customers in California (Cal. Bus. & Prof. Code § 17602(a)(6)). The legal basis for keeping it after the deletion of your account is our legitimate interest in being able to substantiate and defend against claims (Art. 6 (1) (f) GDPR).
Cancellation and withdrawal. If you use “Vertrag kündigen” (“Cancel subscription”) or “Vertrag widerrufen” (“Withdraw from contract”) (also without signing in), we process the email address provided, the contract number (if provided), the type of declaration, in the case of an extraordinary termination your reason, the language and the time. We send you a confirmation link and, after confirmation, an acknowledgment of receipt by email (sent via Resend or, as a substitute, Brevo, section 7). The legal basis is the fulfillment of our legal obligation to enable cancellation and withdrawal via a button and to confirm them (Art. 6 (1) (c) GDPR); we keep the declarations as evidence. If a consumer with habitual residence in Japan has ordered via the Ordering Process for Japan, there is no withdrawal: if he or she uses “Vertrag widerrufen” (“Withdraw from contract”), we treat this as a cancellation (Terms § 11 (5)).
Sign-in with Google. Instead of with email address and password, you can sign in to the web app with your Google account or link Google to your account as an additional sign-in method. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (“Google”).
- Process: As soon as the sign-in dialog shows the button “Continue with Google” — even if it opens by itself, for example under
/loginor when you open an area that requires an account without being signed in — or the account settings offer it for linking, the app loads the script of Google Identity Services (accounts.google.com/gsi/client), which draws the button. Already at this point, i.e., before any click, Google technically receives your IP address, information about your browser and the address of the page; whether Google reads cookies of your Google account in the process is decided by Google. If you click the button and agree in the sign-in window of Google or your browser, Google passes a sign-in token to the app; the app forwards it to our auth service at Supabase (hosting in the EU, Frankfurt region), which creates your session from it. If the script cannot be loaded (for example because of a content blocker), the button instead takes you, only after your click, via Supabase to Google’s sign-in page and back. - Data processed: from Google, we receive your Google user ID, email address and — insofar as stored at Google — name and profile picture address. We store them with your account; the name serves to pre-fill your display name. We never receive your Google password.
- Purpose and legal basis: Signing in to your account at your request serves the performance of the user agreement (Art. 6 (1) (b) GDPR). We base loading the Google script already when the button is displayed, i.e., before you have decided on a sign-in method, on our legitimate interest in a working sign-in with Google (Art. 6 (1) (f) GDPR); we do not obtain consent for this. For this step — embedding the script and the resulting transmission to Google — we are jointly responsible with Google; Google itself is responsible for further processing at Google.
- Third country: Google may also process data in the USA; Google LLC is certified under the EU-US Data Privacy Framework (Art. 45 GDPR). More information: policies.google.com/privacy.
- Storage period: The link with Google exists until you remove it in the account settings or delete your account.
Notification of the provider upon registration. As soon as your email address is confirmed — by clicking the confirmation link or already when the account is created, for example when signing in with Google —, the provider receives a notification email with your email address, your display name (if provided), the language code of your account and the time of confirmation. The purpose is to know about new registrations while building up the offer; the legal basis is our legitimate interest in this (Art. 6 (1) (f) GDPR). The same service providers as described in section 8 apply to sending and mailbox; it is read as described in section 7 under “How we handle messages”. The notification is deleted at the latest with your account or upon your request for erasure.
Country of origin. In order to suggest prices in the appropriate currency and retailers near you in the web app and to choose the usual default settings of your country (length unit of new plans, paper format for printing, notation of numbers and dates, in future also the track systems we show first), we determine the country from which you access the app when you open it. For this, we read exclusively the country code (e.g., “DE”) that our hosting provider Vercel derives from your IP address; we do not process the IP address itself for this, and this query is neither stored nor logged. The exception is a purchase in yen (see “Payment via Stripe”) or in pounds (see “Payment through Link”). If you access the app from Canada, we also read the province code (e.g., “QC”), which Vercel likewise derives from your IP address. We use it to exclude purchases in Québec (Terms § 12 (7)); the legal basis is our legitimate interest in not entering into contracts with customers in Québec as long as we do not meet the requirements that apply to contracts there (Art. 6 (1) (f) GDPR). We do not store the province. If you access the app from the United Kingdom, we show you prices in pounds when ordering through Link is switched on; until then, we do not offer you the subscription or the Premium Pass. If you access it from the Isle of Man, we do not offer you a paid contract. We use the country code to exclude purchases of Trackplanner Family from the United Kingdom and the Isle of Man (Terms § 13 (1)); the legal basis is our legitimate interest in concluding paid contracts only in the way we have set up the tax handling (Art. 6 (1) (f) GDPR). If no country code arrives, we take the country from the language setting of your browser (e.g., “de-CH”). You can change the preselection at any time. If you are signed in, we store the country code the first time, together with the time, in your account, in order to understand from which countries Trackplanner is used, to align our offer (payment methods, retailers, languages) accordingly and, in aggregated form, to show retailers which articles are planned in their region (see section 9c); it is not changed afterwards. In the build plan or in the settings of your account, you can also choose a country yourself (or “other country”) or return to automatic detection; we then use this to determine which retailers we suggest (only those that ship to your country, retailers from your country first), in which currency we display prices and which of the default settings mentioned above apply. If you are signed in, we store this choice like your other settings in your account until you change it or delete your account. The legal basis in each case is our legitimate interest in an appropriately aligned offer (Art. 6 (1) (f) GDPR). The stored country code is deleted with your account.
Partner referral. If you create an account in the same session, or sign in with Google in that session within 24 hours of registering, we store on your account which partner you came through, and when. We use this to ask you whether you would like to set this partner as your retailer, to show you its discount code if it offers one, to suggest its track system or the starter sets of its brand or a track system that suits it, and to evaluate in aggregated form how many accounts were created via a partner and how many of them use Premium (Art. 6 (1) (f) GDPR; our interest is to show you the offers of the partner you came through and to evaluate our cooperations). If you are signed in and came via a partner, we note on your account in which places we have already asked you and whether you have answered or set the partner in the notice on the website, so that the question does not come back, even if no referral is stored. We only pass on aggregated figures to the partner, never information about individual accounts. You can object (Art. 21 GDPR), either yourself in the account settings under “Data” → “Partner referral”, if a referral is stored on your account, or by email to info@trackplanner.io. We then delete the referral, including from the information about your registration (section 9e), and these notes, and your account will no longer be linked to any partner. We note the objection itself on your account for as long as your account exists, so that we continue to respect it (Art. 6 (1) (c) in conjunction with Art. 21 (1) GDPR). Your choice under “My shop” stays; you can change it there.
9a. Premium trial and trial offers with a control group
In the web app, we occasionally offer a free, time-limited Premium trial (Terms § 5a). We measure whether such an offer helps with a control group.
- Allocation: As long as a trial offer is running, we allocate eligible accounts, when the home page or the plan dialog of the app is opened, once and at random to one of two groups: the offer group sees the offer, the control group does not. An account is eligible if it is a free account that has existed for a certain number of days and has never had a paid subscription or a trial. The allocation is fixed; a later offer does not reallocate. Buying Premium regularly is equally open to both groups.
- Data processed: your internal account ID, the identifier of the offer, your group and the time of allocation; if you start a trial, also its start and end. If we unlock a trial for you in support, we additionally record this in our internal admin log: who unlocked it, when and with what justification.
- Evaluation: exclusively in aggregated form — per group, how many accounts were allocated, started a trial or bought Premium after allocation (subscription, paid invoice or redeemed retailer license). Accounts for which we unlocked a trial or Premium in support after allocation are not counted in any group. No usage profiles are created; for this we use neither cookies nor analytics tools and do not pass on any data to third parties.
- Purpose and legal basis: improving our offer — we want to know whether a free trial makes the decision for Premium easier. The legal basis for allocation and evaluation is our legitimate interest in this (Art. 6 (1) (f) GDPR); the provision of a started trial is based on Art. 6 (1) (b) GDPR.
- Storage: in our database at Supabase (hosting in the EU, Frankfurt region) as processor. Allocation and trial data remain stored as long as your account exists — they ensure that each account is allocated only once and receives at most one trial. They are deleted when your account is deleted; they are included in information about your data (Art. 15 GDPR). Entries in the internal admin log (unlock in support) serve to make our interventions traceable and are not deleted when an account is deleted.
- Objection: You can object to the allocation and evaluation at any time (Art. 21 GDPR); an email to info@trackplanner.io is sufficient. We then delete your allocation and note the objection on your account: it no longer takes part in any trial offer, including future ones. You can continue to use a trial that has already started until its end. We store the note as long as your account exists; who entered it, when and with what justification, we also record in the internal admin log, which is not deleted when an account is deleted. The legal basis for this is our legitimate interest in permanently respecting your objection and being able to document this (Art. 6 (1) (f) GDPR).
9b. Storage in the browser for the web app
The web app does not set any cookies. To work, it places entries in your browser’s storage (Section 25 (2) no. 2 TDDDG):
- Sign-in: your session with the auth service (access token) in local storage (localStorage), as long as you are signed in.
- Plans and work status: a database in the browser (IndexedDB “trackplanner”) with your plans, changes not yet transmitted, the undo history and your inventory, so that the app also works with a weak connection and nothing is lost. It remains in your browser even after an account is deleted until you delete the website data.
- Settings and cache: language, country, color scheme, view and tool settings, hints already seen, a cache of retailer offers and a file just imported until the import is completed; if it is older than 24 hours, the app removes it the next time it is opened.
- Campaign identifier: If you come via a link from one of our campaigns (address with
utm_campaign=import-…), the tab remembers this identifier until it is closed (sessionStoragetp-campaign). We only use it to count, in aggregated form, how often steps such as “import started” or “registered” occur per campaign and day — without account ID and without IP address. - Partner identifier: If you come via a link, a QR code or the partner page of one of our partners (retailer or manufacturer; address with
partner=…or/partner/…), the tab remembers until it is closed which partner that was, in which places the question about the preferred retailer has already appeared, whether you have answered it, whether you ticked the box to set it as your retailer when registering with Google (until you return to the app), and whether you have adopted the suggested track system (sessionStoragetp-partner). On the website, the partner is only in the address or on its partner page; there, the tab only remembers the state of the partner notice, and only after you click in it (section 5). If you open the app via a link on the website after setting the partner as your retailer in the notice, the app checks at start-up, using the address of the referring page (referrer), whether you come from a page of trackplanner.io with the same partner. It keeps the result in the same entry until it has adopted or discarded your setting. This check takes place only in your browser; the app neither transmits nor stores the address of the referring page for it. Separate from this is the name of the referring website, which we store with your registration (section 9e). - Email notice when signing in with Google or Apple: If you sign in via Google or Apple, the tab remembers until you return to the app whether the sign-in window showed the notice about our emails, whether you agreed to receive them (only for accounts with a connection to Japan), whether such an account was present and which language the app had (sessionStorage
tp-mail-signup). After sign-in, the app transfers this information once to your account (section 9k) and deletes the entry. - Crash detection: see section 4a.
These entries only leave your device insofar as is necessary for the respective function (for example when saving a plan in your account).
9c. Partner links (affiliate programs)
In the web app, purchase links in the build plan, in the order view, in the info on a selected part and in the “Check” under “What you need for this” lead to retailers. Some of them are partner links: links to Amazon carry our identifier in Amazon’s partner program (Amazon PartnerNet for amazon.de, the Amazon.es Associates Programme for amazon.es, the Amazon.co.jp Associates Program for amazon.co.jp), links to eBay our identifier in the eBay Partner Network; links to idee+spiel our identifier in the partner network AWIN; further retailers may be added. If you buy via such a link, we receive a commission; the price does not change for you (see imprint).
- Before the click, nothing is transmitted to the retailers or partner programs.
- When you click, you leave our offer. Through the identifier in the link, the retailer or partner program learns that you come from Trackplanner and may use cookies or similar technologies in your browser to attribute a purchase. The respective provider itself is responsible for this; its privacy notices apply. We receive reports on sales and commissions from the partner program.
- Click log: To see which purchase links are used, when you click we store the retailer, the identifier of the plan, where applicable the article number and the library or track system, the time, the place in Trackplanner from which you clicked (for example a line in the build plan or the card of a part on a public plan) and — if you are signed in — your internal account ID and your subscription tier at the time of the click (free or Premium), in our database at Supabase (hosting in the EU, Frankfurt region). We do not store an IP address for this. The legal basis is our legitimate interest in measuring the effect of the purchase links and financing our offer (Art. 6 (1) (f) GDPR). A fixed deletion period has not yet been set for the log; if you delete your account, the connection to your account is removed. You can object to the storage (Art. 21 GDPR); an email to info@trackplanner.io is sufficient.
- Order steps (aggregated): We count how often the build plan is opened, a handover to a retailer is started, completed or cancelled and a shopping cart is marked as purchased — per retailer and day, with the number of items and parts and the value of goods at our prices. Likewise, we count how often the build plan suggests a cheaper set, how often this suggestion is clicked and how often the set is used, together with the number of set boxes and the savings shown. On public plans, we also count how often the card of a part is opened and the build plan is called up from there, separately by type of part (track, accessories, requirement, other). For a handover, we also count which articles (article number, quantity and value of goods) were not available at the chosen retailer via our connection and to which other retailer they went instead. In doing so, we store no account ID, no identifier of the plan and no IP address, and we do not link the figures with the click log. We show retailers only monthly totals of this, and only if at least five transactions come together.
- Viewed articles (aggregated): If you open the detail card of a model or vehicle in the catalog in the web app, or the info on a selected part, we count this per day: the library or track system, the article number, the place (catalog or info on the part) and whether the article already occurs in the open plan. The same article counts at most once per browser tab, place and day; for this, the open page remembers the articles already counted until you close or reload it; we do not create a cookie or an entry in local storage or session storage for this. In the count, we store no account ID, no identifier of the plan, no IP address and no time of day; for the request itself, section 4 applies as for every request. This applies with and without signing in. If you are signed in, we only check when counting whether your account is a test account or an operator account or whether you have objected; in that case we do not count. While a kids’ profile is active, we do not count. We compare the totals with the clicks on purchase links to the same articles to see whether purchase links to articles that are already in the plan are clicked more often than those to articles that were only viewed; in doing so, we do not assign individual views to any account, plan or click, we only compare totals over several days. We keep the daily totals without a time limit. The legal basis is our legitimate interest in improving our offer and the reports for retailers and manufacturers (Art. 6 (1) (f) GDPR). You can object (Art. 21 GDPR). If you are signed in, you object to the usage history in the account settings (section 9e) or write to info@trackplanner.io; this also applies here. Without signing in, we do not recognize you. If your browser sends the “Global Privacy Control” signal, we do not count; this also applies when you are signed in. Otherwise, the most effective way to put your objection into effect yourself is to block requests to
/rest/v1/rpc/bump_article_viewin your browser (for example with a content blocker); the web app then works unchanged. - Planned articles (aggregated): Once a week, we count which track articles and track systems occur in the saved plans: in how many plans and how often, separated by purchasing region. We derive the purchasing region from the country code that we store in the account of signed-in users the first time (see “Country of origin”). In the count, we store no account ID and no identifier of the plan. From this, we show retailers articles and track systems that we do not find in their product feed, as totals and only if they occur in at least five plans from at least three accounts. The legal basis is our legitimate interest in improving the product range for our users together with retailers (Art. 6 (1) (f) GDPR). You can object (Art. 21 GDPR); an email to info@trackplanner.io is sufficient.
- Aggregated reports for manufacturers: Once a month, we count for each manufacturer in how many saved plans and by how many accounts its models and track systems occur and how often, separated by country and purchasing region of the account (see “Country of origin”), scale and era of the plan, and by whether the account has Premium. We also count which types of accessories from other manufacturers appear in the same plans, and the clicks on purchase links to its articles per retailer. In the count, we store no account ID and no identifier of the plan. From this, we give manufacturers we work with a monthly report: only figures based on at least five plans from at least three accounts, no figure from which a smaller group could be calculated together with other figures in the report, and purchase clicks only in total and by type of retailer (specialist shop, marketplace, manufacturer shop), each only from five clicks. We do not pass on data about individual users or plans. Accounts that have objected, test accounts and plans in kids’ profiles are not counted. The legal basis is our legitimate interest in improving the offer for our users together with manufacturers and in financing our partnerships (Art. 6 (1) (f) GDPR). You can object (Art. 21 GDPR); an email to info@trackplanner.io is sufficient.
- Abuse protection when loading prices: So that prices and purchase links appear, the web app loads the offers from our server at Supabase (hosting in the EU, Frankfurt region). So that nobody retrieves our retailer data on a massive scale, without sign-in we count the number of requested articles per sender; for this, we do not store your IP address, but only a salted hash value of it (for IPv6, of the /64 prefix) together with the time window and number. If you are signed in, we count the requests per account via a salted hash value of your account identifier. A job running every hour deletes these entries again. If an account exceeds the limit, we note this with its internal account ID in the log of our server at Supabase, which the provider deletes by itself after a short time. The legal basis is our legitimate interest in a functioning offer free of abuse (Art. 6 (1) (f) GDPR).
9d. Feedback portal (feedback.trackplanner.io)
From the web app, we link to our feedback portal feedback.trackplanner.io (wishes, bug reports, roadmap, changelog). The home page and the editor of the web app load the public changelog from there without a click; the portal’s server technically receives your IP address and information about your browser in the process. If you sign in to the portal with your Trackplanner account, Trackplanner transmits your internal account ID, your email address and your display name to the portal after you sign in; for this, a one-time code is created in our database at Supabase (hosting in the EU, Frankfurt region), which can be redeemed exactly once. The purpose is signing in to the portal at your request (Art. 6 (1) (b) GDPR). What you publish in the portal is visible there according to its rules.
Wishes from the web app. If you enter a wish in the web app or vote for one, Trackplanner transmits your internal account ID, your email address, your display name and the content of the wish to the portal; the portal creates you as a user in the process if it does not know you yet. The wish appears publicly with your display name; your email address is not displayed. The portal notifies you by email about changes to wishes you follow; you can unsubscribe in every email. The legal basis is the execution of your request (Art. 6 (1) (b) GDPR). So that we can classify a wish correctly, Trackplanner stores the following in its database: your internal account ID, the identifier of the wish in the portal, its title, where in the app you sent it from, the track systems of the plan that was open at the time, and the identifier of that plan unless you deselect it. If you vote for an existing wish instead, we also store the title and the description you had entered. This information is not passed to the portal and does not appear in the public wish; only we look at it. The legal basis is our legitimate interest in understanding and implementing wishes correctly (Art. 6 (1) (f) GDPR). You can object to this at any time; write to us and we will delete the information for your account. Otherwise we delete it after 24 months, and immediately with your account; if you delete the plan permanently, the reference to it is removed. We count the number of your requests, as with messages to us, via a salted hash value of your account identifier. The home page of the web app asks the portal whether wishes that you created or voted for have been completed; for this, Trackplanner transmits your internal account ID to the portal. When you open the window for a wish in the web app (“Request a feature” or “Request a track system”), it shows wishes that are already on the board and whether you have voted for them; for this, Trackplanner transmits your internal account ID to the portal and, as soon as the window contains a title (typed or taken from your search in the catalogue), that title as a search term.
Translation in the portal. The portal shows its content in German and in English. If it displays a wish, a comment or a changelog entry in a language for which no version has been stored yet, it transmits title and text to the AI service Claude from Anthropic (Anthropic, PBC, USA). Claude recognizes the language and translates the text if necessary. The portal stores the result; if the text changes, it transmits it again. For translation in the portal, we use exclusively commercial access (Anthropic’s API) under Anthropic’s commercial terms and with a data processing agreement, not a consumer account; Anthropic does not use the texts to train its AI models. Data may be transferred to the USA in the process; the basis is standard contractual clauses of the European Commission (Art. 46 (2) (c) GDPR), see also section 11 (4). The legal basis is our legitimate interest in a bilingual portal (Art. 6 (1) (f) GDPR). For evaluation, our AI agents also read the posts and comments in the portal; section 7 “How we handle messages” applies to this.
9e. Usage history in the web app
If you are signed in to the web app, we record what you do in the app in order to improve Trackplanner, to be able to help you in support and to recognize which Premium functions interest you — for example, where new users get stuck or which functions are hardly used.
- Data processed: your internal account ID, an identifier of the session (per open browser tab), type and time of the action and, where there is one, the identifier of the plan. The following are recorded: signing in (with sign-in method, e.g., email or Google, and time of sign-in), signing out and opening the app (with the area opened, such as home page or plan); creating a plan (with track system, scale, number of tracks and route, such as new, import with file format or copy of a starter set), opening (with track system and number of tracks), renaming, duplicating, deleting, sharing (type of sharing and role, not the address of invited persons), changing its visibility and exporting (with format); opening the build plan and findings as well as clicking a finding, viewing its fix, fixing or hiding it (with the check rule); and, per session in a plan, a summary of the work — duration, number of work steps, tracks and accessories added and removed, the number of open track ends of the plan, the work areas (e.g., tracks, landscape, accessories), the most frequent types of steps and, for a fixed list of building and editing actions (e.g., attaching a track, stretching a section, connecting two tracks), how often you used the action and at which work step for the first time — so that we can recognize which ways of operating are found and used; in addition, when you try out a Premium function that is locked in Free (which function and how often), when you click “Get Premium”, open the plan overview (and from where), choose a plan or close the overview again, as well as the answer to the question about your building project and whether you switch the section of a plan; also, when you expand the guide for a build phase in the build plan (“How to go about it”) and click a link to our knowledge pages there (with phase, step and page); also, when you open the “Electrical” phase in the build plan for the first time in a session (whether a controller is chosen) and change an answer there (which question; for the controller only its identifier or “own controller” and whether you already have it, not the name or current of your own controller; for the colors the chosen scheme), and when you change something in the plan with the “Electrical” tool (only the kind of change, such as “feeder moved”, not where). We store the title of a plan when it is created, opened, renamed, duplicated and deleted, so that the history is readable. Not recorded are the content of your plans (no coordinates, texts or images), any IP address and anything while you are not signed in. Without an account, only daily counters without reference to a person are created: how often the app was opened without sign-in (with the area, such as home page or shared plan), how often the sign-in dialog was opened and a registration was submitted (with the route, such as email or Google), with which error a registration failed and how often a purchase from the United Kingdom or the Isle of Man was blocked. For this, we do not set a cookie and do not store anything in your browser. Further aggregated counts without an account, such as the viewed articles, are described in section 9c.
- When using the 3D view: device class (number of processor cores, reported memory, screen density, type of device, rough class of the graphics chip), which 3D functions were active, the plan size in levels and measured frame times. No exact name of the graphics chip.
- Permanent evaluation: From the history, once a day we create a summary per account and day: number of actions, of browser tabs and of sessions in plans, working time, number of work steps, tracks added and removed, accessories added, plans created and edited, the largest number of tracks in a plan, limits of Free reached (which function and how often), how often you opened the plan overview and chose a plan, exports, sharing, build plans opened, sessions in the 3D view and clicks on links in our emails. We also record when you took certain steps for the first time: created the first plan, came back on a second day, built a plan with at least 20 tracks, closed a loop without open track ends, opened a build plan, shared a plan, reached the first limit of Free (which one), opened the plan overview for the first time (from where), began the first ordering process and made the first purchase (which plan and from where you began it). For your registration, we store where you came from: the campaign parameters of the link (
utm_source,utm_medium,utm_campaign,utm_content,utm_term), the referring website without path (only its name, such asforum.example), the page on which you opened the app, a partner referral and the sign-in route (such as email or Google). If you first come to this website (trackplanner.io), its links pass this information on to the app: the name of the website (or, for an Android app, its identifier, such ascom.google.android.youtube) from which you came to us, and the campaign parameters of your first visit, as parameterstp_ft,tp_ref,tp_src,tp_med,tp_cmp,tp_cntandtp_trmin the address. For this, the website does not store anything in your browser, and the app removes the parameters from the address bar again after reading them. When purchasing, we store with your consent record and in the payment information at Stripe from where you opened the plan overview (purchase trigger, such as a function locked in Free or the header of the app). Purpose: understanding how accounts use Trackplanner over time and what leads to a purchase. We store this information until you delete your account. An objection deletes the daily summaries and the first steps immediately; only the time of your first ordering process and of your first purchase remains as contract data (section 9). - Purchase interest: From these actions of the last 30 days and from whether you began but did not complete a purchase, we calculate how much Premium interests you and which functions speak for it. This is an evaluation of your usage behavior (profiling). We use it to improve the app and to show you suitable hints or offers in the app. We do not send you emails because of it, and it does not decide anything automatically about your contract, your price or your access.
- Who sees it: only we as the operator, in the internal admin area, for individual accounts and as a list of Free accounts with their purchase interest. Each access is noted in our internal admin log. We do not pass on the data to third parties and use neither cookies nor analytics tools of other providers for this.
- Purpose and legal basis: improving the web app, support and suitable hints and offers in the app; the legal basis is our legitimate interest in this (Art. 6 (1) (f) GDPR).
- Storage: in our database at Supabase (hosting in the EU, Frankfurt region) as processor. Each history entry is deleted automatically after 30 days, immediately with your account; the permanent evaluation (above) remains until your account is deleted. The history is included in information about your data (Art. 15 GDPR). The app does not store anything additional in your browser’s storage for the history. Before deletion, we aggregate the information on the 3D view once a day into daily totals without account ID and without plan identifier (for example: how many sessions ran smoothly on which type of device). We keep these daily totals without a time limit.
- Kids’ profiles: As long as a kids’ profile is active in the web app (section 9g), we do not record any usage history and do not calculate anything from it; the aggregated usage counters of your account (section 9) do not count either. The same applies in the app Trackplanner Kids as long as no parent profile is selected there.
- Objection: You can object to the recording at any time (Art. 21 GDPR) — yourself in the account settings under “Usage history” or by email to info@trackplanner.io. With the objection, we immediately delete the previous history of your account and the permanent evaluation and do not record anything new; we note the objection itself as long as your account exists. With the objection, we also no longer calculate any purchase interest and no longer count your views of articles (section 9c). You can also withdraw the objection there.
9f. Survey after the Premium purchase
When you return to the web app after buying a Premium subscription, we ask you once what brought you to Premium. Participation is voluntary; you can skip or decline the question.
- Data processed: the reasons chosen (up to three from a fixed list), your free text if any, the calendar week of the answer and whether your subscription runs monthly or yearly.
- Without account reference: We store your answer without your account ID and without day or time, only with the calendar week. Attribution is not ruled out by this: if there are very few purchases in a week, we could theoretically attribute an answer to an account via week and purchase, and, until the nightly reorganization of the table, also via technical characteristics of the database; we do not do that. A free text may contain personal information if you write some into it — please don’t.
- Whether you have already been asked is noted separately on your account (answered or declined), without time, so that we do not ask you again. If you choose “Later”, your browser remembers this in order to show the question once again the next time the app starts.
- Purpose and legal basis: improving our offer — we want to understand which functions are decisive for Premium. The legal basis is our legitimate interest in product improvement (Art. 6 (1) (f) GDPR).
- Storage: in our database at Supabase (hosting in the EU, Frankfurt region) as processor. We delete the answers automatically after 24 months. The note on your account remains as long as your account exists and is deleted with it.
- Evaluation: Our AI agents also read the answers and summarize them in the register (section 7, “How we handle messages”).
9g. Kids’ profiles
In the web app, you can create up to five kids’ profiles in your account, in which your children build their own layouts in the kids’ world. The account belongs to you as a parent: you create the profiles and manage them behind the parental gate, and in the parent profile you see all your children’s layouts. A summary for parents is available at trackplanner.io/datenschutz-kurz (in German).
- Data processed: the profile name, which you choose freely (1 to 24 characters; use a first name or nickname, not a surname), an avatar from a fixed set of images, the creation date, the layouts of the profile and, if you use it, the wish list (section 9h). No date of birth, no age, no photo.
- What does not happen in the kids’ profile: no usage history and no usage counters (section 9e) and no counting of viewed articles (section 9c), no error reports (section 4a), no publication (only parents can publish a layout), no prices, no shop and no links to outside without the parental gate.
- Legal basis: For your account and your contract with us, it is the performance of the contract (Art. 6 (1) (b) GDPR). We process your child’s data (profile name, avatar, layouts, wishes) on the basis of legitimate interests (Art. 6 (1) (f) GDPR): you as a parent and we as the provider have a legitimate interest in making the service you use available to your child as well. In weighing this against your child’s interests, it counts that we only process what is necessary: no date of birth, no photo, a freely chosen name and no evaluation of usage. Nothing in the kids’ profile is based on consent; Art. 8 GDPR (consent of children) therefore does not apply. You can object to the processing at any time (Art. 21 GDPR), for example by deleting the profile or writing to us.
- Building together: If you invite an adult to build on your child’s layout, that person sees the child’s profile name and avatar.
- Without an account: Kids’ profiles can also be created without an account. They are then stored only in the storage of this browser or device. If you sign in, we transfer them to your account (at most five).
- Storage in the browser: For kids’ profiles, the app stores in your browser’s storage the list of profiles, the profile active in the tab, the assignment of layouts to profiles and, without an account, the wish list. This is necessary for the function you use (Section 25 (2) no. 2 TDDDG).
- Storage and deletion: in our database at Supabase (hosting in the EU, Frankfurt region) as processor, as long as the profile exists. If you delete a kids’ profile, you decide whether its layouts move to your parent profile or go to the trash (section 9); the profile’s wish list is deleted. If you delete your account, we delete all profiles with it.
- Access and export: In the profile management, you can download the data of a profile as a file (profile name, avatar, creation date, layouts and wish list). You can receive a complete copy of all account data on request to info@trackplanner.io (Art. 15 GDPR).
9h. Wish list
In the kids’ profile, your child can put parts missing from his or her layout and toys on a wish list. Only you as a parent can view, change and share it, behind the parental gate.
- What is on the list: for each wish, the part or toy (library and article number), the quantity, the layout the wish comes from, whether your child or you entered it and, if someone has marked it as “already got”, the time of the marking. Only what your child has built or selected is on the list; we do not suggest any products.
- Sharing: If you share the list, you set the name on the list (1 to 40 characters, pre-filled with “Wish list for” and the first letter of the profile name; please no full name). We store this name, the time of sharing, the end of the link’s validity, your region and, if you have chosen one, your preferred retailer, so that the page shows suitable ways to buy. You receive a link with a random identifier; we only keep a hash value of it.
- Who sees the list: The page behind the link is accessible to anyone who has the link, without sign-in. It shows the name on the list and the wishes with image, name, manufacturer, article number, quantity and ways to buy, but no profile or account name, no layouts and no images of them. Search engines should not include it (
noindex, nofollow), and if someone follows a link on the page, the target page does not learn the address of the list (no-referrer). - How long the link is valid: 90 days from sharing. With “Renew link”, the same link is valid again for 90 days from that day; a new link is also valid for 90 days, and the old one is then no longer valid. It ends earlier if you withdraw it or the profile or your account is deleted. If it has expired, the page only shows “This wish list is no longer shared.”, without name and without wishes. After withdrawal, the list is private again.
- “Already got”: Anyone who has the link can mark a wish as “already got” and remove the marking again. We only store the marking and its time, no name and no contact details of the person giving the gift. Your child does not see what has already been got.
- When the page is accessed, server log files are created as with every page view (section 4). To protect against trial-and-error and abuse, we count requests and markings per sender via a salted hash value of the IP address (as in section 7); we do not store the IP address itself for this. The page may keep in the browser’s storage for a short time which retailer offers it has already loaded (like the web app, section 9b); it does not remember an account or profile.
- Purchase links: The ways to buy lead to retailers; some of them are partner links (section 9c). We count clicks on the page as there, but without account ID and without plan identifier. Purchases are made at the retailer; we do not sell toys.
- Legal basis: for your child’s wishes as for kids’ profiles (section 9g, Art. 6 (1) (f) GDPR), for sharing and the link the performance of the contract with you (Art. 6 (1) (b) GDPR), for the page for gift givers including abuse protection our legitimate interest in secure provision (Art. 6 (1) (f) GDPR).
- Storage and deletion: in our database at Supabase (hosting in the EU, Frankfurt region) as processor. If you delete a wish, the profile or your account, we delete the associated data. Without an account, the list is only stored in your browser’s storage and cannot be shared.
9i. Trackplanner Kids in the App Store and on Google Play
The app Trackplanner Kids for tablets has its own privacy policy: trackplanner.io/datenschutz-kids-app (in German). It describes which data the app processes; the listings in the App Store and on Google Play link to it. In brief: the app works without an account, sends no error reports, contains no advertising and no analytics tools of other providers, sign-in is only by email, and it only connects to our own servers and, for purchases, to Apple or Google.
9j. Search in the help videos
In the web app, you can search the help videos in the help menu. If your search finds no video or you do not click on any result, we store the search text so that we can add missing keywords and videos. This applies with and without sign-in. We do not count searches on our website.
- Data processed: the search text (in lower case, at most 80 characters), the language of the app and the day. We count identical search texts together per day. Not stored are your account ID, a plan, your IP address or a time of day.
- Kids’ profiles: As long as a kids’ profile is active (section 9g), we do not count any searches.
- Who sees it: only we as the operator, in the internal admin area, as a list of the most frequent search texts.
- Purpose and legal basis: improving the help (adding missing keywords and videos). The legal basis is our legitimate interest in this (Art. 6 (1) (f) GDPR).
- Storage: in our database at Supabase (hosting in the EU, Frankfurt region) as processor. Each entry is deleted automatically after 12 months.
9k. Emails with tips, news and offers
If you have an account in the web app, we occasionally send emails to your account’s address with planning tips, news about Trackplanner and offers for Trackplanner, at most one per week. Only our own services are advertised (Trackplanner, Premium, Pass, gift licenses), no products of retailers or partners. Emails about your account and your contract (such as sign-in, invoice, cancellation) are not included; you receive them regardless.
- Legal basis: our legitimate interest in advertising our own similar services (Art. 6 (1) (f) GDPR) in conjunction with Section 7 (3) of the German Act against Unfair Competition (UWG). We point this out at registration and in each of these emails. For accounts with a connection to Japan (app language Japanese, country Japan or shop country Japan, even if that only applied at registration), we send these emails only with your consent (Art. 6 (1) (a) GDPR; in Japan under the Act on Regulation of Transmission of Specified Electronic Mail, 特定電子メール法); we store the consent and its version with the time.
- Which data controls the selection: the registration date, your activity in the app (on which days you used it, number of your plans and tracks), your track system, whether you have hit a limit of the free version, whether there is a purchase and the language of the app. On this basis, we decide which email suits you and when. We do not use the purchase interest value from section 9e for this.
- Log and clicks: We record which email went to your account and when, so that we do not send too many and can see whether the emails are useful. We recognize whether you click a link in the email by a parameter in the link when you open the app with it. We do not use tracking pixels or other measurements when the email is opened.
- Objection: You can object to these emails at any time, completely or per topic (tips, news, offers): in the account settings under “Data” → “Emails from Trackplanner”, via the unsubscribe links in every email (also via unsubscribing in your email program) or by email to info@trackplanner.io. This does not incur any costs for you other than the transmission costs according to the basic rates. We store every change (topic on or off, objection, consent) with time and route as evidence. Accounts registered before this notice was introduced see it once in the app and can object there immediately; every email also contains it. Accounts registered afterwards that did not see the notice at registration only receive these emails after they have confirmed it in the app.
- Sending: via the email service Resend (Plus Five Five, Inc., USA) as processor, address and basis of the transfer to the USA as in section 7 for the contact form (Data Privacy Framework, in addition standard contractual clauses). These emails do not go via the substitute route Brevo.
- Storage: in our database at Supabase (hosting in the EU, Frankfurt region) as processor. We store your settings, the record of changes and the sending log as long as your account exists; we delete them with the account.
9l. Question about the reason for a withdrawal or cancellation
If you have ended a contract via “Withdraw from contract” or “Cancel contract”, we ask you on the confirmation page whether you would like to tell us the reason. Answering is voluntary. It changes nothing about your withdrawal or cancellation; both already apply at that point. For contracts under the terms for Japan (Terms § 11) we currently do not ask.
- Data processed: the reasons chosen (up to three from a fixed list), your free text if any, the time of the answer, whether it was a withdrawal or a cancellation, the type of contract (monthly subscription, yearly subscription or Premium Pass) and the language of your request.
- With account reference: We store your answer with your account and the related case so that we see it when handling your withdrawal or cancellation. Regardless of an answer, we note on the case that a contract was ended, what type of contract it was, when, and whether we asked; from this we count how many people answer. This note is part of the records of your withdrawal or cancellation and is deleted with your account.
- Free text: A free text may contain personal information if you write some into it, in the worst case also specially protected information such as information about your health. Please don’t. On request we delete an answer immediately.
- Purpose and legal basis: improving our offer: we want to understand why someone ends a contract. The legal basis is our legitimate interest in product improvement (Art. 6 (1) (f) GDPR). You can object to the processing at any time (Art. 21 GDPR); we then delete your answer.
- Storage: in our database at Supabase (hosting in the EU, Frankfurt region) as processor. We delete the answers automatically after 24 months, and earlier together with your account.
9m. Shopping list link (QR code on the printout)
If you are signed in and print the shopping list of your own saved plan, the printout carries a QR code with a secret address of the form https://app.trackplanner.io/l/<identifier>. It leads to the shopping list of this plan with links to the shops. The web app already creates or fetches the link in the background when you open the build plan. There is one link per plan; it stays the same until you reset it. In a kids’ profile in which no prices are shown, the printout carries no code.
- Who sees the list: The page behind the link is accessible to anyone who has the address, without sign-in and without an account. It shows the name of the plan, the date of the list’s version, the parts of all build phases with quantities, prices and purchase links, how many of each part you have in your inventory, as well as your purchasing region, your country and your “My shop”. The page calculates the prices in the viewer’s browser from our offer data for this region and this country. Not visible are the plan itself (its geometry and an image of it), notes, the build status, the plan’s visibility, its address under /p/…, your name and your account. Search engines should not include the page (
noindex), and if someone follows a link on the page, the target page does not learn the address of the list (no-referrer). - What we store: on the plan, a copy of the list with its date, your purchasing region, your country and your “My shop”, the version of the link, whether it is switched on, and a hash value (SHA-256) of the identifier. We do not store the identifier itself (22 characters); it is derived with a secret key from the plan and the version of the link. As long as the link is switched on, the web app updates the copy of the list as well as purchasing region, country and shop when you open the build plan or change region, country or shop there, and also updates the copy every time you save the plan. If you switch the link off or create a new one, this information remains stored with the plan until the plan is permanently deleted or you delete your account.
- How long the link is valid: The link has no validity period; it does not expire. You can revoke it at any time in the plan’s share dialog: with “Create new link”, a new link is created and old printouts lead nowhere; with “Switch off”, no link is valid any more until you switch it on again with “Switch on”; the same link as before is then valid again. While the plan is in the trash, the link is not valid; if you restore the plan, it is valid again.
- When the page is accessed, server log files are created as with every page view (section 4). To protect against trial-and-error and abuse, we count requests per sender via a salted hash value of the IP address (as in section 7), at most 60 requests in 10 minutes; we do not store the IP address itself for this. The address of the list including the identifier may appear in the access logs of Vercel (section 3) and Supabase; we do not include the identifier in the log entries that our function writes itself. The page may keep in the browser’s storage for a short time which retailer offers it has already loaded (like the web app, section 9b).
- Purchase links: The purchase links lead to retailers; some of them are partner links (section 9c). They carry neither an identifier of your account nor one of the plan. We count clicks on the page as there, but without account ID and without plan identifier.
- Legal basis: for the link and the copy of the list the performance of the contract with you (Art. 6 (1) (b) GDPR), for the page including abuse protection our legitimate interest in secure provision (Art. 6 (1) (f) GDPR).
- Storage and deletion: in our database at Supabase (hosting in the EU, Frankfurt region) as processor. If the plan is permanently deleted or you delete your account, we delete the link and the copy of the list with it.
9n. Partner pages: contact details and photos from our partners
Retailers and manufacturers with a Partner Agreement have their own page on trackplanner.io (/partner/… or /hersteller/…). There they show, if they wish, their business contact details and one to three photos of people from their company. They send us the details via a personal link.
- Data processed: business contact details (customer service email, phone, postal address, address of a shop, link to the listing on Google Maps), which may contain names or direct-dial numbers of employees; for each photo, the image and the name and role of the person shown. When submitting via the personal link: name and role of the person submitting, the time, a salted hash value of the IP address and the shortened user agent. For sending the link, the email address the partner gives us for this purpose.
- Source: Everything is supplied by the partner. It obtains the consent of every person shown using our template and assures us that the consent has been given (Partner Terms Part I § 7 (5)).
- Purpose and legal basis: We show contact details to perform the Partner Agreement (Art. 6 (1) (b) GDPR); where they contain names or direct-dial numbers of employees, this is based on our legitimate interest and that of the partner in customers being able to reach it (Art. 6 (1) (f) GDPR). We show photos with names on the basis of the consent of the person shown, which the partner obtains (Art. 6 (1) (a) GDPR; where also applicable, Section 22 of the German Act on Copyright in Works of Art and Photography, KUG). We store the details of the submission as proof of who submitted what (Art. 6 (1) (f) GDPR).
- Responsibility: The partner is responsible for obtaining the consent, we are responsible for storage and publication; you can contact either of us.
- Recipients: Details and photos are kept in our database and a file storage at Supabase (hosting in the EU, Frankfurt region) as processor; the pages are delivered by Vercel (section 3). On trackplanner.io they are accessible to anyone worldwide. How we handle emails to info@trackplanner.io is described in section 7.
- Without metadata: We deliver photos without camera, location and time information. They are kept in a file storage at Supabase, not in our version control, so that we can delete them completely.
- Withdrawal: If you are shown in a photo and no longer want this, write to info@trackplanner.io or to the partner. A withdrawal takes effect for the future (Art. 7 (3) GDPR). If you contact us, we take the photo down without undue delay, without asking the partner first, and confirm to you when it has been removed. The photo can no longer be retrieved after one minute at the latest; name and role disappear from the cached page as soon as the page is regenerated, at the earliest after one hour.
- Objection: If your name or your direct-dial number appears in a partner’s contact details, you can object (Art. 21 GDPR); we will then remove that detail; it disappears from the cached page as soon as the page is regenerated, at the earliest after one hour.
- Storage period: Contact details and photos until an objection or withdrawal or until the partner replaces or withdraws them, at the latest until the end of the Partner Agreement. For a removed or rejected photo, we then keep for 24 months only when and why it was removed, without the image, name and role. We delete original files after the review. For a submission we have decided on, we keep for 24 months only who submitted when (name, role, time, hash value of the IP address, user agent), not the submitted details. We delete a submission on which we do not decide, together with its details and files, after 24 months at the latest. We delete the email address to which we sent the link 30 days after the link expires or is revoked.
- Search engines: The partner pages are open to search engines. We cannot delete copies held by search engines ourselves; on request, we ask the search engine to update them.
10. Your rights
You have the right at any time to access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) as well as to object (Art. 21) and to withdraw consent given (Art. 7 (3) GDPR). You also have the right to lodge a complaint with a data protection supervisory authority.
Competent supervisory authority: Berlin Commissioner for Data Protection and Freedom of Information (BlnBDI), Alt-Moabit 59–61, 10555 Berlin, Germany.
11. Users in Japan (Japanese data protection law APPI)
We process personal data of persons living in Japan in accordance with the other sections of this policy and additionally in accordance with the Japanese Act on the Protection of Personal Information (“APPI”). The Japanese version of this policy is available at trackplanner.io/ja/privacy.
(1) Controller: Georg Wächter (sole proprietor), Prinzessinnenstraße 29, 12307 Berlin, Germany. Representative: Georg Wächter.
(2) Purposes: We use the data for the purposes named in sections 1 to 10: managing the account, providing the service, billing, fulfilling tax obligations (including determining the country in which you live), answering inquiries, protection against abuse, improving the service, evaluating the usage history in the web app in order to calculate your interest in Premium and to show you suitable hints in the app (section 9e), sending emails with tips, news and offers, selected according to your usage (section 9k), measuring the effect of purchase links and partner referrals (sections 9 and 9c), and evaluating feedback and notifying you when a wish has been implemented (section 7).
(3) Disclosure to third parties: Without your consent, we do not disclose personal data to third parties unless a law provides for it. However, we use service providers who process data on our behalf; for service providers abroad, (4) applies. Messages to us also reach Google and Anthropic, which process them under their own terms and with which we have no agreements as described in (4) (section 7 and the last paragraph of (4)); we do not ask for consent for this.
(4) Disclosure to third parties abroad: We are based in Germany (an EU member state) and process personal data predominantly in Germany and in the EU. According to the finding of the Japanese Personal Information Protection Commission (“PPC”), the EU and the United Kingdom have a data protection system equivalent to the Japanese one. The following service providers are based in other countries or may access personal data from other countries, even if the data is stored in the EU. With data processing agreements and standard contractual clauses of the European Commission, we ensure that they take measures within the meaning of Chapter 4, Section 2 of the APPI (Art. 28 (1) APPI), and we regularly check whether they are implemented.
| Service provider | Country | Main task |
|---|---|---|
| Vercel Inc. | USA | Delivery of the website and the web app, audience measurement of the website |
| Supabase, Inc. | USA (storage in the EU, Frankfurt) | Database, sign-in, file storage, server functions |
| Functional Software, Inc. (Sentry) | USA (storage in the EU) | Recording and evaluating errors of the web app |
| Plus Five Five, Inc. (Resend) | USA | Sending emails |
| Sub-processors of Brevo GmbH | USA, India and others | Sending emails (substitute) |
| Migadu | Switzerland | Email mailbox |
| Stripe, Inc. (sub-processor of Stripe Payments Europe, Limited) | USA | Parts of payment processing |
| Anthropic, PBC | USA | Language detection and translation of wishes, comments and changelog entries in the feedback portal (title and text) |
| GitHub, Inc. | USA | Internal register of feedback, without names and contact details (section 7) |
Without such agreements, we also use Google (Google Ireland Limited, Ireland; Google LLC, USA) with a private Gmail account in which we read and answer messages, and Anthropic (Anthropic, PBC, USA; controller for customers in the European Economic Area: Anthropic Ireland, Limited, Ireland, with processing also in the USA) with a Claude subscription under Anthropic’s consumer terms for AI agents that read messages in full, translate them and draft replies (section 7). The assurance in the previous paragraph does not apply to these two; they process the data under their own terms.
On request, we will inform you without delay of an overview of these measures and information about the data protection systems of the countries in which the service providers are based (Art. 28 (3) APPI). The PPC also publishes information on the data protection systems of individual countries.
(5) Security measures: To protect personal data against unauthorized disclosure, loss and damage, we take the following measures:
- Principles: This privacy policy sets them out.
- Rules for handling: For collection, use, storage, disclosure and deletion, it is defined how we handle the data.
- Organizational measures: Georg Wächter is responsible for handling personal data. There is a defined procedure for reporting and responding to data breaches.
- Personnel measures: Georg Wächter is the only person who processes personal data. AI agents he uses (section 7) work on his behalf; he checks and sends draft replies himself.
- Physical measures: Devices with which personal data is processed are protected against theft and loss.
- Technical measures: encrypted transmission (TLS) and management of access rights (including row-level access control in the database).
- Understanding of the environment: We are based in Germany and process personal data in accordance with the GDPR. We have taken into account the data protection systems of the countries in which service providers are based (USA, Switzerland, India) in the security measures.
(6) Access and other requests: Regarding the personal data we have stored about you, you can request that we inform you of the purpose of use, that we disclose it (including the records of disclosures to third parties), that we correct, supplement or delete it, that we stop using it or delete it, and that we stop disclosing it to third parties. To do so, write from your account’s email address to info@trackplanner.io (so that we can verify that it is you). We do not charge any fees. We answer without delay, usually within one month, by email. You can also delete your account yourself in the account settings.
(7) Complaints and inquiries: info@trackplanner.io (also in Japanese).
(8) Data breaches: If a data breach occurs, we report it to the PPC in accordance with the APPI and notify the persons concerned.
(9) Minors: Minors use the service with the consent of their legal representative (for ordering paid pricing plans see Terms § 11 (9)).
12. Users in Canada
We process personal data of persons living in Canada in accordance with the other sections of this policy. In addition:
(1) Person responsible: The person responsible for the protection of personal information is Georg Wächter (owner), Prinzessinnenstraße 29, 12307 Berlin, Germany, email: info@trackplanner.io.
(2) Processing outside Canada: We are based in Germany and process your data outside Canada, mainly in Germany and in the EU. Some service providers are based in other countries, for example in the USA, Switzerland or India, or can access data from there. Which service providers these are and what we use them for is set out in the sections on the individual services (in particular 3, 4a, 6b, 7, 9 and 9d) and in the overview in section 11 (4).
(3) Your rights: You can request access to the personal information we hold about you, request its correction and withdraw consent you have given at any time; an email to info@trackplanner.io is sufficient. The rights under section 10 remain unaffected.
(4) Complaint: You can file a complaint with the Office of the Privacy Commissioner of Canada (priv.gc.ca).
13. Users in the United Kingdom
We process personal data of people in the United Kingdom under the other sections of this policy; the UK GDPR and the Data Protection Act 2018 also apply. You have the rights listed in section 10 under the UK GDPR as well. You can also complain to the Information Commissioner’s Office (ico.org.uk). Data we transfer to service providers in the USA is protected as described in the individual sections; for transfers from the United Kingdom, the UK Extension to the Data Privacy Framework applies where the provider takes part in it.