Privacy, explained plainly.

ClonePlug may handle account information such as your email, profile details, authentication state, and preferences. Email is provided by the authenticated account identity and is not an ordinary profile field.

When you use the product, we handle uploaded faces and other media, transformation and project information, session details, wallet and credit ledger activity, payment or manual crypto deposit records, support conversations, and referral attribution where those features are used.

We use essential cookies or equivalent session storage for authentication, security, and a reliable sign-in experience. Optional analytics or advertising cookies should not be assumed by this baseline policy.

We use this information to provide ClonePlug features, keep private resources scoped to the right account, process and reconcile credit activity, show project history, respond to support requests, prevent abuse, and maintain account security.

Selected features may require carefully limited service providers to process media, authentication, storage, or payments. ClonePlug does not expose provider credentials or unrelated internal implementation details to users.

Saved faces, private proofs, project inputs, and account records are intended to remain accessible only to the authenticated account or authorized operational personnel where support or review legitimately requires it. Do not upload media unless you have the necessary consent and rights.

No policy should be read as a promise that a specific retention period applies. Retention and deletion depend on configured product controls, operational needs, legal obligations, and the state of an account or transaction.

You can manage available profile, security, notification, and account settings inside ClonePlug. You can review project, wallet, payment, crypto, referral, and support records through the relevant authenticated areas. For an account-specific request, sign in and use Help & Support.

Business-specific operator details, legal contact information, and any jurisdiction-specific disclosures must be configured and reviewed before launch; none are invented in this baseline document.