Skip to content
RideWeave
How it worksCompatibilityRWCP v2 ↗IT

RIDEWEAVE / LEGAL

Privacy Policy

Effective: 2026-10-24

Who we are and what this coversThe short versionAudio and other ridersPermissionsBluetooth LE discoveryWhat stays on the phoneDiagnostics, retention, and deletionSharing you initiateWebsite and supportPurposes, legal bases, and recipientsRetention and international processingYour rightsChanges

01. Who we are and what this covers

Syscake S.r.l., Via Quinto Novio 44, 00175 Rome (RM), Italy · VAT / P. IVA 16207441003. Syscake is the controller of personal data it receives for the RideWeave website and support. Contact rideweave-support@syscake.it. This policy covers the RideWeave app for Android, iPhone and iPad, this website, and related support.

02. The short version

RideWeave has no user account or developer-operated cloud relay. Conversation is exchanged directly between participating phones, over Wi-Fi Aware or Bluetooth LE. The app does not send your microphone audio or ride history to Syscake automatically. Technical diagnostics are stored on your phone. You decide whether to share them.

03. Audio and other riders

Microphone audio is processed locally and transmitted to participants in the ride through the local peer network, including relay phones. Where a Bluetooth LE link joins two parts of the group, the phone at each end combines the voices it sends across that link into one stream; this happens on the phone, and nothing is recorded. With “Transmit only while talking” (on by default) audio is sent only while speech is detected, including about 100 ms before it; you can turn this off in Settings. RideWeave does not intentionally save conversation recordings. Participants receive audio and may be able to record it independently; the app cannot prevent that. Rider names, public identities, membership, and connection information are exchanged as needed to establish and maintain the ride. Only share invitations with people you intend to invite; the organizer still approves admission. Encryption protects transport and media within the implemented protocol boundaries, but does not make participants anonymous or protect against every malicious admitted participant.

04. Permissions

Microphone access enables speaking and headset checks. Nearby-device, local-network and Bluetooth access let phones find each other and link over Wi-Fi Aware or Bluetooth LE; Bluetooth also connects helmet audio. Camera access is used to scan invitations, with paste available as an alternative. Notifications, and on Android foreground-service permissions, support an ongoing session. On Android, call-management access lets the ride appear to Android as a call of the app itself, so helmet audio routing and call controls behave as in a phone call; it does not place, read or manage your other calls. On Android 13 and later, and on iPhone and iPad, RideWeave does not request location access, and on Android it declares nearby Wi-Fi and Bluetooth scanning as not used to derive location. On Android 10, 11 and 12 the system ties Bluetooth scanning and Wi-Fi Aware to the location permission and to Location being switched on, so RideWeave asks for it there and explains why first. On every release RideWeave never reads, stores or shares your location; it only checks whether Location is switched on so it can tell you. Permission labels differ by operating system and version. You can change permissions in your phone’s settings; some functions will then be unavailable.

05. Bluetooth LE discovery

While you are in a ride, from joining until you leave, a phone that can accept Bluetooth LE links advertises over Bluetooth LE so that nearby riders’ phones can find it; it stops when it holds as many links as it can. The advertisement contains a ride identifier that is new for every ride, and RideWeave adds no rider name or device name to it. The details needed to connect, such as the phone’s identity in the ride and its route information, are encrypted so that only phones holding the invitation can read them. Someone nearby with a Bluetooth scanner can tell that a phone is taking part in a RideWeave ride and recognize the same identifier for the rest of that ride, but the advertisement does not reveal who you are. Bluetooth LE links use no Bluetooth pairing; RideWeave encrypts and authenticates them as it does Wi-Fi Aware links.

06. What stays on the phone

