Privacy Notice

1. Information CREWW handles

Depending on how you use CREWW, information may include:

• Account and contact details such as the email address you sign in with, an optional phone number you choose to add (CREWW does not verify it), name, date of birth, gender selection, country, and state or region.
• If you choose to verify your identity: the type of ID document, the number you enter, and photos of the document. See section 6 for how long each is kept.
• Professional profile details such as display name, bio, location, roles, skills, availability, portfolio links, and profile or gallery photos and videos.
• Marketplace and trust records such as jobs, applications, invitations, bookings, confirmations, ratings, vouches, historical credits, reports, disputes, and support requests.
• Service and usage information such as sign-in and account events, public job or profile views and shares, event references, source or referrer information, and anonymous or session identifiers stored in browser local storage and sent with public view or share events when available.

2. Public and private information

Information placed on a public Crew or Director profile, including its gallery media, may be visible to people who can access that profile. CREWW also displays selected trust and confirmed-work information according to its product rules. Account contact and identity details such as your email, phone number, date of birth, gender, and ID documents are not public profile fields; some other account or hiring information is restricted to the owner or relevant participants. If an ID document is approved, your profile shows only that it was verified, never the document or its number.

Check each field and upload before submitting it. Do not place private production material in a public profile gallery.

3. How information is used

CREWW uses information to:

• Authenticate accounts and protect sign-in with a one-time code sent to your email.
• Check, when you ask us to, that an account belongs to one real person: CREWW staff compare your ID document with your account details, and a coded fingerprint of the document number stops the same document from verifying more than one account.
• Operate profiles, job discovery, applications, hiring, and production workflows.
• Maintain confirmed-work, ratings, vouches, trust, reporting, and safety features.
• Send account and service notifications, respond to support requests, and improve reliability.
• Understand product usage through limited first-party service events.

4. Service providers and sharing

Public profile information is shared with people who view those profiles. CREWW also uses service providers to deliver email, media storage, hosting, databases, and related operations. The current backend stores profile photos and gallery media in Cloudflare R2; media uploaded earlier may remain on Cloudinary. In production, sign-in codes and transactional email are sent through Zapiack. Outside production, the code routes these messages to Slack or logs them instead. ID document photos are stored in CREWW’s own database, not with a media provider, and are not shared with any verification vendor. PostgreSQL and Redis hosts are supplied through deployment configuration; this codebase does not identify the production hosting vendors or storage regions. Confirm the deployed values and any transfer safeguards before publication.

Cloudflare, Cloudinary, Zapiack, and the configured database, Redis, and hosting providers may process information to provide these services. The codebase does not specify where each provider processes or stores data. The deployed configuration and provider agreements determine those details.

5. Browser storage and service events

The app keeps its short-lived access token in memory and its rotating refresh token in an HttpOnly, same-site cookie. Browser local storage holds the selected workspace, workflow state, and anonymous or session identifiers. Public job and profile view or share events can include the event type, job or profile reference, source, referrer, and anonymous or session identifiers. The anonymous and session identifiers are stored in local storage; clearing it removes the browser copies, but not events already sent to CREWW. The codebase does not define a retention period for those events or implement an analytics consent control. Cookie and consent requirements still need review for the deployed site.

6. Retention, export, and deletion

You can download a JSON export from Settings and request account deletion there. A deletion request disables access immediately. After 30 days, the current process anonymizes identifying account and profile fields, removes the profile photo and gallery assets, deletes notifications and certain user-specific records, and clears selected free text or evidence fields. Some work, trust, or audit records remain to preserve other users’ histories. The analytics table has no automatic expiry or scheduled deletion in this codebase. Email queue job records are configured for removal after 365 days. Sign-in codes expire after five minutes, and refresh tokens default to 30 days (the deployment can configure that lifetime). ID document photos are deleted as soon as CREWW approves or rejects the submission, when you withdraw it, or after 30 days if it has not been reviewed; the full document number is cleared at the same time. CREWW keeps the document type, its last four digits, a coded fingerprint of the number, and the outcome, to stop the document from verifying another account; account deletion removes the fingerprint and digits. Deleted photos may remain in database backups for the backup retention period. Backup and infrastructure log retention is outside this repository. Apart from the specific periods described here, the app does not define a complete retention schedule; the operator must set one and publish it before this notice is final.

The JSON export includes account, profile, marketplace, trust, report, and supported notification and activity records. It does not include uploaded gallery media files, and notification and activity feeds are each capped at 5,000 entries; the export marks when either feed was truncated. It is not a copy of every item of information CREWW may hold.

7. Analytics, sharing, and deletion

Public job and profile view or share events may be submitted without an account and include the related job or profile identifier, anonymous and session identifiers, and available source or referrer details. These events are not linked to an account by the analytics endpoint. As a result, an account deletion request may not identify or remove events created while browsing publicly. These anonymous events are not removed by account deletion. The operator must define and publish an analytics retention period before this notice is final.

8. Your rights, choices, and contacting CREWW

You can update supported account and professional-profile fields, remove gallery items, download the available export, or request account deletion through Settings. Privacy contact: [PRIVACY CONTACT EMAIL — TO BE PROVIDED]. Until that address is set, users can contact support at support@creww.co. The code implements export, correction of supported account/profile fields, gallery removal, and account deletion. It does not define a request process or response timeline for other privacy rights. Depending on applicable law, you may have rights to access, correct, erase, restrict, or object to processing, receive portable data, and complain to the relevant regulator. The applicable rights, lawful bases for each use, request timelines, exceptions, data protection contact, and regulator details need confirmation by the operator and counsel.