1. Controller and contact
EV Connected, at controller address pending, is the controller for the online platform. Privacy contact: contact pending. Country of establishment: Romania.
2. Data we process
- Account: name, email, a password hash, Terms version/acceptance time, session records and hashed short-lived password-reset tokens.
- Gateway: server-issued device ID, hashed device token, hashed app-installation ID, app/protocol version and connection times.
- Vehicle: supported battery, charge, lock, door, light, climate, model/VIN, network and status fields reported by your gateway.
- Phone telemetry: phone battery percentage, car Wi-Fi RSSI, cellular signal level and precise GPS position approximately every 10 minutes when available and enabled.
- Optional advanced trip history: completed-trip time, distance, duration, EV share, battery use, regeneration, engine runtime, average speed and state-of-charge change, plus lean vehicle and route samples at most once every 60 seconds or after at least 500 metres. A sample can contain speed, state of charge, battery and regenerative power, engine RPM, cumulative trip values, latitude, longitude, altitude, bearing and horizontal accuracy.
- Manually saved diagnostic reports: ELM identity, adapter voltage/protocol, request and response counters, decoded measurement summaries, and bounded raw read-only ECU request/response evidence. The report records only whether a VIN was read; the VIN response and value are redacted before upload.
- Commands: command type, bounded arguments, requester, delivery/result status and timestamps.
- Security/operations: authentication, device pairing, command audit events, IP/network metadata available to the server or security proxy, and technical errors. Device pairing uses an app-installation identifier and a private credential stored in Android secure storage.
- Transactional email: recipient address, message type, delivery identifier and provider acceptance/error metadata for welcome, recovery and account-security messages.
Advanced trip uploads are derived and identity-minimized: they do not contain the VIN, raw ECU/diagnostic frames, adapter identity or advertising IDs. A manually saved diagnostic report is a separate explicit support/validation record and does contain bounded raw read-only ECU evidence and adapter information, with VIN responses redacted. We do not intentionally collect contacts, messages, photos, microphone/camera content or arbitrary phone sensors.
3. Why and on what basis
We process account, device, vehicle, location and command data to provide the remote platform you request and perform our agreement with you. Advanced online trip history is optional: pairing only creates a private device credential and does not enable trip uploads. You must separately turn on Advanced online telemetry in the app. Saving a diagnostic report is also optional and happens only after you press its dedicated action. We process limited security logs and enforce one-device ownership for our legitimate interests in preventing unauthorized vehicle access, abuse and service failure. Where Android permission or applicable law requires consent for phone location, you can grant or withdraw that permission in the app or phone settings.
4. Retention
Phone connectivity/location history is stored in 10-minute buckets and deleted after a maximum of 60 days. Advanced online trip summaries and their lean route/vehicle samples are kept on the private server until the owner requests trip-history deletion or account deletion. Each paired installation keeps at most its newest 50 manually saved diagnostic reports; older reports are automatically removed and individual reports can be deleted in the account. Turning Advanced online telemetry off stops trip-API traffic immediately and discards queued remote writes, but does not affect a separate report upload that you explicitly request. With the feature off, the app retains only the latest completed trip on that device. The latest remote-vehicle snapshot remains until replaced or the associated account/device data is deleted.
Pairing codes expire after 10 minutes. Password-reset links expire after 30 minutes; both are single-use and removed after use or expiry. Sessions expire according to the configured session period. Account, command, email-delivery and security records are kept while the account is active and only as long afterward as reasonably required for security, legal claims or legal duties.
5. Who receives data
Authorized infrastructure providers may process data to host, secure, back up and deliver the Service. Cloudflare may process connection/security metadata as the public proxy. Brevo processes account email addresses and transactional message/delivery data when sending welcome, password-recovery and security notices. When the map is visible, your browser requests OpenStreetMap tiles and the tile provider receives ordinary web-request data such as IP address and user agent. We do not sell personal data and do not use vehicle telemetry for advertising or marketing email.
6. International transfers
Some infrastructure providers may process data outside the European Economic Area. Contact the Provider for current information about relevant processor locations and transfer safeguards.
7. Cookies and local storage
The web platform uses strictly necessary secure session and CSRF cookies for sign-in and request protection. Appearance preference is stored locally in your browser. There are no advertising or cross-site analytics cookies in the current implementation.
8. Your choices and rights
You can independently disable Advanced online telemetry, phone telemetry, location permission or cloud connectivity, and you can unpair the gateway. Pairing alone never enables Advanced online telemetry or uploads a diagnostic report. With Advanced online telemetry off, the app makes zero trip-history requests and shows only its latest locally stored completed trip; a diagnostic report is transmitted only when you press Save to cloud. You can inspect, copy, download and delete saved reports from the private account. Contact us using the address above to request deletion of trip history or the account.
Depending on applicable law, you may request access, correction, deletion, restriction, portability or objection, and may withdraw consent where processing relies on it. You may also complain to the Romanian data-protection authority or your local supervisory authority.
9. Security
We use hashed passwords and device credentials, hashed short-lived single-use password-reset tokens, short-lived single-use pairing codes, owner-scoped database queries and WebSockets, CSRF/origin checks, transport encryption at the public edge and command allowlists. A completed password reset revokes all browser sessions. No system is risk-free. Unpair a missing phone and change your password immediately if access may be compromised.
10. Other drivers and children
The account holder must inform authorized drivers that the vehicle may transmit location and status. The Service is not directed to children and accounts may not be created by anyone under 18.
11. Changes
Material privacy changes will be presented in the platform and, where required, a new acknowledgement or consent will be requested. The effective version appears at the top of this notice.