Privacy Policy

OMNIXQ — AI Voice-Agent Fintech Ecosystem by OMNIXQ WORLD

Last updated: January 15, 2025

1. Overview

This Privacy Policy governs the collection, use, disclosure, and protection of your personal information when you interact with OMNIXQ — the AI voice-agent fintech ecosystem operated by OMNIXQ WORLD ("we," "us," or "our").

OMNIXQ provides autonomous AI voice agents that execute financial operations, market analysis, and programmable payments via the π402 Lightning protocol. By using our services — including voice calls, web interfaces, APIs, and agent interactions — you consent to the practices described in this policy.

We are committed to data minimization, transparency, and user sovereignty. This policy complies with GDPR, CCPA/CPRA, and applicable financial privacy regulations.

2. What We Collect

We collect only data necessary to provide, secure, and improve our services. Categories include:

Account & Identity Information

  • Registration data: Email address, username, cryptographic public keys (npub/hex), and authentication credentials
  • Profile data: Display name, avatar, timezone, language preferences
  • Verification data: KYC/AML documents where required by jurisdictional regulation (processed by licensed partners, not stored by us)

Voice Call Recordings & Transcripts

  • Audio recordings: Full call audio between you and AI agents
  • Transcripts: Automated speech-to-text conversions with speaker diarization
  • Metadata: Timestamps, duration, agent ID, call outcome, intent classification

Usage & Telemetry Data

  • Interaction logs: API requests, agent invocations, tool calls, response latencies
  • Device & network: IP address (hashed), user agent, device fingerprint, connection type
  • Feature usage: Module activation, payment flows, energy market queries, world-state requests
  • Error & performance: Crash reports, latency distributions, model confidence scores

Financial & Payment Data

  • Lightning invoices: Payment hashes, amounts, timestamps, counterparty node IDs
  • π402 receipts: Cryptographic proofs of payment-for-API-access
  • Wallet metadata: Balance snapshots, channel states (non-custodial; we never hold private keys)

3. How We Use It

Service Provision
Execute voice-agent conversations, process π402 payments, serve world/energy data, maintain session continuity.
Agent Training & Improvement
Anonymized, aggregated transcripts and interaction patterns fine-tune intent classification, tool selection, and response quality. Opt-out available in settings.
Security & Fraud Prevention
Detect abuse, Sybil attacks, payment fraud, and anomalous agent behavior via behavioral analytics.
Legal Compliance
Fulfill regulatory obligations (AML/CTF, sanctions screening, audit trails) and respond to lawful requests.
Product Analytics
Understand feature adoption, latency bottlenecks, and user journeys to prioritize roadmap.
Communication
Service notifications, security alerts, policy updates (transactional only; no marketing without consent).

4. AI Voice Calls Disclosure

⚠ Important Disclosure

All voice conversations with OMNIXQ agents are recorded, transcribed, and processed by artificial intelligence systems. These agents are not licensed financial advisors, attorneys, or tax professionals. Outputs are algorithmic predictions, not professional advice.

What This Means

  • Recording: Every call is audio-recorded from connection to termination. You hear a tone at start.
  • Transcription: Audio is converted to text in real-time via ASR (Automatic Speech Recognition).
  • Processing: Transcripts feed LLMs and tool-use pipelines to generate responses and execute actions.
  • Retention: Recordings retained 90 days; transcripts retained 2 years for audit/compliance; anonymized training data retained indefinitely.

Your Controls

  • Delete individual call recordings via Dashboard → History → Delete
  • Disable recording for future calls (limits agent functionality) in Settings → Privacy
  • Request full data export or erasure per Section 9

No Professional Advice

Agents may discuss markets, energy prices, Lightning routing, or protocol mechanics. This is information, not advice. Consult qualified professionals for financial, legal, or tax decisions.

5. Machine Payments (π402 Lightning)

OMNIXQ uses the π402 protocol — a Lightning-native standard for programmatic, pay-per-API-call settlements. Key privacy properties:

🔐 Non-Custodial by Design

We never custody your funds. Payments settle directly between your Lightning node and agent endpoints via HODL invoices. We see only payment hashes, amounts, and timestamps — never private keys, seed phrases, or wallet internals.

Data Collected During π402 Flows

  • Payment hash: SHA256 preimage commitment (pseudonymous)
  • Amount (msats): Fee for specific API/tool invocation
  • Timestamp: Settlement time for audit ordering
  • Node pubkey: Counterparty identity (your node or routing peer)
  • API endpoint: Which agent tool was paid for (e.g., /energy/spot, /world/state)

No Financial Surveillance

