Routes, trip samples, launch times, notes, and detailed controller telemetry are stored in your browser, not in a KuKirin Dash cloud account.
1. Scope and data controller
This policy applies to kukirin.app, the KuKirin Dash web application, the Android application distributed through Google Play, purchase verification and license-delivery services, and related support features. KuKirin Dash is operated by Kelixo from Malta. For privacy questions or requests, contact dash@kukirin.app.
In this policy, “we”, “us”, and “KuKirin Dash” refer to the operator of KuKirin Dash. “You” refers to a visitor, buyer, license holder, or rider using the service.
2. Data we handle
| Category | Examples | Where it is handled |
|---|---|---|
| Purchase and support | Email address, order, checkout and provider transaction identifiers, amount, optional support amount, currency, payment and fulfilment status, purchase IP address, browser user agent, supporter number, assigned license, and email-delivery status. | KuKirin Dash servers and selected payment, storage, and email providers. |
| License access and recovery | License key during activation or a reset request, one-way license fingerprint, random browser installation ID, shortened installation fingerprint, activation time and result, IP address, browser user agent, access class, supporter number, and signed entitlement. | KeyAuth during verification; KuKirin Dash servers for access, security, activation history, and reset support; your browser for the installation ID and entitlement cookie. |
| Local ride and scooter data | GPS route, speed, heading, altitude, trip notes, controller speed, battery, mode, odometer, trip counter, launch times, motion, orientation, grade, and weather snapshots. | Primarily in your browser's IndexedDB or memory. |
| Optional founder details | Contact email, chosen public display name, and optional TikTok or YouTube link. | KuKirin Dash servers; only an approved public name and optional creator link may appear publicly. |
| Service measurements | Aggregate purchase-page views, checkout starts, and a random session value hashed for short-lived active-user counting. | KuKirin Dash servers. No ride route, email, or license key is included in these measurements. |
| Communications and support requests | Messages you send, license-reset request details, and related support history. | The communication provider you choose, Resend, and restricted KuKirin Dash support records. |
We do not collect or store full payment-card, Apple Pay, Google Pay, or cryptocurrency wallet credentials. Stripe or MoneyMotion processes payment credentials on its hosted checkout and returns payment status and transaction information. We do not request special-category personal data.
Your account details
In Settings, you can view your purchase and activation dates, reveal or copy your own licence key, and change your main account email for future key delivery, account recovery and ambassador contact, including new payout requests. This address is stored separately from the original purchase email so your membership and rewards remain unchanged. After successful activation, an encrypted copy of the key may be kept on our servers for this account feature, for up to 400 days or until tester access expires. Reveal and copy require an authorized browser; the key is not saved in browser storage. Existing completed purchase records retain their assigned key under the retention rules below.
3. Why we use data
Contract and steps requested before purchase
We process the buyer email, order, payment status, license assignment, activation information, and delivery records to sell and provide KuKirin Dash, deliver lifetime access, verify licenses, provide updates, and respond to purchase or access support. The email typo suggestion and final email confirmation shown before checkout run in your browser; checkout data is sent to the server only after you choose to proceed.
Legitimate interests
We process limited security and service information to prevent fraud and duplicate license allocation, secure the application, diagnose failed purchases or activations, support browser-lock resets, count aggregate usage, maintain supporter status, and establish or defend legal claims. We use the least data reasonably needed and do not use these records for behavioural advertising.
Consent
Where required, your permission is used for precise geolocation, motion, and orientation sensors. Optional Smart Range community sharing is off by default. You may withdraw optional permission in Settings or your browser/device settings. Withdrawal does not affect earlier lawful processing.
Legal obligations
We may retain or disclose transaction information when necessary to comply with tax, accounting, consumer-protection, law-enforcement, or other applicable legal obligations.
KuKirin Dash does not make decisions producing legal or similarly significant effects about you solely through automated processing. Automated checks may reject an invalid license, suspicious request, or incomplete payment, but support can review genuine access or delivery problems.
4. What stays on your device
Detailed trips are stored locally in the browser database named kukirin-dashboard. This can include route coordinates, timestamps, sensor readings, weather snapshots, scooter telemetry, detected ride events, launch timing, trip names, and notes.
- There is no mandatory KuKirin Dash cloud account for ride history.
- Deleting a trip removes it from the app's local database on that browser.
- Clearing site data can delete trips, settings, the local installation identifier, and browser access.
- Exports are created locally and become files under your control.
- Bluetooth commands and normal controller telemetry are handled locally between the browser, Bluetooth layer, and scooter.
The “Help improve Smart Range” preference is optional and off by default. The current web app records that preference locally but does not currently upload community ride summaries. If summary uploads are introduced, the app will show what is shared and will exclude route coordinates, route shape, exact location, trip name, exact timestamp, email, license key, and persistent device identifier.
5. Providers and data transfers
We use specialist providers only where needed to operate the service:
- Vercel hosts the website and server functions and may process standard request logs such as IP address, time, path, and browser information.
- Stripe is the default hosted checkout provider and processes card, Apple Pay, Google Pay, and related payment information. KuKirin Dash receives payment status, amount, currency, email, and transaction identifiers, not full card or wallet credentials.
- MoneyMotion may be used as a fallback hosted checkout provider. KuKirin Dash receives payment status and transaction identifiers, not full payment credentials.
- IPWhois (ipwho.is) receives an IP address over HTTPS when an authorized administrator views purchase or licence-support IP records. We request approximate country and region for support and security review. No email address, licence key, browser history, GPS route or exact location is sent with this lookup. Results are cached for up to seven days and may be inaccurate for mobile networks or VPNs. They are not used to automatically approve or block account access. See the provider privacy policy.
- KeyAuth verifies license keys during activation and applies its browser/HWID lock. The raw key is sent server-to-server for verification and is not saved in JavaScript-readable browser storage by KuKirin Dash.
- Upstash provides server-side storage for orders, license assignments, supporter profiles, activation and reset-support records, aggregate metrics, and administrative records.
- Resend delivers license, purchase, founder, and reset-support emails and processes recipient address, message contents, and delivery metadata.
- Open-Meteo receives current latitude and longitude when weather is requested while GPS is active. Weather results are cached in the app for about 12 minutes.
- Waze receives map parameters, including location when its embedded live map is used.
- OpenStreetMap tile servers receive normal web requests, including IP address and requested map tiles, when a saved trip route map is displayed.
- Beacio, where used on iPhone, provides the Safari Bluetooth bridge under its own terms and privacy practices.
Some providers may process data outside Malta or the European Economic Area. Where GDPR applies, transfers must rely on an adequacy decision, contractual safeguards such as Standard Contractual Clauses, or another lawful transfer mechanism. You may contact us for more information about safeguards relevant to your data. Provider privacy terms may also apply directly to your use of their service.
We do not sell or rent personal data. We may disclose information where required by law, to protect users or the service, or in connection with a lawful business transfer with appropriate safeguards.
6. How long data is kept
- Unpaid pending checkout records: automatically expire from application storage after approximately 2 days.
- Completed purchase and fulfilment records: retained for the lifetime-access relationship and as needed for license recovery, payment support, fraud prevention, accounting, tax, chargebacks, and legal claims. These records are not currently subject to an automatic 30-day deletion.
- Supporter profile, buyer number, assigned license, and license fingerprint: retained while lifetime access and supporter status remain active, or until a valid deletion request where retention is not legally or operationally required.
- Purchase IP and browser information: retained with the purchase/support record only as long as reasonably necessary for payment support, abuse prevention, and claims, then deleted or anonymised where feasible.
- Activation history: the server keeps up to the latest 20 recorded activation outcomes for a license fingerprint. This may include time, shortened installation fingerprint, IP address, and browser user agent.
- License-reset requests: retained while support handles the request and until deleted from the restricted developer console or no longer needed for support, security, or legal purposes.
- Active-user measurement: the server-side active-session entry expires from the active count after approximately 10 minutes; only aggregate counters may remain.
- Aggregate page and checkout counts: may be retained without a fixed expiry because they do not contain route data, email, or raw license keys.
- Entitlement cookie: expires after approximately 400 days unless renewed, cleared, or you sign out.
- Local trips and preferences: remain until you delete them or clear browser/site data.
- Support communications and legal records: retained only as long as needed for the request, contractual history, applicable limitation periods, or legal duties.
When a fixed period is not possible, we use necessity, the lifetime-access relationship, security risk, legal obligations, and limitation periods to determine retention.
8. Your privacy rights
Depending on your location, including under the GDPR, you may have rights to:
- access personal data held about you and receive a copy;
- correct inaccurate or incomplete information;
- request deletion where no lawful reason requires continued retention;
- restrict processing in certain circumstances;
- object to processing based on legitimate interests;
- receive certain data in a portable format where applicable;
- withdraw consent for optional processing at any time; and
- lodge a complaint with a supervisory authority.
To exercise a right, email dash@kukirin.app from the purchase/contact address where possible. We may ask for limited information to verify that the request concerns your record. We normally respond within one month, subject to lawful extensions.
9. Security
We use HTTPS, restricted server-side secrets, signed HttpOnly entitlements, same-site request checks, license fingerprints, idempotent payment fulfillment, access controls, and rate limiting where configured. Detailed trips remain local by design, reducing the amount of route data held centrally.
No internet service or storage system is completely secure. Keep your license key private, secure access to your email and device, and contact us promptly if you believe your access or personal data has been compromised.
Browser access protection
To protect purchased access against key sharing, we associate a licence with a random browser installation identifier. We assess recent activation IP changes, device family, browser changes, last-seen time and previous transfers. These signals support licence delivery and our legitimate interest in preventing misuse; an IP address alone is not proof of identity. Travel or an IP change in the same browser does not by itself remove access.
Low-risk browser changes may be approved automatically. Other changes can require a manual reset review through support. You can ask us to review an incorrect decision. The recent-event window contains up to 30 events from the preceding 30 days and is pruned at subsequent activation; the current binding remains until replaced or removed through an approved account request. The latest risk-decision record expires after 30 days. Existing activation-history and purchase-retention rules still apply.
KeyAuth processes licence creation and verification, and may process a browser reset when approved. Seller credentials stay on our servers and are never included in the public application. Gauge colours and other display preferences remain in your browser.
10. Children's privacy
KuKirin Dash is not directed to children under 16 and is intended for riders legally permitted to use the relevant scooter and payment method. We do not knowingly collect children's personal data. A parent or guardian who believes a child provided personal data should contact us so the record can be reviewed and deleted where appropriate.
Google Play purchase verification
KuKirin Dash is publicly available through Google Play. When you buy or restore access in the Android app, the app sends the Google Play package name, product identifier, purchase token, purchase state, and related order information to our server. Our server verifies the purchase with the Google Play Developer API before assigning or restoring a licence. We retain the Google Play order identifier, provider status, amount and currency information made available to us, verification timestamps, buyer number, and assigned licence so that one verified order reconnects to the same account rather than creating duplicate access.
Google does not necessarily provide your Google Play account email to KuKirin Dash. Until you add a main account email in Settings, an internal Google Play account label may be shown in administrative records. Adding or changing that email updates the contact and recovery address for the same KuKirin Dash account; it does not create a new buyer, purchase, or licence. Purchase verification synchronizes your entitlement and account identity only. It does not upload or synchronize detailed trips, routes, scooter telemetry, or local settings.
11. Changes to this policy
We may update this policy when features, providers, law, or data practices change. The current version will remain available at kukirin.app/privacy with a revised effective date. Material changes may also be highlighted in the app or purchase flow.
Optional Dash Underground referrals
If you join Dash Underground, we link your membership to your existing paid licence identity and purchase email. We keep your member number, current and historical referral codes, accepted terms version, referred order references, rewards, reversals, transfer requests, chosen payout method and destination details, payment references, account status, and relevant support or audit notes. These records administer the Ambassador agreement, calculate and pay rewards, prevent duplicate payments and abuse, and meet applicable accounting or legal obligations.
When referral attribution is enabled and you enter through a valid rider referral link, we set a signed, HttpOnly first-party kukirin_referral cookie, which lasts up to 30 days. It contains a pseudonymous Ambassador identifier, the code used, and an expiry time, not your licence or route. The last valid referral link opened in that browser is attached to an order when checkout starts. Ordinary purchase-page visits do not create referral attribution or show referral controls. The price is unchanged. You can remove the referral cookie in your browser's site-data settings; clearing all site data also removes local trips and preferences. Clearing it does not alter an order already created or remove records we need to account for a completed payment.
Ambassadors see their own balances and activity, not referred buyers' email addresses, IP addresses, licence keys, or routes. Authorized admins can inspect order, reward, payout-destination, and manual-action audit records. Payout details are used to arrange the requested transfer and are not shown publicly. Never provide a full card number, expiry date, security code, password, seed phrase, or private wallet key. We do not add device fingerprinting, advertising pixels, or background activity tracking for referrals. The existing hosting and Redis storage providers process the relevant records; payouts are reviewed manually rather than through an automatic bank connection.
Referral cookies expire automatically. Financial, payout, and audit records are retained for applicable accounting, dispute and fraud-prevention needs under this policy's retention rules, not deleted merely because an ID changes. Historical code reservations remain to prevent reassignment and impersonation; requests to restrict, correct or remove associated personal data can be reviewed through support, subject to legal recordkeeping requirements. The app also stores local flags remembering the Underground introduction and announcement so they do not repeatedly interrupt you.
Underground privacy disclosure updated: 4 September 2026.
12. Contact
For privacy questions, data requests, or concerns, use the support form or email us directly:
KuKirin Dash / Kelixo
dash@kukirin.app