Privacy policy

Last updated: 4 October 2026.

LoEUC is an electric unicycle telemetry application.

Data processed by the app#

• Bluetooth device identifiers and electric unicycle telemetry.
• Ride history and dashboard settings.
• Location data, used to record a ride route when you grant location permission.

Storage and transmission#

These data are stored locally on your device. Uploading rides to loeuc.ru starts only when you voluntarily enable synchronization for your account. Adding an email and password does not enable synchronization.

With synchronization enabled, the server stores complete rides: all saved telemetry samples, GPS routes, diagnostic fields, wheel information and portable application settings. They are available to the account owner after signing in to the personal cabinet. Map tiles are loaded from CARTO or an OpenStreetMap-based provider: your browser sends ordinary network information and tile requests for the visible map area, rather than the ride document. No public route link is created automatically.

For a full account the server stores your email and a password hash. Email verification is optional; password recovery sends a one-time code to that address. Codes and device tokens are stored as hashes. Secrets, system permissions and wheel control commands are excluded from synchronized settings.

Preset sharing is a separate feature, used only when you press "Share", "Copy link" or "QR" on a dashboard preset. At that moment the dashboard layout alone is sent to loeuc.ru and kept there: which tiles you have, their sizes and colours, the pinned band setup, plus the preset name and wheel label you typed. No telemetry, no rides, no routes and no device identifier.

What is worth knowing about those links:

• a link is not password protected — anyone holding it can read the preset;
• a record is deleted automatically once its link has gone a year without being opened;
• with no network the app hands you the long self-contained link instead, which carries the whole preset and puts nothing on the server at all. Sharing by file or through the clipboard works the same way.

For a published preset the app may silently create a guest account so this and later presets have an owner. The server keeps its identifier, public name and a recovery-key hash, not the key itself; the device token remains only in the app's protected storage. Keep your recovery key: the app can show its saved copy while available on the device, but the server cannot issue the same key again. Losing both the key and every active session makes a guest account unrecoverable unless you have added email credentials. You can revoke the local session in settings; this removes the device's access but does not delete already published presets.

Telegram photos are retained for at most 90 days, solely for private administrator feedback ingestion. This has nothing to do with preset sharing: sharing never uploads wheel telemetry, ride history or location.

Apple may process TestFlight diagnostics, crash reports and feedback according to Apple's own privacy terms when you install a beta through TestFlight.

Exported files and backups#

When you save a file through the system file chooser, you select local storage, Google Drive, iCloud Drive or another provider. The file is stored with that provider, rather than in a LoEUC archive service. The selected service determines how its cloud files are protected and deleted. Your own archive may contain complete routes; sharing it can disclose those data.

The loeuc.ru website#

The website counts how many people read it, and does it itself: no third-party counters, no scripts or analytics cookies. The personal cabinet uses a session cookie for sign-in. For each page view it keeps the page address, the day and the site the visit came from, if any. To tell that two views on one day came from the same person, the server mixes the IP address and the browser name with a random key that lives for one day and keeps only the result. The IP address itself is never stored in the database, and the key is deleted at the end of the day, so visits on different days cannot be linked.

Separately, like any web server, it keeps a request log with IP addresses. It is used to investigate failures and attacks and is deleted after 14 days.

Permissions#

Bluetooth access is used to discover and communicate with electric unicycles. Location access is used only to record ride routes. Both permissions can be revoked in your phone settings.

Data deletion#

Rides can be deleted in the app or the personal cabinet. With synchronization enabled, manual deletion propagates between the website and devices. On the server, a ride can be restored for 10 days; its data are then deleted automatically. Only a technical identifier and deletion revision remain to prevent an offline device from uploading the deleted ride again. Automatic retention cleanup on a phone does not delete server copies. Disabling synchronization stops the exchange; previously uploaded rides remain in the cabinet. Removing LoEUC from the device removes its locally stored application data.

Changes#

This policy will be updated if LoEUC begins using additional data or network services.

Contact#

The public contact email published with the LoEUC TestFlight or App Store listing can be used for privacy questions.