Information
Your data in Pedify
How the current studio handles account information, local projects and operations you choose to send to the server.
Updated 12 October 2026
Controller and contact
Zewinu AB, organisation number 559395-8266, Box 2541, 116 74 Stockholm, Sweden, is responsible for Pedify’s processing of personal data. Contact [email protected] for privacy matters. Product support is on Discord. [email protected] sends automated account messages.
Accounts and security
For email accounts, we store your email address, display name, account identifier, creation time and a salted password hash. We use this information to provide the account you request. Sessions use an essential sign-in cookie and server-side token hashes. The normal session lifetime is 14 days; password-reset links expire after one hour. Security checks use connection information such as your IP address to limit abuse.
Discord sign-in
If you choose Discord sign-in, Discord supplies your user ID and display name. We store these to identify your Pedify account and any connection you explicitly choose to make to an existing account. Discord-only accounts have no email address in Pedify. OAuth uses a separate essential cookie valid for five minutes; provider access and refresh tokens are not stored.
Files in your browser
The editor keeps local projects and preferences in browser storage, including IndexedDB. Opening a file locally is different from submitting an operation to the server. Keep a separate project copy before clearing browser data. A local project is not automatically a server backup.
Reports and history
When you submit a check or an export report, we can store the account, project or file names, sizes, diagnostic findings, operation status and timestamps. The server also records credit operations and order references. These records support the operation you requested, troubleshooting, fraud prevention and any applicable accounting obligations.
Optional AI processing
AI planning can send your prompt, selected texture preview, reference images and editing context to Anthropic. Image generation can send the prompt, texture crop, UV guide and selected references to Runway. This happens when you invoke those tools; it is not a general upload of every local project file. Results can be cached temporarily to complete or retry the operation.
AI moderation in the community
This section applies when community features are enabled.
When you use the community, profile text, images and DM requiring review are sent to Anthropic for automated safety moderation. Anthropic processes the data on Pedify's behalf. Profile text includes aliases/handles, display names, bios, links and gallery titles. Post titles, descriptions, tags, listing content and file metadata (MIME type, size, file names and archive entries) may also be sent with selected image data. For DM, this covers the first message in a new contact and reported messages with limited conversation context. Other DM safety checks use behavioural signals, rather than the entire chat. Suspected child-safety material from a report is not sent to AI and goes directly to the human queue. Child safety, threats, rights notices and appeals always receive human review.
The community's own storage is in the EU. Anthropic may process data outside the EEA; such processing may take place in the United States, outside the EU/EEA, under the European Commission's standard contractual clauses. Pedify does not order any training of AI models using the data. AI processing is not promised to remain exclusively in the EU. DM are not end-to-end encrypted. Deleted content is hidden immediately and purged after 30 days. Report evidence and moderation decisions are retained for 12 months. An unresolved child-safety hold then retains only its status and source references (version IDs and file hashes), without report text or private evidence, until human review releases the material.
Payments, delivery and support
Stripe and Swish process payments when their checkout is used. Pedify stores the order, account, amount, status and provider references; card details are entered with the payment provider. Account email is sent through our self-hosted mail service. Cloudflare handles website delivery and connection data. If you use Discord for support, Discord receives your messages under its own policies.
Purposes and legal bases
We process account and requested operation data to provide our agreement with you. Keeping the service secure and investigating failures serves our legitimate interests in reliable operation and preventing abuse. Records needed to meet legal obligations are processed on that basis. Optional data is used for the operation you choose, rather than for an unrelated purpose.
Storage and international processing
Account and operation records are kept while needed to provide the account, resolve an issue, establish a claim or meet legal obligations. Deletion requests are assessed against those purposes. Session and reset tokens stop authorising access after their expiry; local project retention is controlled by your browser. Providers may process data outside the EEA. Contact us for details of a particular transfer and the safeguards applicable to it.
Your rights
You can request access, correction, erasure, restriction or a portable copy where applicable, and object to processing based on legitimate interests. Send privacy requests to [email protected]; we may need to verify your identity. You can also complain to the Swedish Authority for Privacy Protection, IMY.
Provider information
Stripe, Swish, Anthropic, Runway, Cloudflare and Discord publish information about their own services. Contact us if you need information specific to Pedify’s processing.