LUNARQUESTLEGAL
Main site All documents FAQ Leaderboard
Legal / 02

Privacy Policy

What stays local, what the opt-in leaderboard receives, and how erasure works.

Source updatedNovember 17, 2026
01Terms02Privacy03EULA04Disclaimer05Data06License

Last Revised: November 16, 2026
Effective Date: November 16, 2026


PREAMBLE: ZERO-SURVEILLANCE ARCHITECTURAL COMMITMENT

Project Lunar and its contributors ("Project Lunar", "we", "us", or "our") hold the fundamental privacy rights and digital autonomy of software users in the highest regard. LunarQuest ("LunarQuest", the "Application", or the "Software") is fundamentally conceived, engineered, and maintained pursuant to an uncompromising Privacy-by-Design and Local-Execution-First paradigm.

This Privacy Policy ("Policy") provides exhaustive legal disclosure detailing how information is handled, processed, safeguarded, and isolated during the operation of LunarQuest across host operating systems including Apple macOS and Microsoft Windows.


1. SUMMARY OF PRIVACY COMMITMENTS

  • Zero Account Credentials Ingested: We do NOT ask for, read, inspect, store, or transmit your Discord credentials, user authentication tokens, email addresses, passwords, or Multi-Factor Authentication (MFA) secrets.
  • Zero Remote Telemetry & Tracking: We do NOT incorporate tracking cookies, remote analytics beacons, telemetry daemons, crash collectors, or fingerprinting scripts.
  • No Centralized Servers: Project Lunar operates no centralized user database, cloud ingestion infrastructure, or data brokering network.
  • 100% Local Processing: Window generation, process orchestration, and IPC socket communications occur strictly on your physical machine.
  • Auditable & Transparent Architecture: All process managers and network interfaces are fully documented for user transparency and verification.

2. CATEGORIES OF DATA PROCESSED & SYSTEM ISOLATION

LunarQuest performs operations strictly within the perimeter of your local operating system environment. The specific categories of technical variables utilized are detailed below:

2.1 Local Process & Window Title Variables

  • Nature of Variable: Game executable identifiers, process names, and window title strings (e.g., "Warhammer 40,000: Space Marine 2" or "Lethal Company").
  • Purpose & Scope: Necessary to create lightweight local dummy windows and background processes that trigger the host operating system's process table and window server.
  • Storage & Transmission: These strings reside transiently in system volatile random-access memory (RAM) and temporary user-space directories. They are never transmitted to any server operated by Project Lunar.

2.2 Local Inter-Process Communication (IPC) Socket Payloads

  • Nature of Variable: Discord Application Identifiers (client_id / app_id), activity presence state descriptions, elapsed Unix epoch timestamps, and asset keys.
  • Purpose & Scope: Formatted JSON payloads dispatched to the official local Discord desktop client through the standard local operating system IPC interface (Unix Domain Sockets on macOS/Linux at /var/folders/.../discord-ipc-0 or Named Pipes on Windows at \\.\pipe\discord-ipc-0).
  • Storage & Transmission: Data exchange is strictly intra-device (host machine loopback). No external network hop or proxy routing is executed.

