Privacy Policy

1. Scope & commitments

This policy covers the SrvSurvey-XP desktop application maintained by Fenris159, this SrvSurvey-XP website, and the project’s activity-counting endpoint. The original upstream SrvSurvey, third-party services and other applications have their own policies.

Data is used to provide the features described in the application and this policy. Google Drive backup contents are not forwarded to the project’s telemetry endpoint or to unrelated community integrations.

2. Data on your computer

SrvSurvey-XP reads Elite Dangerous journals and auxiliary files such as Status, Cargo, ShipLocker, NavRoute and Market to build its local state. These can contain commander names and Frontier IDs, locations, ship and carrier information, cargo, missions, discoveries, timestamps and other gameplay activity. Supported chat commands are read to operate companion features; raw chat is not part of the daily activity report.

The app stores settings, commander profiles, surveys, maps, routes, bookmarks, mining history, cached reference data, screenshots you attach or process, and diagnostic logs in its local data folders. Some local records, notes, file paths and diagnostic exports can identify a commander or computer.

Optional screen capture for FSS tuning, first-footfall inference and rig detection processes shared pixels locally. The app does not upload the captured screen as part of detection. On Wayland, the desktop’s screen-sharing picker and permission handling are controlled by the compositor and portal.

Diagnostic journal replays remain local until you explicitly export and share them. Redacted exports reduce identifying information but can still contain gameplay details. Review screenshots, logs and exported files before posting them publicly.

3. Third-party APIs & community sharing

Public lookups may send search terms, system names or addresses, coordinates, route criteria, commodity filters and similar request data to services such as Canonn, Spansh, EDSM, Inara, Raven Colonial and application reference hosts. These requests do not require every optional publication setting to be enabled. Public Community Goal lookups use an application identifier without your personal Inara key or commander identity.

Account linking and publication are separate from these reference lookups. Their controls and credentials determine which services receive your gameplay data:

The project does not automatically enable all publishers when you link one service. Disable equivalent sharing in other companion applications when necessary to avoid duplicate submissions. A service’s own policy governs its storage, visibility, retention and redistribution; already-published community data may not be removable through SrvSurvey-XP.

More implementation details are available in the repository’s network privacy documentation. Third-party policies and APIs may change independently of the app.

4. Google Drive backup & sync

Authorization & access

Google Drive is optional. Select Link Google Drive in Settings → Data & migration to authorize the application in your browser. SrvSurvey-XP requests only https://www.googleapis.com/auth/drive.appdata, allowing it to manage its own private application-data files. It does not request access to your ordinary Drive documents, Gmail, contacts or other Google account content. The app does not receive your Google password.

Backups are stored in Google Drive’s hidden appDataFolder. They do not appear as ordinary files in My Drive, cannot be shared through the normal Drive sharing interface, and use your Google storage. See Google’s app-data documentation.

What is uploaded & why

Backups contain supported preferences and saved work: themes, colors, overlay preferences, shortcuts, workspace and search choices, routes, bookmarks, mining history, surveys, exploration records and other supported profile data. They can include user-entered notes, commander-related identifiers, game locations and timestamps. Machine sections include device identity / name, operating system and supported hardware-dependent settings, such as overlay placement and capture configuration, so those settings restore only on the appropriate machine.

Authentication credentials, API keys, raw journal files, screenshot files and queued API reports are excluded from profile backups. Backup and restore are not a complete disk backup; exported files, attachments and unsupported data may need a separate copy.

When automatic sync is enabled, the app checks cloud changes on startup and saves on orderly shutdown; a closing app can finish its backup in the background. Manual backup, sync, download and restore actions operate when you request them. Downloaded cloud data is used to restore or merge your local SrvSurvey-XP profile, with conflict choices when required.

Use, sharing & removal

Google receives the backup files to provide the storage you requested. The app does not send their contents to the maintainer’s server, advertisers or other community APIs. They are not used to train AI models, build advertising profiles or sell information. Maintainers do not obtain access to your Drive merely because the OAuth project belongs to the maintainer.

SrvSurvey-XP’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Access is used for the backup, restore and sync features you authorize.

Use the cloud-history controls to download or permanently delete an individual backup or clear the listed SrvSurvey-XP cloud backups. Disconnect removes local Google authorization; it does not delete existing cloud files. To stop future uploads, disable automatic sync or disconnect on each linked computer. You may also revoke the app’s authorization through your Google Account connections. Revocation alone does not promise deletion of existing backups; use the app’s deletion controls or Google Drive’s app-management controls.

5. Daily installation activity

