Skip to content

Taperly launches on Product Hunt on October 3Take a look

Privacy policy

Last updated: 18 September 2026

This policy explains how Taperly handles personal data on this website and, in the mobile app section below, in the app. Taperly is operated by Dot Systems, Sweden, which is the data controller for everything described here. We keep the policy short because we collect very little.

What we collect

  • Your email address, if you choose to join the waitlist. That is the only personal detail we ask for.
  • Basic, privacy-friendly analytics about page visits (e.g. page views and rough region) so we understand how many people reach the site. This does not identify you personally.

Why we use it

We use your email for one thing: to tell you when Taperly launches. That is one email. We do not sell, rent or share it, and we do not use it for advertising. You can ask us to remove you at any time.

The legal basis for storing your email is your consent, given when you submit the form.

Who processes it

Waitlist emails are stored in a database provided by Supabase, in a data centre in the EU. Only our own server can read or write that table.

The site is hosted on Vercel Inc. (United States), which also provides two of the three measurement tools we use: Vercel Analytics for page views and Speed Insights for load performance. Neither sets a cookie and neither identifies you personally. We also load a small self-hosted visitor counter from tracker-mauve-sigma.vercel.app. It counts visits; because it is fetched from another domain, your IP address reaches that server as part of the request, the same way it does for any image or script.

The homepage can show our latest TikTok videos. That content loads only if you press the button that says so; pressing it fetches the feed from TikTok, which then processes your IP address and may set cookies under its own policy. If you never press it, nothing is ever fetched from TikTok.

All of these providers process data on our behalf and are not allowed to use it for their own purposes. Nothing on this site stores or reads anything on your device without you asking for it, so there is no cookie banner.

How long we keep it

We keep your email until Taperly has launched and you have had the chance to download it, or until you ask us to delete it, whichever comes first.

Your rights

Under the GDPR you can ask us to access, correct or delete your data, to withdraw the consent you gave, or to have it sent to you. Email us and we will take care of it, normally within a few days.

The mobile app

Taperly does not require an account. Your races, bags, checklists, reminders and preferences are stored on your phone. We do not receive a copy of your saved race data.

  • Weather and place searches. The app sends the requested race coordinates or search terms to Open-Meteo.
  • Things you choose to send. Exporting a backup gives the file to your phone's share sheet, where you choose its destination. Loading a race photo, guide or map contacts its publisher.

The reporting details below apply from version 1.2.0. Version 1.0.1 asked first and used a random installation identifier; 1.2.0 asks nothing and stores no identifier.

Anonymous usage counts and error reports. The app sends anonymous usage events and technical JavaScript error reports to PostHog in the EU. This is on from the start and you can turn it off at any time in Settings under Share anonymous usage data. We use these reports to understand which features people use, count return visits per week and find and fix app errors. The legal basis is our legitimate interest in keeping the app working and useful, and because no event carries an identifier, no report can be tied to you or your phone.

There are 24 named usage events, covering opening the app, onboarding, adding or replacing a race, opening and ticking plans and packing lists, sharing a card, reminders being scheduled and opened, the notification permission answer, the review prompt, feedback links and exporting a backup. They can include a predefined screen, onboarding step, phase or reminder type, but never the race name or text you entered. Each event also carries the week the app was installed (or that it was installed before 1.2.0), the country from your phone's region setting (never your location), the number of saved races and the app version.

There is no installation identifier. The analytics library adds the app version and build, device model and manufacturer, operating system and version, screen size, language, time zone, whether it is a simulator, and a random session number that lives only in memory and is never stored. On your phone the app keeps only the day it was first opened and the last day an open was counted, so the same day is not counted twice.

Error reports include the error type and stack positions. Error messages, local variable values and source-code context are removed before sending. We do not attach your saved races, profile fields, email address or race coordinates. There are no screen recordings, advertising identifiers or advertising tracking.

Providers receive your IP address when handling online requests. Taperly discards client IP data in PostHog, disables its IP-based location enrichment and does not send GPS or race coordinates to PostHog.

Turning reporting off in Settings stops new reports and clears unsent reports from the app's queue. It does not recall reports already sent, and because those carry no identifier they cannot be found and deleted afterwards.

Contact

Questions, or a request about your data? Email hello@build2race.com. You can ask us what we hold, ask for it to be deleted, or object to the usage counts at any time, and you can complain to Integritetsskyddsmyndigheten if you are not happy with how we answer.