Data use

This page describes how AfroAmplify uses operational data day to day. It sits beside the privacy policy, which covers collection, storage, and rights.

Forms to the desk

Brand enquiries, creator registrations, and lesson requests land in the team inbox. The team accepts a row instead of retyping it. An enquiry is not yet a client record. Marking an enquiry paid can create a private brand link to creators confirmed for that job. Unpaid enquiries have no such link.

Matching and roster

We use city, country, language, channel, availability, and ability to explain the service to match people to briefs. Follower count is not a filter and is not a registration field. The public brand market does not list creators by name; the roster lives on the desk for the team.

Verification and reporting

Data specialists check payable results separately from content approval. Reports separate handoffs, matched signups, first completed actions, and rejection counts and reasons. Rejected records stay out of accepted totals. Approved content alone is not a verified signup.

Payout preferences

Creators tell us how they want to be paid (mobile-money wallet name, or bank transfer in South Africa). We use that only to pay after verification. Instant pay is not offered. We do not use payout fields for marketing.

What we do not use data for

• Selling contact lists.
• Ranking creators by followers.
• Asking creators to hold customer cash or identity documents.
• Publishing a creator on a public directory without the desk flow that controls that.

Processors

Hosting, private blob storage for enquiries, object storage for profile photos, and mail (when enabled) process data for us. See the privacy policy for storage names and contact.

Contact

Questions: chat@afroamplify.com. Related pages: Privacy, Terms, Content use.