Your information on Take.

Take connects brands and creators to manage content collaborations. This page describes how the current pilot uses information.

Accounts and sign-in

We store your name, email address, and account records. When you sign in with Google, Take requests your basic profile and email to create or identify your account. Take does not request access to your Gmail, Drive, contacts, or calendar. Email passwords are stored as hashes. Session cookies keep you signed in.

Your profile and collaborations

Creator names, locations, categories, biographies, and portfolio links are visible to signed-in members. Published brand briefs are visible to creators. Applications are visible to the campaign’s brand. Submitted videos, collaboration messages, and transaction records are available to the participating brand and creator. Optional M-Pesa phone numbers are private to the account and platform administration.

Storage and service providers

Take runs on Railway and stores account, campaign, message, and video data in PostgreSQL. Google processes information when you choose Google sign-in. Data may be processed outside Kenya by these hosting and authentication services. The current app does not contain advertising trackers or sell profile data.

Payments

Payments in this pilot are simulated. Take does not charge a card or send money to M-Pesa. No payment-provider requests are made.

Retention and your choices

Account and collaboration records remain stored during the pilot until removed by the platform operator. You can edit your profile and log out in the app. To request access, correction, or deletion of your information, contact [email protected]. Requests involving shared collaboration records may require coordination with the other participant.

Google access

You can remove Take’s Google access in your Google Account’s third-party connections settings. Removing access does not automatically delete records already stored in Take; contact the operator to request deletion.