Privacy Policy

Last updated November 13, 2026. Change history

This policy covers ErgIntz: the iPhone and Android apps, the website ergintz.app, and the parts of the ErgIntz Grand Prix game that use your ErgIntz account. It has two parts: this page, which says what we hold, why, for how long, and what we promise; and Privacy details, which lists who can see what today, which companies process data for us, and the cookies the website sets. The details page is part of this policy. “We” means Martin Ahlberger, who runs ErgIntz (below).

Who is responsible for your data

Martin Ahlberger, a private individual resident in Sweden, is the data controller for ErgIntz. A controller does not have to be a company — GDPR Art. 4(7) defines one as “the natural or legal person” who decides why and how personal data is handled.

Contact: hello@ergintz.app. You do not need an account to write.

If someone else takes over running ErgIntz (for example a company formed for it), that person or company becomes the controller. We will tell you in the app and on the website before it happens, saying who it is. They take over this policy as it stands, including “Our promises”, for the data collected under it. If you do not want your data to move to them, you can delete your account before the date. A change of controller does not by itself change what we hold, why we hold it, or any of your rights over it.

Our promises

These hold whatever ErgIntz looks like in future. If one ever had to change, we would tell you first (see Changes).

  • We do not sell your data, and we do not share it with advertisers.
  • No advertising, no tracking, no analytics in the app. The apps contain no advertising, analytics or tracking code. The public website counts its visitors with Cloudflare Web Analytics, which uses no cookies and does not follow you between sites.
  • Your heart rate is stored only if you agree, and turning off “Heart-rate data” erases what is stored.
  • There is no password. Your account is your email address, proved by a code we email you. A Concept2 Logbook is an optional connection you add afterwards, not your identity.
  • You can use ErgIntz without an account. The app works with your erg and keeps your workouts on your phone. Without an account, all that reaches us is a short report when something goes wrong in a workout (which you can switch off) and the technical record any request to our server leaves (see “Technical logs”).

What we hold

We hold these kinds of data. The examples are examples, not a complete list: a new feature may use these kinds of data for the purposes below. A kind of data in none of these categories is announced first (see Changes).

  • Account and sign-in. Your email address and when it was verified — it is your account. For each sign-in code you request: your address, the time, how many attempts, and hashes of the code and the link, never the code itself. One sign-in token per signed-in device, stored only as a hash, with a label and when it was last used. Which version of this policy you were last shown.
  • Profile. What you choose to give about yourself: display name and username, a profile picture, a 5 km benchmark per erg, and, if you give them, weight, height, country and year of birth; gender if a Concept2 Logbook is connected. The benchmark is what “% of 5k pace” targets resolve against; weight and gender derive your Logbook weight class; weight also gives the figures per kilo used where results are compared (see Privacy details). The ErgIntz apps, the website and the Grand Prix game share this one profile; clearing a field clears it everywhere.
  • Training. The workouts you build, save or publish to share by link; your sessions — start and end time, the time zone you erged in, distance, elapsed time, average and max heart rate (see below), average power, calories, the effort you set, which erg, and a second-by-second recording of the session and its laps. That last one is most of what we store about you, and it is what makes splits, personal bests and FIT export work. The results, records and bests calculated from them.
  • Heart rate — only if you have agreed: per session, per lap and per second of the recording.
  • Social. Your username (the @name people can find you by), friends, friend requests you have sent and received (also declined ones, so that declining stays silent), people you have blocked, and reactions and messages you give or receive, such as fist bumps (also one taken back) and cheers, with who sent them and when.
  • Clubs. Which clubs you are in, your role, when you joined and left, the message you wrote when asking to join, which club workouts you completed and when you erged them, and entries in a club's admin log naming you — approved, declined, removed, promoted, left — so a member can ask “who removed me?” and get an answer.
  • Live. While you erg live — in a club's live time, or in a session of your own that others may watch or join — your phone sends your progress (distance, time and watts per interval) every couple of seconds, with the workout, the erg, when you started and who joined.
  • Settings and choices. Your preferences (pace or watts, appearance), every visibility, notification and email switch, your agreement to storing heart rate, and when you were told that your results appear on ErgIntz's public boards.
  • Connections. For each service you connect (a Concept2 Logbook, or a training platform such as intervals.icu): the account id and name it gives us, the tokens needed to reach it (encrypted for a training platform), and what was sent there, so nothing is sent twice and a failure can be retried.
  • Notifications. If you allow them on your phone, a notification token for that phone and a record of each notification sent; and the list of notifications kept in the app and on the website, written whether or not your phone allows notifications. A notification carries names (a person's, with their username, or a club's), a workout's or session's title, which erg and a time.
  • Purchases. Premium is bought in the Grand Prix app, through the App Store. Apple takes the payment; we never see your card, your Apple ID or your name. What Apple tells us, and we keep with your account, is the subscription's status: Apple's id for the subscription, whether it is monthly or yearly, whether you are in the free trial, when the current period ends, and whether it is renewing, in a billing problem, refunded or ended. For a club that is billed: a billing contact name and email, the organisation's org.nr and invoice reference, and a Stripe customer id. No invoice has been issued — this is machinery, not history.
  • Data about people who do not have an account. A personal club invite holds the name and email address a club admin addressed it to. If you are that person and did not ask to be here, email hello@ergintz.app and we will remove the entry. You do not need an account to ask.

