Ridekin

Esta página está disponible actualmente solo en inglés. La versión en inglés es la que tiene validez jurídica.

Privacy policy

Fecha de entrada en vigor: 11 October 2026

This Privacy Policy explains how Dedik Serhii Vitaliiovych, an individual entrepreneur registered in Ukraine under registration number 21030000000108643, with contact email [email protected] ("Provider", "we", "us", "our"), collects, uses, shares, and protects personal data when you use the Ridekin mobile apps, the website at ridekin.app (including its forms), and related features (together, the "Service"). We are the data controller for the processing described here.

Location and safety - the short version

Important - location and safety features. Ridekin processes precise (GPS-level) location to record rides, guide you along a route, show your group where you are during a group ride, place signals on the map, and send an SOS. Many laws treat precise location as sensitive. We process it only after you grant the device permission, only for the feature you have turned on, and you can stop it or revoke the permission at any time. Other riders never see your exact position unless they are in your current group ride or receive your SOS; riders nearby see only an area of about one kilometre. The Service is free, shows no ads, and does not track you across apps. The Service is not an emergency service.

Who we are and how to contact us

Controller: Dedik Serhii Vitaliiovych, an individual entrepreneur (sole proprietor) registered in Ukraine under registration number 21030000000108643. Email: [email protected]. Website: https://ridekin.app.

We have not appointed a representative in the EU/EEA or the UK under Article 27 GDPR / UK GDPR, and we have not appointed a Data Protection Officer. For any privacy matter, contact us directly by email.

Scope

