Orboltlabs Legal DocumentationEffective: 17 October 2026

Privacy Policy

This Privacy Policy describes how Orboltlabs collects, handles, and protects information when you use our website, interfaces, APIs, and AI-powered execution infrastructure for Solana. We are committed to non-custodial data sovereignty and transparency.

Looking for our terms of service?Read the Terms of Service →

1. Overview and Non-Custodial Architecture

Orboltlabs operates an AI-powered execution layer for the Solana blockchain. Our infrastructure is built upon a foundational principle of strict non-custody. We do not operate as a custodian, centralized exchange, or asset manager.

We never request, generate, store, or transmit your private keys or seed phrases. Every on-chain action constructed or recommended by our deterministic parser or AI Copilot requires explicit, manual cryptographic approval within your own self-custodial browser wallet (such as Phantom or Solflare) before transmission to Solana RPC nodes.

2. Information We Collect

We collect only the minimal operational information required to authenticate sessions, provide structured execution interfaces, and maintain API reliability:

  • Account Information: If you authenticate via email or Google OAuth, we store your authenticated email address, user ID, and associated role within our identity service (Supabase Auth).
  • Public Wallet Addresses: When you connect a Solana wallet, we record your public key and Sign-In-With-Solana (SIWS) authentication status for session validation and balance display.
  • Plan Drafts and Local Intent Data: Execution drafts, transaction intent previews, and user preferences are persisted client-side within your browser's local storage (e.g., localStorage['orboltlabs_plans']).
  • Operational Telemetry & Rate Limiting: Masked IP addresses and request timestamps are temporarily processed in memory to enforce per-user rate limits and prevent denial-of-service abuse.
Critical Non-Collection Guarantee:Orboltlabs NEVER collects, logs, or has access to your wallet private keys, mnemonic seed phrases, or arbitrary off-chain asset balances.

3. How We Use Information

The information we collect is strictly used for the following operational purposes:

  1. To verify session integrity, enforce multi-factor authentication (MFA), and protect against account takeover.
  2. To compile deterministic execution plans, calculate estimated Solana transaction fees, and render transaction simulations.
  3. To enforce daily request limits (such as AI intent generation quotas) and protect system infrastructure.
  4. To communicate service-critical security notifications or authentication alerts.

4. AI Copilot and MCP Execution Boundaries

When you interact with our AI Copilot or Model Context Protocol (MCP) tool registry:

  • Natural language prompts are processed through enterprise AI endpoints strictly to extract structured parameters (e.g., token names, mint amounts, liquidity pool configurations).
  • Prompts and structured tool calls are never used to train third-party public foundation models.
  • The AI Copilot maintains zero execution authority. It produces proposals (Draft Plans) which you must review, approve, and sign with your hardware or software wallet.

5. Solana Blockchain Transparency & Third Parties

Transactions broadcast to the Solana network are inherently public, immutable, and accessible to anyone via blockchain explorers. By signing and submitting a transaction, you acknowledge that the public key, token balances, transaction signatures, and metadata involved in that on-chain action will become permanent public records on Solana.

We interact with third-party RPC providers (such as official Solana clusters, Raydium protocols, and DEX liquidity contracts) solely to query account states and broadcast signed transactions.

6. Data Storage, Security, and Retention

We implement industry-standard cryptographic and administrative security measures, including:

  • Encrypted HTTPS and TLS communication across all web, server action, and API endpoints.
  • Strict Row-Level Security (RLS) on database tables ensuring users can only read their own profile.
  • Time-based One-Time Password (TOTP) two-factor authentication and single-use cryptographic recovery codes.
  • Zero storage of sensitive session tokens in unencrypted client-side scripts.

7. User Rights and Data Control

You have full control over your stored data:

  • Wallet Disconnection: You may disconnect your Solana wallet at any time from the navigation bar or settings page, which immediately clears active signing permissions in your session.
  • Draft Removal: Saved drafts and temporary plans can be deleted directly from the Activity page, which purges them from your local browser storage.
  • Account Deletion: You may request the deletion of your authentication profile by contacting our privacy team at the contact address below.

8. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect enhancements in our architecture, smart contracts, or legal obligations. When changes are published, we will revise the “Effective Date” at the top of this document. We encourage you to review this page periodically.

9. Contact Information

For questions, concerns, or requests regarding this Privacy Policy or our data practices, please reach out to our designated privacy contact:

Entity: [Orboltlabs Legal Entity / Operator]

Attention: Privacy & Security Compliance Team

Email: [legal@orboltlabs.com]

Postal Address: [Orboltlabs Physical / Registered Address Placeholder]