bindu sovereign cloud
verified_user Zero Surveillance · Local Data Sovereignty

Privacy Policy & Sovereign Data Residency

Effective Date: October 17, 2026 Version: 1.0 (Sovereign Core) Identity: Local Ed25519 · Zero-Egress
Section 01

Sovereign Data Architecture & Local-First Philosophy

At bindu.cloud and the bindu.protocol mesh, privacy is not merely a policy—it is an immutable mathematical property of our architecture. Traditional cloud platforms operate on data ingestion, server-side profiling, and extractive surveillance telemetry. Bindu operates on an anti-hyperscaler, local-first paradigm:

  • Local Residency by Default: All code, prompts, training weights, client contracts, financial ledgers, and telemetry generated within your private nodes (e.g. bindu.local) reside on your physical storage (host NVMe, local PostgreSQL 17, and encrypted local state).
  • No Global Centralized Datastore: We do not operate a centralized data lake that scrapes, ingests, or stores tenant prompts, conversation history, or proprietary assets.
  • Zero Forced Hyperscaler Telemetry: Bindu does not embed third-party tracking scripts, advertising trackers, or invasive analytics pixels.
Section 02

Telemetry Collection & Operational Truth

We adhere strictly to the Operational Truth and Fleet Evidence Directive (BINDU-DIR-2026-011). The only telemetry processed within the mesh consists of objective, deterministic system metrics required for compute routing:

  • Hardware Capacity Metrics: Physical CPU utilization, GPU VRAM allocation, memory headroom, and network latency used solely for dynamic 4-tier QoS workload scheduling.
  • Zero Payload Inspection: Gateway routers inspect headers and cryptographic Ed25519 signatures to verify authorization. Router nodes do not log, parse, or persist the semantic content of inference payloads or confidential project files.
  • Redaction on Public Surfaces: Public and observer-facing telemetry endpoints automatically strip internal IPv4/IPv6 addresses, physical hostnames (e.g. mac.lan), non-standard listening ports, and exact storage byte figures.
Section 03

Cryptographic Identity & Key Custody

Identity within the Bindu network is anchored by asymmetric cryptography rather than centralized email/password accounts:

Key Custody Rule: Your private Ed25519 signing keys and TLS client certificates are generated on your local machine and never leave your hardware. Bindu has zero knowledge of, and zero mechanism to exfiltrate or recover, your private keys.

Public keys are broadcast to the mesh solely to verify task signatures, sign barter attestations, and validate Merkle audit trails.

Section 04

Local Root CA & Transport Layer Security (TLS)

When you install the Bindu Root Certificate Authority (bindu-ca.crt) on your local devices:

  • Scope of Trust: The certificate is explicitly constrained to your sovereign local mesh domains (bindu.local, mac-studio.local, and Tailscale private network endpoints).
  • No Global Interception: The Bindu Root CA cannot intercept, inspect, or decrypt public internet traffic (e.g., your bank, personal email, or external web browsing). It exists exclusively to eliminate browser self-signed security warnings across your own local hardware nodes.
  • Local Revocation: You retain complete control to inspect, distrust, or delete the certificate from your operating system keychain (macOS Keychain Access, Linux /usr/local/share/ca-certificates/, or Windows Certificate Store) at any time.
Section 05

Cross-Node Telemetry & Merkle State Anchoring

When participating in distributed compute or barter pools across nodes (such as Mac Studio nodes, NVIDIA Spark rigs, or ASUS GB10 workstations):

  • Deterministic Merkle Receipts: Work execution generates local SHA-256 Merkle proofs containing timestamps, token velocity, and task hashes. These cryptographic proofs verify that work was completed without disclosing proprietary source inputs.
  • Optional Blockchain Anchoring: Public ledger anchoring (e.g. Solana Proof of History) is strictly optional (default: disabled). When enabled by tenant preference, only the cryptographic root hash is recorded; zero tenant payload data is written to any public ledger.
Section 06

Regulatory Alignment & Data Subject Rights

Because Bindu operates as sovereign software rather than a multitenant public cloud scraper:

  • GDPR / CCPA Alignment: As the sovereign node operator, you are the exclusive Data Controller of all data stored on your node. You possess full capability to inspect, export, and delete records directly from your local PostgreSQL database without requiring permission from Bindu.
  • HIPAA / PHI Zero-Egress: Gate 6 fail-closed firewall port locks and PHI zero-egress policies prevent accidental data egress from protected health or sensitive legal environments.
  • Right to be Forgotten: Removing a tenant from your local PostgreSQL 17 cluster drops all corresponding tables, indices, and audit records with immediate cryptographic finality.
Section 07

Third-Party Data Disclosures

We do not sell, rent, monetize, or disclose your personal data or operational workloads to third parties:

  • No Data Brokers: We do not partner with or license information to advertising networks, data brokers, or AI training consortiums.
  • External API Integrations: If you explicitly configure external cloud inference models (e.g. DeepSeek, OpenAI, Anthropic), requests egress directly from your environment under your own API credentials and terms, governed by your explicit pre-flight approval.
Section 08

Security Governance & Contact

We maintain rigorous security practices, including automated defect prevention, memory isolation, and continuous vulnerability audits across the Bindu codebase.

If you have questions regarding this Privacy Policy, sovereign data residency, or certificate governance, please contact our team:

Creatives Guide Us / Sean Halls Studio
Attn: Data Protection Officer
Email: privacy@creativesguide.us · sean@creativesguide.us
Web: https://bindu.cloud