ProjectCollab Privacy Policy

Version 2026-09-15. Effective September 15, 2026.

This Privacy Policy explains how Creators Hub LLC, a California limited liability company, doing business as ProjectCollab (ProjectCollab, we, us, or our), collects, uses, discloses, and protects personal information through the ProjectCollab Platform.

Privacy, security and legal requests: info@projectcollab.io

1. Scope and roles

1.1 This Policy covers visitors, account holders, client contacts, creators, crew, organization members, external recipients, and people whose information users submit for a production.

1.2 ProjectCollab generally acts as the business/controller for Platform account, marketplace, transaction, safety, and operational data. Stripe acts under its own terms and may act as an independent controller or regulated service provider for payment, identity, fraud, and tax data. Other vendors generally process data for ProjectCollab.

1.3 This Policy does not govern a client's or creator's independent handling of production information outside the Platform. They may have their own privacy duties.

2. Information we collect

2.1 Account and contact information. Name, email address, authentication identifiers, avatar, city, preferred local time zone, organization membership and authority, and account settings. The onboarding mobile number is stored as private contact data, not a public profile field, and is not shared with other users.

2.2 Professional and portfolio information. Roles, bio, city, skills, gear, credits, portfolio video or links, thumbnails, captions, claimed role in work, availability, application samples, and portfolio-review submissions and decisions. Profiles and published portfolios intended for Discover may be public.

2.3 Job and production information. Job descriptions, public budget range, exact posting snapshot, roles, structured job days, city and neighborhood, exact address, parking and access notes, schedules, call sheets, kits, attendance reports, cancellation records, contracts, invoices, and production files.

2.4 Applications, offers, and communications. Applications, snapshotted work samples, saved or declined activity, versioned offers and counters, rates, acceptance state, conversations, attachments, reviews, reports, and support communications.

2.5 Payment and transaction information. Customer and payment-method references, payment type, limited payment-method details such as brand or last four digits where available, accepted quote, processing fee, allocations, transfer state, refunds, chargebacks, ACH returns, provider event identifiers, payout readiness, ledger entries, and reconciliation records.

2.6 Stripe identity, bank, and tax information. Stripe collects identity, bank, card, and tax information through its services. ProjectCollab's application database does not store raw identity documents, full card or bank credentials, Social Security numbers, or complete tax forms. We receive provider account references, capability/readiness status, limited method details, and requirement or error information needed to operate payments.

2.7 Verification and trust information. Portfolio-review evidence and outcomes; whether Stripe reports payment onboarding ready; disputes, immutable parties, evidence, settlement proposals, responses, decisions, and appeal information when built; DMCA notices and counter-notices; abuse reports; and moderation or account actions.

2.8 Device, usage, and security information. IP address, user agent, authentication events, session and request metadata, terms-acceptance records, audit logs, webhook and command events, security alerts, and diagnostic error information.

2.9 Information about people without accounts. A user may submit a name, email, role, offer, contract, invoice, or kit for an external recipient. We allow that person to complete the relevant action without first creating an account and may invite them to create one afterward.

2.10 Sensitive information. Exact shoot locations, private phone numbers, payment state, pay amounts, dispute evidence, identity status, and some production materials are treated as restricted information.

3. Where information comes from

3.1 We receive information:

1. directly from you;
2. from another user who adds you to a job, organization, contract, invoice, offer, or dispute;
3. from Stripe and other providers that report transaction or service status;
4. automatically when you use the Platform; and
5. from public or user-directed portfolio sources, such as a video link you choose to embed.

3.2 A user who gives us another person's information must have a lawful reason to do so and must provide any notice or obtain any consent required by law.

4. How we use information

4.1 We use information to:

1. create, authenticate, secure, and support accounts;
2. publish profiles, portfolios, and job information according to visibility settings;
3. review portfolios for authenticity and claimed roles;
4. match, apply, communicate, make offers, accept work, and plan productions;
5. limit exact locations and call sheets to accepted participants;
6. capture, hold as a Platform balance, allocate, transfer, refund, reconcile, and record payments;
7. check Stripe-reported payout readiness and send setup reminders;
8. enforce pay privacy across allocations, offers, booking snapshots, and indirect records;
9. record attendance, wrap, cancellations, disputes, evidence, and reviews;
10. provide transaction, security, legal, and operational notices;
11. detect fraud, abuse, infringement, security incidents, and violations;
12. audit commands, investigate failures, reconcile provider events, and keep financial records;
13. comply with law and protect users, ProjectCollab, and others; and
14. improve and debug the Platform using information appropriate to that purpose.

4.2 ProjectCollab does not use private crew rates to recommend or set rates and does not publish rates on profiles.

5. What other users can see

5.1 Public visitors and users may see information you intentionally publish, such as your name, avatar, city, roles, public profile, published portfolio, and public job range.

5.2 A job owner or relevant recipient may see an application and the application sample snapshot. Later edits to a public portfolio do not rewrite that snapshot.

5.3 Before acceptance, applicants see city and neighborhood, not the exact address. Accepted participants can see the exact address, parking, access notes, and call sheet. A participant removed before the shoot loses access; a participant recorded as having worked may retain records needed for a dispute.

5.4 Offer and offer-revision details are limited to the sender, recipient, or claimed external recipient. A client cannot see a private crew offer merely because the client owns or funds the booking.

