Flayr doesn't train on you.
We do not fine-tune, embed, cluster, or otherwise use your brand content, chat history, generated output, or uploaded assets to improve the product for other users. You're a customer, not a training dataset.
Privacy Policy
Last updated: October 22, 2026
Your data stays yours
Flayr's three-layer privacy commitment. Last provider verification: 2026-04-11.
Our model providers don't train on you either.
Every AI call Flayr makes routes through Anthropic, Google Vertex, or OpenAI commercial APIs — all three contractually commit to not training on your inputs. Links to each provider’s own data-governance page are listed below.
You control retention.
Brand profiles, generations, and chat history can be deleted at any time from settings, with verified deletion across Convex, file storage, and any CDN cache. Your data is yours — including the right to remove it.
Provider citations
- Anthropic Claude APIverified 2026-04-11
“Anthropic will not use your Inputs or Outputs to train our models.”
Read the full terms → - Google Vertex AIverified 2026-04-11
“Google does not use your prompts or responses to train its models without your permission.”
Read the full terms → - OpenAI APIverified 2026-04-11
“Data submitted through our API will not be used to train or improve our models.”
Read the full terms →
Deliberate carve-outs
Without these, the three-layer commitment would overstate what Flayr does. Here's exactly where the line sits:
- Voice clone training uses your voice to build your clone.When you opt in to voice cloning, Flayr fine-tunes a per-user voice model on your recordings. That clone is stored only in your account, is never aggregated with anyone else's recordings, and is not used to train any shared model.
- Generation outputs are not used to improve the product.Competitors sometimes feed generated content back into training via "feedback loops." Flayr does not. The outputs you keep belong to you; the outputs you delete are deleted.
- We do log for debugging — but not for training.Error traces, API request metadata, and usage metrics are logged to Sentry and PostHog so we can fix bugs and size infrastructure. Those logs are never used to train any model, and they're scrubbed of brand content before long-term storage.
Flayr is operated by Firefly Events. This policy explains how we handle information when you create an account, connect a service, or use Flayr to create and publish content.
What we collect
Account information you provide (name, email, organization) through Clerk, content you generate or upload, usage metrics to improve the service, and billing information processed by Autumn.
Google sign-in information
If you choose to sign in with Google, Clerk receives your Google account identifier, name, email address, and profile picture to authenticate you. Flayr stores account information, including your name, email address, and profile picture, in Convex to maintain your profile and associate your saved work and organization memberships with your account.
Google sign-in requests only your basic identity, email address, and profile. It does not grant access to your Gmail messages, Google Drive files, calendar, or YouTube account. Connecting another service is a separate action with its own permissions. You can review or revoke Flayr's Google access in your Google Account's third-party connections.
How we use it
To provide the service, personalize AI generation, send product updates you've opted into, and comply with legal obligations. We do not sell your data.
Third-party services
We share data with: Clerk (auth + billing), Convex (database), PostHog (analytics), Vercel (hosting), Sentry (error monitoring), and AI providers (Anthropic, Google, OpenAI, Zernio) when you generate content. For speech-to-text for chat dictation, we send your audio clip to OpenAI, routed through Vercel AI Gateway. Audio clips are sent for transcription only and are not stored by Firefly Events after the transcript is returned.
Shopify stores
If you connect a Shopify store, we read your products to make sample posts. Your sample posts stay in your Library after you uninstall the app. The store data they were made from is deleted, as Shopify requires.
Google data sharing and protection
Google sign-in information is processed by Clerk for authentication, Convex for account storage, and Vercel for hosting the service. We do not sell this information or use it to train AI models. Access to account data is subject to authentication and authorization checks; connections to our hosted service use HTTPS.
Flayr's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Data retention and deletion
We retain account information and saved content while you use Flayr and to preserve your saved work. Revoking Google access stops future Google authorization but does not delete information already stored in Flayr. Deleting your sign-in account disables account access; saved posts and other stored data are not automatically erased by that action.
To request deletion of retained account information, Google sign-in information, or content, contact privacy@flayr.social. Tell us which account and data your request concerns so we can verify the request and address it.
Your rights
You can manage your profile in account settings. To request access, export, correction, or deletion of your stored data, contact privacy@flayr.social with your request.
Questions
Reach us at hello@flayr.social.