• Account fabric: email vectors, optional telephony identifiers, profile facets, role embeddings (buyer / vendor / delivery / admin).
• Transactional holograms: cart fingerprints, order graphs, Paystack references, shipment artefacts, chat transcripts scoped to commerce threads.
• Telemetry sheaves: device/browser hints, security logs, coarse geolocation when riders / buyers opt into mapping surfaces — never weaponized for unrelated ads profiling absent future disclosure & consent refreshes.

• Authenticate identities & enforce Supabase Row Level Security predicates.
• Execute checkout, notify stakeholders, score fraud heuristics, orchestrate admin moderation playbooks.
• Maintain reliability SLOs — aggregated telemetry diagnostics minus unnecessary persistent individuality ( see Cookies layering).

Ledgers persist across statutory bookkeeping windows, unresolved disputes, or AML-flavored investigations. Upon validated deletion eligibility, purge cascades propagate across Postgres partitions & object storage namespaces controlled via Supabase policies — subject to immutable audit carve-outs where regulators insist.

Infrastructure may leverage Supabase regions, Paystack settlement geography, transactional email gateways ( e.g. Resend-class APIs when configured), and CDN strata — each imposing territorial processing footprints disclosed at onboarding-depth for enterprise counterparties upon request.

Exercise privacy rights through authenticated pathways or operator-published secure channels. We validate requestors before exposing extracts — mitigating social-engineering replay attacks impersonating concerned users.

Route nuanced inquiries via dashboard ticketing or official emails plastered in genuine announcements — cross-check domains vigilantly. Escalate suspected phishing to operators promptly so defensive patterns update.

Granular storage taxonomy expands inside our Cookie Policy — consult before aggressively blocking first-party essentials lest dashboards fail hydration mysteriously.