This Policy applies to personal data we process about users of the Ridekin apps, visitors to this website, people who use our website forms, and people who contact us - worldwide. Where mandatory data-protection laws of your country of residence (including the EU/EEA GDPR, the UK GDPR, the California CCPA/CPRA, and Ukraine's Law "On Protection of Personal Data") give you rights or protections beyond this Policy, those laws prevail.

Personal data we collect

Account: you sign in with Apple or Google. We receive the account identifier the provider issues for Ridekin and, only if the provider shares it, your email address (with Apple this can be a private relay address). We never receive your Apple or Google password. You choose a display name (up to 40 characters) and your units, and you can turn on "receive SOS from riders nearby". We also record which version of the Terms you accepted, when, and your confirmation that you are 18 or older.

Precise location (sensitive): GPS location while you record a ride, follow a route, take part in a group ride, send or update an SOS, place a host or tools signal, or are visible on the map. Ride recording, route guidance, an active group ride, and your visibility can continue while the screen is off or the app is in the background; your phone shows a location indicator or a notification while this happens, and it stops when you end the feature. When you are visible, the app sends your exact position to our server, which stores it exactly so that an SOS sent within about 25 km can reach you; other riders are shown only an area of about one kilometre, never your exact position. Your visibility ends on the schedule you pick (1 hour, 4 hours, or until you stop, at most 12 hours at a time) or when you choose hidden. If you turn on "receive SOS from riders nearby" while you are hidden, the app shares only an approximate area of about one kilometre with our server, so that an SOS sent within about 25 km can still reach you. That area is used only to match SOS alerts, is never shown to other riders, and is deleted when it expires or you turn the setting off.

Ride tracks and routes: the tracks you record (time, position, altitude, speed, and GPS accuracy for each point, and the ride statistics), the routes you import, draw, or copy, their names, and an optional share link. You can cut the start and end of a track (trim); the removed part is deleted permanently and cannot be restored.

Signals: when you send an SOS or place a host or tools signal, we process its type, position, optional note (up to 280 characters), duration, and the responses to it. For an SOS we also determine and store its recipients: the members of your current group ride and the riders who turned on "receive SOS from riders nearby" and are within about 25 km. An SOS stays active until you end it and ends automatically after 3 hours.

Group rides: the group name, the leader, an optional route the leader shares with the group, the members, and each member's position, speed, and heading while the group ride is active.

Reports and blocks: when you report a rider or content, we store the reason you choose, your optional note, a snapshot of the reported content as it was when you reported it (without location coordinates), and a link to your account as the reporter. The report is emailed to [email protected] for moderation, and we act on it within 24 hours; a rider who breaks the Terms can be suspended. When you block a rider, we store that block.

Website forms and contact: if you use a form on this website (for example the contact form, an account-deletion request, or a waitlist while one is open), we process the email address and the message or request you send, and the form's category or signup source.

Device and technical data: device platform (iOS or Android), app version, language, push-notification token (where you allow notifications), and your IP address, which we use transiently for security, rate limiting, and abuse prevention.

Product analytics in the app: small usage events (for example "ride saved" with distance and duration in broad ranges, "group joined", "signal sent"), together with app version, platform, and device language and region setting, linked to a random account id. Events are pseudonymous (tied to your account id), never contain coordinates, names, email addresses, or notes, and the IP address is discarded. Analytics is off until you allow it: the app asks you once, and you can change your choice at any time in Settings.

Crash reports: when the app or website hits an error, a technical report (device and app details, the error and its context) is sent to our error-monitoring provider in the EU, with personal-data collection disabled, no account id attached, and coordinates removed.

Beyond precise location, we do not intentionally collect special-category (sensitive) data. Please do not put sensitive information, or other people's personal data, in signal notes, names, or other free-text fields.

How we use personal data, and our legal bases

To provide the Service - your account, ride recording and history, routes, share links, signals, group rides, and notifications: performance of a contract (GDPR Art. 6(1)(b)).

Precise location for recording, route guidance, group rides, signals, and visibility: your consent (Art. 6(1)(a)), given through the device permission and by turning the feature on, together with contract for the feature you request. You can withdraw consent at any time in the app or in your device settings.

SOS alerts you send, and receiving SOS alerts from riders nearby: consent and contract, and vital interests or our legitimate interests where relevant (Art. 6(1)(d)/(f)).

Product analytics in the app: your consent (Art. 6(1)(a)), which you give or decline when the app asks, and can withdraw at any time in Settings. Aggregate website analytics: our legitimate interests in understanding how the site is used so we can improve it (Art. 6(1)(f)).

Crash reports, security, and abuse prevention - including enforcing our Terms and removing unlawful signals or names: legitimate interests (Art. 6(1)(f)); legal obligation where applicable.

Reports and blocks - keeping riders safe and enforcing our Terms, including suspending a rider who breaks them: legitimate interests (Art. 6(1)(f)).

Recording your acceptance of the Terms and your age confirmation: legal obligation and legitimate interests (Art. 6(1)(c)/(f)).

Website forms: to answer your message or handle your request (Art. 6(1)(b)/(f)); waitlist and product-news emails only after you confirm your signup: consent (Art. 6(1)(a)), withdraw any time via the unsubscribe link.

To comply with legal obligations and respond to lawful requests: legal obligation (Art. 6(1)(c)).

Where we rely on consent, withdrawing it does not affect processing carried out before withdrawal.

What others can see

Riders nearby: if you choose "group and riders nearby", other riders see a marker for an area of about one kilometre around you - never your exact position, your name, or your account. If you choose "my group" or hidden, riders nearby see nothing.

Your group ride: members of your current group ride see your display name and your exact position, speed, and heading while the group ride is active, and the route the leader shares. They stop seeing it when you leave or the ride ends.

SOS: the recipients of your SOS see your exact position while it is active, your note, and whether other recipients are on their way, and your display name may be shown to them. When you respond to someone else's SOS, the sender sees your response.

Host and tools signals: other riders see the type, your note, when it expires, and an area of about one kilometre - never the exact spot. Anything you write in a note is visible to every rider who views that area, so share contact details there only if you are comfortable doing so.

Share links: a ride or route you share by link shows its name, date, statistics, and a preview of the line with the first and last 300 metres removed - no raw GPS points, no name, and no account. Anyone with the link can open it until you revoke the link or delete the track.

Recipients may keep or misuse what you show them, which is outside our control; choose your visibility and your groups carefully.

Maps and navigation

Map tiles are served from our own infrastructure, and route guidance is computed on your device from the stored route. Your location and routes are never sent to a third-party map or routing provider. GPX import and export happen on your device.

Notifications

Push notifications (for example an SOS near you, a response to your SOS, or a regroup call) are sent through Google Firebase Cloud Messaging and, on iPhone, delivered via the Apple Push Notification service. To deliver them we store a push token for your device. Notifications never contain coordinates. You can manage or disable notifications in the app and in your device settings at any time.

Waitlist emails

Joining the waitlist is double opt-in: we first send a confirmation email, and we send no marketing until you confirm. Confirmation links expire and are built so that automated email scanners cannot trigger them.

Once you are confirmed, the emails we send about the launch may include standard delivery measurement: a tiny open-tracking image and wrapped links that record when an email is opened and which links are clicked, together with the IP address and browser type of the click. Click IP addresses and browser data are deleted within 12 months. Every email contains a one-click unsubscribe link (RFC 8058); unsubscribing stops all marketing immediately.

Waitlist and contact data is processed in our own feedback service running on our own infrastructure - it is not handed to a third-party marketing platform.

Cookies, analytics, and error monitoring

Strictly necessary storage: your theme choice (light/dark) is kept in your browser's local storage and never leaves your device. The Cloudflare Turnstile bot check used on our forms may set its own strictly necessary cookie; it loads only where a form needs protecting.

Privacy-preserving website analytics: we use PostHog (EU Cloud, hosted in the European Union) in a cookieless configuration - no cookies, no persistent identifier, no cross-site tracking - and it is disabled entirely when your browser sends the Do Not Track signal.

Google Analytics: this website also uses Google Analytics 4 (Google Ireland Ltd / Google LLC), running under Google's Consent Mode with analytics storage denied by default and never granted, so it sets no cookie and no persistent identifier on this site - only aggregate, cookieless measurement pings reach Google's servers, including in the United States. Google Signals and ads personalization stay disabled, and we use it only to measure aggregate site usage. You can opt out with Google's browser add-on at https://tools.google.com/dlpage/gaoptout or by blocking the googletagmanager.com domain.

In the app: the apps contain no advertising SDK, do not use your device's advertising identifier, and do not track you across apps or websites. Product analytics (PostHog, EU Cloud) are explicit events only - no automatic screen or tap capture and no session recording - linked to a random account id and never to your name or email; the IP address is discarded and IP-based location lookup is disabled. Analytics is off until you allow it: the app asks you once, and you can change your choice at any time in Settings.

Error monitoring: the website and the apps send crash and error reports to Sentry (EU region), with personal-data collection disabled, no account id attached, and coordinates removed.

Who else sees this data (processors and recipients)

We do not sell personal data. We share it only with the people you choose to show it to (see What others can see), with service providers acting on our documented instructions under Article 28 GDPR data-processing terms, and in the limited cases below.

Our processors: Hetzner Online GmbH (cloud hosting of the app backend, database, and website - Germany, EU); Cloudflare (DNS, CDN, DDoS and bot protection, Turnstile on website forms, and R2 object storage for encrypted database backups); Sentry (crash and error reports, EU region); PostHog (EU Cloud - product analytics in the app and website analytics); Forward Email (email delivery for website forms and support replies); Google (Sign in with Google, Firebase Cloud Messaging push delivery, Google Play, and Google Analytics on the website); Apple (Sign in with Apple, the App Store, and the Apple Push Notification service). A current list of sub-processors is available on request at [email protected].

Legal and safety: we may disclose data to comply with law, legal process, or enforceable governmental requests; to enforce our Terms; to address fraud, security, or technical issues; or to protect the rights, safety, and property of any person.

Business transfer: in connection with a merger, acquisition, reorganization, or sale of assets, subject to this Policy.

We do not disclose personal data to third parties for their own independent marketing, and we do not "sell" or "share" personal information for cross-context behavioural advertising as those terms are defined under California law.

International data transfers

The Service runs on servers in Germany (EU). The Provider operates from Ukraine, and some of our processors (for example Google, Apple, Cloudflare, Sentry, and PostHog, which are or belong to companies based in the United States) may access or process data outside the EU/EEA. When personal data of EU/EEA or UK users is transferred to a country without an adequacy decision, we rely on appropriate safeguards - principally the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum for UK data), or the EU-U.S. Data Privacy Framework where the recipient is certified - with supplementary measures where needed. You may request details of these safeguards at [email protected].

