AD51 ALIENDISTRICT51
Legal

Privacy Policy

Effective date: September 6, 2026 · Applies to ALIENDISTRICT51 Agentic Command and this website (aliendistrict51.space)

1. Overview

This Privacy Policy explains how ALIENDISTRICT51 ("AD51," "we," "us") handles information in connection with ALIENDISTRICT51 Agentic Command ("Agentic Command") and this website. Agentic Command is a local-first desktop application: its core functionality runs on the user's own machine, and it does not require creating an account with us.

This policy is written to specifically address Agentic Command, including its optional use of Google APIs, rather than to serve as a generic template.

2. Information this website handles

This website (aliendistrict51.space) is a static informational site. It does not use advertising trackers, does not run analytics, does not offer account registration, and does not include contact forms.

We do not control the infrastructure that serves this website. GitHub Pages, or any other hosting or content-delivery provider we use, may process standard technical request information (such as IP address, request timestamps, and user-agent strings) as part of ordinary web server operation, under that provider's own privacy policy. We do not claim that infrastructure providers never generate such logs.

3. Google account authorization

Agentic Command can optionally connect to a user's Google account using Google's own OAuth 2.0 authorization system. A connection is only established after the user affirmatively initiates it and completes Google's consent screen. Agentic Command never asks for or handles the user's Google account password directly.

4. Google data Agentic Command may access

Depending on which optional integrations a user authorizes, Agentic Command may request:

Identity

  • OpenID identity information
  • The connected Google account's email address, used to verify the authorization is bound to the exact expected account

Gmail, when authorized

  • Message metadata and content needed to fulfill a user-requested read
  • Search results, threads, and labels
  • Draft messages the user asks Agentic Command to prepare
  • Sending a message, only when the user has explicitly approved that specific send

Google Calendar, when authorized

  • Calendar event information relevant to a user request
  • Free/busy availability
  • Creating or updating an event, only when the user has explicitly approved that specific action

Agentic Command does not access Google Drive, YouTube, Google Contacts, Google Photos, or other Google services not listed above.

5. How Google data is used

Google data is used only to carry out the specific, user-directed functionality of Agentic Command. For example: answering an explicit request about the user's inbox, preparing a requested draft, sending an email the user has explicitly approved, retrieving a requested schedule, checking availability, or preparing and, once approved, executing a calendar action.

Google data is not used to build advertising profiles, and is not used for any purpose unrelated to the specific workflow the user requested.

6. Data minimization

Agentic Command is designed to request and retain only the information needed for the workflow the user asked it to perform. This is a design goal rather than a claim that every piece of data is transient — some non-content operational records are retained as described in Section 8, so that the user has an accurate record of what the application did.

7. Local credential security

Reusable Google OAuth credentials (such as refresh tokens) are protected locally using Windows DPAPI (Data Protection API) tied to the current Windows user account. These reusable secrets are not stored as plaintext records inside the Cognitive Core database. A short-lived access token may exist transiently in memory only while an authorized operation is being performed. Durable tool and connector records reference credentials indirectly (an opaque credential reference), never by storing the plaintext secret itself.

8. Durable operational records

To give the user an accurate account of what Agentic Command has done, the application may locally retain non-secret operational evidence, such as: provider identifiers, the type of operation performed, timestamps, status, provenance, and approval information associated with an action.

Sensitive Gmail message bodies and Calendar write payloads are designed to be redacted or minimized before they are written into this durable operational evidence, rather than stored there in full.

9. Sharing and sale

We do not sell Google user data. We do not use Google user data for advertising. We do not share Google user data with unrelated third parties for advertising or marketing purposes. Google APIs are called only as needed to perform the specific functionality the user requested. We do not use any third-party data processors beyond the Google APIs and infrastructure described in this policy.

10. Human access

Agentic Command's current architecture is local-first: there is no routine server-side ingestion of a user's mailbox or calendar by ALIENDISTRICT51. We do not claim that no human could ever access data under any circumstance — for example, the user themself has direct access to their own local application data — but there is no ordinary operational path by which ALIENDISTRICT51 personnel view a user's Google data.

11. Google API Services User Data Policy

Agentic Command's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not represent that Agentic Command has undergone Google's verification or certification process unless and until that process is actually completed.

12. User control

Users control every optional integration and may disconnect Gmail or Google Calendar within Agentic Command at any time. Google account authorization can also be revoked directly through the user's own Google Account permissions and security settings, independent of the application.

13. Data deletion

Disconnecting or revoking an integration removes Agentic Command's stored access credentials for that service and prevents any future access to that provider on the user's behalf. Disconnecting an integration does not automatically erase historical, non-secret operational records (see Section 8) that were already created before disconnection; those remain part of the user's own local operational history unless the user separately removes them.

14. Security

Agentic Command applies local secure credential protection, explicit user permissions, approval gates for consequential external actions, scoped connector bindings limited to specific authorized capabilities, and redaction or minimization of sensitive content in durable records. No system can be described as completely secure, and we do not claim Agentic Command is "100% secure," "unhackable," or "military-grade."

15. Changes to this policy

We may update this Privacy Policy as Agentic Command's functionality evolves. Material changes will be reflected by updating the effective date at the top of this page.

16. Contact

For questions about this Privacy Policy, please reach out through ALIENDISTRICT51's official public channels or open an issue on GitHub.