ProRDP policy
A clear account of the information used to prepare orders, verify payments, provide support, and protect the service.
Effective date: July 22, 2026
Checkout asks for your name, email address, Telegram username, server-location preference, Windows-version preference, optional notes, selected plan, payment method, and transaction reference. Avoid placing secret credentials or unnecessary sensitive information in any field.
In the default static flow, your payment screenshot is checked locally in your browser for supported image type and size. It is not uploaded by this website, is not written to localStorage, and is deliberately excluded from optional order API requests. You must choose what to send privately through Telegram.
When no backend is configured, order confirmation data is temporarily placed in sessionStorage so the next page can display it in the same browser tab. It normally disappears when that browser session ends. The site does not claim that the order has been saved remotely.
If the operator configures the optional Supabase integration, validated order metadata may be stored in a private orders table for fulfillment and support. Server-only credentials must be protected by the deployment platform. Screenshots are not included in the provided integration.
Deployment, database, network, and communication providers may process limited information as necessary to operate their services. For example, a hosting platform may retain access and security logs, Supabase may process configured order records, and Telegram processes messages under its own privacy terms.
Customer information should not be sold. It may be shared with infrastructure or support providers when needed to deliver the service, address abuse, protect users, comply with lawful requests, or complete a business transition subject to appropriate safeguards.
Order and support records should be retained only as long as reasonably needed for fulfillment, accounting, dispute handling, security, and applicable legal obligations. The final commercial operator must adopt and document specific retention periods appropriate to its jurisdiction.
The project uses validation, sanitization, server-only optional credentials, and a design that keeps screenshots off public storage. No method of online processing is risk-free. Customers should send proof only to the verified Telegram account and should never disclose private keys, seed phrases, passwords, or API secrets.
The provided application does not intentionally add advertising or behavioral-tracking cookies. Hosting providers may process IP addresses, browser details, timestamps, and request logs for delivery and security. Any future analytics or cookie tools should be disclosed and configured in accordance with applicable requirements.
Depending on your location, you may have rights to request access, correction, deletion, restriction, or a copy of certain personal information. Contact support at @Theytproo. Identity may need to be verified before a request is completed.
The service is not directed to children who cannot legally enter a service agreement in their jurisdiction. This policy may be updated when processing practices change; the effective date should be revised when material updates are published.