How BlueEV handles personal data.

This Privacy Policy applies to the BlueEV mobile application, website, application programming interfaces, CarPlay experience, Tesla browser experience, widgets, Live Activities, App Intents, notifications, and related services (together, the “Service”).

BlueEV operates the Service and is the controller of the personal data described in this Policy. BlueEV can be contacted at privacy@blueev.ldev.cloud or at 33 Ushangi Chkheidze Street, Tbilisi, Georgia. “BlueEV,” “we,” “us,” and “our” refer to that operator. BlueEV is the service brand and is not described in this Policy as an incorporated company.

Independent charging providers separately control the provider accounts, charging, reservations, payments, refunds, station operations, and related personal data they process under their own terms and privacy notices. This Policy governs BlueEV's own processing, including its collection and transmission of data to those providers.

This Policy applies when you browse the Service anonymously, sign in with Apple, save or synchronize preferences, link or create an account with a charging provider, request a reservation or charging action, facilitate a provider-direct payment, receive a notification, submit content, or communicate with BlueEV.

A provider, payment service, Apple, mapping service, station operator, or external website may process data for its own purposes. Its notice applies to that independent processing. Links to third-party services do not extend this Policy to those services.

Depending on the features you use, BlueEV processes the following categories:

• Account and identity data: your Apple user identifier, name, Apple relay or other email supplied through Sign in with Apple, authentication and session state, profile details, linked devices, and account status. We receive this from you, Apple, and our authentication systems.
• Device and app data: install, device, and vendor identifiers; device model and model identifier; operating system; app version, build, and bundle identifier; app language; locale; time zone; push token, notification settings, and last-seen state; App Attest keys, challenges, and results; and IP address or user agent when used for sessions, reports, security, diagnostics, rate limiting, or abuse prevention. We receive this automatically from your device and network interactions.
• Location and route data: precise location, accuracy, and timestamp when you grant access; the precise location automatically attached to feedback or a station report when available; route origin and destination; rounded or cached origins; active navigation and handoff state; and background location during an active navigation session. We receive this from your device when the relevant permission and feature are active.
• Discovery, preference, and synchronization data: searches, filters, favorites, selected stations, recent destinations, navigation handoffs, provider preferences, app-language preference, and state synchronized among iPhone, CarPlay, Tesla, widgets, or other signed-in surfaces.
• Reports, support, and submitted content: message text, report category, email, station identifier, photos, screenshots, files, inbound support email, moderation status, diagnostic metadata, and identifiers or hashes used to control spam and abuse. We receive this from you and from the app context accompanying your submission.
• Notification data: push token, effective app language, preferences, message and delivery records, read state, and retained notification history. We receive this from your device and our delivery systems.
• Charging-provider registration and account data: first and last name, email addresses, phone numbers, verification status, provider username, protected provider credentials or tokens, provider account identifier, account readiness, balance, and provider responses. We receive this from you and the independent provider. Where a provider requires it, a password can be encrypted and recoverable so BlueEV can act on your instruction; it is not described as irreversibly hashed.
• Provider action data: account linking, assisted registration and provider-consent evidence, reservations, charging start and stop requests, live or reconciled charging status, station, EVSE and connector identifiers, remote-command state, failures, action evidence, and audit records. We receive this from you, BlueEV systems, and the relevant provider.
• Payment and transaction data: provider, amount, currency, transaction or payment identifier, status, timestamps, balance, wallet or card-network metadata, Apple Pay result metadata, top-up, refund, reversal, and dispute evidence. Payment credentials are submitted through Apple, the provider, or its payment service. BlueEV does not intentionally receive or store your full payment-card number.
• Station and provider data: provider names, provider station identifiers, locations, connectors, tariffs, availability, images, and operational metadata from charging providers, station operators, and public or operator-supplied sources. This generally describes stations and providers rather than you.

Location access is optional at the operating-system level, but some functions cannot work without it. BlueEV uses precise location to show nearby stations, calculate and update a requested route, support active navigation and device handoff, and attach relevant context to feedback or a station report. When your location is available at submission time, the app automatically includes its coordinate, accuracy, and timestamp with that submission.

For driver-to-station directions, BlueEV may round the route origin to a small geographic cell for lookup and caching. Google or OpenRouteService may receive the route origin and station destination when needed to calculate a route. Background location is used only while an active navigation function requires it and the applicable iOS permission remains enabled. You can change location permission in iOS Settings, but doing so may disable nearby, route, report-location, or active-navigation behavior.

