Privacy Policy

IONIQ Telemetry ("we", "our", or "us") respects your privacy. This Privacy Policy describes how information is collected, used, and safeguarded when you use our Android or iOS application ("App").

Both versions of the App behave the same way: vehicle telemetry is processed and stored on your own device, and no telemetry, trip log or account data reaches a server of ours. The one exception is route and place lookups made without your own routing key, which pass through a proxy we operate purely to attach a shared routing key — it stores nothing, and section 3 describes it in full. Where the two platforms genuinely differ — the permissions each operating system asks for, the in-car surface, and voice input — this policy says so explicitly.

1. Information We Collect and Process

A. Vehicle Telemetry Data (On-Device)

When connected to your vehicle via a Bluetooth OBD-II adapter, the App queries and decodes standard vehicle diagnostic CAN signals (such as State of Charge, Pack Voltage, Cell Delta, Speed, Tire Pressures, and Battery Temperatures).

Storage: All decoded vehicle telemetry and trip logs are stored locally on your device in local app storage. We do not transmit or upload your vehicle telemetry data to any external server.

B. Bluetooth & Device Permissions

The App requests Bluetooth access solely to discover, pair, and establish a serial data transport connection with your OBD-II adapter.

• Android: BLUETOOTH_CONNECT and BLUETOOTH_SCAN.
• iOS: Bluetooth access via Core Bluetooth (NSBluetoothAlwaysUsageDescription). The iOS app keeps a background Bluetooth session so telemetry continues while the screen is off during a drive.

C. Location Data

The App requests Location access to:

• Scan for nearby Bluetooth Low Energy (BLE) OBD adapters (required by the Android OS framework).
• Calculate your current vehicle coordinates for live EV trip planning and nearby charging station corridor matching.
• Determine whether the vehicle is moving or parked, which is how drives are separated from charging sessions in your trip log.

Android: ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION. iOS: "When In Use" or "Always" location (NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription). Location runs only while an OBD adapter is connected — with nothing connected there is no trip to log, and the App stops using it.

Location data is processed in real-time on your device and is never shared, sold, or uploaded to remote tracking databases.

D. Motion & Fitness (iOS only)

On iOS the App may request Motion & Fitness access (NSMotionUsageDescription) to read the system's automotive-activity signal. It is used for one purpose: telling a parked car apart from one that is simply out of GPS reception, so a trip is not left open indefinitely in a tunnel or a basement car park. No motion or activity history is stored or transmitted, and the App works without this permission — it falls back to GPS displacement and the vehicle's own odometer.

E. Advertising & Analytics

The App contains no advertising and no analytics or attribution SDKs. It does not read your Advertising ID, and no ad network receives data from it.

F. AI Features (Gemini or DeepSeek, BYOK Model)

AI features — AI Trip Planning, Post-Trip Briefing, Weekly/Monthly Digest, Charging Intelligence, Battery Health Report, and AI Assistant — use either Google's Gemini API or the DeepSeek API, whichever provider you select in Settings, via a Bring Your Own Key (BYOK) model.

• All AI features are opt-in. With no API key entered, every AI surface is hidden and no AI request is ever made. A single Enable AI features switch in Settings turns them all off again at any time, and the App shows you what a request would send before you enable it.
• Your personal Gemini or DeepSeek API key is stored locally on your device in private app storage, readable only by this app, and is never sent to our servers.
• When an AI request is initiated by you, current vehicle telemetry context (trip data, battery stats, charging history, efficiency, temperatures, fault codes) is sent directly from your device to your selected provider's API endpoint using your key. It does not pass through any server of ours.
• We do not collect, store, or sell any of your AI conversation prompts, vehicle data, or responses.
• Some AI results — such as the post-trip briefing — are cached on your device alongside the trip they describe, so re-reading one costs no further request. Deleting the trip deletes the cached text with it.

G. Voice Input & Spoken Responses (Android only)

Voice input is an Android feature. The iOS app has no voice input and requests no microphone access; on iPhone, the Assistant and the trip-planning prompt are typed.

On Android, where the App offers voice input (the Assistant and the trip-planning prompt on the phone), tapping the microphone hands off to your device's own speech recognizer via the standard RECOGNIZE_SPEECH intent. The App does not record, buffer, or transmit audio itself — it receives only the transcribed text, which is then handled exactly like text you typed. Spoken answers are produced by your device's built-in text-to-speech engine. Audio handling is governed by your device's speech and assistant settings.

2. How We Use Information

We use local data exclusively to:

• Provide live vehicle dashboard instrumentation and battery health metrics.
• Calculate EV route consumption, charger stop recommendations, and navigation waypoints.
• Provide read-only telemetry, battery health, charging and trip-history displays on the car screen — via Android Auto on Android, and Apple CarPlay on iOS.

3. Data Sharing & Third Parties

We do not sell, trade, or transfer your personal data or vehicle telemetry to any third party. Data is shared with external services only in the following user-initiated instances:

• Routing provider: Route coordinate and destination-search queries are sent to the routing provider you select in Settings — OpenRouteService (built on OpenStreetMap data) or Google Maps — and are subject to that provider's privacy policy. If you supply your own API key, the request goes directly from your device to the provider under your own account. If you have not supplied an OpenRouteService key, the request instead passes through a proxy we operate (proxy.spenit.my) whose only job is to attach a shared OpenRouteService key before forwarding it; the proxy keeps no logs or database of its own, stores no coordinates, and is not linked to any account or device identifier. Supplying your own key bypasses it entirely. Google Maps routing always requires your own key. Any key you enter is stored locally in private app storage and never reaches a server of ours.
• Open Charge Map: Coordinate queries used to look up public charging stations near your route.
• Navigation hand-off: Launching turn-by-turn navigation hands destination coordinates directly to a maps application already installed on your device — Google Maps where it is present, otherwise Apple Maps on iOS. The App does not navigate itself and sends nothing to these apps until you tap to start navigation.
• In-app purchases: The optional one-time Pro unlock is processed entirely by Google Play Billing or the Apple App Store. We never see or handle your payment details, and the App stores only whether the purchase is active.

4. Data Retention & Deletion

You have full control over your local data. You can clear all recorded trip logs, saved OBD adapter preferences, and telemetry sessions at any time from within the App. Removing the App also removes its data: on Android you may additionally clear the App's data in Android Settings, and on iOS deleting the App removes its container in full.

Backups: The App can write backup files containing your trips, charging sessions, saved plans and settings — including any API keys you have entered. These files are written to the App's own storage on your device and are uploaded nowhere. They leave your device only if you explicitly share or export one, at which point they go wherever you send them; treat a backup file as you would a password, and delete it when you no longer need it.

5. Security

We implement industry-standard security practices. Telemetry communication occurs directly between your phone and the paired OBD adapter over a local Bluetooth connection, and does not traverse the internet.

6. Contact Us

If you have any questions or feedback regarding this Privacy Policy, please contact us at:

Email: hello@faizalmzain.com