The app's diagnostic log, if you switch it on

The app keeps a technical log of what it does with your erg — the Bluetooth connection, the workout it sends, what the PM5 answers. It is there because that is the only way anyone can work out why a workout would not load on a machine we cannot see.

It is off unless you turn it on. The app asks once, the first time you open it, and you can change your answer at any time under Diagnostics in Settings — the exception is a test build handed out for testing on an erg, which starts with it on and says so on that same screen. Not every version of the app has that section; where it is absent, nothing is sent at all. Turning it off stops it immediately. While it is on, the log is sent to us with your account, an id for that installation of the app, and which build it is. It holds no heart rate, no e-mail address and no sign-in code: those are stripped on your phone before anything is sent, and stripped again when it reaches us.

A short report when something goes wrong

Separately from the log above, and on unless you switch it off under Diagnostics in Settings, the app sends us a short report when something goes wrong during a workout — for example when the erg drops the program it was given, the connection stalls, or the app is ended before your session was. The report is the last few minutes of the same technical log, with the same things stripped on your phone and again when it reaches us (no heart rate, no e-mail address, no sign-in code), and the workout program the app sent to your erg (the workout's steps and the commands the erg was given), which is what usually explains why a workout stopped. It also holds a few facts about the circumstances: whether the app was on screen, how much memory was free, and the power and battery state. It is sent with your account if you are signed in, and without any account if you are not — then it carries only an id for that installation and the build, and no name or e-mail address. Turning the switch off stops it immediately.

Technical logs

Like any website, our server and the proxy in front of it record each request they receive: the time, the address asked for, the IP address, and the app or browser name. They are used to find faults and abuse.

What we do not collect

No advertising identifiers, no contacts, no location, no browsing activity, no third-party analytics or tracking SDKs in the app, and no payment card details — a card is handled by Stripe or the app store and never reaches us.

Bluetooth

The app talks to your PM5, and to a heart-rate strap if you pair one, over Bluetooth. That connection is between your phone and the device. The data becomes ours only if you are signed in and the session syncs.

What we use it for, and why we are allowed to

  • Performance of a contract — running the service you signed up for: your account and sign-in, storing and syncing your workouts and sessions, calculating results, records and bests, syncing to a service you connect when you ask, the notifications you allow, and knowing whether you have Premium.
  • Performance of a contract — clubs. A club's boards, roster and live screens are what you ask for by joining it, so your name and results are shown to its members for as long as you are one. When you leave, you stay on its past boards as a former member; to have your name taken off them, email us.
  • Performance of a contract and legitimate interests — sharing beyond your clubs as your settings say: being found, friends seeing your sessions and records, others watching or joining you live, and showing you on ErgIntz's public boards. ErgIntz is an app for erging with other people, and this sharing is part of the service you sign up for; where it reaches people outside it, our legitimate interest is that it works for everyone who uses it. Each has its switch in Settings, which you can turn off at any time, and turning it off is how you object. Results are shown next to names by default: that is what the app is for. If the year of birth you give says you may be under 16, “Show me in search” starts off.
  • Explicit consent — heart rate. Heart rate can say something about your health, so we treat it as special-category data (GDPR Article 9) and store it only after you have agreed in the app. Sessions synced before you agree carry no heart-rate data. If you had already recorded heart rate before the app started asking, we took that as your agreement. Withdrawing is one switch: turn off Heart-rate data in Settings (Sharing & privacy) in the app, and that erases the heart rate already stored — here and on your phone — and stops new readings being recorded. Deleting a session or your account removes its heart rate too.
  • Legitimate interests — keeping ErgIntz safe and working: security, preventing abuse, technical logs, the diagnostic log and failure reports, the test copy (see “Where it is stored”), and the club admin log, because a member must be able to find out who removed them.
  • Telling you about your account and this policy — sign-in codes, notices about your data, and the notice shown when this policy changes. These are part of the service and our duty to inform you.
  • Legitimate interests — news by email. Now and then we may email you news and tips about ErgIntz. Every such email has an unsubscribe link, and once you use it we stop. You can object at any time.
  • Legitimate interests — counting visits to the website's public pages, without cookies.
  • Legal obligation — payment records, which Swedish bokföringslagen requires us to keep for seven years, and answering a request from an authority that the law obliges us to answer.

What you must give. To have an account you need an email address; without it we cannot sign you in. Everything else is optional, and the app works on your phone without an account.

No automated decisions. We make no decision about you by automated means that has legal or similarly significant effects. (The Grand Prix game flags rides that look wrong for us to review; the flag never stops a ride.)

Who can see what

What others see depends on your settings and on the clubs you join. These rules hold whatever the app looks like; the exact, current list — which audience sees which item, and which switch controls it — is on Privacy details.

  • In a club, members see your name, your results and attendance on the club's workouts, and your sessions of those workouts. Admins also see the club's admin log, and which members have not erged lately. Leaving a club keeps your past results on its boards, marked as a former member; ask us and we take your name off.
  • Beyond your clubs, your sessions, records and live sessions are shown only as far as your settings allow, and you can hide a single session.
  • Being found by name, by username or as a suggestion can be switched off.
  • People without an account see only what is published: ErgIntz's own public boards, a club's public page, a workout or live link someone chose to share, and a club's live screen if the club published it. Where results are compared, figures per kilo are part of what is shown if you have set a weight.
  • Reactions and cheers show who sent them, to everyone who can see what they were sent to.

Anything that would let more people see something than today, or start sharing something by default that is off today, is announced first (see Changes).

Who else receives it

We do not sell your data and we do not share it with advertisers. It reaches others only in the roles below. Which companies fill each role today, where they are and what they get is on Privacy details.

Companies that work for us — processors, under a data-processing agreement, using your data only on our instructions:

  • hosting and storage: the server ErgIntz runs on, and its backup;
  • email delivery: sign-in codes, notices about your account and your data, and news unless you have unsubscribed;
  • notification delivery: a phone's notification token and the notification itself;
  • visitor counting on the website's public pages;
  • payments for clubs, once a club is billed.

Services that handle data under their own policy — independent controllers, handling what reaches them under their own privacy policies and their own legal basis, so there is no data-processing agreement with them:

  • the app stores (Apple and Google), which distribute the apps and sell subscriptions; we receive a subscription's status, never your card or store account;
  • services you connect yourself, such as a Concept2 Logbook or a training platform: only what you choose to send after you connect, with heart rate only if you agreed to store it. They may process it outside the EU, and may forward it to services you connect on their side.

Apps that sign in with your ErgIntz account, such as the ErgIntz Grand Prix game, are run by us; see ErgIntz Grand Prix.

Authorities, only when the law obliges us to give them something.

The people who run ErgIntz can see account data to support you, fix faults and keep the service safe. Today that is Martin alone.

Where these companies are. Several of them, including Resend, Cloudflare, Google and Stripe, are US companies. Your data is stored in the EU — the app and database run on a server in Germany or Austria, and the backup bucket is restricted to the EU — but sending a sign-in email through Resend routes your address through US infrastructure, and notifications pass through Apple's and Google's networks. Where personal data reaches the US like this, the transfer is covered by the company's certification under the EU–US Data Privacy Framework or by the European Commission's standard contractual clauses (and in several cases both), which are the safeguards EU law recognises for sending personal data to the US. Services you connect yourself are outside this: you send the data there.

Where it is stored

On a server in the EU, with a continuously replicated backup that is also kept in the EU. Privacy details names the provider and the country.

A test copy. To try new versions before they are released, we run a test server on the same machine, with a copy of the database made from the backup every night. Every email address except those of a few invited testers, and every sign-in token, connection and notification token, is removed from the copy, and so is the heart rate of everyone but those testers; your sessions, clubs and friends stay in it, on an encrypted disk. An erasure reaches the copy at its next refresh. If you are one of the testers and link the test app to your account, the sessions you erg there are sent on to your real account, and the test server keeps an encrypted sign-in token to do that until you unlink.

How long we keep it

These are maximums; we may keep things for less.

  • Your account, profile, workouts and sessions — until you delete them or your account. There is no automatic expiry.
  • The backup — a rolling seven days, so what is deleted is gone from it within eight days.
  • Friends, friend requests, blocks and fist bumps — until you remove them, or the session goes, or you are erased. A declined friend request is kept, so that declining stays silent.
  • Your profile picture — until you remove it or are erased.
  • Your results on a club's boards — for as long as the club exists, including after you leave, unless you ask us to take your name off.
  • Live progress — a club's live time, or a live session of your own and everyone's progress in it: 30 days, then it is deleted.
  • Notifications — each one sent to a phone is kept 30 days, then deleted. A phone's notification token is kept until you sign out on that phone or it stops accepting notifications.
  • Your notification list — 60 days.
  • Sign-in codes — 24 hours. The code itself expires in 15 minutes, and only its hash is ever stored.
  • Admin log entries — 400 days.
  • The app's diagnostic log — 30 days, if you switched it on at all.
  • A failure report from the app — 30 days, unless you switched reports off.
  • Technical logs — until overwritten: they are capped by size, so the oldest lines go as new ones arrive.
  • Contact details on a personal invite — cleared when the invite expires (30 days) or is withdrawn.
  • Premium subscription status — while your account exists. It goes with an erasure.
  • Connection tokens — until you disconnect, revoke the device or ErgIntz's access from the service, or are erased. Disconnecting a training platform also asks it to withdraw ErgIntz's access. What already reached a service stays there until you delete it there.
  • Payment records — seven years, as Swedish bookkeeping law requires. An erasure request does not override this.

Your rights

Under GDPR you can ask us to give you a copy of your data, correct it, delete it, restrict how we use it, or hand it to you in a form another service can read. You can object to anything we do on the basis of legitimate interests, and to news by email at any time. You can withdraw consent at any time, without affecting what was done before. Email hello@ergintz.app.

Things you can do yourself, right now, without asking:

  • change or clear anything in your profile, in Settings;
  • turn each sharing, notification and email switch on or off, and hide a single session from your friends and your clubs;
  • add or remove your profile picture, unfriend or block someone;
  • delete an individual session, from its own page;
  • revoke any device's access, and disconnect a service you connected;
  • leave a club;
  • delete your account, in the app under Settings › Account & profile › Delete account, or in Settings on the website (see below for what that does).

What an erasure actually does

Worth setting out, because it is not “everything vanishes”.

Destroyed: your sessions and their recordings, your workouts, your club memberships and completions, your join requests, workouts you published to share, invites you created, your Premium subscription status, every token, and every sign-in code ever issued to your address — including from before you finished signing up. Also your contact details wherever somebody else typed them: an invite addressed to you, a club billing contact that is you. It also deletes your data in apps that sign in with your account, such as Grand Prix.

Kept, with you removed from them: admin log entries (the entry stays, your name comes out, and the sentence is rewritten to a general one — an audit trail that disappeared with its subject would evidence nothing); a workout you shared into a club (it is the club's — deleting it would delete every other member's results against it); and payment records, for seven years, by law.

Refused until you fix it first: if you still own a club, we will not erase you. A club holds other people's data. Transfer it or wind it up, then ask again.

Erasing your account does not cancel a Premium subscription. Apple bills it, so it is cancelled in your App Store account settings — do that first if you no longer want it.

It is irreversible. There is no undo and no backup we will restore you from.

Complaints

If you think we have handled your data wrongly, please tell us first. You also have the right to complain to Integritetsskyddsmyndigheten (IMY) — imy.se — or to the equivalent authority in the EU country you live in.

Cookies

The website sets only cookies that are strictly necessary: to keep you signed in, to remember light or dark, to carry a sign-in, an invite or a connection safely between pages, and to keep a signed-out visitor's cheers together. None is shared with anyone. No analytics cookies, no advertising cookies, no third-party cookies. Their names and lifetimes are on Privacy details. If we ever wanted a cookie that is not strictly necessary, we would ask you first.

Children

You must be at least 13 to have an ErgIntz account. ErgIntz is not directed at children under 13 and we do not knowingly hold data about them. If we learn that an account belongs to someone under 13, we will close it and delete what it holds.

ErgIntz Grand Prix

You sign in to the game with your ErgIntz account. The game has its own server and its own privacy page, gp.ergintz.app/privacy, which says what it keeps and for how long; this is where it touches ErgIntz.

  • What the game reads from ErgIntz (read only; you edit these in ErgIntz): your account number, display name, FTP (from your 5 km benchmark), weight, height, whether you have agreed to store heart rate, your clubs (name, role, member count), your Premium status and your leaderboard switch. Your email address is read at sign-in and not stored by the game. Your best-power profile (5 seconds to 20 minutes, per erg) is used on your phone, and by the game's server only for its fairness check and, in a scheduled race, to estimate an FTP when you have no 5 km benchmark; the game keeps neither the profile nor the estimate. The fairness check keeps, with each ride, the one value it compared the ride with, and flags rides that look wrong; the flag is seen only by us and never stops a ride.
  • What the game writes to ErgIntz: each race you finish, as a training session; a note that a club session finished; and the game's short diagnostic log (kept 30 days, and you can switch it off). Heart rate does not reach the game's server.
  • What the game keeps itself, when you are signed in: your race history, ride recordings (used as ghosts), a backup of your profile, your display name, segment times, course records, copies of your clubs and Premium status, your settings, “I'm riding” (the race, your account number and the time) and the results of races with friends and scheduled races. As a guest, your races and progress stay on your phone. On Android, a start-up report (phone make and model, Android version, memory, crash text and game log lines; no account, name or email) is sent by default when a launch fails, even without an account, and is deleted after 90 days (a daily clean-up).
  • Who sees your name: other players, on the weekly boards, the course records, the segment boards, the streak list, with your ghosts and in races with others. A scheduled race's “I'm riding” list shows up to 12 display names, and a count to anyone. If you have hidden yourself from ErgIntz's leaderboards, you are left off those boards and records, are not raced as ghosts, and are counted but not named on “I'm riding”.
  • Where it runs and how long: on the same server and web proxy as ErgIntz (Netcup, Germany or Austria), with a backup in an EU-restricted Cloudflare R2 bucket. Race data is kept until you delete it. The proxy log (IP address, app or browser name) is kept about 2 days. The game's own request log (account number, no IP address) is cleared by size and can reach back a few months. The game ran on Fly.io (Stockholm) until 12 November 2026; a switched-off copy of its database is kept there until it is deleted on 12 December 2026.
  • Deleting it: in the game under Settings › Privacy › Delete my race data, or by deleting your ErgIntz account (in the game, on ergintz.app or in the app), which deletes the game's data too (gp.ergintz.app/delete-account). In other riders' finishing orders, in races with friends and scheduled races, a deleted rider is then shown as “Deleted rider”. Deleting your account does not cancel a Premium subscription.

Changes

We update this policy, and Privacy details, when ErgIntz changes. The date at the top and the change history say what changed and when.

We tell you first — in the app and on the website, before the change takes effect, and we keep a record of which version you were shown — if we:

  1. give your data to a new kind of recipient: a company in a role not listed under “Who else receives it”, or a kind of person who could not see it before;
  2. use your data for a purpose not described under “What we use it for”;
  3. store your data outside the EU, or send it outside the EU/EEA in a way not described above;
  4. start collecting a new kind of sensitive data, or use heart rate in a new way, such as showing it to other people; or collect a kind of data in none of the categories under “What we hold”;
  5. change who runs ErgIntz (see “Who is responsible for your data”);
  6. let more people see something than today, or start sharing something by default that is off by default today;
  7. keep something longer than the maximum under “How long we keep it”;
  8. remove a switch or a way to exercise your rights, or weaken any of “Our promises”.

A change in this list takes effect 10 days after we publish it, and continuing to use ErgIntz after that means you accept it. You can delete your account at any time, before or after. A correction of a mistake, or a change the law requires, may take effect at once.

Where the law requires your agreement to a change, we ask for it and do not assume it.

Anything else may be updated without a notice — for example a new feature that uses the data and purposes described here within the rules under “Who can see what”, a new company in a role already listed, shorter retention, a new switch, or a clearer sentence. The date at the top and the change history still show it.

Change history

  • November 13, 2026: The policy is now in two parts: the rules and promises, and Privacy details, which lists who can see what today, the companies we use and the cookies. It now also says what we will always tell you about before it changes, and covers news by email, server request logs and requests from authorities. It gives the legal basis for what others see by default (the service itself, with a switch for each), how long the backup keeps data, and the companies that deliver notifications. If your year of birth says you may be under 16, you start out of search, and our test copy no longer holds anyone's heart rate except a few testers'. Nothing else about what we collect or who can see it changed.
  • November 13, 2026: We added social features: live sessions, friends, seeing each other's activity, fist bumps and ErgIntz Grand Prix. To support them we updated our privacy policy. Your data is kept as secure as before, but what others can see of you changes a little. Heart rate is stored only if you agree. You can decide what is shown to others in Settings.
  • November 13, 2026: The Grand Prix game's use of your account is now described in the policy. Grand Prix shows your name and times to other players; riders hidden on ErgIntz are left off its boards. It runs on the same servers as ErgIntz, and deleting your account deletes its data.
  • November 11, 2026: ErgIntz now runs on a server in Germany (Netcup) instead of Sweden (Fly.io). Your data stays in the EU, and nothing else about who can see it changes.
  • November 10, 2026: Friends can see your sessions and records unless you choose Only me. You choose who can watch you erg; it starts at Only me. Club pages can be opened by people who aren't members.

Contact

hello@ergintz.app

See also Privacy details and our Terms of Service.