Privacy · Risegate

Last updated: 30 October 2026

The short version

The computer app keeps your runs on your computer. It analyses videos there, and we never see them, unless you turn on "Send my videos to Risegate".
The iPhone app sends a video to our computer to time it, and the video is deleted as soon as it's timed. Your runs and videos are kept on your phone. Only their times are kept in your account, so your other devices show them too, never the videos.
Your account holds your name, your email and how you sign in, and, if you use them, your username, your team, your messages, your runs' times and any feedback you send us.
Usage and crash reports are anonymous. Both apps ask first, and send none until you say yes. They never contain your videos, times, name or email.
We don't sell anything. No ads, no selling, no sharing beyond the companies listed under Who handles your data, which work for us.
You're in charge. You can see, download, correct or delete your data, and delete your account in the app. Write to [email protected] for anything else.

Who we are

Risegate is run by Kiddi, s.r.o., Moravská 63, 040 01 Košice, Slovakia (company ID 46703756, VAT ID SK2023555193, registered in the Commercial Register of the Municipal Court Košice, section Sro, entry 30010/V). The company is responsible for your data (the "controller" under the EU's General Data Protection Regulation, the GDPR). For anything on this page, write to [email protected].

What the app does on your computer

When you add a video, Risegate copies it into its library folder on your computer and analyses it there: it finds the skier, the gates and the time. None of that is sent anywhere. You can see the folder under Settings, then Library, and delete any run in the app.

The Windows app checks for updates by asking download.risegate.eu (run by Cloudflare) for the newest version. That sends only the app's version; the server sees your IP address.

What the iPhone app keeps on your phone

Your timed runs, their videos, your trainings and, for a coach, the names of your athletes are kept on your phone, for each account separately. Your sign-in is kept in the phone's Keychain. Signing out keeps them on the phone; deleting your account deletes them. Deleting the app deletes all of it. These are needed for the app to work, so they need no extra agreement.

Timing a run in the iPhone app

The iPhone app can't time a run on the phone yet. When you pick a video to time, the app sends it to a Risegate computer in Slovakia. That computer times it and sends the times back to your phone. You need to be signed in to do this. The computer checks your sign-in with the account service, and shows a run's times only to the account that sent it.

What the computer receives

The video file. A video longer than a minute is cut to the part you keep, and one bigger than 1080p is made smaller, on the phone first. That includes the people in it, and whatever your phone saved in the file. That's usually when it was filmed and the phone model, and often where it was filmed.
The file's name, the run's name, the discipline you picked, and which account sent it.
Your phone's notification address, so the computer can tell you when the run is timed (see Notifications). With notifications off it is still sent, only so the computer can quietly wake the app to bring in the times: nothing shows on your screen.
Your IP address. Every upload over the internet reveals it.

How long it's kept. The video is deleted from the computer as soon as it has been timed, usually within minutes. A video that never finishes uploading is deleted within 6 hours. The times, the run's name and the notification address stay on the computer for up to 3 days, so your phone can fetch them, and are then deleted. The computer also counts how many runs each account sent today, to keep the daily limit; only today's count is kept. Nobody looks at the videos, and they are used for nothing else.

Who else handles it. The phone reaches the computer through Cloudflare, Inc. (Cloudflare Tunnel), which passes the upload on and may keep IP addresses in its logs for a short time.

Why we're allowed to: it is needed to give you the time you asked for (GDPR Article 6(1)(b), contract). If other people are in the video, see Other people in your videos.

Your runs on all your devices

So that the iPhone app and the web app show the same runs, and a new phone, or the app installed again, gets them back, each run's times are kept in your account: the run's name, the athlete's name, the date it was filmed, the gate times, the frame rate, the video's length, the part of the video kept, the first and last gate you marked, the video file's name, your note, the warnings it got, which gates you checked, the lean timing the web app found, the training it belongs to (its name, date and discipline) and your groups of trainings. Never the videos: a run that came from another device shows its times, and says its video is on that device. Runs that couldn't be timed, and runs still being timed, stay on the device.

These are kept by Supabase, Inc., the same service that runs sign-in. Only your account can read them; a coach doesn't see the runs athletes keep in their own accounts. A run, training or group you delete is deleted there too (a note that it was deleted stays, so your other devices delete it as well), and everything goes with your account. Why we're allowed to: it is needed to give you your runs on every device you sign in on (GDPR Article 6(1)(b), contract).

Notifications

If you allow notifications, the iPhone app tells you when a run is timed or couldn't be timed, shows runs being timed on the Lock Screen (a Live Activity), and rings when a message comes in. Notifications are delivered by Apple's push service, so they pass through Apple, Inc.

Your phone's notification address (a code Apple gives the app, not your phone number) is kept with your account by Supabase. It's deleted when you sign out, turn notifications off, Apple says it no longer works, or you delete your account.
A message notification shows the sender's first name, in a team chat the team's name, and the first 180 characters of the message. A run notification shows the run's name and its time.

You can turn each kind off in the app's Settings, then Notifications, or all of them in the iPhone's Settings. Why we're allowed to: you asked for them by allowing notifications (GDPR Article 6(1)(b), contract).

Usage and crash reports

In the computer app the app asks you once whether it may send anonymous usage and crash reports, and you can change your answer any time in Settings, then Privacy. Until you say yes, it sends none.

What they contain: which screens and buttons you use, when the app opens, whether each analysis was a quick time or a full analysis, how long it took and whether it finished, the video's length, frame rate and resolution, the discipline you picked, the number of gates found and whether a time came out, the app's version, and your computer's system and processor type (for example "Mac, macOS 15, arm64"), and, when something breaks, the error and where in the app's code it happened. An error message can include a file's name; your computer's user name is removed from it.

What they don't contain: your videos, your times, your name, your email or your account. Each report carries only a random number made when you say yes and thrown away when you say no, so it isn't linked to you, and saying yes again starts a new one. Why we're allowed to: you agreed (GDPR Article 6(1)(a), consent), and you can withdraw that any time.

In the iPhone app the app asks you once whether it may send anonymous usage reports, and you can change your answer any time in Settings, then Data controls. Until you say yes, it sends none. They contain when the app opens and how long it stays open, which tab you open (Home, Runs, Messages), how many videos each analysis sends, how many runs it adds without a video, whether they go into an existing training, and which discipline, whether each run was timed, how long that took, the video's length and the number of gates, the reason when a run couldn't be timed, whether you're signed in and as a coach or athlete, the app's version, and the phone's system version and whether it's an iPhone or iPad. They don't contain your videos, your times, your name, your email or your account: each report carries only a random number made when you say yes and thrown away when you turn reports off. Why we're allowed to: you agreed (GDPR Article 6(1)(a), consent), and you can withdraw that any time by turning the switch off.

Both apps' reports are kept for us by PostHog, Inc., in data centres in the EU (Frankfurt). Sending them reveals your IP address; PostHog is set to throw it away and doesn't look up your location. Only the Risegate team sees the reports, and uses them only to find bugs and improve the app. We keep them for at most a year.

Your account

To time and analyse your runs you sign in: with a code we email you, with your email and a password, with Apple or with Google. The account holds your name, your email, how you sign in, your password if you set one (stored scrambled, so nobody can read it back, us included), your authenticator app's key if you turn on two-step sign-in, whether you subscribe and until when, and how many of your free analyses you've used. Nothing about your videos. If you use them, the account also keeps your username, team and messages (see Teams and messages), your runs' times (see Your runs on all your devices), your notification address (see Notifications) and your feedback (see Feedback and bug reports).

The sign-in codes and account emails are sent for us by Resend, Inc. from [email protected].

Signing in with Apple. If you choose Continue with Apple, Apple confirms the sign-in is really you and gives us your email address and, the first time only, your name. You can choose to hide your email, and Apple then gives us an address that forwards to yours. Apple's own privacy policy applies to what Apple does.

Signing in with Google. If you choose Continue with Google, Google tells us your name, your email address and a link to your Google profile picture, and confirms the sign-in is really you. That's all we ask Google for: nothing from your Gmail, contacts, Drive or anything else. We use your name and email for your account and nothing else; the picture link is stored with the account but Risegate doesn't show or use it. We never sell this information or use it for advertising. Risegate's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can remove Risegate's access at any time in your Google account's security settings; deleting your Risegate account deletes what Google told us.

The computer app asks the account whether you may analyse: when you sign in, when you start an analysis, and about once a day while it's open and online. Each time, the account service sees your computer's IP address and the time. It keeps the answer, so the app keeps working offline for up to 30 days.

Deleting your account. You can delete it yourself, in either app's Settings or on the website's Sign in page. That deletes the account and everything listed in this section at once, except messages you sent to a team (see Teams and messages). If you pay for a subscription, cancel it first.

The account is run for us by Supabase, Inc., in data centres in the EU (Ireland). Why we're allowed to: the account is needed to give you what you signed up for (GDPR Article 6(1)(b), contract). We keep it while you have it, and delete it within 30 days after you ask us to, or after 2 years without a sign-in.

Teams and messages

In the iPhone app, a coach can make a team and athletes can join it. This is optional. If you don't use it, none of this applies to you.

What we store

The team: its name.
Your username: you choose it (3 to 20 letters, numbers, dots or underscores) and can change it in Settings. A coach who types your username exactly can see it together with your name. There is no list or search of usernames. Only coaches can look one up, only by the exact name, and only 30 times an hour; we note when each look-up happened, to keep that limit, and clear the note after an hour.
Invites and team links: a coach can invite you by your username, as an athlete or as a coach, together with the name the coach uses for you in the app, and you accept or decline in the app. A coach can also share team links. Each link joins as an athlete or as a coach and works for 5 minutes. A coach link works only once: when one person has joined with it, it stops working. Anyone signed in who opens a link while it works can join the team that way, so share it only with the people it's for. If a coach leaves the team or is removed, their open invites and links stop working. We keep who invited whom and the answer, and each link with the coach who made it; a coach link is deleted as soon as someone joins with it, and any other link that has stopped working is deleted when the team's next link is made.
Who is in the team: each person's display name (your account name, or the part of your email before the @), and whether they are the coach or an athlete.
Messages: the text people write, reactions, and run cards. A coach can send a run card: the run's name, the athlete's name, the date, the run time and the gate-to-gate times. Never the video. The video stays on the phone.

Who sees what. Everyone in a team reads the team chat, including messages sent before they joined. A message between a coach and one athlete is seen only by those two. Messages are not scrambled so that only you can read them. They sit on our account server, so Noel Gedeon, who runs it, could technically read them. We don't, unless we need to fix a problem or the law says we must. A new message also passes through Apple to ring the other person's phone (see Notifications).

Leaving and deleting. You can delete a message you sent: its text or run card is erased, and the chat shows that a message was deleted. If you leave a team, you can no longer see it, but the messages you sent stay in it. If an athlete deletes their account, they are removed from the team and their messages stay, shown as from a deleted user. If a coach deletes their account, the team, its members and all its messages are deleted. Your username and your invites are deleted when you delete your account. Invites and links are also deleted with the team.

Where and how long. This is kept by Supabase, Inc., the same service that runs sign-in. We keep it until the team is deleted. There is no automatic deletion yet. You can also ask us to delete your messages. Why we're allowed to: it is needed to give you the team and chat you chose to use (GDPR Article 6(1)(b), contract).

Feedback and bug reports

If you send feedback from the iPhone app, we receive your message, up to 3 pictures you add, the app's version, the phone model and system version, and your account's name and email, so we can answer. If you report a bug from the computer app, we receive your text, the screen you were on, the app's version, your computer's system and, if you're signed in, your email.

Feedback is kept by Supabase and emailed to the Risegate team through Resend, Inc.; bug reports are emailed through Cloudflare, Inc. Both land in our mailbox, run by Google. The pictures are deleted from Supabase as soon as the feedback reaches us. Pictures that never reach us, because you closed the feedback without sending it or the email failed, are deleted within a day. We keep feedback and bug reports as long as we need them to deal with them, and delete them when you ask; deleting your account deletes the copy kept by Supabase. The copy kept by Supabase is deleted after 2 years at the latest. Why we're allowed to: you sent them to us to get help or to tell us something, and we have a legitimate interest in answering and fixing the app (GDPR Article 6(1)(f)).

Testing the iPhone app

While the iPhone app is in testing, it's installed through Apple's TestFlight. If we invited you by email, Apple shares your name and email with us. If you send feedback or a crash report through TestFlight, Apple passes it on to us, with your device model, system version and, if you add one, a screenshot. We use it only to fix the app. Apple's own privacy policy applies to TestFlight.

Paying

Paying isn't open yet: the iPhone app is a free beta, and the computer app's Subscribe button says it isn't open. When it opens, subscriptions will be sold by Lemon Squeezy (Lemon Squeezy, LLC, part of Stripe), which is the seller on your receipt and handles payment and tax. You give your name, email, billing address and card to them, not to us, and their own privacy policy applies: lemonsqueezy.com/privacy. They tell us what we need to run your subscription: your email, the plan, whether it's paid and until when, your customer number with them and your country for tax. We never see your card number. Lemon Squeezy keeps receipts and tax records as long as tax law requires.

The app's typefaces are built into it, so it doesn't fetch them from Google Fonts or anywhere else. Versions before v0.8.8 loaded them from Google Fonts when the app opened, which let Google see your computer's IP address; no video or other data went with it.

If you turn on "Send my videos to Risegate"

This is a switch in the computer app, off until you switch it on. While it's on, every video you add to the app is uploaded to us once. Videos you added before switching it on are not sent.

What we receive

The video file, exactly as it is on your computer. That includes the people in it, and whatever your phone saved in the file. That's usually when it was filmed and the phone model, and often where it was filmed.
The file's name, and the date we received it.
Your IP address. Every upload over the internet reveals it, and the upload service may keep it in its logs for a short time.

What we don't receive: your name, your email, your analyses and times, or anything else on your computer. Shared videos aren't linked to your account.

What we use it for: only to test and improve how well Risegate finds the skier and the gates, for example by checking the app's gates against the real ones on your run. We won't publish your videos or use them in marketing, and we won't use them for anything else without asking you first.

Why we're allowed to: because you agreed by turning the switch on (GDPR Article 6(1)(a), consent). You can withdraw that agreement at any time. It doesn't affect anything sent before.

Where shared videos are kept, and who sees them

Shared videos are stored with Cloudflare R2, a storage service run by Cloudflare, Inc. It holds them for us and may not use them for itself. They're kept in data centres in the European Union.

Only the Risegate team, Noel Gedeon, looks at them. We keep them for as long as they're useful for testing Risegate, and no longer than 2 years after we receive them. After that we delete them. We delete them sooner if you ask.

Children

Many racers are young. Someone under 16 may use a Risegate account, teams and chat only with a parent's or guardian's agreement. A coach can't give it for them. If you're a parent and think your child uses Risegate without your agreement, write to us and we'll delete the account.

So the app asks everyone for their birth month and year, once, and keeps it with the account. Nobody else sees it, not even a coach. If you're under 16, it asks for a parent's email and sends them one email with a link. Until they tap "I agree" there, the account is locked. If they say no, the account is deleted. We keep the parent's email and when they agreed, as proof, for as long as the account exists. All of it is deleted with the account.

Who handles your data

These companies work for us and may use your data only to do that work, under a data processing agreement:

Supabase, Inc.: accounts, sign-in, teams, messages, runs' times, notification addresses, feedback (EU, Ireland).
Cloudflare, Inc.: the website, the link from the iPhone app to our computer, shared videos, update downloads, bug-report emails.
PostHog, Inc.: usage and crash reports (EU, Frankfurt).
Resend, Inc.: sign-in and account emails, feedback emails, and the waitlist's welcome email (sent from the EU, Ireland).
Apple, Inc.: delivering notifications.
Google LLC: our email inbox, where feedback, bug reports and your emails to us arrive.

Apple and Google for signing in, Apple for TestFlight, Cal.com for booking a call and Lemon Squeezy for payments handle your data on their own terms, as described above.

Outside the EU. Several of these are US companies, so your data can be reached from, or sent to, the United States, even when it's stored in the EU. Each such transfer is covered by the EU-US Data Privacy Framework where the company is certified under it, and otherwise by the EU's Standard Contractual Clauses in our agreement with them (GDPR Articles 45 and 46). Write to us for a copy.

Your rights

You can ask us to:

tell you whether we hold data about you, and send you a copy
send you the data you gave us in a common, machine-readable format, or to another service
correct anything wrong
delete it, or your account (you can also delete your account yourself in the app)
limit what we do with it
stop using it where we rely on a legitimate interest, such as feedback and bug reports
withdraw an agreement you gave, at any time (for example by turning a switch off), without affecting what was done before

For your account, write from its email address. Shared videos aren't linked to your account, so for those tell us the file names (or roughly when you added them) so we can find them. We answer within a month. It's free.

You don't have to give us any data, but without an account you can't analyse or time your own runs. Notifications, usage reports, teams and chat are optional. Risegate makes no decisions about you by automated means that have legal or similarly significant effects.

If you think we've handled your data wrongly, you can complain to a data protection authority, for example the one where you live, or ours: the Office for Personal Data Protection of the Slovak Republic (dataprotection.gov.sk).

This website

Signing in on the website. The Sign in page uses the same account as the app, run by Supabase as described under Your account; the account service sees your IP address each time the page asks it something. To keep you signed in, your browser stores your sign-in in its own storage on your device. It's a full sign-in to your account, the same as in the app: the page only uses it to show your plan, but anyone who got it could use your account. Signing out removes it, so sign out on a computer you share. It's needed for the sign-in to work, so it isn't a tracking cookie and isn't used for anything else. The page also loads Google's sign-in button from Google, which sees your IP address; choosing Continue with Google works as described under Signing in with Google.

The waitlist. Joining the waitlist on the home page saves your email address, your browser's language setting and the time you joined, with Supabase as described under Your account. Joining sends you one welcome email to say you're on the list, and tells the Risegate team that you joined; both emails are sent through Resend, Inc. After that we use your address only to email you when Risegate is ready for you, and delete it on request or once you have an account. The legal basis is your consent (GDPR Article 6(1)(a)), which you can withdraw at any time by writing to [email protected].

Booking a call. Request a demo opens a booking page run by Cal.com, Inc., where you give your name and email to book a time. We use them only to hold the call and to follow up on it, and delete them on request. The legal basis is taking the steps you asked for (GDPR Article 6(1)(b)).

The site's typefaces are served by the site itself, not by Google Fonts. It’s hosted by Cloudflare (Cloudflare Pages), whose servers keep short-lived logs of visits (IP address, time, page). It has no ads, no analytics and no tracking cookies.

Changes

If we change what we do with your data, we update this page and the date at the top. A bigger change, such as using shared videos for something new, needs your agreement again before it applies to you.