Policy
How we handle your data
Clear rules for collection, use, sharing, and your choices across the Creator Collective platform.
1. Introduction
Creator Collective Media provides a platform for creators to learn, earn, and connect. This policy describes what information we collect, how we use it, and the choices you have.
2. Information We Collect
2.1 Information you provide
- Account and profile: name, email, handle/display name, profile photo, bio, location, social links, and preferences.
- Membership and billing: subscription status, plan type, and payment-related metadata. Payment card details are handled by our payment processor and are not stored on our servers.
- Marketplace activity: listings you create, orders, shipping/delivery updates, disputes, and related communications.
- Opportunities and contracts: job applications (such as name, email, phone, portfolio link, cover letter, rate/availability) and contract and signature records.
- Community and messaging: message board posts, direct messages, and any media/files you upload in threads.
- Safety and integrity: reports you submit, moderation actions (such as strikes), and related evidence you provide.
- CC Projects workspaces: client records, client contacts, posts, captions, files, notes, tasks, projects, intake form answers, comments, and invoices that you and your team add. Proposals also store the client’s name, email, phone, prices, electronic signature, IP address, and the time they agreed to sign.
- Reviews: a rating, optional text, a display name of first name and last initial, and the booking or project the review is about.
- Text notifications: if you opt in, your mobile number and a record of your consent and opt-outs, described in Text messages (SMS) below.
2.2 Information about agency clients and reviewers
Agencies and creators on CC Projects plans can add their clients’ reviewer names and email addresses so we can send review links and updates. When a reviewer opens a review link, we collect the name and email they enter, their comments and markup, and a decision log that records who approved or requested changes, on which version, when, and from which browser. Clients can also submit ideas, links, images, and form answers through their portal. The agency that invited the client decides what to collect and is responsible for having permission to share it with us. Reviewers can ask the agency, or contact us, to correct or remove their information.
2.3 Information collected automatically
- Usage data: pages viewed, features used, and interaction patterns.
- Device and log data: browser type, operating system, IP address, and approximate location inferred from IP.
- Cookies and similar technologies: used to maintain sessions, remember preferences, and support core functionality.
3. How We Use Information
- Provide and maintain Platform services (courses, marketplace, opportunities, community, messaging).
- Process subscriptions, purchases, refunds, disputes, and payouts.
- Send administrative messages and in-app notifications (for example, order updates or policy changes).
- Support safety features like reporting, blocking, and enforcing platform rules.
- Improve and secure the Platform, prevent fraud, and debug issues.
- Send review links, reminders, and decision emails to client reviewers on behalf of the agency that invited them.
- Run optional AI features that draft captions, briefs, forms, and calendar ideas when you ask for them.
5. Google user data
This section describes the Google user data Creator Collective accesses when you connect Google Calendar from Schedule. We request it only after you click Connect Google and allow access on Google’s screen. You can use the rest of the Platform without connecting Google.
5.1 What we access
- Google account email (https://www.googleapis.com/auth/userinfo.email): the email address of the Google account you connect. We show it on the Schedule card as “Signed in as” so you can confirm which account is linked, and we store that address with the connection.
- Calendar events you can open (https://www.googleapis.com/auth/calendar.readonly): events on Google calendars you already have turned on. For each event we keep the title, place, calendar name, start, and end. We skip cancelled events, events you marked as free, events you declined, hidden calendars, and the calendar our app creates. Google’s response can include more fields than we keep. We do not store the event description, the guest list, or attachments. We look at whether you declined an event only so we can leave it off the schedule.
- Busy or free times (https://www.googleapis.com/auth/calendar.freebusy): whether a window is busy or free, without the event name. We use this so a client is not offered a time you are already using. Busy or free alone cannot show the event name or place, which is why we also request read-only event access above.
- A calendar our app creates (https://www.googleapis.com/auth/calendar.app.created): we create a Google calendar named Creator Collective and add confirmed jobs and sessions to it. An event we add can include the booking title, time, place, and the other party’s name. We do not edit or delete events you created on your other Google calendars.
5.2 How we use it
We use this Google user data to show your events on your Creator Collective Schedule and to keep clients from booking over a time you are already using. We do not sell it. We do not use it for advertising. We do not send it to OpenAI, and we do not use it to train generalized artificial intelligence or machine learning models.
You see the event title, time, place, and calendar name on your own Schedule. People who can open your agency or studio Schedule see those same details there. A client checking open times, and anyone booking a service, receives only busy or free. They do not receive the event title, place, description, or guest list.
5.3 How we store and share it
We store the connected email address, an encrypted refresh token, and the event copies listed above in Firebase (Google Cloud). The refresh token is used only to keep the connection working. Access is limited to the systems that run Schedule. We do not transfer Google user data to other apps or to advertisers. A transfer happens only to operate this feature on our own infrastructure, to comply with law, or to protect the security of the Platform.
Creator Collective’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5.4 How to delete it
On Schedule, choose Disconnect. We revoke Creator Collective’s access at Google, delete the stored connection and refresh token, and delete our copies of your Google events. If “When I disconnect, delete the jobs and sessions we added to Google” is checked, we also delete those events on the Creator Collective calendar in Google. Events you created yourself stay on Google. Leaving that box unchecked leaves the events we added on the Creator Collective calendar, and a later change in Creator Collective will not update them.
Deleting your Creator Collective account does the same revocation and deletes our copies. It does not delete the Creator Collective calendar, or the events already on it, inside Google. You can also remove Creator Collective at any time from your Google Account permissions at https://myaccount.google.com/permissions. To ask us to delete a connection, use the Contact page.
6. Data Storage & Security
We store platform data using Firebase (Google Cloud Platform) and apply security measures such as encryption in transit (HTTPS/TLS), access controls, and security rules designed to restrict data access.
Payment processing is handled by Stripe. We do not store full payment card numbers. We may store limited payment metadata (for example, subscription status or transaction identifiers).
7. Data Retention
We retain information for as long as needed to provide the Platform and for legitimate business purposes such as compliance, dispute resolution, safety enforcement, and recordkeeping. Retention periods vary depending on the type of data (for example, transaction records may be retained longer than profile preferences).
When a plan with CC Projects ends, the workspace stays read-only with export for 90 days. Records, including the review decision log, are then kept with the dormant account. Uploaded media is permanently deleted 12 months after the plan ends, after email notices 30 days and 7 days before. Items moved to trash are permanently deleted after 30 days.
8. Your Rights & Choices
- Access and correction: you can update many account and profile fields through your dashboard.
- Email preferences: you can manage marketing and alert emails in your dashboard settings when available.
- Text messages: reply STOP to any text, or turn off text notifications in your account settings.
- Deletion: you may request deletion of your account and associated data, subject to legal and operational retention requirements. Disconnecting Google Calendar deletes the Google data described in Google user data above.
- Facebook data: you may ask us to delete a Facebook Page connection, the access token, and our record of posts we sent. We do that within 30 days. The steps are on the Facebook data deletion page. Posts already on Facebook stay on Facebook until you delete them there.
9. Facebook Data
If you sign in with Facebook, or connect a Facebook Page so Creator Collective can publish for you, we store the Facebook data listed on our Facebook data deletion page. That page is the public instructions for the Course Creator Academy Facebook app.
Email us from that page and we delete the Page connection, the access token, and our record of posts we sent within 30 days. Posts that are already on Facebook stay on Facebook until you delete them there.
10. Text Messages (SMS)
Text notifications are optional. We collect your mobile number only when you enter it and check the text notifications box in your account settings or on our Text notifications page. With your number we store when you agreed, the page you agreed on, your IP address, the consent wording you saw, and any later opt-out or opt-in.
We use your number only to send the account notifications you chose and to confirm the number with a one-time code. Texts are sent through Twilio, which processes your number and message content to deliver them.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with or sold to any third parties. This does not include the messaging provider that delivers our texts.
Reply STOP to any text, or turn off text notifications in settings, and we stop texting you. Reply HELP for help. Message and data rates may apply. The full program terms are in the Terms of Service.
12. International Transfers
Your information may be processed in countries other than your country of residence, including the United States, where our service providers operate.
13. Children's Privacy
Creator Collective is not intended for users under 18. We do not knowingly collect personal information from children. If you believe a child has provided us information, contact us so we can address it.
14. Changes to This Policy
We may update this Privacy Policy from time to time. We will post the updated policy on this page and update the “Last updated” date. Material changes may also be communicated through the Platform or by email.
15. Contact
If you have questions about this Privacy Policy, contact us through the Contact page or via the in-platform messaging system.
