Privacy

Pilot scope

Zeloris Cash is in limited pilot testing. Features, data handling, and retention may change as we learn from invited participants. We aim to collect only what is needed to operate the service and to keep merchant-facing views within clear boundaries.

Data we use to operate the service

To run the pilot, the product uses information such as:

• Device and app session data needed to authenticate and sync your wallet
• Payment request metadata (amount, status, reference codes merchants share)
• Technical logs for reliability, abuse prevention, and support
• Merchant portal session data when a business signs in to its dashboard

This marketing site (zeloris.cash) is informational only — it does not process payments or store API keys in your browser.

What merchants can see

Merchants can see their own payment requests and merchant-safe request data — for example request status, amounts received against a request, and reference codes they created.

Merchants must not receive or display:

• Payer identity or a payer relationship graph
• Internal holder references, device identifiers, unit identifiers, or spend payloads
• Cryptographic signatures or secret material from payers

Product design targets this separation; during the pilot we continue to validate it in real flows.

Secrets and public UI

API keys, session secrets, and other credentials belong on the server or in secure app storage — not in public web pages, share links shown on this site, or merchant-visible exports intended for pilot use.

What we do not claim

• Not full anonymity. Pilot systems may retain technical and operational records. Privacy-oriented design is a goal, not a guarantee of complete anonymity.
• Not a compliance certificate. This page does not state GDPR, banking, or payment-regulation compliance. We handle data responsibly for a pilot and will publish fuller policies before any broader launch.

Questions

For privacy or security questions during the pilot, contact us via the contact page.