Legal & Trust Center

Your Data.
Your Rules.

BOREXIA does not sell, rent, or trade your personal financial intelligence. Read our comprehensive Privacy Policy below to understand exactly how we collect, sanitize, and obliterate your state memory.

Last Updated: October 2026

1. The Manual-First Promise

The foundation of our privacy policy is rooted in our architecture. By refusing to implement Open Banking APIs (such as Plaid or Yodlee), we physically prevent ourselves from accessing data you do not explicitly wish to share.

We only collect the cryptographic hash of your email address for authentication, and the exact ledger strings you manually input into the dashboard.

  • We never ask for or store bank passwords.
  • We do not scan your email for receipts.
  • We do not run background location tracking.
Data Collection Scope
Routing & Account Numbers NEVER COLLECTED
Device Advertising IDs (IDFA) NEVER COLLECTED
Third-Party App Analytics NEVER COLLECTED
Manual JSON Ledgers ENCRYPTED

2. LLM Processing & PII Sanitization

To provide actionable intelligence, BOREXIA must process your manual ledger entries through Large Language Models (LLMs). We employ a strict data sanitization pipeline to ensure absolutely no Personally Identifiable Information (PII) is included in the inference prompts.

  • Names, emails, and exact dates are stripped client-side.
  • Data is sent to Groq LPUs via ephemeral, stateless API calls.
  • Zero-Data Retention Policy: Our LLM partners do NOT train on your prompts.
sanitization_pipeline.ts
1. Raw Input (Client Side)
"User: Alex Chen. Transfer $5000 to Chase Acct ending in 8892 on 10/24/2026."
2. Sanitized Payload (Sent to LLM)
{ "intent": "transfer", "amount": 5000, "destination": "[REDACTED_INSTITUTION]", "date": "[REDACTED_TIMESTAMP]" }

3. Verified Sub-Processors

We do not sell your data to marketers, ad networks, or data brokers. However, to run an enterprise-grade web application, we must utilize world-class infrastructure partners. We have strict Data Processing Agreements (DPAs) with the following sub-processors.

Google Firebase / GCP

Used exclusively for AES-256 encrypted database storage (Firestore) and secure cryptographic authentication routing. Data is stored in US-Central region.

Groq / Meta Llama

Used exclusively for stateless inference. Prompts are transmitted via TLS 1.3, processed in memory, and immediately discarded. Zero training retention.

Your Rights

4. The Right to Erase

In strict adherence to GDPR and CCPA, BOREXIA provides programmatic, instantaneous tools for data export and permanent deletion.

Data Portability

You have the right to request a complete, machine-readable copy of your entire state memory. This includes all ledger entries, categorical tags, and AI-generated insights.

Wipe Engine Memory

This triggers an immediate cascading delete across our Firestore clusters. It permanently obliterates your user collection, all sub-collections, and invalidates your authentication token. There are no "soft deletes."

5. Cookie & Tracking Policy

BOREXIA does not utilize third-party advertising pixels (such as Meta Pixel, TikTok Pixel, or Google Ads tags). We utilize strict, first-party functional cookies exclusively for maintaining your secure cryptographic session (JWTs) and preventing Cross-Site Request Forgery (CSRF) attacks.

Functional Cookies Only

Questions about your privacy?

Our Data Protection Officer is available to discuss our architecture, audit reports, or individual data requests.