Processing
Establishing connection...
Effective Date: May 2026 | Document Reference: PDEP-V3.4-SEC
Mahabaraha is engineered around the principle of strict data minimization. Unlike traditional public listing directories that aggregate, monetize, and index user profiles, our system architecture isolates data into fragmented nodes. We do not maintain unencrypted identities, trackers, or behavioral profiling graphs.
Your presence on this platform operates under an absolute cryptographic shield. Session state, directory interactions, and transactional communications are encrypted end-to-end to ensure structural privacy against third-party analytics vectors.
When registering an alias profile or interacting with our automated billing or escrow relays, the network processes data via the following strictly enforced encryption layer:
Authentication is governed strictly under Supabase SSR PKCE protocols. Passwords and emails are salt-hashed on isolated authentication micro-services, rendering raw credentials unreadable to platform database administrators.
Payment properties like credit lines or mobile transfer routes (MPESA) pass through specialized, tokenized Paystack webhook callbacks. Mahabaraha never stores, indexes, or views your primary financial accounts or billing vectors.
We eliminate tracking cookies. The network implements server-side JSON Web Tokens (JWT) strictly for authorization states, ensuring your active session remains valid across internal page loads without persistent cross-site footprinting.
IP addresses routing into our proxy gateway are obfuscated within temporary edge runtime memory contexts to perform regional localization (e.g., currency alignment or regional filtering) and are completely dropped immediately upon closing your browser or completing your session termination handshake.
Mahabaraha values your explicit right to be forgotten. Users retain absolute control over their placement records and profile variables. When a user requests profile erasure from their dashboard settings panel, a series of automated background cron jobs are executed:
*Note: Transaction logs connected to completed escrow operations or active Paystack billing records are retained in an immutable state for a legal minimum timeframe to satisfy sovereign anti-fraud and financial processing mandates.
Irreversible Action Warning: Executing a Profile Erasure Sequence is structurally final. Because our systems do not maintain archival shadow backups or historic ledger recovery states, deleted records cannot be recovered by administration support teams.