Privacy policy · Nevar Bridge

Who we are and what this covers

Effective October 25, 2026. Adhereii LLC publishes Nevar Bridge. This policy describes the current iPhone app and nevarbridge.com. Contact us at admin@adhereii.com with privacy questions.

Nevar Bridge is a location publisher. You configure compatible receivers and decide when to share. There is no required Nevar Bridge account, built-in hosted location service, advertising SDK or analytics SDK in the current app.

What the app processes and sends

With your permission and sharing enabled, the app processes location on your phone and sends reports to each enabled destination you configure. A report can contain:

Your chosen sharing name, including an optional connection-specific name and color.
Latitude, longitude, horizontal accuracy and measurement timestamp.
Available speed, GPS travel direction and true-north compass heading.
A random installation UUID and a random sample UUID used for authentication, acknowledgments and duplicate handling.

Your sharing name is not a verified identity. The installation identifier is not an advertising identifier, but it is stable for the installation and is used across configured destinations. Changing a name does not prevent receivers from correlating reports. A receiver also sees network information such as the connecting IP address.

Connection testing sends the installation identifier and authentication token, but no coordinates. A stop request sends the identifier and token. Receiver operators control their own authentication and processing.

Where reports go

The app sends reports directly over HTTPS to the primary or explicitly configured alternate address for each enabled destination. There is no built-in route through Adhereii LLC’s location backend. We do not automatically receive your location reports merely because you use the app.

If you configure a receiver operated by us, your organization or another party, that receiver’s operator can access the data it receives and determines its uses, retention and sharing. Obtain the operator’s privacy information before connecting. HTTPS protects transport to the receiver; the receiver can read accepted reports. It is not a claim of end-to-end encryption beyond that server.

Storage on your phone

Server addresses, connection labels, display settings, the installation ID and your sharing preference are stored on the phone. Bearer tokens are held in the device-only iOS Keychain, available after the first unlock following restart. Tokens are not placed in location queue records or URL query strings.

Each destination has a durable local delivery queue capped at seven days and 20,000 pending deliveries. Explicitly acknowledged records are removed from that queue; older records may also be removed at the retention or capacity limit, with a visible removal count. Pending queue files are excluded from device backups and use iOS file protection that permits an active locked-phone session after first unlock. Ordinary app settings follow iOS storage behavior.

Protection depends on your device’s security. Reinstalling or losing the phone can lose queued data; iOS may retain Keychain items across an uninstall. Ask your receiver operator to revoke a token when replacing or retiring a device.

Your choices and deletion

Location collection requires iOS permission and active sharing. You can change location permission or precision in iPhone Settings. Previously enabled sharing may resume when the app is reopened; use Stop sharing to pause collection and uploads.

You can disable a destination, clear its queued reports or remove it. Removal clears that destination’s local queue and token. These actions do not remotely delete reports already received. Contact each receiver operator for server-side access, correction, deletion or revocation. An offline stop notice cannot immediately update a remote server’s status.

Optional review receiver

We operate a separate receiver for App Review and controlled testing. It is used only when you explicitly configure its address and a supplied review credential; the app does not select it automatically. It receives the same report fields described above.

Review reports expire after 24 hours from receipt, with cleanup running every five minutes. Capacity limits may remove reports sooner. Live status expires after five minutes without a fresh fix; Stop sharing clears live status when its stop request reaches the receiver, but does not immediately erase previously accepted history. Test-only installation identifiers and rate-limit counters are also expired. The receiver does not provide a public report viewer or forward reports to our other services.

Routine access logging is disabled for this API; operational errors may still produce security records. Review data is kept out of the website’s source/configuration backups. See the review receiver notice for setup and contact information.

Website and support information

This website does not request your location, run analytics or advertising scripts, or set application cookies or browser tracking identifiers. It serves product information and documentation. Our hosting infrastructure processes requests needed to serve those pages.

Web server access and error logs can include IP addresses, request paths, timestamps, status codes and browser information. We use them for service operation, security and troubleshooting. Routine logs are configured for daily rotation with 14 retained rotations; low activity or an investigation may result in longer retention. Hosting providers may also process network and security records under their own terms.

If you email support, we receive the information you send, including your email address and message contents. We use it to respond and troubleshoot, and may retain the correspondence for follow-up or recordkeeping. Do not send bearer tokens, pairing files or location history unless a specific need has been discussed; remove sensitive details from screenshots.

We do not use the current app or website to sell location data or for targeted advertising. Website hosting and email service providers process information needed to operate those services. We may disclose records we hold when legally required, to address abuse or protect service security. A receiver you choose has its own independent practices.

App Store or TestFlight distribution can involve Apple’s diagnostics and feedback services under Apple’s settings and terms. Information you deliberately submit to us as feedback is handled as support information. The current app has no separate third-party crash-reporting SDK.

Policy updates and contact

We will update this page and its effective date when these practices change. A future hosted service, new SDK or other material data-processing change will require updated disclosures. This policy does not promise future features.

For questions about this app, the website, or personal information you supplied to us, contact Adhereii LLC at admin@adhereii.com. Requests about reports stored by another receiver should go to that receiver’s operator.