Retention

We keep personal data only as long as needed for the purposes above, then delete or anonymise it. In particular: your visibility position - until the visibility period you chose ends (at most 12 hours at a time) or you go hidden, then deleted within about an hour; SOS, host, and tools signals with their recipients and responses - while active (an SOS until you end it, at most 3 hours; host and tools for 24 hours, 7 days, or until you remove them), then deleted within about an hour; group rides - a group ride ends after 24 hours without activity, and an ended group ride, including its members' positions, is deleted 7 days after it ends; ride tracks, routes, and share links - until you delete them or your account; reports - 12 months from creation, then deleted automatically by a daily job, whether the report is open or handled; blocks - until you unblock or until either account is deleted; account data and consent records - for the life of your account; sign-in sessions - up to 60 days of inactivity; push tokens - until you sign out, delete your account, or the token stops working; product-analytics events - up to 12 months, without IP addresses; crash reports - up to 90 days; server logs - up to 12 months; support and feedback message content - removed from the product database within days of being relayed to our support tooling, with any residual copy deleted within 18 months; waitlist emails - until you unsubscribe or ask us to delete them; email open/click records - IP and browser data removed within 12 months; encrypted database backups - overwritten within 30 days.

De-identified or aggregated data that can no longer reasonably identify you may be retained.

