Privacy Policy

StintBox ("we", "us") is developed by Kameli ApS, based in Denmark. This policy explains what data we collect, why, and how we protect it.

StintBox may offer optional cloud storage for video and telemetry files. This is always opt-in: your data is never uploaded without your explicit action. Cloud-stored data is encrypted at rest and only accessible to your account. If your paid access ends, uploading stops, but nothing is locked: everything already in the cloud stays visible and downloadable for another 365 days, and you never have to pay to get it back. We email you during that window (weekly, then daily for the last three days) with the exact deletion date and what renewing would restore. Renewing at any point turns syncing back on with your data still in place. After the 365 days the cloud copies are permanently deleted; the copies on your own computer are untouched. You can also delete your cloud data yourself at any time. It stays recoverable for 30 days, then it is gone for good. Legal basis: performance of our agreement with you while your plan is active (GDPR Article 6(1)(b)); for the 365 days after it ends, our legitimate interest in giving you a fair chance to come back without losing your work (Article 6(1)(f)), which you can end at any time by deleting your cloud data.

You can link StintBox to services you already use. Today that means Strava. When you connect Strava, we ask for read access to your profile and activities, including activities you have marked private, because importing those is the point of the feature. StintBox reads activity data such as GPS position, speed, heart rate, power, cadence and altitude, and turns it into telemetry you can overlay on your video. In the desktop app your Strava tokens are encrypted and stored only on your own computer. If you connect from the website instead, they are encrypted and stored on our servers so the site can list your activities. Disconnecting inside StintBox revokes our access at Strava and deletes the stored tokens. Disconnecting from inside Strava has the same effect: Strava tells us, and we delete our copy. Legal basis: performance of our agreement with you (GDPR Article 6(1)(b)), for as long as the connection is active.

• Social platforms: link a YouTube, TikTok, Instagram, Facebook or X account and we hold the token that lets us post for you, until you unlink it. For Instagram, Facebook and X the video passes through our server on the way; for YouTube and TikTok it goes straight from your phone to the platform. Once it arrives it is on their terms, not ours.
• Your own cloud storage: connect Dropbox, OneDrive or Google Drive and your sessions and videos go into your account there, under that provider's terms. We hold the token until you disconnect. Deleting your account cancels every one of these connections at the provider as well as here.

Going live is off until you start it. While a broadcast runs, your speed, lap times and position go out to a link once a second. Anyone who has that link can watch, and can pass it on. Inside a privacy zone your position is left out, and your heart rate is sent only if you switch that channel on, for that one broadcast. The video is not part of a broadcast: it stays on your phone unless you back it up yourself.

• We hold the last 30 seconds back before viewers see them, so a broadcast can be stopped before those seconds reach anyone. Up to 500 people can watch at once, and a broadcast that goes quiet for 120 seconds ends on its own.
• We keep a copy of the telemetry you broadcast for 30 days after it ends, so that we can investigate misuse of the service, for example if a broadcast is used to help commit an offence or to harass someone. The copy never contains your heart rate, and it never contains anything about the people who watched. It is kept for those 30 days whether or not you delete your account, and is then deleted automatically. There is no other copy.
• A copy that exists is a copy an authority can require us to hand over. That is true of any service that keeps anything, and it is why this one is small, short lived and has a single purpose. About the people who watch we know nothing except their IP address.

A StintBox camera is pointed at you and your vehicle, which is what it is for. In practice someone in the paddock or on the road can end up in the background of a clip. They are never the subject, we do not identify anyone, and we do not search your footage. But if you upload, publish or broadcast something with other people in it, that decision is yours, and it is worth making the way you would want it made about you. On a group ride, remember that your position is roughly everyone else's too.

• License validation: verify your license is active and within device limits
• Account management: login, password reset, subscription status
• Support: respond to your inquiries
• Product improvement: aggregate, anonymized statistics (e.g., "X% of users are on Windows"), never individual tracking

We do not sell or share your personal data with third parties, except:

• Paddle.com: processes payments as merchant of record
• Backblaze B2 (EU region): stores the files you back up to the cloud, meaning your video, telemetry and project files. They hold the storage; only your account can retrieve them. Data processing agreement signed.
• Sentry (Functional Software, Inc.): receives anonymous crash reports and performance data to help us fix bugs. No personal data is shared. See Sentry's privacy policy at sentry.io/privacy
• SparkPost (EU region): delivers our email (sign-in links, account notices, and the newsletter if you asked for it). Data processing agreement signed.
• Hetzner (Falkenstein, Germany): hosts our servers and database. Your data does not leave the EU.
• Law enforcement: if legally required by Danish or EU law
• VersaTiles: serves the optional satellite map background. Every tile request tells them roughly where your track is, along with your IP address. The background stays off until you switch it on.
• Platforms you publish to, and cloud accounts you connect yourself: YouTube, TikTok, Instagram, Facebook, X, Dropbox, OneDrive, Google Drive. Nothing reaches any of them until you link the account and press publish or back up.

That's it. No ad networks, no data brokers.

• Server located in Germany (Hetzner Cloud, Falkenstein)
• Data encrypted in transit (TLS 1.3) and at rest
• Passwords hashed with bcrypt
• Machine IDs stored as SHA-256 hashes only
• Database: PostgreSQL with regular backups

Under EU/GDPR, you have the right to:

• Access: request a copy of your data
• Correction: update inaccurate data
• Deletion: request complete deletion of your account and data
• Portability: receive your data in a standard format
• Objection: object to specific processing

To exercise any right: email [email protected]. We will respond within 30 days.

stintbox.app uses minimal cookies:

• Session cookie: keeps you logged in (essential, no consent required)
• Referral attribution cookie: 30-day first-party cookie for referral tracking (legitimate interest)

We do NOT use third-party tracking cookies, Google Analytics, Facebook Pixel, or similar.

StintBox is not directed at children under 16. We do not knowingly collect data from children.

• Account data: retained while your account is active. Deleted within 30 days of account deletion request.
• Cloud backups: kept until you delete them. There is no time limit while your plan is active.
• Cloud backups on the free quota: kept while your account is active, with no time limit. There is no lapse to count from, so nothing expires on its own. Deleting your account removes them on the same 30-day schedule as the rest of your data.
• After paid access ends: uploading stops, but everything already in the cloud stays visible and downloadable for another 365 days at no cost. We email you first (weekly, then daily for the last three days) with the exact deletion date. After 365 days the cloud copies are permanently deleted.
• Cloud data you delete yourself: kept for 30 days so you can undo a mistake, then permanently deleted. Deleting your account removes your cloud data on the same 30-day schedule.
• Storage capacity: in rare cases we may need to remove an exceptionally large project earlier than the periods above. We give at least 30 days' notice by email first (see our Terms).
• License validation logs: retained for 12 months, then automatically purged.
• Payment records: kept for five years after the end of the financial year they belong to, as Danish bookkeeping law requires.
• A payment made without an account: the whole record, including name, billing address, country and VAT number, kept for five years after the end of the financial year it arrived in, then deleted.
• Live broadcast telemetry: an administrative copy kept for 30 days after the broadcast ends, then deleted automatically. It never contains heart rate.
• Security and administration log: the event is kept, and the user id and the IP address on it are removed after two years.

You delete your account in the app, under Settings, Account, Delete account. You are signed out everywhere at once, your profile stops being visible to anyone else, and we email you a link that puts it all back. After 30 days it is permanent, and we send one reminder first. At that point your sessions, videos, tracks, presets, settings, devices and login are deleted from our database and from our storage, and your connections to other platforms are cancelled at those platforms as well as deleted here.

• You choose what happens to what you shared with other users, such as a track outline, a preset or a PID definition: take it with you, or leave it for everyone else without your account attached. Leaving it does not make it anonymous, because a track is still a place and a preset is still a configuration. Anything you wrote in your own words, such as a review, is deleted either way.
• Your payment history goes with the account, apart from the bookkeeping record described under Data Retention. What survives is the amount, the currency, what the payment was for, the date and the payment reference, not your name, email address or billing address. If you paid us without ever creating an account, we keep that record whole, including name, billing address, country and VAT number, for its five years. That is wider than a bookkeeping voucher needs, and it is a deliberate decision: an unmatched payment has to stay reconcilable to the person who made it for as long as we hold it at all. Your invoices are held by Paddle under their own legal obligations, which we cannot shorten.
• What we cannot take back, because it was never only ours: what someone has already watched, a link someone saved, a post you published to another platform, a file you sent to your own Dropbox, OneDrive or Google Drive, and whatever our payment provider must keep. We can switch a broadcast off; we cannot unsee it for anyone.

We will notify you of material changes via email at least 30 days in advance. Non-material changes are posted here with an updated date.

• General: [email protected]
• Privacy-specific: [email protected]
• Data Protection: Kameli ApS, Denmark