Privacy Policy for Waza Speeding
This Privacy Policy applies to Waza Speeding, the mobile app, support channels, website product pages, cloud storage used for eligible trips, trip-processing services, subscription-entitlement checks, and related operations. N.I.E.22 LIMITED is the controller of personal data processed through Waza Speeding unless a different role is stated in a signed agreement. Contact us at info@nie22.com.
1. What Waza Speeding Does
Waza Speeding records consented car-like journeys for later private review. The app is retrospective by design: it detects journeys, stores route samples, and then lets the user decide whether to process a recorded trip for speed-limit heat-map analysis. It is not a live speed dashboard, public route-sharing service, social network, navigation service, enforcement service, insurance telematics service, or emergency service.
2. Personal Data We Collect
We may collect email address, Waza user ID, account state, consent records, selected review personality, notification choices, vehicle energy profile and trip-experience preferences, subscription entitlement tier, support messages, privacy requests, device and diagnostic information, operational logs, and security events. After explicit consent and iOS location permission, we may collect precise location, speed, heading, GPS accuracy, timestamps, route samples, journey start and end times, trip duration, trip distance, trip status, sync state, processing state, provider lookup status, speed-limit observations, heat-map bands, and generated retrospective summaries.
3. Sensitive Driving and Location Data
Location traces and driving patterns can be sensitive because they may reveal where a person travels, when they travel, habits, routines, home or workplace patterns, and possible driving behaviour. Waza treats raw location traces, speed samples, and route analysis as private user data. The app is not designed to infer health, credit, employment, insurance, criminal, relationship, or special-category profile traits from trip data.
4. Sources of Data
We collect data directly from you when you register, grant consent, set preferences, manage subscriptions, ask for a trip review, delete trips or account data, or contact support. We generate data from your app activity, device state, GPS signals, journey detection, trip sync, processing results, notifications, and security events. Apple may provide purchase and entitlement information through App Store purchase systems. Speed-limit or map-matching providers may return road, route, speed-limit, and confidence information after a user-requested review.
5. How We Use Data
We use personal data to create and maintain accounts, save consent choices, detect car-like journeys, record route samples, sync eligible trip records, process trip reviews only when requested, generate retrospective speed-limit heat maps, send optional local trip-ready notifications, prepare on-device spoken briefings and post-analysis summaries, check subscription entitlements, prevent abuse, secure the service, troubleshoot reliability, respond to support requests, process privacy requests, and comply with legal obligations.
6. UK/EU Lawful Bases
For UK/EU users, our lawful bases may include contract where processing is necessary to provide account, trip recording, review, subscription, support, and deletion features; consent for location permission, trip storage, retrospective processing, optional notifications, and optional analytics where applicable; legitimate interests for security, fraud prevention, abuse prevention, service reliability, diagnostics, and limited improvement; and legal obligation where we must preserve, disclose, or delete records.
7. Consent and Withdrawal
Waza does not record trips before explicit Waza consent and iOS location permission. Consent choices cover location tracking, trip storage, retrospective processing, selected review personality, trip-ready notifications, and optional anonymous analytics where available. You may withdraw consent in Settings or by contacting info@nie22.com. Withdrawal does not make earlier processing unlawful, but it stops recording eligibility until consent is granted again. You can also control iOS permissions in device settings.
8. What Other People Can See
Waza Speeding is not a social product. Other Waza users do not see your raw coordinates, speed samples, routes, journeys, heat maps, generated summaries, selected review personality, account deletion requests, consent records, or internal logs. The service does not publish leaderboards, public speeding scores, public route history, or social profiles based on driving data.
9. Route Processing and Service Providers
Route samples may be sent to speed-limit or map-matching providers only to process a trip review requested by the user. Provider results may include speed limits, matched-road information, and confidence values. We do not send route samples to providers for advertising, social ranking, or unrelated profiling. Provider lookup logs should avoid raw coordinates where practical. Third-party providers may process limited data under their own terms, privacy notices, or service contracts.
10. On-Device AI Narration
Waza includes required on-device AI narration. The app may download public model files from Hugging Face into an app-scoped cache. Qwen generates spoken-brief copy and post-trip retrospective summaries on device, and Kokoro renders spoken audio on device. Trip traces and trip analysis facts are not sent to Hugging Face, OpenAI, Azure OpenAI, or another hosted LLM for narration. If Qwen preparation fails, Waza may use a deterministic local template as a safety fallback. Model files and generated summaries can be removed by deleting app data; the AI model cache can also be downloaded, refreshed, or deleted from Settings where available.
11. Purchases and Entitlement Data
App Store purchases are processed by Apple. Waza stores subscription entitlement tier needed to decide whether additional retrospective trip reviews are available after the first processed review. Waza does not receive raw StoreKit transaction identifiers according to the current product design. Apple may process payment, refund, tax, transaction, and account information under its own terms and privacy notices.
12. No Advertising or Cross-App Tracking
Waza Speeding does not use Apple's Advertising Identifier, advertising SDKs, or third-party tracking SDKs. We do not sell personal data, share personal data with data brokers, or combine app data with third-party data for advertising, advertising measurement, or tracking across apps or websites owned by other companies. Optional analytics, if enabled, must not include raw coordinates, speed samples, access tokens, or provider API keys.
13. Retention
Free accounts retain trip recordings locally on device for seven days. Older local-only recordings are discarded and purged automatically. Paid accounts retain trip recordings locally on device for seven days, then archive eligible recordings to Waza backend storage. Backend retention is capped at thirty days from the trip end time, and older recordings are purged automatically. Processed summaries and on-device narrative summaries are retained until deletion or the applicable retention cap. Support, privacy, consent, transaction entitlement, security, and legal records may be kept where required or permitted by law.
14. Deletion and Privacy Rights
You can delete account and location data from Settings where available. Account deletion removes account state, consent state, entitlement state, and stored trips from the Waza Speeding service. Location-data deletion removes trip location data while preserving the current subscription tier where needed. UK/EU users may have rights to access, correction, deletion, restriction, objection, portability, consent withdrawal, and complaint to a supervisory authority. UK users may complain to the Information Commissioner's Office.
15. Security
We use administrative, technical, and organisational safeguards appropriate to a small consumer service, including authenticated access, HTTPS/TLS transport, platform security, access controls, provider-secret protection, retention limits, and operational monitoring. Application telemetry must not log raw coordinates, raw speed samples, access tokens, or provider API keys. No system can be guaranteed secure.
16. International Transfers
Waza Speeding may be operated, hosted, processed, or supported from countries outside your location, including through Microsoft Azure, Apple, route-processing providers, support tools, and operational vendors. Where required, we use appropriate safeguards such as contracts, vendor due diligence, and applicable transfer terms.
17. Children
Waza Speeding is not directed to children and is not listed in the Kids category. Users should use the app only where they can lawfully grant the required account, location, trip storage, and retrospective processing permissions.
18. Changes and Contact
We may update this Policy as the product, law, vendors, or app-store requirements change. Material updates should be reflected in the app, website, and App Store privacy disclosures before the relevant build is released. Contact info@nie22.com for privacy, support, or legal concerns.