Privacy built around local files.

Ped files stay local

Ped files are processed on your device and are not uploaded to PedForge.

Model files, textures and generated geometry remain in your browser storage or in a folder you choose. PedForge may ask you to reconnect the original files when a local working copy is unavailable.

Account and project records

When you sign in, PedForge stores your account identifier, your Discord membership status in PedForge’s server (whether you are a member with the Verified role, and when that was last checked), your referral code and the account that invited you, project names, timestamps, local-availability status, edit events, credit entries, export receipts and export reports (whether an export succeeded or what went wrong, how many garments it had and how long it took, never the files themselves). Once you buy something, it also stores your Stripe customer id. These records help reconnect projects, pay each bonus once and prevent duplicate charges; they do not contain ped or texture binaries.

Local browser storage

Autosaves, working files and up to 25 project history points may be stored in your browser. Clearing site data can remove that local copy.

Accounts and payments

Discord provides sign-in information, and PedForge’s Discord bot reads whether you are a member of PedForge’s server and have the Verified role. Stripe is the payment processor: it handles checkout and card details, and PedForge receives purchase status, transaction references and your Stripe customer id rather than card details. Final retention periods must be confirmed before live payments are accepted.