EV Plug Finder
Trip Business Account

Privacy

Privacy Policy

Updated: November 3, 2026

EV Plug Finder is operated by Big Data Analytica LLC, doing business as EV Plug Finder, located in Fairfax, Virginia (referred to as “we,” “us” or “our”). We determine how information is used to operate this service. Contact privacy@evplugfinder.com for privacy questions.

This policy applies to the EV Plug Finder website, the native EV Plug Finder app for iPhone and iPad, and the EV Plug Finder Android app. It explains how EV Plug Finder handles information when you find chargers, plan trips, contribute reports and share links. You can search for chargers, preview trips and share the app or a station without an account. Saving trips, ratings and reviews require sign-in. Charger status and charging price can also be reported as a guest at supported stations.

Location and searches

Charger search requests your location when you choose “Use My Location”; previously granted permission can also be used to bias address suggestions. Trip Planner may request location automatically when its start field is empty, or when you tap its location control. Your browser asks for permission unless a permission choice already exists. Coordinates are used to find nearby chargers and can help bias address suggestions when permission is already granted. You can search by city, postal code or address instead, and change location permission in your browser or device settings.

Search text, selected places and coordinates are sent to the services needed to resolve locations, find stations and amenities, or calculate a route. These requests can reveal where you are searching or planning to travel. A station location in a report or shared link identifies the charging location; it is not proof of your physical presence there.

In the iOS app, location is requested only after you use a current-location control. The app requests when-in-use access and a one-time location fix; it does not request background location. Coordinates are sent to EV Plug Finder station-search functions and relevant map or routing services to return nearby chargers or calculate a requested route. Apple may process searches, route endpoints and directions when the app uses MapKit, local search, routing or opens Apple Maps. The Android app is a Trusted Web Activity that displays the website through a supported browser; location permission and website data are therefore managed by Android and that browser.

Accounts, saved chargers and trips

Supabase provides authentication and account-data storage. Depending on your sign-in method, account information may include your email address, display name and profile image. We also record an explicit 18-or-older declaration and the accepted Terms version, server confirmation time and interface used when you save your Terms confirmation. This declaration is not independent age verification. We store account preferences, such as your selected EV, and chargers you save.

When you save a trip, stored information includes its name, start and destination labels and coordinates, selected charging stops, vehicle selection, and creation and expiry information. Saved trips are associated with your account and are not published through the app’s station-sharing or general sharing buttons. Trip-planning drafts can also remain in browser session storage.

App privacy summary

For App Store privacy disclosures, information handled by EV Plug Finder can include the categories below. Whether information is linked to an account depends on the feature and whether you are signed in.

EV Plug Finder does not use these categories to track you across apps or websites owned by other companies, and does not sell them. Optional Google Analytics is configured without Google Signals or advertising-personalization signals. This summary describes our current practices and does not replace the more detailed explanations below.

Native-app device data and permissions

The iOS app stores app settings, selected filters, saved-charger copies, hidden-review choices, account display information and authentication-session values on the device. If you choose “Use Face ID to unlock,” iOS performs the biometric check and EV Plug Finder does not receive your face image or biometric template. A protected copy of the session credentials is stored in the iOS Keychain with access limited to the device and current biometric enrollment. Turning this option off deletes that protected Keychain item. Some session and preference values also use the app’s local preferences storage; signing out clears the active account session values used by the app.

The iOS app can ask for notification permission after a saved trip is available. If allowed, it schedules a local reminder on the device shortly before that trip expires. EV Plug Finder does not use that reminder feature to upload your notification history or a push-notification token. You can disable notifications in iOS Settings.

For supported guest-report security, the iOS app may use Apple App Attest. Apple provides an app-instance key and assertion so our server can check that a request came from an authentic instance of the app and reduce automated abuse. We store the App Attest key identifier on the device and may send that identifier, a one-time challenge and cryptographic assertion to our server. App Attest does not give us your Apple ID or biometric information.