BlueEV uses reports, feedback, support messages, and attachments to respond to you, investigate a problem, correct station information, moderate content, improve service quality, prevent abuse, and establish or defend legal claims. Do not include unnecessary personal data about yourself or another person.

A station photo is submitted for possible public display. It becomes public only after BlueEV reviews and approves it. An approved photo and its station context may be visible to anyone using BlueEV. Your account credentials, email, phone number, precise report location, and unapproved submission do not become public merely because the station page is public.

BlueEV processes personal data only where an applicable legal basis supports it:

• Providing a requested service or taking requested steps: station discovery, an account, synchronization, routing, provider linking or registration, reservations, charging actions, provider-direct payments, support, and account deletion require the data reasonably necessary to perform your request or our service relationship.
• Consent and device choice: BlueEV relies on consent or your permission where law requires it, including for permission-gated location, push notifications, or provider credential transmission. You may withdraw consent through the relevant setting or by contacting us. Withdrawal does not invalidate processing already lawfully performed.
• Legitimate interests: we use data where necessary for service security, fraud and abuse prevention, reliability, moderation, debugging, support quality, and the establishment or defense of claims. We assess necessity and balance those interests against your rights and reasonable expectations.
• Legal obligations: we process or retain data where required for accounting, tax, consumer, privacy, security, regulatory, court, or other legal duties and valid official requests.
• Protection of vital interests: in a genuine emergency, data may be processed where necessary to protect a person's life or physical safety and the law permits it.

BlueEV does not use consent as a blanket basis. The basis depends on the purpose and context. Contact us if you want information about the basis applied to a particular operation.

You may browse basic public station information without a BlueEV account. Information marked required in an account, provider, report, payment, or action flow is contractual or technically necessary for that feature unless the screen states otherwise. If you do not provide it, BlueEV may be unable to create or secure the account, link the provider, transmit the requested command, process the report, facilitate the payment, or respond to you. Optional fields may be left blank without losing unrelated functions.

BlueEV uses data to authenticate users, manage devices and sessions, synchronize selected state, present stations, calculate routes, moderate reports and photos, communicate with providers, execute and reconcile requested actions, facilitate provider-direct payments, send service notifications, provide support, secure and observe the Service, prevent fraud or abuse, comply with law, and resolve complaints and claims.

• BlueEV does not sell personal data.
• BlueEV does not use personal data for third-party advertising.
• BlueEV does not send direct marketing. Notifications concern requested features, provider operations, charging, security, support, service status, or material legal or service changes.
• BlueEV does not use personal data or user content to train general-purpose machine learning models.

BlueEV discloses only the categories reasonably needed for the stated integration, request, security need, or legal duty. Depending on your use, recipients include:

• Apple for Sign in with Apple, push notifications, App Attest, Apple Pay, operating-system integrations, and App Store distribution.
• Cloudflare for application and API hosting, databases, cache, object storage, delivery, security, analytics, and operational observability.
• Google for Maps, Directions, and Geocoding used by the requested station or route function.
• OpenRouteService for route calculation when used as the available routing service.
• Resend for support email and related inbound or outbound message handling when used.
• Independent charging providers and their technical or payment services for station data, account linking or creation, verification, reservations, charging, balances, payments, refunds, and support. These providers are not BlueEV processors when they determine their own purposes and means under their own terms and notices.
• advisers, auditors, insurers, authorities, courts, counterparties, and a lawful successor where reasonably necessary for professional advice, security, a transaction, legal compliance, or claims.

No recipient necessarily receives every category listed in this Policy. BlueEV may also disclose data when you direct us to do so or when necessary to protect a person, the Service, or legal rights under applicable law.

BlueEV and its recipients may process personal data outside Georgia, including in jurisdictions whose privacy rules differ from Georgian law. International transfers are made only where a lawful transfer condition applies, such as an adequacy determination, appropriate contractual or organizational safeguards, another safeguard recognized by law, a statutory exception, or explicit informed consent where that consent is valid.

You may contact us for available information about the safeguard applicable to a transfer of your data. BlueEV does not represent that all data is stored only in Georgia.

BlueEV keeps personal data only while it remains necessary for the purpose described below, and longer where law, an unresolved operation, security, accounting, fraud prevention, a complaint, dispute, or legal claim requires it. Necessity is assessed using the data's sensitivity, the feature lifecycle, operational risk, and applicable duties.

