Privacy Policy

Bot Name: Osiris (`Osiris#0963`) Developer: gahk.wtf Contact: osiris@gahk.wtf Last Updated: July 2026
Core Data Minimization Covenant and Exclusivity of Access The Osiris application (`Osiris#0963`) is engineered in strict accordance with principles of data minimization. The Service does not record, harvest, or retain specific message contents. Furthermore, all operational metadata ingested by the Service is maintained in absolute confidentiality by the developer (gahk.wtf) and shall never be sold, rented, shared, or made accessible to outside commercial entities.

1. Controller Identity and Comprehensive Disclaimer of Liability

This Privacy Policy constitutes the formal regulatory disclosure detailed by the sole proprietor and developer of the Osiris Discord application (gahk.wtf, hereinafter "Controller," "Developer," or "We"), delineating the precise mechanics governing the collection, processing, and retention of digital metadata across the Discord Inc. ("Discord") platform.

Comprehensive Exclusion of Accountability: By authorizing or interacting with the Service (`Osiris#0963`), you explicitly affirm and covenant that the Controller operates the application strictly on an "as is" and "as available" basis, assuming no fiduciary responsibility, statutory obligation, or civil liability of any nature. Under no legal theory shall the Controller be held accountable for any direct, indirect, incidental, or consequential damages, processing delays, API outages, or third-party disputes arising from the ingestion, evaluation, or erasure of digital records.

2. Strict Categorization of Ingested Operational Metadata

To maintain functional equilibrium within multi-tenant Discord guilds and execute real-time verification when triggered via Apps → Osiris → Fact Check, the Service strictly ingests and retains only the exact, limited metadata categories detailed below:

  • Message Identifiers (`message.id`): Numerical Discord snowflake identifiers utilized strictly to reference target payloads and prevent duplicate verification computation;
  • User Identifiers (`user.id`): Numerical Discord snowflake identifiers associated with individuals who trigger the verification context menu or configure persistent user preferences;
  • Guild Identifiers (`guild.id`): Numerical Discord server identifiers designating the specific guilds wherein the application has been authorized or invoked;
  • Verification Classifications: The final algorithmic evaluation output generated during a verification check—specifically recording whether the target claim was classified as correct, incorrect, or mixed;
  • Configured User Preferences: Customized operational parameters, display toggles, or persistent preferences that the User explicitly saves or configures through formal bot interactions.

3. Absolute Prohibition on Message Content Retention

Absence of Persistent Textual Storage: The Controller explicitly warrants that Osiris does not collect, log, scrape, or store specific chat messages, ambient communications, or textual dialogue within permanent databases. When a User initiates the right-click verification command (`Verify with Osiris`), the targeted text payload (`message.content`) is held purely in transient Random Access Memory (RAM) for the brief duration required to complete neural inference, after which the raw textual string is permanently purged from active memory.

4. Exclusivity of Controller Access and Non-Disclosure Covenants

The metadata categories enumerated within Section 2 are governed under strict protocols of exclusivity and confidentiality:

  • Prohibition on Commercial Transfer: The Controller covenants that your metadata shall never be sold, leased, traded, syndicated, or monetized with data brokers, advertising networks, or third-party analytical firms;
  • Single-Entity Access Control: All retained diagnostic rows and preferences remain strictly encrypted and solely accessible by the individual Developer (gahk.wtf), exclusively for purposes of maintaining system stability and fulfilling explicit user configurations.

5. Artificial Intelligence Processing and Epistemic Notice

Osiris relies upon sophisticated Large Language Models ("LLMs") to parse assertions and synthesize verification outputs. Because neural natural language processing operates upon probabilistic statistical correlations rather than infallible deterministic logic, the resulting verification classifications (whether correct, incorrect, or mixed) and accompanying analysis may occasionally exhibit factual inaccuracy, hallucination, or algorithmic bias. By utilizing the Service, you formally acknowledge these inherent limitations of artificial intelligence and agree that the Controller assumes no civil liability or accountability for errors, misclassifications, or third-party actions taken in reliance upon LLM-generated outputs.

6. Data Erasure Protocols, Identity Verification, and Operational Timeframes

In accordance with principles of digital autonomy, any User or Guild Administrator retains the right to submit a formal request for the complete export or permanent erasure of their retained metadata (such as stored snowflake identifiers, classification rows, and saved preferences).

To initiate an official data access or erasure request, formal electronic correspondence must be transmitted directly to the designated compliance address:
osiris@gahk.wtf

Operational Timeframe Disclosure (Single-Developer Infrastructure) Please be explicitly advised that because the Osiris application and its underlying databases are architected, administered, and operated entirely by a sole individual developer (gahk.wtf), the manual verification and execution of data erasure requests require an operational window ranging from several business days up to multiple calendar weeks. We ask for your patience during this rigorous manual verification process.

Mandatory Identity Authentication Requirements:

To mitigate the risk of fraudulent exfiltration or bad-faith erasure submissions by unauthorized third parties, the Controller enforces strict identity verification standards prior to processing any data request. The claimant will be required to prove rightful ownership over the specific User ID (`user.id`) or Guild ID (`guild.id`) through authenticated protocols, including:

  • Executing cryptographic or interactive verification through the official Osiris application (`Osiris#0963`) within a verified Discord channel; and/or
  • Transmitting direct, authenticated verification correspondence to the Developer identifier @gahk on the Discord platform.

7. Policy Ratification and Contact Information

The Controller reserves the right to periodically update or amend this Privacy Policy to reflect evolving architectural improvements or platform API guidelines. Continued usage of the Osiris application following any modification constitutes formal ratification and binding acceptance of the revised instrument. For all data requests, privacy inquiries, or compliance notices, direct all correspondence to:

Osiris Application Privacy and Compliance Office

Developer Portfolio: https://gahk.wtf

Official Discord Application Handle: Osiris#0963

Developer Discord Identifier: `@gahk`

Designated Privacy and Erasure Contact: osiris@gahk.wtf