Privacy Policy

What Fludge does

Fludge is an AI creator platform that lets you upload images, train a personalized subject or LoRA style model, generate new images, manage your gallery, and optionally connect YouTube to upload videos and view analytics.

Personalized training note: Any “training” features in Fludge refer to user initiated, per user personalized models based on content you upload to Fludge. We do not use data obtained via Google/YouTube APIs to train generalized or foundational AI models.

Fludge is a multi tenant service. Your data is scoped to your user account. Fludge also supports multiple creator personas under one account (creator identifiers used to organize and filter content and settings).

Information we collect

Account and profile information

• Email address and authentication data for sign in (for example, magic link or one time passcode).
• Profile and settings information, such as display name, language, timezone, theme, and feature preferences.
• Creator persona information (for example, creator name and creator identifiers).

User content and content you generate

• Images you upload (including any metadata included in the file, such as EXIF metadata, if present).
• Generated images, thumbnails, videos, and other media you create or store in Fludge.
• Prompts, parameters, and related metadata used to provide generation, editing, or training features (for example, seeds, aspect ratios, trigger words, and provider metadata).
• Workflow artifacts and project assets you create in Fludge, such as scripts, captions, transcripts, edit manifests, and related files.

YouTube connection and YouTube API data

If you connect a YouTube channel, we may process and store information such as:

• Channel identifiers and basic channel metadata (for example, channel ID and channel title).
• Upload actions you initiate (for example, uploading a video, setting metadata, uploading a thumbnail).
• Analytics information retrieved via YouTube APIs, such as KPIs, retention metrics, and traffic sources, which we may store in Fludge to show you analytics over time.

Billing and payment information

• Subscription plan status, credits, and billing related identifiers.
• Stripe customer and subscription identifiers.

Payment card details are processed by Stripe and are not stored by Fludge.

Technical, usage, and security information

• Request metadata and logs needed to operate and secure the Services (for example, timestamps, error logs, and basic request logs). Our hosting and infrastructure providers may also process IP address and user agent as part of normal web delivery and security.
• Operational records such as job status, workflow identifiers, rate limiting events, and idempotency records.

Marketing and communications data

