Privacy Policy for the App "RUDX"
Translation for convenience. In case of differences, the German version prevails.
Last updated: 3 November 2026
We take the protection of your data seriously. RUDX connects drivers on shared tours – for this we need certain data, in particular your location during a tour. Here we explain in plain language which data we process, when, for what purpose and for how long, and what rights you have.
This policy applies to the RUDX app (iOS) and the associated services. It is based on the Swiss Federal Act on Data Protection (FADP/DSG) and – where applicable – the EU General Data Protection Regulation (GDPR/DSGVO), the UK GDPR, Canadian law (PIPEDA, in Québec Law 25 (Loi 25), in Alberta and British Columbia PIPA) and the data protection laws of the US states (including California: CalOPPA, CCPA/CPRA).
1. Who is responsible?
Brevity GmbH
Seestrasse 15
6052 Hergiswil NW
Switzerland
UID: CHE-152.350.548
Email for data protection matters: datenschutz@rudx.ch
Person in charge of data protection (also under Québec Loi 25): David Arturo Imminger-Perez, Chairman of the Management, reachable at the address above.
Representative in the EU (Art. 27 GDPR/DSGVO): will be appointed before the official launch in the EU and named here
Representative in the United Kingdom (Art. 27 UK GDPR): will be appointed before the official launch in the United Kingdom and named here
2. Key points at a glance
- Location only during the ride: Your position is shared with the other participants for the whole ride you take part in, from the start until you end it. In a free ride we share it with your group as long as you are visible. We do not store live positions permanently.
- You decide what others see: You individually release your profile, garage, tours, photos and performance data. Emergency contact and health information are never public.
- No selling, no advertising, no tracking: We do not sell data, do not show personalised advertising and do not use any tracking or advertising SDKs.
- Mesh without servers: In mesh mode (without mobile network), data travels encrypted directly between the phones of the group, not via our servers.
- Delete at any time: You can delete your account and your data in the app. Deletion is final.
3. What data we process, for what purpose and on what legal basis
Legal bases under the GDPR/UK GDPR (under Swiss law, a legal basis is generally not required; where the DSG requires consent, we obtain it):
Contract = Art. 6(1)(b) (provision of the app) · Consent = Art. 6(1)(a) or Art. 9(2)(a) · Legitimate interest = Art. 6(1)(f) · Legal obligation = Art. 6(1)(c) · Vital interests = Art. 6(1)(d) / Art. 9(2)(c).
3.1 Account and profile
- Data: name or display name, email (with "Sign in with Apple", possibly an anonymous relay address from Apple), profile picture, place of residence (optional), short bio, language, confirmation of minimum age, time of acceptance of the Terms of Use.
- Purpose: maintaining your account, making you recognisable in groups, sign-in.
- Basis: contract.
3.2 Vehicles (garage)
- Data: make, model, colour, power, top speed, off-road values (tilt limits, ground clearance, etc.), your own photos of your car. Cutting out the car from the photo is done on your device.
- Purpose: display in the convoy, limit warnings, speedometer scale, garage.
- Basis: contract. Note: when uploading, make sure that no licence plates or persons are recognisable if you do not want this.
3.3 Location during tours
- Data: GPS position, accuracy, speed, heading, altitude; in the background with the screen locked, as long as the tour is running (iOS then shows a blue indicator at the top).
- Purpose: convoy map, distances, turn instructions, notices at specific locations, calls for help with position, accident/rollover alarm with position.
- Who sees it: the participants of the ongoing ride; in a free ride the members of your group as long as you are visible. A call for help with position also reaches the members of your group.
- Retention period: live positions are not stored permanently; they are deleted no later than 24 hours after the end of the tour. Only what you deliberately record is stored permanently (3.6). Your last place also stays on your iPhone, rounded to about one kilometre, so that RUDX knows the right emergency number after a restart without reception; it is not sent to us for this.
- Basis: contract and your consent via the iOS location permission, which you can revoke at any time in the iOS settings.
3.4 Sensor data and safety features
- Data: acceleration (g-forces), tilt and lean angle from your iPhone's motion sensors; if you allow “Motion & Fitness”, also the type of movement recognised by iOS (on foot, in a vehicle) – only so that a phone in a pocket does not raise an accident alarm.
- Purpose: inclinometer (off-road), accident and rollover detection, performance data.
- Processing: continuously on your device. Only a triggered alarm (type of event, measured value, position, time) is transmitted to the group, and only if you do not cancel it within 20 seconds.
- Basis: contract; in the case of an alarm, additionally vital interests.
3.5 Radio, voice notes and chat
- Data: voice recordings when pressing the push-to-talk button, voice notes, text messages, photos in the chat, time, sender.
- Purpose: communication within the group.
- Retention period: radio messages in the history according to your setting (10–120 minutes, default 30), then deleted; group chat until the message is deleted, the account is deleted or the group is dissolved.
- Basis: contract.
- Note: All participants of the tour hear radio messages. Do not say anything that not everyone should hear.
3.6 Recorded routes, recaps, performance data (optional)
- Data: recorded track, altitudes, speed, inclines, notices, analysis generated from them; tour recap (distance, driving time, your top speed); performance data (0–100, 0–200, 0–300 km/h, braking distance 100–0) and whether they were obtained in measurement mode on a closed circuit.
- Who sees it: top speed and performance data only you, unless you share them yourself or release them in your public profile. If you publish a route, the RUDX team reviews it before approval. After that, all signed-in users see your profile name, title and text, the line and the key figures in "Discover". If you have set a private zone, the part of the line inside it and a margin of about 500 m around it are removed on your device. Without a private zone the line is published in full; you see it before sending. Timestamps and per-point speed are not transmitted.
- Retention period: until you withdraw or delete them or delete your account.
- Basis: contract; publication only with your consent.
3.7 Emergency contact and health information (optional, sensitive personal data)
- Data: name, relationship and phone number of your emergency contacts; optionally blood type, allergies, medication.
- Purpose: in an emergency, you can show this information yourself to the rescue services or to people helping you.
- Visibility: The information stays on your iPhone. RUDX transmits it neither to the group nor to the server. Nobody else can access it through RUDX.
- Basis: health information only with your explicit consent (DSG Art. 6 para. 7; GDPR/DSGVO Art. 9(2)(a)), which you can revoke at any time by deleting the information; in an acute emergency, additionally vital interests (GDPR/DSGVO Art. 9(2)(c)).
- Third-party data: Your emergency contacts are not users themselves. Please inform them that you are storing their number. Their data stays on your iPhone.
3.7a Heart rate during the ride (optional, sensitive personal data)
- Data: heart rate during a ride – from the Health app (e.g. Apple Watch) or from your Bluetooth heart-rate strap – and from it the average per section and the heart rate in curves.
- Apple Watch: With the RUDX app on the Apple Watch, the ride is saved as a workout ("Other") together with your heart rate in your Health app. You manage and delete it there yourself; we do not receive this data.
- Purpose: only your own recap. Not a medical device, no health statements.
- Where and who sees it: only on your iPhone, only you. Nothing goes to our server unless you tap "Share heart rate with the group" in the recap – then exactly the text shown (average, peak, sections) goes to the group chat. No advertising, no sale, no disclosure to third parties.
- Retention period: the detailed values for 30 days, after that only the summary in the recap; can be deleted with the ride or your account. Saved rides with heart rate are excluded from iCloud backup.
- Legal basis: your explicit consent (switching it on under Settings → Heart rate; FADP Art. 6(7); GDPR Art. 9(2)(a)), revocable at any time by switching it off.
3.8 Groups, feed, comments, photos
- Data: memberships, roles (admin, organiser), join requests, invitation codes, posts (photos, text, associated tour), likes, comments, reports, blocks.
- Purpose: community features, moderation, protection against abuse.
- Who sees it: posts are visible to the members of the group; on your public profile only if you have released "Photos".
- Retention period: until deleted by you; reports and moderation decisions up to 12 months for traceability and abuse prevention.
- Basis: contract; moderation additionally legitimate interest and legal obligations (including the EU DSA).
3.8a Group history and official clubs
- Data: the time of joining, leaving, admission, removal and ban in a group; for a request "Official club" or a report "Fake club", the name of the club, the website or e-mail address given and your explanation.
- Purpose: administration of the group by its admins; checking whether a group belongs to the club it names; protection against deception.
- Who sees it: the history is visible to the admins and co-admins of the group; requests and reports only to the RUDX team. To verify, we may contact the club at the address given.
- Retention period: history 12 months; requests and reports for as long as the group exists.
- Basis: contract; legitimate interest in protection against abuse.
3.9 Public profile
- Data: what you release: garage, statistics (tours, kilometres on RUDX tours, elevation gain, trophies), tours driven, photos, performance data. Selectable audience: all RUDX users, only your groups, or no one.
- Basis: consent (through your release), changeable at any time.
3.10 Mesh connection without mobile network
- Data: position, hazards, calls for help, short voice messages, device name in the group.
- Processing: directly between the group's devices via Bluetooth/Wi-Fi (Apple Multipeer Connectivity), encrypted with a group key, relayed via other cars in the group. No server, no storage on our side. Messages are only cached briefly on the devices and passed on to cars joining later: alarms (help call, accident, all-clear) for up to 15 minutes, other messages for up to 10 minutes.
- Basis: contract.
3.11 Premium and purchases
- Data: subscription status, purchase date, term. Payment is processed by Apple; we do not receive any payment data.
- Basis: contract; retention of business records in accordance with legal obligations (in Switzerland 10 years).
3.11a Paid events (Stripe)
- Data: name, email, event and date, number of people/cars, amount, currency, payment status, payment reference; you enter card, Apple Pay or TWINT details directly with Stripe – we do not receive them.
- Purpose: payment and refund of events that a group sells in the app.
- Recipients: Stripe (Stripe Payments Europe Ltd., Ireland, and Stripe, Inc., USA) processes the payment. The seller is the organiser or the group (own Stripe account); the organiser sees your payment details (name, email, amount, payment method) in their Stripe account and is responsible for their own processing. Brevity receives a fee and the details needed for the booking.
- Basis: contract; retention in accordance with legal obligations.
3.12 Technical data, security and support
- Data: device type, iOS and app version, language, time zone, IP address when establishing a connection, push token, crash reports (if you share them via Apple), support requests.
- Purpose: operation, security, troubleshooting, support, notifications.
- Push notifications: are delivered via the Apple Push Notification service (APNs). For this, Apple receives your device's push token and the content of the notification, including a short preview (e.g. sender, group and the beginning of a chat message). You choose in the app which notifications you receive; you can hide previews in the iOS settings.
- Retention period: server logs for a maximum of 30 days.
- Basis: contract and legitimate interest (secure operation).
3.13 Weather, maps and routes
For weather, elevation profiles and maps, the app calls third-party services (section 5). In doing so, the coordinates of the requested location and, for technical reasons, your IP address are transmitted, but no account data.
3.14 What we do not do
No personalised advertising, no selling or "sharing" of data within the meaning of the CCPA/CPRA, no tracking SDKs, no recording of your screen usage, no automated decisions with legal effect. For this reason, Apple's App Tracking Transparency prompt does not appear.
4. Who receives data
- Other users: only as described in section 3 and released by you.
- Service providers (processors) who process data only on our instructions and are contractually obliged to protect it (list in section 5).
- Authorities: only if we are legally obliged to do so or if it is necessary to protect life and limb.
- Buyers/successors: in the event of a sale or merger of the company, subject to this policy.
5. Service providers and disclosure of data abroad
| Service | Purpose | Location / safeguards |
|---|---|---|
| Apple (App Store, Sign in with Apple, push notifications via APNs incl. a short message preview, Apple Maps) | Distribution, sign-in, notifications, maps and routes (road) | USA/worldwide; EU-US or Swiss-US Data Privacy Framework / standard contractual clauses |
| Stripe Payments Europe Ltd., Ireland / Stripe, Inc., USA | Payment for paid events (seller: the organiser with their own Stripe account) | EU/USA; EU-US or Swiss-US Data Privacy Framework / standard contractual clauses |
| Infomaniak Network SA, Geneva (own server, operated by Brevity) | Account, groups, rides, chat, feed, files, routing, offline maps, calendar | Switzerland |
| Infomaniak Network SA, Geneva (own server) | Radio over the internet (encrypted with the group key) | Switzerland |
| Infomaniak Network SA, Geneva | Email (support, data protection requests) | Switzerland |
| Open-Meteo | Weather, elevation profiles (coordinates + IP only) | Switzerland/EU |
| Own map and routing server (OpenStreetMap data, Protomaps) at Infomaniak | Offline maps, routes incl. tracks | Switzerland |
If data is transferred to a country without an adequate level of data protection (pursuant to Annex 1 of the Swiss Data Protection Ordinance or the EU adequacy decisions), we rely on certified frameworks (Data Privacy Framework) or the standard contractual clauses of the European Commission including Swiss adaptations. You can obtain a copy on request.
6. How long we store data
| Data | Duration |
|---|---|
| Live positions | during the tour, deleted no later than 24 h after the end of the tour |
| Radio history | 10–120 minutes (your setting) |
| Mesh cache on devices | alarms up to 15 minutes, other messages up to 10 minutes |
| Account, garage, recordings, posts, chat | until you delete them or your account |
| After account deletion | immediately from the active system; backups are overwritten no later than after 30 days |
| Requests via the form on rudx.ch | 12 months after being dealt with, no later than 24 months after receipt |
| Reports and moderation decisions | up to 12 months |
| Server logs | up to 30 days |
| Purchase/accounting records | in accordance with legal obligations (CH: 10 years) |
Deleting your account is final. A deleted account cannot be restored – not even from backups. If you signed in with Apple, we also revoke the Sign in with Apple authorisation with Apple when you delete your account. Backups are only used to restore the whole system after a failure or data loss, never to bring back individual accounts; they are overwritten no later than after 30 days. We only keep what the law requires (e.g. accounting records).
7. Data security
Encrypted transmission (TLS), encrypted mesh with group key, encrypted storage at the server provider, access rights based on the principle of least privilege, regular updates. In the event of a data security breach with a high risk, we inform the competent authorities (in Switzerland the FDPIC (EDÖB), in the EU the supervisory authority, in Canada the Privacy Commissioner or, in Québec, the Commission d'accès à l'information) and the data subjects in accordance with the legal requirements.
Support access. If there is a problem or reported content, an employee of Brevity GmbH may join a group to help. They then appear to all members as “RUDX Support” in the member list; every such access is logged. Without this visible join, Brevity does not see a group’s feed, chat or radio content.
Cookies and storage on rudx.ch. On your first visit the website asks what it may store. Only your choice itself is technically necessary; it stays in your browser. If you agree, a cookie with your language (one year), an entry for the one-time intro and the statistics described below are added. You can change your choice at any time through the link in the footer.
Statistics of the website rudx.ch. Only if you agree do we count page views without cookies and without IP addresses: the page, the referring domain (e.g. google.com), language, device type and a random ID per browser tab that expires when it is closed. No person can be identified from this. The data is stored on our server in Switzerland and deleted after 400 days. If “Do Not Track” or “Global Privacy Control” is on in your browser, we count nothing.
Request form on rudx.ch ("Request access"). We store what you enter: name, e-mail, whether you are a driver, an organiser or club, or a business, optionally your crew or club, number of cars, road/off-road and your message, plus the language of the page and your consent. Purpose: to contact you, answer your request and make you an offer (e.g. access or founding crew). The data is stored on our server in Switzerland; the RUDX team also receives it by e-mail. We do not pass it on. We delete it 12 months after your request has been dealt with, no later than 24 months after receipt. Basis: your consent (tick box in the form), which you can withdraw at any time via datenschutz@rudx.ch.
8. Your rights
You can at any time – free of charge, to the extent provided by law:
- request access to your data,
- receive a copy of your data in a common format (data disclosure/data portability),
- rectify incorrect data,
- have data erased or delete your account in the app,
- restrict the processing or object to it (in particular in the case of legitimate interest),
- withdraw consents (with effect for the future),
- in California and other US states: know what data we collect, request deletion, request correction, opt out of sale/sharing (we do not sell/share) – without discrimination; requests may also be made through an authorised agent,
- in Canada/Québec: access, rectification, withdrawal of consent, information about automated decisions (RUDX does not make any).
Requests to datenschutz@rudx.ch. We respond within 30 days (in exceptional cases with an extension as permitted by law) and may need to verify your identity.
Complaint to a supervisory authority: Switzerland: Federal Data Protection and Information Commissioner (FDPIC/EDÖB), www.edoeb.admin.ch · EU: the authority of your country of residence · UK: Information Commissioner's Office (ICO) · Canada: Office of the Privacy Commissioner of Canada, in Québec Commission d'accès à l'information, in Alberta/BC the respective Information and Privacy Commissioner · California: California Privacy Protection Agency.
9. Minimum age
RUDX is intended for persons aged 18 and over and is not directed at children. We do not knowingly collect data from children under 13 (USA, COPPA) or under 16 (EU). If we become aware of this, we delete the account.
10. Permissions on your iPhone
The app only asks when needed and explains each request: Location (convoy, also in the background during the tour), Microphone (radio, voice notes), Photos (saving images such as your stats card; you pick car and tour photos yourself in the iOS photo picker), Camera (only to scan the QR code of an invitation; no images are stored), Motion (tilt, accident detection), Bluetooth and local network (mesh). You can change each permission in the iOS settings; individual features will then not be available. Health (reading heart rate, only if you switch it on; with the Apple Watch also saving the ride as a workout with heart rate), Bluetooth also for a heart-rate strap.
11. "Do Not Track" and Global Privacy Control
Since we do not track across apps or websites, there is nothing to switch off. We respect signals such as "Do Not Track" or "Global Privacy Control" as an objection to sale/sharing – which we do not engage in anyway.
12. Changes
We will amend this policy if the app or the law changes. We will announce material changes in the app; where necessary, we will obtain your consent again. The current version can always be found in the app under Settings → Legal.
Language versions: In case of differences, the German version prevails, unless the applicable law provides otherwise (in Québec, the French version is authoritative).