Data in the ProxyCrest workflow
An account is associated with a browser session. You can add a username and password to sign in again. Top-ups record the crypto amount, payment network and payment status; transaction references may be attached to the payment record. Orders record the selected proxy configuration and the amount deducted from the USD balance. Support messages you send are also stored in the application.
A crypto transaction may be public
A transaction hash can reveal transfer details through a public blockchain explorer. Do not publish your order history on the assumption that a crypto payment leaves no publicly accessible information.
Preserve access to your account
Without a configured username and password, access depends on your browser session. Clearing its cookies can leave you unable to access that account. Configure a sign-in method and keep your order references. The current workflow does not provide email recovery.
Define the scope of privacy
A proxy changes the connection path to a destination; it does not delete cookies, sign you out of an account or automatically hide every browser characteristic. The network provider practices and log retention must be confirmed before use. This page describes the local product, rather than a legal guarantee or a no-logs commitment.
Frequently asked questions
Do I have to provide an email address?
The current local account can use a browser session, followed by a username and password. This workflow does not request an email address.
Does no KYC also apply to my crypto wallet?
No. It describes only what ProxyCrest requests in its current interface. Your wallet or exchange has its own terms.