Data Encryption Protocol // Privacy.02

Privacy Policy.

Classification Status: Encrypted Ledger

01 // Data Stream Capture Parameters

When you register, initialize a checkout run, or authorize account configurations inside the Barrison ecosystem, we map and ingest the following explicit data payloads into our secure database network:

  • First name, last name, telemetry contact lines, and mail address vectors.
  • Physical logistics delivery coordinates (street, city, state, postal code).
  • Metadata array state tracking flags (favorites watchlists and active cart cache items).

02 // Cookie Tracking & Persistent State Storage

Our platform drops small local cache variables ("Cookies") to maintain your active authentication JWT tokens, trace session survival metrics, and retain shopping cart choices across reboots. You can manually disable cookie data ingestion via your browser settings, but it will corrupt your authorization flow, locking you out of secure workspace page modules.

03 // Payment Processor Cryptographic Isolation

Barrison Gadgets **never** logs or stores credit/debit card numbers on its servers. When selecting online transaction methods, your credentials route directly to the Paystack gateway architecture via PCI-DSS compliant SSL encrypted connections. Our server records *only* retain metadata transaction callback strings (e.g., Paystack References) to authorize order generation loops.

04 // Data Retention & Node Purging

Your user information remains active within our database arrays for as long as your profile trace exists. If you decide to completely drop your identity node, submit an explicit data deletion directive message to our legal operations team. We will completely purge your profile parameters out of active memory blocks within 7 business days, excluding immutable legal financial ledger records.

[ DATA SAFETY DEPLOYMENT COMPLIANCE // ADVANCED COMPUTE SECURE LOCK ]