Privacy Policy

1. Data the current product handles

• Account data: sign-in email, authenticated user identifier, role, account status, and password credentials managed by Supabase Auth.
• Creator and brand data: profile names, company names, profile images, biography, location/region, topics, social links, creator types, portfolio media, packages, pricing and onboarding/review state.
• Marketplace activity: campaigns, applications, saves/signals, package orders, conversation messages, read state and associated timestamps.
• Safety and consent records: reports, account blocks, and the accepted document type, version, source and time.

2. Why the product uses it

The application uses this data to authenticate accounts, display marketplace profiles and opportunities, save onboarding progress, support creator-brand workflows, deliver messages, maintain read state, enforce access and blocking rules, review reports, and record versioned legal acceptance.

3. Visibility

Profile and portfolio fields can be shown to marketplace participants according to listing and review state. Campaign and conversation data is limited by account role, ownership, participation, and database access rules. Blocking stops new messages but does not automatically erase existing conversation history.

4. Current infrastructure

The current application uses Supabase for authentication, database records and media storage, and Vercel for web delivery. A complete, approved processor/subprocessor list and cross-border transfer disclosure are still required before this shell can be treated as a final privacy policy.

5. Account controls

Users can edit supported profile data, change their password, sign out, review blocked accounts, and request permanent account deletion in the authenticated mobile app. The deletion endpoint verifies the current session and password and deletes only that authenticated Auth user; related application rows configured with database cascades are then removed.

See Delete account for steps and current boundaries.

6. Retention and requests

Exact retention periods, backup expiry, legal-hold exceptions, support identity-verification procedure, and response timelines are not established in this repository. They must be approved and published with a monitored contact route. Until then, use the in-app controls described on Support.

7. Advertising measurement on our website

Advertising disclosure added 28 September 2026. If you accept advertising cookies, our website loads Meta Pixel, provided by Meta, to measure page visits, the first submission of a completed creator application for review, and successfully saved brand enquiries. These signals help us measure and improve advertising on Facebook and Instagram.

Meta receives technical information such as your IP address, browser/device information, page URL, and advertising cookie or click identifiers. Our event parameters describe the action and account type; they do not include your email, name, application text or uploaded files. We do not enable automatic advanced matching in our website code.

You can accept or reject advertising cookies, and reopen Cookie settings on the website or this page at any time to change your choice. Rejecting does not prevent registration or form submission. We do not load Meta Pixel before acceptance or replay conversions that happened before acceptance. Withdrawing consent stops further events and removes accessible Meta cookies on this website; it does not erase data already received by Meta.

We remember your choice in this browser for up to 180 days. After acceptance we also keep a local record for up to 180 days to avoid counting the same creator application twice. Meta cookies may include _fbp and _fbc. See Meta's Privacy Policy and Meta's Cookies Policy for Meta's handling and retention of that information. This describes website advertising measurement; mobile-app tracking is separate.