No-routine-KYC policy

Scope of the commitment

Routine means the ordinary path used by a customer whose payment and account do not present a specific review need. In that path, the customer should not be asked to upload a passport, national identity card, driving licence, or biometric selfie merely to buy a VPS. Information that is actually needed to create the account, communicate, invoice, secure the service, and meet applicable obligations may still be processed.

This page does not redefine the privacy notice, acceptable-use policy, payment-provider terms, or mandatory law. Those documents identify the current contractual and processing details. If the checkout contradicts this summary, pause the order and request clarification before submitting information.

• The policy covers routine identity-document collection.
• It does not promise that no account or technical data exists.
• It does not apply to data collected independently by a payment service.

Exceptional review

Additional review can be appropriate when required by applicable law or a competent authority; when a payment appears stolen, disputed, or manipulated; when sanctions or risk controls require resolution; when account recovery cannot be completed safely; or when credible evidence links a service to harmful or prohibited activity. An initial review may seek transaction details or an explanation rather than an identity document.

Any request should be limited to what is needed for the stated purpose. Access should be restricted, transmission should use an authenticated channel, and retention should follow the applicable legal and operational schedule. A customer may ask what category of issue prompted the request, although some details may be withheld where disclosure is prohibited or would undermine security.

• Never send a wallet seed phrase, SSH private key, or account password.
• Verify that a request appears inside the official account or support channel.
• Do not email identity material unless explicitly directed to a protected method.

Why no-routine-KYC is not anonymity

Public blockchains, email delivery, IP connections, support discussions, service logs, external applications, and upstream systems can all generate records. Some are controlled by the customer, some by VPSEverywhere.com, and others by independent processors or network operators. No single signup policy can eliminate them.

Customers must use accurate required information, obey the acceptable-use policy, and comply with laws that apply to their workload. Attempts to conceal abuse or impersonate another person are not protected by data minimization.

• Use privacy engineering for the application itself.
• Collect only the end-user data the workload needs.
• Publish truthful notices for your own users.

Questions and accountability

Before ordering, review the live checkout, privacy notice, data-logging policy, payment privacy page, and acceptable-use terms. Direct policy questions through the published contact channel and retain the response with the order record. Material policy changes should carry an updated date and a clear explanation.

This narrow, testable promise is more useful than an unqualified no-KYC badge because customers can understand what is reduced and what remains possible.