2.3 Public API Directory Queries (Direct Client-Side)

  • Nature of Variable: HTTP GET requests initiated to publicly accessible catalog endpoints (e.g., Discord's public detectable applications directory at https://discord.com/api/applications/detectable or static mirror endpoints).
  • Purpose & Scope: To retrieve public lists of recognizable game titles, application IDs, and asset strings for user selection within the catalog user interface.
  • Storage & Transmission: Standard client-side HTTPS queries dispatched directly from the user's network stack to the target CDN/server. No intermediary server owned or operated by Project Lunar captures or logs this transaction.

3. EXCLUSION OF THIRD-PARTY TRACKING AND TELEMETRY LIBRARIES

The Software does NOT integrate, bundle, or invoke any commercial software development kits (SDKs), advertising libraries, or telemetry instrumentation tools, including but not limited to:

  • Google Analytics / Firebase Analytics;
  • Sentry / Datadog / Bugsnag crash monitoring;
  • Segment / Mixpanel user event telemetry;
  • Advertising identifier attribution networks.

The compiled executable artifacts are strictly limited to the necessary Tauri / Rust backend dependencies, native operating system bindings, and bundled frontend user interface assets.


4. LOCAL PERSISTENCE AND ARTIFACT LIFECYCLE

4.1 Local User Preferences: Any configuration settings (such as UI theme selections, recently activated quest profiles, or favorite game templates) are stored exclusively in local user application storage (e.g., localStorage or local JSON configuration files within the operating system's designated app support directory).

4.2 Ephemeral Dummy Executable Storage: When the application generates dummy runner binaries or dummy application bundles to simulate games, these files are written into a dedicated local sandboxed workspace directory. Users maintain absolute control over these files and may delete them manually or utilize the in-app cleanup controls at any time.

4.3 Total Deletion & Removal: Complete erasure of the Application and its generated local files can be accomplished at any moment simply by removing the application bundle (LunarQuest.app) from /Applications or deleting the application directory and associated local app data folders. No remote data unlinking or deletion requests are required, as no remote records exist.


5. CHILDREN’S PRIVACY AND STATUTORY COMPLIANCE

5.1 COPPA Compliance: LunarQuest does not knowingly collect, harvest, solicit, or store personal information from children under the age of thirteen (13), or under the applicable age of digital consent specified by local jurisdiction (such as sixteen (16) under the European Union General Data Protection Regulation - GDPR).

5.2 Parental Inquiries: Because the Software operates purely as a local utility without unauthorized data retention capabilities, Project Lunar holds zero identifiable child data. Parents or legal guardians may inspect documentation or supervise the local computer environment directly.


6. INTERNATIONAL COMPLIANCE DISCLOSURES (GDPR, CCPA/CPRA)

6.1 General Data Protection Regulation (GDPR - EU/EEA):

  • Under default operation, Project Lunar acts neither as a "Data Controller" nor as a "Data Processor" regarding end-user operational data, because no personal data is collected, stored, processed, or transmitted to any server controlled by Project Lunar.
  • All operational data remains in the continuous custody and sovereign control of the user on their personal hardware.
  • Where a user voluntarily chooses to participate in the public Community Leaderboard (Section 7), Project Lunar processes strictly non-sensitive telemetry pursuant to explicit opt-in consent under GDPR Article 6(1)(a).

6.2 California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA):

  • Project Lunar does NOT "sell", "share", or "monetize" consumer personal information as defined under the CCPA/CPRA.
  • Project Lunar does not maintain behavioral advertising profiles or cross-context tracking databases.

7. PUBLIC GAMEPLAY TELEMETRY & COMMUNITY LEADERBOARD (CLOUDFLARE EDGE SERVICE)

7.1 Nature and Default Activation of Public Gameplay Telemetry: To coordinate community quest rewards and verify cross-platform runner stability, LunarQuest initiates basic, non-sensitive public gameplay telemetry by default upon launching quest emulation. No sensitive credentials, passwords, or personal communications are ever transmitted. Users retain absolute control and may opt out of telemetry at any time by toggling off "Community Telemetry" in the application settings or submitting a self-service data erasure request.

7.2 Permitted Telemetry Categories (Strictly Public & Non-Sensitive): Pursuant to the principle of Data Minimization (GDPR Article 5(1)(c)), only the following non-sensitive attributes are collected:

  1. Public Pseudonym / Handle: User-selected display alias (e.g., AstroRunner#4021) or public Discord username.
  2. Public Discord Identifier: Public Discord snowflake ID for verified profile badge linking (e.g., discord.com/users/<snowflake>).
  3. Avatar Glyph: Non-identifying visual vector glyph (e.g., Crown, Bolt, Rocket, Visor).
  4. Operating System Platform: High-level platform architecture classification (macOS arm64, Windows x64, Linux ELF).
  5. Quest Completion Statistics: The Discord Application ID, game title (e.g., Delta Force), quest campaign name, emulated duration in minutes, and estimated Orbs earned.
  6. Cumulative Counters: Total count of completed quests, total minutes emulated, and ISO 8601 timestamps of quest completions.
  7. Client Version: Semantic application version string (e.g., 1.1.0).

7.3 Strictly Prohibited & Protected Secrets (NEVER COLLECTED / ZERO SURVEILLANCE): Under NO circumstance does Project Lunar, LunarQuest, or the Cloudflare API request, intercept, inspect, ingest, or store:

  • Zero Discord Authentication Credentials: No user tokens, bot tokens, session cookies, OAuth tokens, or passwords. Attempting to harvest Discord tokens is strictly prohibited by our architecture.
  • Zero Discord Account Messages or Private Graphs: No direct messages (DMs), guild/server memberships, chat histories, friend lists, or email addresses.
  • Zero Personally Identifiable Information (PII): No real legal names, physical addresses, telephone numbers, or financial details.
  • Zero Local Filesystem Probing: No directory listings, username paths, or hardware serial numbers are collected.

7.4 Administrative Moderation & Network Abuse Mitigation (IP Blacklisting): To safeguard the community network against DDoS attacks, automated scraping, bot spamming, and fraudulent quest spoofing, Cloudflare edge nodes monitor traffic anomalies. Project Lunar administrators reserve the right to enforce administrative actions against malicious actors, including:

  • Immediate disqualification and removal from the public community leaderboard;
  • Temporary or permanent IP address blacklisting (IP Ban);
  • Forwarding abuse incident reports to designated security channels (1572149879281688636).

7.5 Data Retention and Right to be Forgotten (GDPR Article 17 / CCPA): Any user may exercise their Right to Erasure at any time:

  • Users may submit a self-service purge request via the automated endpoint POST /api/user/delete or via the "Request Data Erasure" interface on the Cloudflare website.
  • Upon receipt of the request, all records, handles, cumulative counters, and quest logs associated with the identifier are permanently and irreversibly expunged from the database within sixty (60) seconds.

8. SECURITY ARCHITECTURE & LOCAL INTEGRITY

While LunarQuest transmits no data to Project Lunar, the security of the local machine remains of paramount importance:

  • Zero Privilege Escalation: LunarQuest executes entirely within standard user-space privileges and does not require administrative (sudo / root) elevation for normal operation.
  • Input Sanitization: Process arguments and window titles are sanitized prior to dispatching to operating system process management routines to prevent command injection vulnerabilities.
  • Secure Native IPC: Communications with the local Discord desktop client utilize standard operating system IPC socket access controls, preventing unauthorized cross-user interference on multi-user systems.

9. AMENDMENTS AND MODIFICATIONS TO THIS POLICY

Project Lunar reserves the prerogative to amend, revise, or refine this Privacy Policy at intervals to reflect architectural updates, regulatory requirements, or platform modifications. When changes are made, the revised Policy will be published within the repository and packaged with subsequent releases of the Software, bearing an updated "Last Revised" date. Users are encouraged to inspect this document periodically.


10. CONTACT INFORMATION

For formal legal, security, privacy, or data-handling inquiries regarding this Policy or the architectural safeguards of LunarQuest, you may contact the development and compliance team directly:

  • Email: contact.theraj01@gmail.com
  • Issue Tracker: Official Project Lunar repository issue tracker.
Project Lunar / independent software
Legal centerContactBack to LunarQuest