Privacy Policy

Back to Home

Effective Date: October 12, 2026

Publisher: Meigen Creative L.L.C.

Address: 30 N Gould St Ste R6, Sheridan, WY 82801, United States

This Privacy Policy applies to the AI Image Gallery and AI generation services provided by MeiGen (referred to as "we" or "the Service") on our website at meigen.ai and in our official MeiGen mobile applications for iOS and Android, and through our account-linked ChatGPT and Codex plugin. We understand the importance of personal information to you and will make every effort to protect your personal information securely and reliably.

ChatGPT and Codex Account Linking

When you connect MeiGen, we store your account identifier, the connected client, approved permissions, authorization expiry and revocation status. With your permission, OpenAI receives an account identifier and your verified email through the account-linking process. Your password and internal generation credentials are not returned in tool results.

When you request generation through the plugin, OpenAI sends MeiGen your prompt, model settings, reference image, video or audio URLs, and a request identifier used to prevent duplicate submissions and recover the original task. MeiGen and the model providers and processing partners described below process these inputs. Tool results sent back to OpenAI contain the request identifier, task status, model and media type, output URLs, and the reported credit cost or refund status, and, when you request a balance check, the purchased credits available to this integration. Daily free credits are excluded. OpenAI handles its copy of conversations, inputs and tool results under its own terms and privacy policy.

For OAuth connections, we also store the client identifier or fingerprint, client name, connection channel and approximate last-use time to understand which integrations are used. This usage summary does not store individual tool calls or their contents.

With separately approved upload permission, you can select an image, video or audio attachment or a direct public HTTPS media URL. The host may supply a temporary download URL and file identifier. MeiGen downloads the selected material, validates its format, size and model-specific limits, and stores it on Cloudflare R2 with a public URL accessible to anyone who has the link; it is not automatically published in the gallery. Images may be resized and have embedded image metadata removed. Video and audio are stored without re-encoding or metadata removal. OAuth-prepared media are scheduled for cleanup seven days after their latest upload; cleanup is asynchronous and does not remove cached or third-party copies. Accepted generations retain separate, durable image reference copies for history and reuse; imported video and audio remain temporary and may no longer be available for reuse after cleanup. Contact [email protected] to request removal. Do not upload material you do not intend to share with the service. Search permission uses your account’s gallery search allowance. Search text is processed by our embedding provider (Cohere) and, when translation is enabled, Alibaba Cloud Qwen-MT. Supabase stores search diagnostics including query text, result count and timing; these are separate from generation records. A daily scheduled task deletes search diagnostics older than 90 days, so removal can occur at the next daily run. Search terms may also appear in request URLs processed in hosting and security access logs; the technical-log recipients and periods below apply. Shared Upstash caches can contain search text, translations and results: ordinary result caches last up to two hours per write; paginated result snapshots and translations last up to 24 hours per write. Search diagnostics do not carry account identifiers, so we cannot locate them by account. Contact [email protected] with specific search terms for assistance; otherwise the retention periods above apply. Do not include confidential information in searches. Workflow permission covers background removal, upscaling, background replacement, marketing posters and product-detail images; workflow briefs, selected modules, source image URLs and per-module result or refund states are processed for those operations. These new permissions are not automatically added to existing connections.

With separate saved-character read permission, the connected app can retrieve your character names, identifiers, preview links, preparation status and reference tokens. When you request a supported generation using a character, MeiGen retrieves the character assets owned by your account and sends the selected references to the model provider. This permission does not allow creating, editing or deleting characters. Existing connections need new consent; legacy API keys cannot access saved characters. Revoking access does not remove copies already received by the host or provider.

Account-linking permission expires after 30 days unless revoked earlier. Pending consent expires after 10 minutes, authorization codes after 5 minutes, and unused authorization records and billing identities after 5 minutes. Refresh credentials rotate; an encrypted retry response is retained for at most 30 seconds. Authorization and refresh state is stored by Upstash in a dedicated Redis database in the United States. This state, including consumed or revoked state needed to prevent replay, expires no later than the original 30-day authorization expiry. The billing identity and related transaction records are retained with your account and billing history under the retention and account-deletion provisions below.