5.5 A crew member can see their own allocation and no other crew member's allocation. The lead sees allocations it sent and needs to release; the client sees the roster and accepted job total without individual crew pay.

5.6 Organization owners can see organization lead offers that commit organization funds. Crew offers stay private.

5.7 Reviews remain blind until both members of the review pair submit or the 14-day window expires. Visibility depends on each review's own publication state.

5.8 Messages are visible to their participants. Authorized ProjectCollab staff may access messages only when needed for support, a payment or safety investigation, legal process, or security, and staff access should be attributable and logged.

6. How we disclose information

6.1 We disclose information:

1. to users and external recipients as needed for the job, offer, transaction, production, or dispute and as described in Section 5;
2. to service providers listed in the Service Providers and Subprocessors list;
3. to Stripe for payment, connected-account onboarding, identity, fraud, transfers, disputes, and tax-related services;
4. to professional advisers, insurers, auditors, and financing or transaction counterparties under appropriate confidentiality duties;
5. to authorities, courts, payment networks, rights holders, or others when required by law or reasonably necessary to protect rights, safety, security, and the Platform; and
6. in a merger, financing, reorganization, bankruptcy, acquisition, or sale, subject to applicable protections.

6.2 We may disclose a DMCA notice to the user who posted the challenged material and a counter-notice to the claimant, as the DMCA and Intellectual Property Policy explains.

6.3 ProjectCollab does not sell personal information for money and does not share personal information for cross-context behavioral advertising as those terms are presently understood. No advertising or analytics SDK is in use.

7. Stripe and payment information

7.1 When you provide personal data in connection with payment services, Stripe receives that data and processes it under Stripe's Privacy Policy. A connected account is also governed by Stripe's applicable connected-account and services agreements.

7.2 ProjectCollab may instruct Stripe to create or link accounts, capture a client payment, inspect capabilities, initiate allocation transfers, issue refunds, and reconcile disputes, returns, and unknown events, as authorized by the applicable terms.

7.3 Stripe has a direct contract with connected accounts, but that alone does not establish that ProjectCollab has no regulated or reporting obligations.

8. Cookies and similar technologies

8.1 The Platform may use cookies or local storage needed for authentication, session continuity, security, preferences, and core operation.

8.2 No behavioral advertising or general product-analytics provider is in use. Before adding analytics, session replay, advertising, or non-essential cookies, we will update this Policy and the Service Providers list and add consent controls where required.

9. Retention and deletion

9.1 We keep information while an account is active and as needed to provide the Platform, complete transactions, preserve immutable accepted terms, maintain financial and tax records, resolve disputes, prevent fraud, handle IP claims, enforce agreements, and comply with law.

9.2 Deleting public content or closing an account does not necessarily delete transaction snapshots, payment and ledger entries, attendance, dispute evidence, terms acceptances, DMCA records, security logs, backups, or information another user is entitled to retain.

9.3 We keep each category of information only as long as it is needed for the purposes in Section 4 and for legal, tax, dispute, safety and security requirements, then delete or de-identify it. Account data is kept while the account is open. Transaction, payment, ledger, tax, dispute and terms-acceptance records are kept for as long as law and provider rules require after the transaction. Security and audit logs are kept for a limited period appropriate to their purpose.

9.4 A crew allocation delayed by incomplete Stripe onboarding remains payable; financial and contact records needed to identify and pay that recipient remain available until payment, lawful claim, or another legally permitted disposition, including applicable unclaimed-property law.

10. Security

10.1 We use access controls, row-level database policies, least-privilege service roles, audit logs, signed webhooks, idempotent money commands, restricted location and pay tables, and provider-hosted payment identity collection to reduce risk.

10.2 No system is perfectly secure. Keep your login protected and report suspected unauthorized access to info@projectcollab.io.

10.3 This section describes controls but does not promise a particular certification or absolute security.

11. Your choices and rights

11.1 You can update many profile and account fields, change public visibility, remove portfolio items, and change your local time zone in the product. You may request access, correction, deletion, or a copy of personal information at info@projectcollab.io.

11.2 We may need to verify your identity, clarify a request, preserve information an active transaction or law requires, and retain records that cannot lawfully or safely be deleted.

11.3 Depending on where you live, you may have rights to know/access, correct, delete, obtain a portable copy, restrict or object to processing, withdraw consent, limit use of sensitive information, or appeal a denial.

11.4 ProjectCollab will not unlawfully discriminate against someone for exercising a privacy right.

12. International data transfers

12.1 ProjectCollab and its providers may process information in the United States and other countries listed by those providers.

12.2 Vendor DPAs and subprocessor locations must be reviewed for the selected plans and regions.

13. Children

13.1 The Platform is not intended for children to hold their own accounts. You must be at least 18 to hold an account.

13.2 Production records may refer to minors lawfully involved in a shoot. Users must not submit more information than necessary and must comply with guardian consent, child-performer, education, trust, and privacy requirements.

14. Changes to this Policy

14.1 We will post changes and update the effective date. We will give additional notice or seek consent when a material change or applicable law requires it. Existing immutable transaction records remain governed by the disclosures and terms applicable when created, except where law requires otherwise.

15. Contact and complaints

Privacy requests: info@projectcollab.io

Security reports: info@projectcollab.io