The iOS share sheet and Android/browser sharing interface are controlled by the operating system or browser. EV Plug Finder supplies the public link and descriptive text to that interface but does not receive your contact list or the identity of the recipient. Opening directions passes the selected destination or ordered route locations to Apple Maps, Google Maps or another mapping app you choose.

Audience and countries

Our current business focus is the United States. Charger search also supports selected European countries, including Germany, the Netherlands, France, Sweden, Denmark, Austria, Belgium, Spain, Portugal and Norway. Trip Planner currently supports the United States. Accounts and contributions are for users aged 18 or older. If you believe a minor has provided account information, contact our privacy address so we can review and handle the account.

Community contributions and rewards

We store submitted ratings, reviews, availability and status reports, charging prices, optional price notes, actual session costs and optional fee or energy information. Contributions are associated with your account and station, together with submission information. For ratings, reviews and reports, we store whether the station was opened through a QR-tagged link, an ordinary shared link, or the site's search. This describes the link used, not a verified physical scan, and is stored even if you decline optional analytics. We also store contribution totals, points history, earned badges, display choices and onboarding state to operate these features and apply reward limits.

Guest status and price reports are stored separately from account contributions. We keep the station, reported status or price, entry source, submission time, review state and a server-derived abuse-control identifier. The identifier helps limit repeated reports and is not displayed publicly. A one-day browser cookie supports these limits; it is not used for advertising. We do not request the guest's GPS position for reporting. Status reports at implausibly distant stations in a short period may be held from public display. Guest prices require review before public display. Guest reports earn no points or badges. A QR-tagged link does not verify a physical scan or presence at the charger.

Public station information can include ratings, reviews, report summaries, charging prices, price notes and session-cost information. Reviews can display a first name derived from your profile and your selected comment badge. Badge display choices can accompany community content. Your email address is not displayed as a review author. Do not include private contact details or other sensitive information in public contributions.

Signed-in users can mark another driver's written review as helpful. We store which account cast each helpful vote and when it was cast, whether its author has viewed the notification, and the review it concerns. Review authors can see helpful counts and in-app notifications and can open the related review, including an older review that is no longer in the recent list. Other users can see the helpful count and whether they themselves voted; voter identities are not shown publicly.

Review reporting, hiding, blocking and moderation

You can flag or report a written review from its review controls. When you submit a report, we store the review reference, your account reference, selected reason, optional details, submission time and resolution status in a private moderation queue. The report itself is not shown publicly. Authorized moderators review the queue, investigate the content and record the outcome. Depending on the result, they can dismiss the report, hide the review, remove content or restrict the contributor’s ability to post reviews. Automated checks also reject reviews containing detected abusive language, threats, contact details or links; these checks are not perfect. Contact Contact@EVPlugFinder.com to report a concern or appeal a moderation decision.

The iOS app also lets you hide an individual review on that device. The hidden-review identifier is saved in the app’s local preferences. Hiding is personal to that app installation: it does not report the review, remove it for other users or cause a moderation decision. You can separately use the report control when you want our moderation team to review the content.

Blocking a contributor stores a relationship between your account and that contributor so their reviews are hidden for your signed-in account, including on other devices. You can unblock contributors in Account settings. Blocking does not remove their contributions for everyone or suppress anonymous charger-status and price summaries. Block relationships are removed when either account is deleted. Abuse reports are removed when the reporting account or associated review is deleted; review restrictions and linked moderation records are removed with the associated account or review. Backups and support emails follow their separate retention settings.

Services that process requests

These providers receive information needed to serve requests and may process technical information, such as IP addresses, browser details and request logs, under their own policies. We require providers that process personal information for us to protect it consistently with this policy, their contractual obligations and applicable law. External map, sponsor and sharing destinations that you choose to open operate under their own privacy practices.

Analytics and cookies