The independent plugin adapter logs event category, tool name, status code and submission state, without prompts, media URLs or tokens. The MeiGen backend processes the same request and may record task/request identifiers, model metadata and diagnostic events. Some provider error diagnostics may include excerpts of submitted content or media URLs returned by the provider; these are used only for troubleshooting. Hosting and security access logs may contain IP addresses, request timestamps and browser information. These logs support troubleshooting and abuse prevention. The adapter and Web backend are hosted by Vercel. Cloudflare provides delivery and security services for MeiGen endpoints routed through its network; the plugin endpoint uses Cloudflare DNS only. The log recipients and operational retention periods are listed in Section 4. To request access to or deletion of logs associated with your account, contact [email protected]; we verify ownership before processing the request.

With separately approved library read permission, the plugin can retrieve your favorites, boards and completed generation history, including prompts, notes, model information and media links. These selected results are returned to OpenAI to answer your request, such as finding an earlier prompt or using relevant favorites as creative references. Library write permission allows saving selected items to your favorites and private boards at your request. Saving does not publish an item to the gallery or a public board. Existing connections do not automatically receive these permissions. Removing an item in MeiGen does not remove copies already received by OpenAI.

You can revoke future plugin access on the Connected apps page while the integration is available; if it is suspended, contact [email protected] to manage retained authorization data. Disconnecting does not cancel an accepted generation, delete its prompt or media, or remove copies already received by OpenAI or model providers. You can manage generation records in MeiGen or request deletion of reference video, audio and generated media through [email protected]. Account deletion is available at Delete account. Provider copies follow the respective provider policies described below.

1. What Information We Collect

Our Commitment: We only collect the minimum information necessary for service operation

  • Email Address: We collect your email address for account login, security alerts, transactional emails (such as billing confirmations), and marketing communications about features, promotions, and updates. You may opt out of marketing emails via the unsubscribe link in each email; you will continue to receive service-related emails;
  • IP Address: We log signup and access IP addresses for security, fraud prevention, and abuse mitigation;
  • User Identification: We only record user names/IDs for account management and service provision;
  • Purchase Records: We record payment transactions and credit consumption for billing, delivery verification, and refund processing. Purchases made on the website are processed by our payment processors; purchases made inside the iOS or Android app are processed by Apple's App Store or Google Play — we never receive your card details, only a transaction confirmation used to credit your account;
  • App and Account Security: Our apps can use Apple App Attest and Google Play Integrity to verify genuine app requests and protect free benefits from abuse. We process attestation public keys, verification counters, app/device integrity verdicts, and associations with your sign-in session. Apple and Google receive an opaque request challenge; we do not include your prompts or reference images in it. Private attestation keys remain on your device. We may also receive signed account-security events from Apple or Google and revoke affected sign-in sessions;
  • Camera and Reference Editing: Camera access is requested only when you choose to take a reference photo. Selecting, cropping, rotating, and reviewing a reference happens on your device before you confirm it for the existing upload flow. This still-photo feature does not request microphone access;
  • Uploaded Images: Reference images you select are stored to prepare and perform the requested operation. Stored files can have public URLs; anyone with a URL may access the file. They are not automatically published in the gallery;
  • Generated Images: Generated images and their URLs are stored to deliver your requested results. Record deletion and physical media cleanup are separate; see Section 4;
  • Indexed Content: We index publicly shared AI artwork from third-party platforms (currently X/Twitter) via their official APIs or public endpoints to power our prompt gallery. The original creator retains all rights to their content. Creators or rights holders can request removal by emailing [email protected];
  • Prompts and AI Assistant Logs: The text prompts you submit are stored alongside your generations so you can revisit and reuse them. For AI assistant features (AI Edit, image-to-prompt, prompt enhancement), we additionally keep detailed call logs (input, instruction, model output, timing) for up to 90 days to debug issues and improve the system. This content is not used to train our own AI models; transmission to third-party AI providers for inference is described in Section 2;
  • Technical Logs: Service operation and security logs can contain IP addresses, timestamps and browser information used for security and troubleshooting.
  • App Crash Diagnostics: When the iOS or Android app encounters an error, it saves a crash report in the app's temporary storage on your device, which is not included in device backups, and sends it to us: errors shown on an in-app error screen are sent right away, and other errors are sent the next time the app opens. A report contains the error type and message, code stack locations, the app screen route (without content identifiers), app version and build, operating-system version, device brand and model, time since launch, and a random identifier that the app generates and stores on your device and that is not linked to your account (the same identifier is used for anonymous usage statistics and may be carried over when device data is backed up, restored or transferred). Before sending, the app removes recognizable email addresses, access tokens and API keys, and the query and fragment parts of full URLs (those with a scheme such as https://). This redaction is limited: error messages and stack traces can still contain fragments of text the app was handling when the error occurred. The app does not add your account ID, prompts or images to crash reports as separate fields. Crash reports are stored in Supabase and used only to find and fix app defects. IP addresses are not written to the crash report store; infrastructure logs that may contain IP addresses are handled as described under Technical Logs;