The app retains a device identity protected by the platform (the Android Keystore, or the iPhone and iPad Keychain for this device only), rider preferences (including audio settings), and local diagnostic history. On iPhone and iPad it also remembers which Wi-Fi Aware-paired device belongs to which rider, so pairings carry over to later rides with the same riders; iOS itself manages the pairings. Local diagnostic records may include ride labels, dates, device and app information, phone state (battery, temperature, charging, screen on or off, power-saving and idle mode, thermal state), processor and memory use by app component, connection events, Wi-Fi Aware and Bluetooth LE link details such as the radio channel and link counters, voice-mixing counters, audio route and processing settings, and audio-level and voice-activity statistics. They do not store speech, recordings, packet contents or Bluetooth device identifiers. Android app backup is disabled. On iPhone and iPad, diagnostic history is excluded from device backups; preferences and remembered pairings can be included in a device backup you make. Ride credentials are used for the session and are not included in the website or ordinary diagnostic exports.

07. Diagnostics, retention, and deletion

Detailed telemetry is bounded to approximately 16 MB per session and 100 MB overall, with small temporary overages possible during queued writes. Older details are removed as needed, while summaries remain until you delete them. You can delete completed records individually, in selected groups, or together in Ride history; active sessions are protected. Clearing app data or uninstalling removes local history and settings; on iPhone and iPad, iOS can keep the device identity in the Keychain after the app is removed. Export cache is limited to 20 MB; files older than 24 hours are cleaned on the next export. Deleting a record removes its cached exports, but cannot delete copies already shared with another app or person.

08. Sharing you initiate

Invitation copy/share actions put the invitation in the clipboard or the system share sheet. Diagnostic sharing creates a report and opens your chosen destination. Exports omit rider names, local ride labels, invitations, keys, raw network addresses, and speech/packet content. They include technical information and per-ride correlation identifiers: these are pseudonyms, not a guarantee of anonymity to someone who already knows the ride identities. Review who receives a report. The chosen recipient or service handles a received copy under its own policies.

09. Website and support

This website has no analytics, advertising trackers, cookies, contact forms, or remote fonts. GitHub Pages hosts it and may process IP address, user agent, requested URL, and request timing for delivery and security. See GitHub’s privacy statement. Store and external links take you to independently operated services. If you email us, we receive your address, message, attachments, and ordinary mail metadata. Providing support information is voluntary, but we may be unable to resolve a request without relevant contact and technical details. Send only information necessary to resolve your request; do not send private ride invitations or keys.

10. Purposes, legal bases, and recipients

Where Syscake processes personal data, we use it to respond to support and service requests, fulfil applicable contractual obligations, protect our services and handle disputes based on legitimate interests, and comply with legal obligations. Where processing depends on consent, it can be withdrawn without affecting earlier lawful processing. Authorized personnel and necessary hosting/email service providers may process information for these purposes; authorities may receive it where required by law. We do not sell personal data or use it for advertising profiling. Data handled directly by participating phones is not automatically available to Syscake.

11. Retention and international processing

We retain support correspondence only as long as needed for the request, related follow-up, and applicable legal or dispute requirements; we periodically review continued need. Hosting and email providers may process data outside the European Economic Area. Where Syscake transfers personal data and a transfer safeguard is required, we use an applicable adequacy decision or other lawful mechanism, such as standard contractual clauses. Provider privacy notices describe their own processing. Contact us for information about safeguards relevant to your request.

12. Your rights

Subject to applicable law, you may request access, correction, deletion, restriction, or portability of personal data Syscake controls, and object to processing based on legitimate interests. Contact rideweave-support@syscake.it; we may need to verify your identity. Some data may be retained when required or permitted by law. For data stored only on your phone, use the app and the phone’s deletion controls. You may complain to the Italian Data Protection Authority or the supervisory authority where you live or work. We do not make automated decisions with legal or similarly significant effects about you.

13. Changes

We will update this page when the app or our practices change and revise its effective date. Material changes requiring additional notice or consent will be handled as required. This policy describes current behavior, not a promise that future versions will have identical functionality.

Privacy PolicyTerms & ConditionsSupportRWCP v2
Made with love by Syscake ❤️Syscake

© 2026 Syscake S.r.l. · P. IVA 16207441003