Google Analytics is optional and applies to website content, including that content when displayed in the Android Trusted Web Activity or an in-app web view. The native SwiftUI screens do not load the Google Analytics tag. We load the tag only after you choose “Allow analytics” for the applicable browser or web view. You can decline without losing charger search, trip planning or account features, and change your choice through “Analytics preferences” in the footer or Account settings. The choice lasts up to 180 days for that browser or web-view data store and website origin; clearing website data can reset it. We do not treat a refusal as permission. Choosing analytics is separate from Terms agreement and location permission. Google Analytics uses cookies and similar identifiers and processes browser/device information and activity on the site. See how Google uses information from sites that use its services and Google Analytics data safeguards.

Custom events cover feature clicks and authentication/contribution funnels as well as searches and filters, station views, directions, saved chargers, trip previews, first-trip onboarding, successful reports, sponsored placements and sharing. Parameters can include a country code or market region (typed city/address labels are excluded), selected vehicle and filters, station ID, station name, network, entry source, route length, stop count and points awarded. QR-tagged station links allow us to distinguish those arrivals from ordinary shared links; they do not establish a verified physical scan or location.

Our custom events do not include email addresses, account IDs, report text or recipient contact details. Share clicks, copy actions and native share-menu outcomes do not confirm that another person received or opened a message. We do not intentionally send full typed street addresses or precise device GPS coordinates in custom analytics events. Page-view configuration omits query strings and URL fragments from the page location sent to Analytics.

Declining or withdrawing analytics disables further site analytics measurement and clears accessible Google Analytics cookies for this site. This does not delete information already received by Google. We disable Google Signals and advertising-personalization signals in the site configuration; provider-side settings and any automatic measurement also affect processing. You can manage cookies and site data through your browser. Google also offers an Analytics opt-out browser add-on for supported browsers. Browser controls may affect sign-in and remembered settings; deleting cookies alone does not necessarily stop future analytics requests.

While analytics is allowed, a short-lived browser record connects a feature click to an authentication attempt and a subsequent action. It contains the action, page surface, method and time, not email, account ID, station selection or report text. The context is considered valid for one hour; validity expiry does not itself erase every browser record. Authentication events are usage measurements, not proof of registration or legal acceptance.

Sharing links

“Share EV Plug Finder” shares a public website link with campaign parameters. “Share station” shares the station’s public link and, when supported, its name and address through your device’s share menu. Neither action includes your saved trip or account credentials. Copy fallback writes the link to your clipboard, or lets you copy it manually if clipboard access is blocked. Your chosen sharing app handles recipients and delivery; EV Plug Finder does not request your contact list.

Browser storage and caching

Browser storage is used for sign-in sessions, vehicle and filter preferences, cached station/location/amenity lookups, trip drafts and a flag that limits the post-contribution sharing invitation. Cached lookups and trip drafts may reflect searched areas or planned travel. The invitation flag records only that it was shown, not your account identity. Clearing browser data can reset these preferences and allow the invitation to appear again.

The Android Trusted Web Activity uses the selected Android browser’s website storage. Its “manage space“ control opens the app’s website-data management destination. Removing the Android app does not necessarily erase website data retained separately by the browser; use the browser’s site-data controls when you also want to clear that data. Removing the iOS app normally removes its app-container preferences and locally saved charger copies, while Keychain items can be retained by iOS unless deleted through the app’s controls or otherwise removed by the system. Deleting an app or clearing local data does not delete server-side account records.

Route requests include trip coordinates and may pass through hosting/CDN caches and request logs. Address/route lookup cache keys can include search text or coordinates; a cache validity limit is not a guarantee of immediate physical erasure.

A service worker caches the site’s own pages and static assets for faster loading and offline fallback. It does not cache third-party map tiles or API traffic through that service-worker cache; some lookup results are cached separately by the app in browser storage. Previously loaded information can be out of date while offline.

Sponsored placements

Clearly labeled sponsored nearby-business information may appear in station results and details. We record placement impressions and clicks, including aggregate counters in Supabase and, when optional website analytics is allowed, analytics events. The sponsorship counter records do not contain account identities, IP addresses or precise device coordinates; this does not mean that hosting or analytics providers process no technical request data. Opening a sponsored link takes you to the business’s website.

