Privacy // Data Protocols

System Release v7.4.0 | Imperial Standard Compliance

1. Data Ingestion Protocol

To establish a secure uplink, Nav-Fi³ collects the following personnel markers:

Email Address: Used for sector identification and encrypted session recovery.
OAuth Identifiers (Google/Discord): Unique signal keys used strictly for authentication handshakes.
In-System Assets: Campaign data, vessel manifests, and financial ledgers created by the pilot.

2. Operational Clearance

Your telemetry is used solely to maintain your **Tactical Operating System** state. Nav-Fi³ does not engage in data-shadowing or illicit signals intelligence. We do not sell coordinates or pilot identities to megacorporations or orbital authorities.

3. Data Persistence & Purge

Digital trails are stored on **Imperial Standard Servers**. Pilots retain full command over their archives:

Access Request: You can view your stored telemetry via the profile HUD.
Total Eject (Deletion): You may request a complete data purge (deletion of account and all associated assets) by contacting the Support Terminal.

4. Session Beacons (Cookies)

The system deploys **Temporary Session Beacons** (Cookies) solely to maintain your bridge connection. These beacons are ephemeral and essential for encrypted uplink stability. No third-party tracking beams are allowed.

[ EXIT_PROTOCOL // RETURN_TO_BRIDGE ]

Beacon // Dock Ready