We do not link π402 payments to real-world identity beyond your npub/pubkey. No chain analysis, no address clustering, no sharing with analytics firms. Payment metadata serves only: (a) proof-of-service for dispute resolution, (b) capacity planning, (c) protocol fee accounting.

6. Cookies & Tracking

We use minimal, first-party cookies only. No third-party advertising trackers, no fingerprinting scripts, no cross-site profiling.

Cookie Purpose Duration Type
qfi_session Authentication & session continuity 30 days Essential
qfi_prefs UI preferences (theme, language, agent voice) 1 year Functional
qfi_consent Cookie consent & training opt-out state 1 year Essential
qfi_csrf CSRF protection for state-changing actions Session Essential

You may disable non-essential cookies via browser settings or our Consent Manager (footer link). Essential cookies cannot be disabled without breaking authentication.

7. Data Security

We implement defense-in-depth controls appropriate to the sensitivity of financial and voice data:

Encryption

  • In transit: TLS 1.3 everywhere; mTLS for inter-service; DTLS/SRTP for WebRTC voice
  • At rest: AES-256-GCM for databases, object storage, and backups; keys managed via HashiCorp Vault
  • In use: Confidential computing (AMD SEV-SNP) for transcript processing workloads

Access Control

  • Zero-trust network (Tailscale + WireGuard); no public SSH/RDP
  • Just-in-time access via Teleport; all sessions recorded
  • Principle of least privilege; engineers cannot access production voice recordings

Monitoring & Incident Response

  • SIEM (Vector + ClickHouse) with real-time anomaly detection
  • Automated PII scanning in logs (nightly)
  • Incident response plan tested quarterly; 72-hour breach notification per GDPR Art. 33

Retention & Disposal

  • Voice recordings: 90 days → secure shred (cryptographic erasure)
  • Transcripts: 2 years → anonymization → aggregation
  • π402 receipts: 7 years (financial record retention)
  • Account data: Deleted within 30 days of closure request

8. Third-Party Processors

We engage subprocessors strictly for infrastructure and AI capabilities. All execute DPAs with SCCs. No data sold.

ElevenLabs (Voice Synthesis & ASR)
Processes audio for TTS generation and speech-to-text. Data processed in US/EU per region. Privacy Policy
Twilio (Voice Connectivity & WebRTC)
Provides PSTN termination, SIP trunking, and WebRTC media relay. Call metadata only; no recording access. Privacy Policy
Cloudflare (Edge, DDoS, Workers, R2, Stream)
CDN, WAF, DNS, serverless compute, object storage, video streaming. Logs retained 24h. Privacy Policy
Anthropic / OpenAI (LLM Inference — Optional)
Used only when you enable "Advanced Reasoning" mode. Zero-retention API endpoints. Anthropic Privacy · OpenAI Privacy
Lightning Network Nodes (Routing Peers)
Public routing nodes see payment hashes and amounts — standard Lightning privacy model. No identity linkage.

Subprocessor list updated quarterly. View current register →

9. Your Rights

Depending on your jurisdiction, you may exercise:

Access & Portability (GDPR Art. 15/20, CCPA §1798.100)
Request a machine-readable export of all personal data (JSON + audio ZIP). Fulfilled within 30 days.
Rectification (GDPR Art. 16)
Correct inaccurate profile or account data via Dashboard → Settings.
Erasure / "Right to be Forgotten" (GDPR Art. 17, CCPA §1798.105)
Delete account and all associated data. Exceptions: π402 receipts (legal retention), fraud prevention logs.
Restriction & Objection (GDPR Art. 18/21)
Object to processing for training/analytics. Toggle in Settings → Privacy → "Allow Training Use."
Withdraw Consent (GDPR Art. 7)
Revoke optional consents (marketing, advanced AI models) anytime without affecting core service.
Non-Discrimination (CCPA §1798.125)
Exercising rights never degrades service quality or pricing.

To exercise rights: Email privacy@qfi.p2pcity.com with subject "Data Rights Request" + your npub/email. We verify identity via cryptographic signature challenge.

10. Contact

Questions, complaints, or requests regarding this policy or your data:

Data Protection Officer (OMNIXQ WORLD)
dpo@omnixq.world
Privacy Team (OMNIXQ)
privacy@qfi.p2pcity.com
Postal Address
OMNIXQ WORLD Ltd.
128 City Road
London EC1V 2NX
United Kingdom
Supervisory Authority
UK: Information Commissioner's Office (ico.org.uk)
EU: Lead SA per GDPR Art. 56 (Ireland DPC)

We respond to all inquiries within 30 days (15 days for CCPA). If unsatisfied, you may lodge a complaint with your local data protection authority.