Privacy, explained clearly.

1. Scope

This Privacy Policy explains how KuDash handles personal data when you use the KuDash website, contact support, join the pre-launch notification list, create or use a KuDash account, use Cloud Sync, or use app features that depend on Bluetooth, location, maps, weather or ride recording.

KuDash is the service name used in this policy. Privacy questions can be sent to kudashapp@gmail.com.

2. Data we may process

Account and sign-in data

If you choose to sign in, KuDash may process your account identifier, email address, authentication provider and, where provided by the sign-in provider, profile information such as a name. KuDash supports account access through supported sign-in providers and email verification.

Scooter and connection data

KuDash processes information needed to identify and connect to supported scooters, such as scooter model, connection state, Bluetooth discovery information, app-created scooter identity, supported telemetry and user-selected connection preferences. Device-local Bluetooth identifiers are used for local binding and reconnection and are not treated as proof of a scooter's physical identity.

Ride and scooter history

If you record rides, KuDash may process ride start and end times, duration, distance, moving and stopped time, speed summaries, battery information, drive mode information, scooter model, ride notes, telemetry-gap indicators and trusted odometer information when available.

Route and location data

When you grant location permission and use location-dependent features, KuDash may process precise or approximate location, route coordinates, timestamps, accuracy and movement-related information. Location is used for features such as maps, route recording, navigation context, ride intelligence and optional weather information. Location permission is requested contextually rather than solely because the app is opened.

Support, contact and launch emails

If you email KuDash, we receive the address you use and the contents of your message.

Waitlist email address: when you choose to join the KuDash pre-launch waitlist, KuDash collects the email address you submit. It is used to record your requested signup, send the confirmation message, and send the KuDash launch notification you asked for. Joining this waitlist does not by itself subscribe you to a general newsletter.

3. How data is used

Data is used only for purposes reasonably connected to providing and operating KuDash, including authentication, connecting to a scooter, presenting live ride information, recording and reviewing rides, route features, Cloud Sync, restoring account-owned ride history, support, security, service integrity, and sending a launch notification when specifically requested.

KuDash is not designed to sell personal data or build advertising profiles from your ride, scooter or location data.

4. Cloud Sync and service providers

Signed-in account and Cloud Sync functions use Supabase infrastructure for authentication, account sessions and account-owned cloud data. Depending on the feature you choose, authentication may also involve Apple, Google or email verification services.

Cloud Sync can include completed ride records, route files and account-owned scooter profile data. Route files can contain precise coordinates. When a synced ride is deleted, KuDash may retain minimal deletion metadata, such as a ride identifier and deletion time, where needed to prevent an older device from restoring a ride that you deliberately deleted.

Map functions can rely on Apple's MapKit services. Optional weather requests use Open-Meteo and may send latitude and longitude needed to return local weather.

The website waitlist uses Cloudflare infrastructure. A Cloudflare Worker receives the signup request, Cloudflare Turnstile helps reduce automated abuse, and Cloudflare D1 stores the normalized waitlist email address together with limited timestamps and status fields needed to operate the list. KuDash does not intentionally write a visitor's IP address into the KuDash waitlist database.

Google Gmail infrastructure is used to send the waitlist confirmation email from KuDash <kudashapp@gmail.com>. Google and Cloudflare may process ordinary technical information in operating their services under their own terms and privacy practices.

These providers process information under their own terms and privacy practices. KuDash limits integrations to what is reasonably necessary for the relevant feature.

5. Online presence and technical data

When a signed-in account is active, KuDash may use short-lived, pseudonymous connection or presence information to operate account-related realtime functions. Technical services may also generate ordinary security, network and diagnostic records needed to operate or protect the service.

6. Legal bases where GDPR applies

Depending on the feature and context, processing may rely on your consent, steps or services you request, legitimate interests such as security and service integrity, or legal obligations. Optional permissions such as location remain subject to the controls provided by iOS, and you can change those permissions in system settings.

7. Retention and deletion

KuDash keeps personal data only for as long as reasonably needed for the purpose for which it was processed, for account or Cloud Sync continuity, to answer support requests, to administer the waitlist and provide a requested launch notification, to protect service integrity, or to comply with applicable legal obligations.

A waitlist record may be retained while it is reasonably needed to operate the requested launch-notification list and related service records. You can request removal from the waitlist at any time by contacting kudashapp@gmail.com. A removal request may be subject to reasonable verification and any retention that applicable law requires or permits.

Local app data generally remains on your device until you remove it through available app controls or remove the app, subject to normal iOS behavior. Cloud account and sync data remains associated with the account until it is deleted or no longer needed, subject to limited records that may need to be retained for security, integrity or legal reasons.

Account deletion and associated data deletion must be made available in a manner consistent with applicable platform and legal requirements before public App Store release. Where a deletion request requires verification, reasonable identity checks may be used to protect the account from unauthorized deletion.

8. Data rights

Depending on where you live, you may have rights to receive information about personal data, request access, correction or deletion, restrict or object to certain processing, obtain portable data, or withdraw consent where processing is based on consent. These rights can be subject to lawful conditions and exceptions.

To exercise a privacy right, or to request removal from the waitlist, contact kudashapp@gmail.com. KuDash may ask for information reasonably necessary to verify that a request relates to the correct account or email address.

If GDPR applies, you also have the right to lodge a complaint with the competent data protection authority. Nothing in this policy limits rights that applicable law gives you.

9. Security

KuDash uses technical and organizational measures intended to reduce unauthorized access, loss or misuse. No internet-connected service can promise absolute security. Do not send passwords, one-time verification codes, access tokens or other secrets to support.

10. Children

KuDash is not intentionally designed to collect personal data from children in a manner that would require parental consent under applicable law. If you believe a child has provided personal data improperly, contact KuDash so the situation can be reviewed.

11. Changes to this policy

This policy may be updated when KuDash features, service providers or legal requirements change. Material changes should be reflected by updating this page and its "Last updated" date before the changed processing is relied on.