Clear Statement: We do not share or sell your email to third parties for marketing. We do not request precise location, names, phone numbers, or ID numbers; IP addresses are recorded for security and abuse prevention purposes.

2. How We Use Collected Information

  • Provide Services: Usage records are used for normal service operation and accurate credit deduction;
  • Service Optimization: Anonymized usage statistics help us improve functionality and performance;
  • Technical Support: Technical logs help us troubleshoot and fix service issues;
  • Data Protection: We do not sell your email or generated content to third parties for their own marketing. We may use your email for product updates and marketing emails, which you can opt out of at any time.

Important Commitment: We do not sell user profiles to third parties for their own marketing. We may use account behavior signals (such as registration recency and feature usage) internally to determine which product updates or promotional emails to send. You can opt out of marketing emails at any time via the unsubscribe link in each email.

Third-Party AI Processing: To generate images and videos, the prompts you write, reference images, videos, and audio you provide, and character assets you create are transmitted to third-party AI model providers and processing partners for inference. Each provider handles data according to its own privacy and data retention policies; we do not authorize them to use your content for their own marketing. In our mobile apps, we ask for your explicit consent before your first generation. We recommend avoiding submitting confidential information.

3. Information Sharing and Disclosure

Our Commitment: We never sell your identity, email, or generated content to third parties for their own marketing

  • Basic Principle: We do not sell your account identity (email, name) or generated content to third parties for their own marketing;
  • Service Providers: We use third-party cloud infrastructure, payment processors, AI model providers, and email delivery services (such as Resend) to operate the service. We do not use third-party ad networks; our native iOS and Android apps display no third-party ads, and the only ads on our mobile web gallery are directly-contracted sponsored cards (see below). Google Ads receives a hashed, pseudonymized email solely for conversion measurement on the website. Each provider handles data under its own published terms and privacy policies; we do not authorize these partners to use your data for their own marketing;
  • Optional Apple Refund Information: With your separate permission in the iOS app's Profile settings, we may send Apple the delivery status of an App Store credit purchase and, only when our records support it, its consumption percentage to help Apple assess refund requests. This report does not include your prompts or images. Permission is optional and can be withdrawn for future reports without affecting sign-in, purchasing, or generation; Apple controls the refund decision;
  • Direct Sponsorships: Our mobile web gallery may show a clearly labelled sponsored card from an advertiser we work with directly. Tapping it takes you to the advertiser's own website through a redirect on our servers, where we record the click (time, which creative and language, and your browser's user-agent) for our own billing and reporting. We do not share your identity, email, or account data with the advertiser, and sponsored cards are never personalized to you. These click records are kept for up to 24 months and are then removed by a daily cleanup job;
  • Legal Requirements: Only when explicitly required by law may we need to cooperate with law enforcement agencies.

4. Data Retention Policy

