Privacy Policy

Privacy enquiries

Contact ZePayCrypto@proton.me with questions about how ZePay handles your information. This draft describes the current local implementation.

Information you provide

Registration requires an email address and a password. The server stores the email, a salted password hash, account creation time, role and email-verification status. Email sign-in verification is not connected. No name, telephone number, residence or identity-document field is requested.

If you email support, your message, email address and any attachments are received through the support mailbox. Please share only what is needed to answer your question.

Technical information and cookies

The local server processes connection IP addresses and request information. Its login rate limiter stores keyed hashes of account and IP identifiers in the local database; server logs may include request details. The dipay_session cookie is necessary to maintain your signed-in session and expires after eight hours. Blocking it prevents persistent sign-in. A separate CSRF cookie protects account requests.

The current site has no connected third-party analytics or advertising trackers. It stores local funnel counters in sessionStorage for card views, card choices, completed sign-ins or registrations and order reviews. These contain only an event name, a card category and a count, with no email, amount, password or visitor identifier. They are not transmitted and are cleared when the tab session ends. Passwords and session tokens are not stored in browser localStorage. The database holds server session records and expiry times. Recovery records hold the account reference, a keyed code digest, expiry and attempt counts. Codes are never returned by the API.

Why information is used

Account information supports registration, sign-in, password changes and session management. It also supports password recovery when available. Mailbox confirmation, email sign-in codes and email changes are not connected. Technical information supports request handling and abuse prevention. Support correspondence is used to address your enquiry. Processing purposes and legal bases for the live service will be documented in the final policy.

Storage, sharing and transfers

Local account records are stored on the computer running the server. Any payment provider that receives data must be identified in the final policy. The current implementation does not sell account data or send it to advertising platforms.

Emailing the published contact uses the support email service. When transactional email is configured, the selected mail provider will receive the destination address and the email content needed to deliver account codes. That provider has not yet been selected. Before launch, this policy must identify hosting, email and payment recipients, storage locations and any international-transfer arrangements. Future live transfers may involve wallet addresses and public transaction hashes; blockchain activity is not private merely because registration uses little information.

How long records remain

Account records remain in the local database until the server owner removes them. There is no automatic account-retention schedule or self-service deletion tool yet. Sessions expire after eight hours; expired server session records require server cleanup. Recovery codes expire after ten minutes. Automatic retention cleanup for recovery records is not configured. Clearing browser cookies does not erase the account database.

Retention periods for support email, logs, backups and future payment records must be finalised before production use.

Your requests and choices

You can change your password in Settings. Email changes are not connected in the current version. You can also sign out or block the session cookie. To ask about access, correction or deletion, contact ZePayCrypto@proton.me; for a locally hosted copy, its owner controls the stored database. Rights such as portability, restriction, objection and complaints to a regulator depend on the applicable law, which must be identified for the live service.

No automatic deletion or response deadline is promised in this draft. We will need an operational request-verification process that does not collect unnecessary information.

Security and updates

See Protection & safety for implemented account controls and current limitations. Password recovery uses a one-time code when available. Email confirmation and email sign-in codes remain unavailable. This notice will be revised when integrations or data practices change.