NEXUS COLLECTIVE INC · WORLDVIEW

Privacy policy

Updated November 5, 2026. Contact: contact@nexuscollectiveus.com.

Information used to provide WorldView

We process your enrolled email or verified phone number, account identifier, shared-space membership and role to authenticate you and control access. Shared-space records include activity dates and places, notes, messages, sharing choices, saved places, assignments, and operator-entered flight details and updates. A trip is not required to use a shared space. Authorized clients may see assigned personnel names and photos, and vehicle type, color and plate. Assigned participants may also see the meeting point, handoff instructions and duties explicitly saved for their activity. Private profile notes and credentials are excluded from those recognition views; historical client summaries also exclude private VINs. Information entered in notes or messages is stored with those records; avoid entering sensitive information that the invited participants do not need.

Optional group photos and avatars

You can choose your own photo, upload an avatar image, or select a built-in symbol for a group. Uploaded images are cropped and re-encoded on your device as small round icons; the original file and its metadata are not uploaded. Active invited group members can see the saved icon even when location sharing is off. Only you can replace it or choose initials to remove the stored image. These images are separate from identity-vault portraits and operational personnel profiles.

Optional identity records

With the traveler’s permission, the dedicated identity vault can store a current portrait and images of a passport photo page for international travel, or a driver’s license for domestic travel. These records are separate from shared trip profiles and messages. Only the designated account owner and explicitly designated security managers may use the vault; an ordinary staff assignment does not grant access. File access and changes are logged. Uploaded images are resized for storage. A manual review status records a person’s review; WorldView does not authenticate government documents, perform biometric face matching, or establish proof of life from a stored image.

Optional location and battery sharing

After you start sharing and approve the iPhone permission prompt, WorldView sends your device identifier, observed location, accuracy, observation time, and available battery and charging state to the private service. Precise sharing may include observed GPS speed. Approximate sharing rounds the location to a broader area and omits speed. Sharing is limited to the spaces you approve and their active invited members. You can stop one space or all spaces from Safety & sharing. Stopping collection on the phone happens before WorldView asks the server to confirm withdrawal; if the phone is offline, server confirmation may take longer. Shared location displays are removed when withdrawal is confirmed, and old observations are labelled as last known rather than live.

Saved-place arrival and departure rules, battery alerts, expected-arrival checks, movement summaries, and traffic-aware arrival watches use approved sharing. Each arrival watch lasts at most 24 hours and stops when sharing is withdrawn, access ends, the destination changes, or arrival is confirmed. A route estimate is not proof that someone arrived. Sharing can continue in the background for the period you approve, subject to iOS permission and connectivity. If permission was previously denied or restricted, iOS may require action in its Settings; WorldView cannot bypass that decision.

Notifications and requests for help

If you approve notifications in a push-enabled build, WorldView registers a private Apple device token linked to your account. Shared alerts, group-message notices and operator updates can be queued for those devices. Receiving group messages does not require sharing your own location. Lock-screen notifications use generic text; opening WorldView retrieves details under your current shared-space permissions. Provider acceptance is not proof that you saw an alert. An SOS records a request for Nexus operators to acknowledge; it does not itself confirm a staffed response or contact public emergency services. Automatic crash monitoring is disabled unless a supported, entitled build and separate user permission are in place.

Optional Apple item-sharing links

If you approve sharing an Apple Find My item link, WorldView stores its label and URL for the active invited members of the selected group. Apple’s page may show item-location and owner information and may require Apple sign-in. Apple controls access and expiry; links can stop working within seven days, when the item is found, or when its owner stops sharing. WorldView does not fetch or import item positions into its map. Removing a link from WorldView clears its stored URL and hides it from the group, but does not revoke Apple sharing or copies already received. Stop sharing separately in Find My when needed.

Service providers and external services

Supabase provides authentication and the private database; Vercel hosts the web service and API. These services receive information needed to process and secure requests, including network/request metadata. Apple MapKit provides native maps and venue searches. Google Maps provides the shared web map and traffic layer, receiving the map area and normal request metadata. If you start an arrival watch in an environment with traffic routing activated, its approved precise origin and saved destination coordinates are sent to Google Routes for driving estimates; WorldView does not send participant names or account identifiers in that routing request. Opening Google Street View shares the selected planned place coordinate with Google. Apple delivers notifications when push delivery is activated. Opening WhatsApp supplies the selected contact number to WhatsApp; you choose what to send there. WorldView does not import that conversation or automatically send the message. External services apply their own privacy policies.

Access and security

Protected operations verify identity, membership, roles and permission expiry. Native sign-in credentials are stored in iOS Keychain; selected space identifiers, approved sharing-session metadata and an app-generated device identifier are stored in local preferences. These preferences do not contain the sign-in secret. Requests use HTTPS. Trip messaging and identity-vault records are not end-to-end encrypted. Infrastructure administrators and service providers remain part of the service’s security trust boundary. The reviewed WorldView native app contains no advertising or analytics SDK and does not implement cross-app advertising tracking.

Retention and deletion

Identity scans and portraits in the dedicated vault are retained until the traveler requests their deletion; they do not automatically expire at trip end. A verified request can be made through WorldView support, and the account owner can process the requested deletion in the vault. Deleting the linked traveler account also removes the linked vault record and images. Audit metadata remains without the deleted images. Provider backups and logs follow the separate retention described below; deletion from the active vault does not promise immediate erasure from backups.

Account and trip records remain in the active service until removed. Trip expiry restricts access and is not automatic deletion of all records. The legacy pilot position table holds the latest submitted position. Enhance also retains location observations for up to 30 days for movement history and summaries; expired observations are removed during telemetry processing and scheduled cleanup. Other members can access history only while the person is actively sharing in that space; retained observations may still be available to that person after sharing stops. Shared alert history and operator-entered records remain until removed or the linked account or owning workspace is deleted. Stopping sharing is not the same as deleting retained history or previously shared messages. Infrastructure logs and any provider backups are separate from active application records and follow provider retention and rotation; account deletion does not promise immediate removal from those systems.

You can initiate immediate deletion from the updated iPhone app’s Help & privacy requests panel or the account deletion page. Fresh verification and explicit confirmation are required. Regular accounts verify an email code; the isolated Apple review account re-enters its password. Successful deletion removes your authentication account, linked memberships, messages, sharing records, active location and linked itinerary records. It also removes independent trips you own and their shared contents for all participants. The operation must succeed as a transaction before WorldView confirms deletion. Information other people supplied separately, including unlinked contact or personnel records, may require a separate request so we can identify it.

Your choices and questions

Signing out stops WorldView collection on that iPhone and disables its active notification registration, but does not erase your account. Signing out on one phone does not stop a separately approved session on another phone. You can request access, correction or help identifying separately supplied information at contact@nexuscollectiveus.com from your enrolled email. Do not email passports, driver’s licenses, passwords, verification codes, invitation codes or live location. We may need to verify your identity. Contact local emergency services directly for emergencies.

Main map & board · WorldView support