Purposes, legal bases and international processing

We use account and saved-item information to provide requested account features and administer the Terms. We use community contributions to provide public station information and operate rewards. We use technical records and moderation information for service reliability, security and preventing misuse, and correspondence to answer questions and handle requests. Where the GDPR applies, the legal bases are performance of the account contract for requested account features, consent for optional analytics, legitimate interests in operating a reliable service and handling support/moderation (subject to your rights), and legal obligations where required. Browser location permission is a technical permission; it does not authorize unrelated uses of location.

Providers may process information outside your country, including in the United States. Their processing locations and contracts affect any applicable transfer safeguards. Contact us for information about the safeguards applicable to your data; naming a provider does not mean every request stays in the same country. We do not promise that provider copies or logs are stored only in Virginia.

Retention and deletion

Signed-in availability and guest status reports are used for recent status summaries and routinely deleted after seven days. Signed-in price reports are used in public price summaries for up to 30 days after their last update; current rows are deleted after 45 days without an update, and daily price snapshots are deleted after 12 months. Held guest price reports are deleted after seven days. Accepted guest prices may appear as separately labelled public observations for up to seven days after submission. Accepted and rejected guest price records are deleted 45 days after submission; their server-derived abuse-control identifier is cleared after seven days. Daily cleanup can run almost a day after a retention threshold. Public session-cost display uses recent observations within 30 days, while the underlying account contribution history remains until account deletion or another applicable removal. Saved trips expire 60 days after creation; editing does not reset the expiry. Expired trips are hidden from account access and removed by scheduled cleanup. Display expiry and physical cleanup are different.

Reviews, favorites, account preferences, contribution history, points and badges are retained while the account/content remains, unless removed earlier. Self-service deletion removes the account and linked active database records, including linked price history and moderation records. Legacy records already unlinked from an account may remain and may not be identifiable for deletion. Clearing browser data does not delete server records. On successful deletion, the current browser clears account-related app state; other devices, old tabs or previously saved copies may retain local information.

Routine database cleanup depends on scheduled jobs. Providers can retain technical logs and previous backups under their configured retention periods; removing active account data does not immediately erase those copies. Correspondence and privacy-request records are retained as reasonably necessary to respond, document the request, prevent fraud and meet legal obligations.

You can delete your own review from its station page. This removes both its rating and written comment from the active review record, along with helpful votes and in-app notifications linked to that review. Your contribution totals, points, and badge records may still reflect the original contribution until account deletion or another applicable removal. A person who voted can withdraw their helpful vote, which removes that vote and its related notification.

Your choices and requests

EV Plug Finder does not sell personal information. Public contributions are visible as described above. You can delete your own rating and comment from its station page, withdraw a helpful vote, hide an individual review locally in the iOS app, report a review for moderation, block or unblock a contributor, remove saved chargers and saved trips using the available controls, change badge display choices, revoke location permission and clear browser storage. Clearing local storage does not delete information saved to your account.

For self-service account deletion, use Account settings, verify your sign-in and confirm deletion. If you cannot use that control, or for other privacy questions or account-data deletion requests, contact privacy@evplugfinder.com. Please do not send passwords or sign-in codes. Removing a report from a current station summary does not by itself mean that all related contribution history, reward records or provider backups have been deleted.

Depending on applicable law, you may have rights to access, correct, delete or obtain a copy of your information, restrict processing, object to processing based on legitimate interests, withdraw consent and complain to your data-protection authority. Contact our privacy address to exercise rights or challenge a response; we may need to verify your identity without requesting your password or sign-in code. Rights and exceptions depend on applicable law. Withdrawing consent does not affect earlier lawful processing, and using an account does not waive mandatory privacy rights.

Changes

We may update this page as features and data practices change. The date above identifies this version. See also our Terms of Use and About page.