OracleBot
How It Works Security Features Pricing Dashboard Add to Discord
How It Works Security Features Pricing Dashboard

Privacy Policy

Last Updated: August 18, 2026

1. Overview & Architecture

Oracle is designed to provide voice AI capabilities for Discord while ensuring complete privacy and isolation for host computers and voice channel participants. The service is built upon a zero-trust local isolation model: Oracle only processes audio during active speech, handles voice streams in temporary memory, and operates without access to personal files or local network infrastructure.

2. Ephemeral Voice Processing (Memory-Only)

Voice interaction with Oracle adheres to strict data minimization principles:

  • Zero Disk Storage: Voice audio is held strictly in volatile RAM for the duration of transcription and response synthesis. Audio buffers are immediately wiped from memory after each conversational turn.
  • No Server Audio Archiving: Speech-to-Text and voice generation occur directly on the subscriber's host machine. Oracle servers function solely as a secure relay between Discord and the subscriber's client, never recording, storing, or inspecting audio content.
  • Push-to-Talk Turn Boundaries: Audio is received only between speaking-start and speaking-stop events. Ambient audio and background conversation are never captured or streamed.

3. Local Operating System Isolation (OracleWorker)

When executing local operations via Oracle Bundle on Windows:

  • Dedicated Low-Privilege Account: The background agent executes under a dedicated, low-privilege system account (OracleWorker). Windows NTFS access control lists strictly deny read and write permissions to personal folders including Documents, Desktop, Downloads, browser profiles, saved credentials, and session tokens.
  • Windows Firewall Network Restrictions: The worker account is restricted by Windows Firewall rules that prohibit inbound and outbound access to local network subnets, routers, and smart devices. Only direct encrypted TLS outbound connections to authorized AI endpoints and Oracle relay servers are permitted.
  • Session Canary Verification: An automated decoy test executes at the start of every voice session to independently verify sandbox isolation before any conversational prompt is processed.

4. Account & Server Data

To manage bot permissions and service configurations, Oracle collects and stores only essential operational metadata:

  • Discord Identifiers: Discord user IDs, guild IDs, and guild permissions obtained via Discord OAuth2 to authenticate administrative access to the Web Dashboard.
  • Pairing Tokens: Client pairing tokens are stored exclusively as non-reversible Argon2id cryptographic hashes. Plaintext tokens are never retained server-side.
  • Subscription Billing: Premium subscriptions are processed directly through Stripe. We do not store or process payment card details on our infrastructure.

5. Third-Party API Keys

API keys configured for third-party inference providers (such as Groq or Google AI) remain stored locally on the subscriber's machine. They are never transmitted to, stored on, or accessible by Oracle servers.

6. Data Control & Deletion

Server administrators maintain full control over stored configurations. Pairing tokens can be revoked, custom personas deleted, and server associations removed at any time through the Web Dashboard.

7. Contact Information

For privacy inquiries, security questions, or data requests, please contact: