Privacy, without the fog.

Google sign-in

If you choose Google sign-in, Google provides your account identifier, name, email address, verification status and profile picture when available. We store the account link and authentication tokens needed to sign you in and provide access to your Minglyph workspace. We request only basic identity permissions, not access to Gmail messages or Google Drive files.

Google identity and authentication records are stored with our account data on Cloudflare and used for sign-in, account security and support. You can revoke the connection in your Google Account or contact support@minglyph.com to request deletion of your Minglyph account data, subject to the retention requirements below.

What we collect

We collect information you provide when creating an account, including your name, email address, and authentication records. We also store the text, meaning, style choices, visibility setting, generated images, and version history you create in the Studio.

We collect limited technical and security information needed to operate the service, such as request timing, device or browser signals, IP-derived rate-limit keys, error records, and usage events.

• Account and workspace data
• Generation briefs, outputs, and selected visibility
• Credit balances and ledger entries
• Security, abuse-prevention, and reliability data

Browser preferences and draft recovery

We store your language preference in this browser. Studio drafts and pending generation IDs are stored in this tab for refresh recovery, scoped to the current account and cleared on sign-out. When you start Google sign-in from an anonymous Studio, a one-use copy of your draft is kept in this tab for up to 30 minutes so you can continue after returning. Reference image bytes and passwords are not stored in this draft record. Closing the tab clears its session storage.

Product usage measurement

We record visits to selected pages, generation submissions and request outcomes, displayed results, authentication and password-recovery steps and outcomes, artwork download clicks, and checkout starts to understand how the product is used. These records contain a random tab-session identifier, approved page paths and campaign tags, a referring hostname, event time, relevant attempt or generation IDs, and predefined authentication methods, outcomes and error codes. They do not contain your creative text, prompts, email address, payment-card details, or access tokens.

Attribution and recent attempt IDs are stored in this tab; the session resets after 30 minutes of inactivity. We respect browser Do Not Track and Global Privacy Control signals for this measurement. Product events are retained for up to 90 days and removed during subsequent event processing. They are separate from the account, generation, payment, and security records needed to operate the service.

Payments

Dodo Payments acts as the merchant of record and processes checkout, tax, invoicing, refunds, and payment details. Minglyph receives transaction identifiers, purchased package information, payment status, and the account or workspace that should receive credits.

Minglyph does not receive or store your full payment-card number. Dodo Payments processes payment data under its own privacy terms.

How we use data

We use your data to provide accounts, preserve your work and versions, generate images, deliver purchased credits, prevent fraud and abuse, troubleshoot errors, support users, and improve service reliability. We do not sell personal information or generation content.

Private and public work

Signed-in work is private by default unless you choose a public visibility option. Anonymous previews are public and watermarked. Public work may appear in the Minglyph archive and can be viewed by anyone. Do not publish confidential text, personal data, or content you do not have permission to share.

Changing a work item from private to public is your choice. Removing public work from display does not guarantee that copies already downloaded or cached elsewhere disappear.

Service providers

Minglyph uses service providers to operate the product. These currently include Cloudflare for hosting, databases, object storage, security, and AI infrastructure, and Dodo Payments for payments. A model provider may process a generation brief solely to create the requested output.

Providers process data under their own terms and are given only the information reasonably needed for their role. Data may be processed in countries other than your own.

Retention and security

We retain account and private workspace data while your account is active and as reasonably needed for service, security, tax, dispute, and legal obligations. Failed generation artifacts are not intentionally retained as completed work. We may retain transaction and security records after account deletion when required.

We use access controls, signed payment webhooks, private-by-default workspaces, and other reasonable safeguards. No internet service can promise absolute security.

Your choices and rights

You may ask to access, correct, export, or delete personal data, subject to identity verification and legal retention requirements. You can choose whether each generation is private or public. You may also stop using the service at any time.

To make a privacy request, email support@minglyph.com with “Privacy request” in the subject.

Children and updates

Minglyph is not directed to children under 13, and we do not knowingly collect their personal information. If local law requires a higher minimum age, that higher age applies.

We may update this policy as the product or law changes. Material changes will be posted here with a new effective date.