Render402 does not require an account or API key. It does need your wallet address, request, media, and order data to review, process, deliver, and reconcile a paid generation.
1. Data we process
| Data | Why it is used |
|---|---|
| Wallet and authentication | Public wallet address, signed login message, session and payment authorization data used to identify your orders and verify authorization. We never receive your private key. |
| Creation inputs | Prompts, settings, images, audio, and related metadata used for content review, generation, recovery, and support. |
| Orders and payments | Order IDs, exact quotes, status, transaction references, refund references, timestamps, and delivery records used for settlement, reconciliation, and disputes. |
| Technical and risk data | Request metadata, browser data normally sent with HTTP, errors, and a keyed hash derived from the connecting IP address for rate and abuse controls. |
2. How data is used
- quote, review, generate, deliver, and recover your order;
- authenticate a wallet without storing a password;
- verify x402 payments and process required refunds;
- apply content, rate, download, and fraud controls;
- diagnose failures, secure the service, and handle reports;
- meet legal, accounting, licensing, and dispute obligations.
Render402 does not sell personal data or use your prompts or media to train a general-purpose AI model.
3. Service providers and public systems
Data is shared only as needed with these categories:
- Cloudflare for edge hosting, delivery, and network security;
- Google Fonts and Iconify to deliver the site typography and interface icons; their servers receive standard web request data when those assets load;
- DreamBiuBiu channel infrastructure, generation providers, automated content-review providers, and object storage;
- PayAI to verify and facilitate x402 settlement;
- Base and USDC smart contracts, where wallet addresses, transfers, and transaction references are public blockchain data and cannot be deleted by Render402; and
- authorities or professional advisers when reasonably required by law, security, or a legal claim.
4. Retention
| Record | Current handling |
|---|---|
| Unpaid temporary media | Normally expires after 30 minutes unless a paid order extends the media required for that order. |
| Generated video | The protected result link expires 24 hours after successful delivery. Storage cleanup follows the active 1–30 day media retention setting and may complete asynchronously. |
| Operational logs | Retained for 7 days. Application logs exclude prompts, media content, private URLs, credentials, and authorization headers. |
| Order and safety records | Order identity, prompt and settings, content-review metadata, payment evidence, provider receipts, and ledger records are retained as needed for recovery, reconciliation, abuse prevention, disputes, and legal obligations. |
5. Browser storage and security
The website stores the last order ID for a connected wallet and the accepted policy version in local storage so you can resume an order and avoid repeated prompts. It does not use advertising cookies. Clearing site data removes those browser records.
We use access controls, limited download capabilities, content review, request budgets, and restricted operational logs. No online system is risk-free; do not submit media or information that is not needed for the requested video.
6. Your requests
Depending on applicable law, you may request access, correction, or deletion of data associated with your wallet. We may need a wallet signature or order evidence to verify the request. Some records cannot be removed from a public blockchain, and some transaction, safety, or legal records may need to be retained.
Privacy contact
Send privacy questions or requests to support@render402.xyz with “Render402 Privacy” in the subject line. Include your public wallet address or order ID, but never send a private key or seed phrase.