• Subscription status and marketing preferences.
• Email engagement data, such as whether an email was opened and whether links were clicked (where supported by the recipient's email client).
• Tagging and segmentation data used to organize audiences and tailor communications.

How we use information

We use personal information to:

• Provide, operate, and maintain the Services, including authentication, storage, and account management.
• Process uploads, training, and generation requests, and return outputs to you.
• Run background workflows that support long running tasks (for example, training, generation, post processing, and cleanup).
• Process payments, subscriptions, credits, fraud prevention, and accounting.
• Provide support and respond to requests.
• Protect the Services, prevent abuse, enforce policies, and troubleshoot issues.
• Comply with legal obligations and protect rights, safety, and security.

How we share information

We do not sell personal information.

We share information with service providers that help us operate the Services. These providers process information on our behalf under contract and only as needed to provide their services to us.

Service providers may include:

• Hosting and infrastructure providers (for example, Vercel).
• Authentication, database, and storage providers (for example, Supabase).
• Workflow orchestration providers (for example, Inngest).
• Payment providers (for example, Stripe).
• AI inference providers (generation and analysis): We may share prompts and user provided content with AI providers to generate outputs you request (for example, text generation, image generation, transcription, video generation, avatar rendering, or music generation), such as OpenAI, fal.ai, BFL API, HeyGen, Mubert, and Google Gemini.
• Model training providers (personalized models): Where Fludge offers user initiated personalized training, we use providers and infrastructure that process only the user’s uploaded training data for that user’s model. We do not use Google/YouTube API data for this purpose.
• Amazon Web Services (AWS), including Amazon Simple Email Service (SES), for email delivery and handling delivery and engagement events (for example, opens and clicks).
• Google and YouTube APIs when you connect YouTube and use YouTube related features.

For example, when we use OpenAI's API as an AI inference provider, OpenAI states that it does not use API data to train or improve its models unless the customer explicitly opts in. We do not opt in to such training.

We may also share information:

• If you direct us to do so (for example, when you choose to connect YouTube or upload content).
• To comply with law, respond to lawful requests, or protect rights, safety, and security.
• In connection with a business transaction (for example, a merger or acquisition), as permitted by law.

YouTube API Services and Google user data disclosures

This app uses YouTube API Services

Fludge uses YouTube API Services to enable YouTube connection, uploads, and analytics features.

YouTube Terms of Service: https://www.youtube.com/t/terms

Google Privacy Policy: https://policies.google.com/privacy

Your control over YouTube data and access

You can disconnect YouTube inside the app. You can also revoke Fludge's access through Google's security settings page: https://security.google.com/settings/security/permissions

If you revoke access through Google's security settings page, we will delete YouTube API data (including any data derived from it) in Fludge that was accessed or stored based on that authorization.

Disconnect and Delete YouTube Data

Fludge provides "Disconnect" and "Delete YouTube Data" controls.

When you disconnect or request deletion, we revoke tokens and remove stored YouTube tokens from Fludge. We also delete YouTube API data (including any data derived from it) stored in Fludge as described below.

"Delete YouTube Data" deletes YouTube API data (including any data derived from it) stored in Fludge. It does not delete content on YouTube itself. To delete content on YouTube, you must use YouTube or other authorized tools.

Validity checks

We periodically reconfirm that authorization tokens remain valid. If tokens cannot be refreshed, we will disconnect the channel and delete YouTube API data (including any data derived from it) stored in Fludge that was accessed or stored based on that authorization.

Google API Services User Data Policy and Limited Use

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

We use Google user data only to provide user facing features that you request and that are prominent in the Fludge user interface, such as connecting your YouTube channel, uploading content you choose to upload, and showing analytics.

We do not use Google/YouTube user data obtained via Google APIs (including any data derived from it) to create, train, or improve any generalized, foundational, or frontier AI/ML models. We use such data only to provide user facing features that you request, and only as permitted by the Google API Services User Data Policy and Limited Use requirements.

We do not use Google user data for advertising purposes, and we do not sell Google user data.

Marketing communications

We may send you marketing emails, for example product updates, tips, and offers. We may use email tracking technologies (such as pixels and tagged links) to understand delivery and engagement, for example whether a marketing email was opened or a link was clicked, and to improve our communications. You can opt out at any time by using the unsubscribe link in a marketing email, or by contacting us at support@fludge.io.

Even if you opt out of marketing emails, we may still send you non marketing emails that are necessary to provide the Services, such as account, security, billing, or transactional messages.

Cookies and local storage

We use cookies and similar technologies that are necessary to run the Services, such as:

• Essential authentication and session cookies.
• A YouTube OAuth state cookie used to help protect the OAuth flow and prevent fraud.

We also store certain preferences locally in your browser (for example, theme settings in local storage).

We do not use third party advertising cookies. We use Vercel Web Analytics to understand page views and usage, and it does not use third party cookies.

Data retention

We retain personal information for as long as necessary to provide the Services and for legitimate business purposes, such as security, troubleshooting, and compliance.

Our retention goals by category include:

• YouTube tokens and YouTube API data (including any data derived from it): retained while your YouTube connection is active. After you disconnect, revoke consent, request "Delete YouTube Data", or delete your Fludge account, we revoke access and delete YouTube API data stored in Fludge as soon as possible and within 7 calendar days.
• Training intermediates (for example, training ZIP files): automatically deleted about 7 days after creation.
• Job and workflow debug payloads: about 30 days, after which we delete or minimize them. These payloads are designed to exclude YouTube API data (and data derived from it). If any such data is captured, it is deleted within 7 calendar days as described above.
• Idempotency records: about 7 days.
• Rate limiting events: about 30 days.
• Stripe webhook event payloads (raw): about 60 days, after which we delete or minimize them.
• Provider usage records (cost and performance metadata): about 90 days.
• User content (uploads, generated media, models, projects): retained until you delete it or request account deletion. After deletion requests, we aim to remove data promptly and complete storage cleanup within a reasonable period (commonly up to 30 days), subject to backups and legal obligations.
• Marketing email engagement data and tagging: retained while you are subscribed to marketing communications. If you unsubscribe, we retain a record of your opt out to honor your preference and help prevent future marketing sends.

If you request deletion, we may retain certain information as required by law or for legitimate purposes such as fraud prevention, security, and accounting.

Account deletion

You can delete your Fludge account in the app settings.

When you delete your account, we will delete or deidentify personal information associated with your account, including your stored content, subject to the retention and legal exceptions described above. We aim to complete account deletion within a reasonable period (commonly up to 30 days), and we will delete YouTube API data stored in Fludge within 7 calendar days as described above.

Security

We use reasonable administrative, technical, and organizational safeguards designed to protect information. These may include access controls, encryption in transit (HTTPS), database access policies, token protection for connected integrations, rate limiting, and other measures.

No method of transmission or storage is completely secure. We cannot guarantee absolute security.

Your choices and rights

You may be able to:

• Access and update certain profile information in the app.
• Delete certain content you uploaded or generated.
• Disconnect YouTube and request deletion of YouTube API data stored in Fludge.
• Delete your Fludge account in the app settings.

You can also contact us to request access, deletion, or export of personal information by emailing privacy@fludge.io. We may need to verify your request.

California privacy rights

If you are a California resident, you may have rights under California privacy laws, depending on applicability, including rights to know, access, delete, and correct certain personal information.

We do not sell personal information, and we do not share personal information for cross context behavioral advertising.

International transfers

We are based in the United States, and our service providers may process data in the United States and other locations. If you access the Services from outside the United States, your information may be transferred internationally.

Children

Fludge is not intended for children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us and we will take appropriate steps.

Changes to this Privacy Policy

We may update this Privacy Policy from time to time. We will update the "Last updated" date and, if changes are material, we will provide additional notice within the Services or as required by law.

Contact us