Deleting your account, and data export

You can delete your account at any time in the app (Settings -> Delete account). Deletion is immediate and permanent: your account, sign-in links, display name, settings, consent records, rides, routes, share links, signals, visibility, group rides you lead, group memberships, and push tokens are erased from our database at once, with no anonymised copy kept. The only remaining copies are in encrypted database backups, which are overwritten within 30 days. Product-analytics events stay linked only to the random account id, which no longer points to anyone once your account is gone, and are removed on their normal schedule; crash reports never carry your account id. Blocks by and of you are deleted immediately. Reports are the exception to "at once": if you filed a report, your link to it is removed, and if you were reported, the link to you is removed, but the report itself stays until it is deleted automatically 12 months after it was created.

If you cannot sign in, you can request deletion through the web form at https://ridekin.app/delete-account or by emailing [email protected]. We confirm the request with you before we delete anything, and complete it within 30 days.

You can export each ride or route as a GPX file in the app. A full copy of your account data is available on request at [email protected] and will be provided within the time the law requires (generally one month).

Sign in with Apple: when you delete your account, the app asks Apple to revoke its access token. You can also revoke Sign in with Apple or Google access for Ridekin in your Apple or Google account settings at any time.

Security

We use technical and organisational measures appropriate to the risk: encryption in transit, sign-in through Apple or Google so we hold no passwords, sign-in tokens stored only in hashed form, server-side rules that reduce what other riders can see about your position, access controls, least-privilege practices, and encrypted off-site backups. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. Keep your device and your Apple or Google account secure, and choose your visibility and groups carefully. We will notify you and/or the relevant authority of a personal-data breach where the law requires it.

Your rights

EU/EEA and UK: if you are in the EU/EEA or the UK, you have the right to access your personal data, rectify inaccurate data, obtain erasure ("right to be forgotten"), restrict processing, receive your data in a portable format, object to processing based on legitimate interests (including product analytics) and to direct marketing, and withdraw consent at any time - including consent to precise location. We do not carry out solely automated decision-making that produces legal or similarly significant effects. To exercise any right, email [email protected]; we respond within the statutory time (generally one month). You may also complain to your local Data Protection Authority or, in the UK, the Information Commissioner's Office (ICO).

California (CCPA/CPRA): we are likely not a "business" as defined by the CCPA/CPRA because we do not meet its thresholds. As a courtesy, we extend to California residents the rights to know and access, correct, and delete personal information, exercisable directly or through an authorised agent. Precise geolocation is "sensitive personal information" under California law; we use it only to provide the Service you request and for permitted purposes, and we do not use it to infer characteristics. We do not sell or share personal information as those terms are defined by the CCPA/CPRA.

Ukraine: if Ukrainian data-protection law applies, you have the rights set out in the Law of Ukraine "On Protection of Personal Data", including to know about the processing of your data, access it, demand rectification or deletion of unlawfully processed or inaccurate data, withdraw consent, object, and complain to the Ukrainian Parliament Commissioner for Human Rights (Ombudsperson) or the courts.

We will never discriminate against you for exercising your rights.

Children

The Service is intended for adults (18+) and is not directed to children. We ask every user to confirm they are 18 or older, and we do not knowingly collect personal data from anyone under 18. If you believe a child has provided us personal data, contact [email protected] and we will delete it.

Changes to this Policy

We may update this Policy from time to time. We will update the effective date above and, for material changes, give reasonable notice (for example in-app, by email, or on this page). Your continued use after changes take effect constitutes acceptance, except where the law requires fresh consent (for example, for new processing of precise location).

Contact

Privacy questions and requests: Dedik Serhii Vitaliiovych, [email protected]. You may also complain to your supervisory authority (see Your rights).