• Account, profile, session, device, preference, and synchronization data is kept while the account or relevant device relationship is active and afterward as needed to complete deletion, secure the Service, and meet legal or claims duties.
• Provider credentials and tokens are kept while the provider account is linked and they are needed for requested actions. They are deleted or disabled after unlinking or BlueEV account deletion, except for limited security evidence or mandatory retention.
• Precise navigation location and route caches are kept only while needed for routing, active navigation, synchronization offered to you, debugging, security, or a related request.
• Reports, feedback, photos, and support records are kept through review or resolution and afterward while needed for public approved station content, quality history, abuse prevention, rights complaints, disputes, or law.
• Provider action, payment, refund, consent, and audit records are kept while needed for completion, reconciliation, accounting, fraud prevention, complaints, disputes, and legal claims.
• Security, App Attest, IP or user-agent, abuse, and observability records are kept according to the relevant risk, incident, investigation, and defense need, with access and duration limited to what remains necessary.
• User notification history remains retained and queryable for at least one year, and longer only when another stated purpose or legal duty requires it.
• Approved station photos are kept while used as public station content and afterward only as needed for moderation, complaints, rights, security, or legal evidence.
• Isolated backups remain until overwritten through the normal backup cycle. A restored backup remains subject to the deletion and retention rules in this Policy.

You may request BlueEV account deletion through the available in-app flow. BlueEV revokes sessions and deletes account-linked personal data that is no longer required. An active charging session or reservation may need to be completed, stopped, reconciled, or safely transferred to the responsible provider before deletion can finish.

BlueEV may detach or de-identify operational records so they no longer identify you and may retain limited records required for incomplete transactions, security, fraud prevention, accounting, provider reconciliation, disputes, legal claims, or other law. Account deletion does not delete data independently controlled by Apple, a charging provider, a payment service, or a station operator; contact that party for its deletion process.

BlueEV uses proportionate administrative, technical, and organizational measures designed to protect personal data, including access controls and protection of provider credentials and tokens in storage and transit where appropriate. Access is limited according to operational need. No transmission, device, provider integration, or storage method is completely secure, so BlueEV cannot guarantee absolute security.

Protect your devices, Apple account, provider accounts, passcodes, and authentication messages. Contact privacy@blueev.ldev.cloud promptly if you suspect unauthorized BlueEV or provider-account activity.

Subject to the conditions and exceptions in applicable law, you may ask BlueEV to provide information about processing and access or a copy of your data; correct, update, or complete inaccurate data; erase data or terminate processing; block or restrict processing; provide portable data in a structured, commonly used, machine-readable format where portability applies; explain or review applicable processing; and honor an objection where the law grants that right.

Where processing relies on consent, you may withdraw consent at any time without affecting earlier lawful processing. You can also control location, notification, and other device permissions in iOS Settings; unlink a provider account; revoke a linked BlueEV device; or delete your BlueEV account using available controls.

Send a request to privacy@blueev.ldev.cloud or the address above. We may need to verify your identity and clarify the data concerned. We respond within the periods and subject to the restrictions provided by applicable law. You may appeal to the State Audit Office of Georgia or a competent court.

BlueEV imposes no separate minimum age and does not perform age verification. A minor must nevertheless have the authorization required by applicable law. Where processing of a minor's data relies on consent and law requires a parent or legal representative to give or authorize that consent, BlueEV will require that authorization and will consider the child's best interests.

Apple, charging providers, payment services, station operators, and driving or payment law may impose independent age or capacity requirements. A parent or legal representative who believes a minor's data was processed improperly should contact privacy@blueev.ldev.cloud.

BlueEV may automatically rank, filter, secure, rate-limit, or reconcile service activity. Under the specified Service, BlueEV does not make a decision based solely on automated personal-data processing that produces legal effects or similarly significant effects for you. Independent providers may use their own automated systems under their notices.

BlueEV may publish a revised Policy when the Service, processing, recipients, or law changes. A revised edition applies prospectively from its stated effective date and does not make previously unlawful processing lawful or change the rules governing past conduct. Where mandatory law requires direct notice, a delay, or renewed consent for a material change or new purpose, BlueEV will provide it. Prior editions may be retained to establish which Policy applied at a particular time.

For privacy questions, requests, complaints, or security reports, contact privacy@blueev.ldev.cloud or write to BlueEV, 33 Ushangi Chkheidze Street, Tbilisi, Georgia. Questions about an independent provider's account, charging, payment, refund, or station processing should also be directed to that provider. You retain the right to complain to the State Audit Office of Georgia or bring a claim before a competent court.

The BlueEV Terms of Use apply to your use of the Service.