Privacy
Last updated: September 2026 (PoC draft)
This page describes what the Ray proof of concept collects and why. It is not a substitute for a counsel-reviewed privacy policy at public launch.
What we collect
Phone number (account key), passport image and short verification video for manual KYC, agent intake details (amounts, currencies, optional receipt photo), wallet and card lifecycle metadata (token, last four, status — never full PAN/CVV in Ray’s database), ledger entries for funding, FX, spend, and off-ramp, and operational audit records for staff actions.
Why we collect it
To create a phone-first account, verify identity by hand, credit wallets against agent confirmations, issue and freeze cards via a processor adapter, show a complete transaction history, and run a staff ops console.
Where it is processed (PoC)
PoC deployments store data on the environment you run (local disk uploads, SQLite or optional Postgres). There is no claim of a specific production region or certified hosting stack on this page.
Sharing
Staff operators see KYC packs and ledger data in /ops. Card issuing and authorizations involve a partner processor when connected — we do not name a bank as fact until signed. We do not sell personal data.
Your choices
Contact support via the human WhatsApp channel published for the deployment. Freeze the card from the app when that surface is available. Rejected KYC includes a reason in your language.
Honesty note
Marketing and this policy do not invent licence numbers, regulators, or partner banks. When legal and banking relationships are signed, this page will be replaced with a counsel-reviewed version.