You can delete records through the service. Removing a record does not necessarily remove its underlying media file or copies already received by others; media retention is described below.

  • Uploaded References: Images, videos and audio prepared through OAuth upload permission are scheduled for automatic storage cleanup seven days after their latest upload, even if no generation is submitted. Cleanup is asynchronous. Image references used by accepted generations are copied to durable storage for history and reuse; those image copies have no fixed automatic expiry. Imported video and audio remain temporary, including after generation. Storage cleanup is not a guarantee that a public URL or cached copy becomes inaccessible at the same time. Other existing reference uploads have no fixed automatic storage expiry; contact [email protected] with the relevant URLs to request removal. Deleting a generation or disconnecting an integration does not immediately delete these files;
  • Generated Content: Deleting a generation removes its record from your account and requests deletion of the associated stored output and derivatives. Failed storage cleanup can be retried asynchronously. This does not automatically delete separately uploaded reference files, gallery publications or copies held by others;
  • Indexed Content: Publicly indexed AI artwork remains available until the creator requests removal by emailing [email protected];
  • Prompts: Prompts you submit are stored alongside their corresponding generations and are deleted when you delete the generation;
  • AI Assistant Logs: Detailed logs from AI Edit, image-to-prompt, and prompt enhancement calls (inputs, model outputs, timing) are retained for up to 90 days and then automatically purged by a scheduled job;
  • App Crash Reports: App crash reports are retained for up to 90 days and then deleted by a daily scheduled task, so removal can occur at the next daily run. Crash reports have no account identifier field, so we cannot locate them by account;
  • Account Data: Only essential account information (email for login) is retained for service provision;
  • Technical Logs: Vercel processes our application and access logs, including request identifiers, status, timing, IP addresses and browser information, for troubleshooting and abuse prevention. Our current Pro plan makes runtime logs available for up to 1 day; Observability Plus and external Log Drains are not enabled. Vercel firewall traffic is viewable for up to 24 hours. Cloudflare processes access and security data for proxied MeiGen endpoints: security events are available for up to 24 hours and sampled security analytics for up to 7 days. We have no Cloudflare Logpush export configured. These periods describe the operational logs available to us; service providers may separately process security or legal records under their own privacy policies.

Data Recovery: Save important results before deleting records. Deletion of records is distinct from physical media cleanup. Cached or downloaded copies and copies held by OpenAI or model providers may remain outside our control.

5. Data Security Protection

  • Technical Security: We use industry-standard encryption technology to protect all data transmission and storage;
  • Access Control: Strict limits on data access permissions, only necessary technical personnel can access service data;
  • Data Minimization: We only collect the most basic information necessary for service operation;
  • Regular Audits: Regular security assessments and system updates to ensure data security;
  • Cross-Border Data Transfers: Our service operates on cloud infrastructure primarily located in the United States. By using the Service, you acknowledge that your data is transferred to and processed in the United States and other jurisdictions where our service providers operate;
  • Mobile Sign-in Storage: Mobile sign-in sessions are encrypted locally using a key held in the iOS Keychain or Android Keystore. Signing out removes the stored session. Security verification records support replay prevention; session associations are removed when the associated sign-in session is deleted;
  • Cookies and Local Storage: We use essential cookies and browser local storage for session management, language preferences, and security. We may also use analytics and advertising cookies to measure service performance and conversions. By using the Service, you consent to such use.

6. Your Rights

We minimize the personal data we collect. You have the following rights regarding data we hold about you:

  • Service Control: You can stop using our services at any time;
  • Self-Service Deletion: You can delete individual generations, favorites, and boards through the service interface. Generation deletion also requests cleanup of its stored outputs. For separately uploaded reference files or cleanup assistance, contact [email protected] with the relevant URLs; the retention and third-party-copy limits in Section 4 apply;
  • Account Deletion: You can permanently delete your account and associated personal data yourself at meigen.ai/account-deletion, or in the mobile app via Profile → Delete Account. Deletion is immediate; community submissions that were accepted and published to the public gallery remain there in anonymized form ("MeiGen Community", see Terms §5.5), and payment records are retained in an archived, identity-disconnected form as required for tax and accounting compliance. If you cannot sign in, email [email protected] and we will process the request within 30 days;
  • Data Access: You can view your generation records on your profile page. For a complete copy of data we hold about you, email [email protected];
  • Data Correction: To correct inaccurate personal data (such as changing your account email), email [email protected];
  • AI Assistant Log Deletion: AI assistant call logs are automatically purged after 90 days. To request earlier deletion of logs associated with your account, email [email protected];
  • Marketing Opt-Out: You can opt out of marketing emails at any time via the unsubscribe link in each email; service-related emails will continue;
  • Service Transparency: You have the right to understand our data processing methods.

7. Policy Updates

We may revise this Privacy Policy from time to time based on business development and changes in laws and regulations. When this Privacy Policy changes, we will display the updated content through prominent positions on the website or push notifications.

8. Contact Us

If you have any questions, comments, or suggestions about this Privacy Policy, please contact us at: [email protected]