Platform policies
Privacy and your data
What the application processes, how access is controlled, and the actions available in your workspace.
01 / Platform policies
Data used to operate the marketplace
The application uses account identity and contact details, organization memberships, profile preferences, public social-account references, campaign participation, submitted post URLs, measurement evidence, messages and financial records. Staff review records capture the responsible reviewer and the reason for a decision.
02 / Platform policies
Identity, payments and external providers
Clerk handles authentication. Convex stores application records. The platform privately collects identity evidence for human staff review. Payment processors handle payment and payout destination details; the application stores processor references and payment status. Authorized measurement providers supply ownership and view evidence. Optional AI briefing classification requires campaign opt-in.
03 / Platform policies
Who can see your records
Account and workspace access is checked in backend functions. Clients see their authorized campaign results; contributors see their own submissions and earnings. Platform roles provide access for specific operational duties. Private social token references are excluded from customer views. Public campaign data uses a deliberate limited shape.
04 / Platform policies
Optional website measurement
When enabled, optional Vercel analytics and performance measurement require acceptance in privacy preferences. The application excludes authentication and private workspace routes and removes query strings from permitted public-page URLs. Do Not Track and Global Privacy Control are respected. You can change your measurement choice from the site.
05 / Platform policies
Export and erasure
Your workspace provides a JSON export and an account-erasure request. Large exports use paginated categories. Erasure is reviewed for open campaign/payment obligations and processor deletion. Required financial records may be retained after other data is redacted; the implemented request records a retention deadline. The current cleanup is not yet a complete financial-retention lifecycle.
06 / Platform policies
Policy approval and privacy enquiries
A complete production privacy notice still requires the operator identity, contact details, approved lawful bases, retention schedule, processor agreements and applicable rights information. Use workspace support to raise a request or question. These operational details must be reconciled with the approved notice before launch.