Privacy policy
Last updated: March 20, 2026
This page explains how Fluencity currently collects, uses, shares, and retains marketplace data. It is written to match the current product behavior rather than generic boilerplate.
Information we collect
Fluencity collects the account, authentication, profile, application, contract, messaging, attachment, payout, report, and operational data needed to run the marketplace.
That includes identity and contact details, creator profile details such as categories, audience countries, rates, social handles, city or region, organization and membership records, contract and deliverable records, payment and payout records, moderation reports, and notification preferences.
Operational logs, audit events, and error-monitoring data may also be collected to support security, fraud prevention, reliability, and troubleshooting.
How we use data
We use data to create and manage accounts, match brands and creators, power applications and invites, run contracts and messaging, review deliverables, process payments and payouts, handle reports, and enforce platform rules.
Data is also used to support support operations, improve marketplace quality, prevent abuse, and maintain accounting, payout, and compliance records.
Marketing and digest-related preferences are handled separately from core service communications where the product captures those preferences.
Who data is shared with
Information is shared with marketplace counterparties when needed to complete an application, opportunity, contract, collaboration, or payout workflow.
Fluencity also uses infrastructure and service providers for hosting, authentication, database and storage services, email delivery, payments, and monitoring. Based on the current stack, this includes providers such as Supabase, Stripe, Resend, Vercel, and Sentry.
Data may also be reviewed internally by authorized operators for fraud prevention, report triage, payout operations, and support.
Messages, attachments, and reports
Messages, attachments, contract submissions, and reports may be stored and reviewed when needed to support platform operations, disputes, fraud prevention, trust and safety, or legal obligations.
Attachments currently rely on platform upload controls and signed access links. File handling should still be reviewed further before broad public launch.
Retention, security, and controls
Fluencity keeps data for operational, accounting, fraud-prevention, trust and safety, legal, and support purposes for as long as reasonably needed.
Access to administrative tools is role-restricted, and audit logs are used for sensitive operational changes such as report status updates and country-routing changes.
Users should treat the current product as a controlled-launch system. Additional account-access, deletion, and data-export workflows may be added over time.