Privacy policy
Last updated: March 20, 2026
This page explains how Fluencity collects, uses, shares, and retains marketplace data.
Policy status
Active and enforced.
These policies govern how Fluencity operates. They may be updated as the platform evolves. Material changes will be communicated through the platform or by email.
Section 01
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.
Section 02
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.
Section 04
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 are managed through platform upload controls and signed access links. File handling follows standard security practices and is reviewed on an ongoing basis.
Section 05
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.
Additional account-access, deletion, and data-export workflows may be added over time as the platform evolves.