Current releases automatically attempt a check-in once per UTC day on the first application session. This is separate from the optional community-publication controls and is not tied to a commander account.

• Random installation ID: generated locally and reused by instances sharing that installation’s data directory. It is not a commander name, Frontier ID or hardware fingerprint.
• Application version and operating-system label: used to understand which releases and platforms are active.
• First-seen and last-seen times: recorded by the server to calculate seven-day and thirty-day activity.

The check-in goes to the project’s Cloudflare Worker at srvsurvey-telemetry.fenrisnihilus.workers.dev. The configured user record stores these fields, not your journals, chat, game location, email, Google account, Frontier account or API credentials. As with any network request, Cloudflare can process connection metadata such as the source IP address under its own service policies.

A persistent ID makes this reporting pseudonymous rather than fully anonymous. Public endpoints and badges publish aggregate activity, operating-system and version totals, not individual installation IDs. Counts represent installations; a person using multiple independent data folders or computers may be counted more than once.

Current releases do not offer an in-app switch for this check-in. Blocking that endpoint at the network level prevents reporting and does not stop local companion features. Deleting the local activity-state file generates a new ID on the next run and does not delete the previous server record.

6. Website, downloads & network providers

This SrvSurvey-XP website is a static GitHub Pages site. It has no account login, advertising scripts, analytics tracker or project-set cookies. Its screenshot viewer and navigation run in your browser. Images, styles and scripts for this page are served from this site; browsing it does not send an installation activity check-in.

GitHub receives normal hosting request information when you visit, download releases or use the issue tracker. See GitHub’s Privacy Statement. Links to external websites send you to services with their own policies. Community services and Cloudflare likewise receive normal network metadata for requests directed to them; see Cloudflare’s Privacy Policy.

The desktop app may contact GitHub and configured reference hosts to check or retrieve releases and catalogs. These requests are separate from publishing gameplay data.

7. Storage & security

Supported credentials and authorization tokens are stored on your computer, not in the project’s activity database. Protection depends on the integration and platform. Frontier tokens use operating-system credential protection; Google authorization uses Windows Data Protection on Windows and a user-only authorization file on Linux. Personal API keys are stored in local commander settings. Protect your computer, backups and local profile files accordingly.

Network integrations use HTTPS where supported by their service endpoints. Google controls access to its app-data storage. SrvSurvey-XP does not add end-to-end encryption to the profile backup contents. Local backups and downloaded exports should be treated as files that may contain private notes or gameplay information.

No storage or transport method guarantees complete security. If you find a suspected exposure, contact the maintainer without publishing tokens, keys or unredacted account details.

8. Retention & deletion

Local profiles, settings, records and diagnostic files remain until you remove them or the application’s applicable cleanup / retention routines replace them. Uninstalling an executable may leave its data directory intact. Back up wanted data before deleting a profile.

Profile backup history retains up to ten recent local backups and ten recent cloud backups per machine under the current implementation. New linked-machine activity can create additional backups after you clear cloud history. Individual cloud deletion is permanent.

Activity records currently have no automatic expiry configured in the Worker. The last-seen time makes inactive installations fall out of seven-day and thirty-day counts, while their entry can remain in the lifetime total until removed. For a deletion request, the maintainer needs your installation ID to locate a pseudonymous record; a commander name alone cannot identify it.

Third-party publishers control their own copies of data you submitted. Removing a key or turning off publication stops future applicable submissions; it does not delete records already held by that service. Contact the relevant service for its deletion options.

9. Your choices

• Use local companion features without linking Google Drive or Frontier.
• Enable or disable each available publisher separately, and remove personal API keys when you no longer want that integration.
• Manage local backups or export files without a Google account.
• Delete cloud backups before disconnecting if you want both authorization and stored files removed; repeat any required settings change on other linked machines.
• Review and redact logs, screenshots, notes and diagnostic bundles before sharing them.
• Ask the maintainer about access, correction or deletion of project-held data. Available rights and any required retention depend on applicable law and the service involved.

These controls do not promise that a service can retract observations already redistributed to public community datasets. The project does not sell personal data or offer a marketing-data exchange.

10. Changes to this policy

The effective date above identifies this policy version. Material changes to data practices should be reflected here and, where required, communicated in the application or release notes. Newly introduced optional permissions or publication features should provide their applicable controls and disclosures.

11. Contact

The project maintainer is Fenris159 on GitHub. Use the SrvSurvey-XP issue tracker for general support or to request a private contact route for a privacy matter. Issues are public: do not include passwords, API keys, tokens, unredacted logs or private account details. We will not ask you to supply your Google or Frontier password.