Effective date: October 20, 2026 | Last updated: October 20, 2026
1. Who we are and what this policy covers
Crew Solutions LLC ("CrewSolutions," "we," "us," or "our") provides temporary staffing of its own W-2 electrical trainee employees to licensed C-10 electrical contractors for assignments in California. CrewSolutions is the employer and is responsible for its employment and payroll obligations. Everee processes payroll for CrewSolutions; it is not the trainees' employer. Client contractors direct and supervise authorized work at their sites.
This policy describes personal information handled through our website, contractor app, trainee app, administrative and backend systems, and related recruiting, onboarding, employment, assignment, support, billing, and safety activities (together, the "Services"). It applies to applicants, trainees, contractor representatives, supervisors, and others whose information we receive in connection with these activities, including information provided outside the apps.
Assignments are currently in California, and trainee participation is limited to people who are at least 18. This policy describes our information practices; it does not replace a separate notice, permission, authorization, or consent required for a particular activity.
2. Information we collect and its sources
Account, contact, and professional information
We collect information provided when someone registers, applies, or maintains an account, such as name, email, telephone number, home address, date of birth, account and login details, company, role, experience, availability, job preferences, training, electrical trainee registration, and certifications. Our systems store names, contracts, and uploaded trainee cards, pay stubs, DAS logs, resumes, school records, and proof of hours. Authorized administrators can view these uploaded documents.
Documents can contain additional personal information, such as earnings, work history, signatures, or sensitive identifiers. Their contents are separate from the limited verification and onboarding fields returned by our vendors. Please provide only the information needed for the requested verification.
Contractor, supervisor, and business information
We collect business and representative contact information, C-10 license information, supervisor qualifications, certification and verification records, insurance documents, billing details, authorized-user information, and worksite details needed for the staffing relationship. Information can identify individual supervisors, inspectors, site contacts, property owners, or other people included in work records.
Sources include you and your device; applicants and trainees; contractors and their representatives; our service providers; and public or government sources used to check licenses and credentials. We also create records such as approval decisions, assignment status, timecard flags, and administrative notes when operating the Services.
Identity verification and payroll onboarding
Veriff identity verification is integrated into the CrewSolutions app and requires an identity-document image and a selfie. Our configured verification flow does not capture video. Authorized CrewSolutions administrators can view those images and other verification-session details in the Veriff platform. The images are not relayed to or saved by the CrewSolutions application. Our application retains the session ID, status, decision code, decision reason, and decision time.
Veriff uses automated identity and fraud checks. Its service can derive facial measurements from verification images, which may constitute biometric information under applicable law. Veriff describes its processing in its Privacy Notice and the disclosures shown during verification. Administrator access to document images and selfies is distinct from possession of any underlying biometric template.
Everee payroll onboarding is also integrated into our app. From onboarding and verification, our application retains the worker ID, onboarding status, and tax ID verification status, not the tax ID number itself. These integration fields are separate from payroll and other employment records, and from documents people upload to CrewSolutions. Authorized administrators can view information needed to onboard employees through Everee. Sensitive tax, bank, identity, and onboarding records submitted directly to Everee remain in Everee rather than being copied into CrewSolutions databases, file storage, or local files. This does not apply to separate documents that users upload directly to CrewSolutions. Provider collection, retention, and access also depend on the applicable service arrangements and notices.
Assignment, timekeeping, payment, and safety records
We collect job locations, schedules, tasks, rates, assignment status, worker and supervisor details, clock-in and clock-out times, recorded hours, timecard changes and approvals, off-site clock-out flags, payroll status, invoices, payments, signed agreements, and related work records. Location collection is explained in Section 4.
We also collect information provided for credential verification, orientation and training, site inspections, hazards, corrective actions, safety reports, and incident or claim handling. An incident, accommodation, or work-restriction report may contain injury or health information. The information received depends on the report and the needs of the employment, safety, or claim process.
Communications and uploaded materials
We receive support requests, emails, SMS-related records, notification information, feedback, ratings, administrative correspondence, and documents or images submitted through the Services or directly to our team. Information provided by a contractor or another person can become part of an assignment, safety, employment, or dispute record.
Device, network, and diagnostic information
Our routine server request logs record IP address, the page or route requested, and device type; they do not record the submitted request contents. We also use ipify for public IP address lookup. Requested URLs and technical error details can contain information beyond the name of a page, depending on their contents.
Both mobile apps use the following Google services:
| Service | Current use and information context |
|---|---|
| Google Analytics for Firebase | Automatic event collection to understand app use, including first opens, session activity, engagement, screen transitions, app/device information, and associated identifiers. No current custom analytics events. |
| Firebase Crashlytics | Crash reports, crash traces, app/device details, and installation-related identifiers for reliability and troubleshooting. |
| Firebase Cloud Messaging | Installation or registration identifiers and notification information for routing and delivery. |
| Firebase Authentication | Google sign-in, account identifiers and sign-in information such as email, and security-related device/network information. |
Sentry separately provides technical error and crash reports, which our development tools can read for troubleshooting. Our current Sentry configuration does not capture session replay, screenshots, request contents, or user identifiers. This description applies to Sentry; Firebase services still process the information described above. Technical error details are not necessarily anonymous merely because a user-identifier field is absent.
3. How we use information
We use information for recruiting, identity and credential checks, account security, assignments, communications, timekeeping, employment, payroll and taxes, billing and accounting, safety and training, incident and claim handling, support, technical troubleshooting, fraud prevention, recordkeeping, agreement enforcement, and legal obligations. Section 6 separately addresses AI-assisted development.
4. Location collection and timecard checks
Signup and profile address entry
While the app is in use, it requests precise device GPS information to help populate address information during signup or profile use. Coordinates associated with the saved home address are retained. The device position used for address entry may differ from a person's intended home address, so inaccurate account information should be reported or corrected.
Starting and ending a shift
At the start of a shift, the trainee app checks whether the device location is within 100 meters of the jobsite. The app does not allow the normal clock-in flow to start a shift when that check fails. At the end of a shift, the app performs the same distance check. An off-site clock-out is permitted, but the recorded hours are flagged for manual review by the contractor.
Older location readings and limits of the check
If a fresh location reading is unavailable, the app can use the phone's last known position, which may be several minutes old. A stored reading or off-site flag is therefore a timekeeping input, not proof of continuous presence, absence, or the amount of work performed. Report an inaccurate location result or time record to CrewSolutions so the record can be reviewed.
A failed location check or unapproved timecard does not determine whether wages are owed. Compensable time must still be recorded through an available backup process and reviewed by CrewSolutions. Employee payment remains subject to applicable wage obligations, independent of contractor approval or payment.
When location is not collected
CrewSolutions does not continuously track device location during a shift, collect device location in the background, or collect it while the app is closed. Its location access uses the device's "while using the app" permission. Stored readings remain in our systems after collection; that storage is different from ongoing tracking.
Access and your controls
Authorized CrewSolutions administrators can view stored location information. Contractors can see off-site clock-out flags for relevant assignments. They cannot view trainee home addresses, raw GPS coordinates, stored home coordinates, or location history through the Services. Device settings control whether the app can obtain location. Disabling permission can prevent address autofill and the normal location-dependent timekeeping flow; contact CrewSolutions if a permission or location problem prevents accurate recording of work.
5. How information is disclosed
Contractors and trainees. Information is exchanged to arrange and supervise work, verify relevant qualifications, communicate assignments, review timecards, document safety and training, and address incidents or disputes. Trainees receive contractor, site, supervisor, schedule, and work-requirement information. Contractors receive relevant trainee, assignment, timekeeping, and safety information, including off-site clock-out flags. Section 4 explains location access and its limits.
The staffing agreement limits contractor use of personnel information to legitimate assignment, safety, access, or legal needs and restricts demands for sensitive identity, medical, or background records without a lawful basis. A contractor's access to a work record does not entitle it to all information in a trainee's account.
Technology and administration providers. We use the following providers and technologies to operate the Services. Information is disclosed or made available as needed for their functions.
| Tool or service | Function or processing context |
|---|---|
| Framer | Website publishing and hosting, including submitted forms and technical website information. |
| DigitalOcean | Backend server hosting in the United States. |
| MongoDB and Redis | Database and caching technology; our database infrastructure is in the United States. |
| AWS S3 | Storage of uploaded documents and platform files in the United States. |
| Google Maps | Mapping and address-related features, including requests needed to support location and site information. |
| Firebase / Google Analytics | Automatic analytics, Crashlytics, Cloud Messaging, and Authentication for Google sign-in on both mobile apps. See Section 2. |
| Sentry | Error and crash reporting. No session replay, screenshots, request contents, or user identifiers in the current configuration. |
| ipify | Public IP address lookup used by the platform. |
| Twilio and SendGrid | SMS and email delivery and related delivery or communication records. |
| DocuSign | Electronic document signing, signed records, and related transaction information. |
| Veriff | Identity-document and selfie verification. Administrators can view images in Veriff; our app stores only the listed verification-result fields. See Section 2. |
| Everee | Payroll and worker administration. Retained onboarding/verification fields: worker ID, onboarding status, and tax ID verification status, not the tax ID number. |
| Stripe | Payment processing, billing, and associated payment or transaction records. |
| Anthropic / OpenAI | Claude Code and Codex for development, diagnostics, and maintenance. Access includes production servers and Sentry reports; see Section 6. |
Our backend, databases, and uploaded-file storage are hosted in the United States. Outside developers no longer have access to personal information; their access has been revoked. Individual service providers may use their own personnel, infrastructure, or subprocessors as described in their applicable notices and service arrangements.
Providers may also process information under their own notices and legal responsibilities. Google Analytics has terms separate from other Firebase services. CrewSolutions remains responsible for practices within its control. Each provider receives information relevant to its function; not every listed category goes to every provider.
Professional, insurance, and legal recipients. Relevant information may be disclosed to accountants, legal advisers, insurers, brokers, claims administrators, auditors, and authorities for the applicable accounting, employment, insurance, safety, legal, or regulatory purpose. Disclosures in response to legal process or governmental requests are subject to applicable law.
Business transactions. Relevant information may be disclosed in connection with a financing, reorganization, acquisition, or transfer of business assets, subject to applicable confidentiality, notice, and other legal requirements.
6. Artificial intelligence and automated tools
Current development, diagnosis, and maintenance
CrewSolutions uses Anthropic's Claude Code (Claude Max) and OpenAI's Codex (ChatGPT Pro) for code, debugging, and maintenance. They are not integrated into ordinary user-facing workflows or used to screen resumes. Most development uses source code and test data in staging.
The tools also have production-server access and can read Sentry reports. Material returned through connections or included in prompts may be processed by the provider, including technical logs, errors, and any personal information present.
Our internal rules prohibit opening customer data during production debugging, maintenance, and documentation. These rules govern use; they do not remove server access or guarantee that diagnostic output never contains personal information.
We have turned off the accounts' standard model-improvement settings. This does not prevent provider processing or retention, which depend on applicable terms, settings, and separate sharing choices. These subscriptions are not zero-retention services.
Planned resume review
CrewSolutions is considering AI-assisted resume review. Before introducing it, we will explain the use, intended human review, and applicable rights, and provide any additional notices, choices, or authorizations required by law.
Other automated processes
Location checks, eligibility rules, timecard flags, and vendor verification systems are separate from our development tools. Veriff uses automated, AI-assisted verification; the absence of an app integration with Claude Code or Codex does not mean every vendor process is free of AI. Contact CrewSolutions about inaccurate information or results. An off-site clock-out flag triggers manual review and does not by itself determine wages owed.
7. Cookies, diagnostics, sale, and advertising sharing
We do not sell personal information or share it for cross-context behavioral advertising. Our website is built on Framer and does not use advertising pixels such as Meta Pixel or Google Ads tags. We do not use Firebase for targeted advertising or share Firebase information for advertising.
Our apps still use automatic Firebase analytics, crash reporting, authentication, and notification identifiers as described in Section 2. The absence of custom analytics events does not mean no information is collected. The website and app services may use cookies, local storage, or similar technology for operation, authentication, security, or measurement unrelated to advertising.
Browser and device settings offer controls over cookies, location, and notifications. Disabling location or push notifications does not necessarily disable analytics or crash reporting. Our practice of not selling information or sharing it for cross-context behavioral advertising applies whether or not a browser sends a Do Not Track or Global Privacy Control signal. Contact us for assistance with privacy choices.
8. SMS, email, and notification choices
We use phone numbers and contact information for account verification, security notices, job opportunities, assignment and schedule updates, timekeeping reminders, payroll status, and support. Message frequency varies; message and data rates may apply. Reply STOP to opt out of SMS messages or HELP for assistance. Device settings control push notifications. Follow any unsubscribe instructions for marketing email.
We do not share, sell, rent, or trade mobile numbers or SMS consent information with third parties or affiliates for their marketing or promotional purposes. Communication providers can process the information needed to deliver and administer CrewSolutions messages. Operational, payroll, security, and legal communications may also be delivered through other appropriate channels.
9. Account closure, deletion, and retention
Deleting an account
Users can initiate account deletion within the app. The account closes 48 hours after the deletion request. At closure, active sign-in sessions are ended and the user can no longer sign in. We delete account-related records from our active database, except the records described below that must or may lawfully be retained for a specific purpose.
You can also contact support@crewsolutions.work to request deletion, ask about retained records, or obtain the status of a deletion request. Account closure does not end outstanding wage obligations or remove employment-record access rights.
Limited records retained after deletion
We retain only information necessary for applicable employment, payroll, tax, safety, contractual recordkeeping, and legal obligations, or to establish, exercise, or defend legal claims. Retention is limited to the applicable period and purpose. Other account-related personal information is deleted. The categories that may remain are:
| Records | Retention purpose and period |
|---|---|
| Employment and qualification records | Applications, resumes, hiring and termination records, employment documents, trainee cards, school records, DAS logs, and proof of hours needed for employment and qualification records. Generally at least four years from creation or receipt or the later applicable employment action; longer when required by law or a claim. |
| Payroll and tax records | Wages, statements, deductions, reimbursements, tax records, and necessary identifiers. At least four years under applicable payroll and employment-tax requirements, measured from the applicable filing, tax-due, payment, or recordkeeping trigger; a later required trigger or longer statutory period controls. Includes records maintained through Everee. |
| Timekeeping and assignments | Work Orders, shift times, meals, hours, corrections, approvals, worksite and assignment information. At least four years under the MSA recordkeeping rule, or longer under applicable law or a claim. |
| Employment eligibility records | Form I-9 and required supporting records: three years after hire or one year after employment ends, whichever is later, and longer if another applicable obligation requires it. This is not a basis to retain every verification image or selfie. |
| Agreements and transactions | Signed agreements, invoices, payment records, and correspondence needed for legal recordkeeping, outstanding transactions, or claims. MSA-covered records: at least four years, with longer retention only for an applicable legal, tax, contractual, or claim requirement. |
| Safety, training, and incidents | Supervisor verification, orientation, training, inspections, hazards, incidents, insurance, and claims. MSA-covered records: at least four years; required injury/illness logs generally five years after the relevant calendar year. Covered exposure records can require 30 years and covered employee medical records employment plus 30 years, subject to statutory scope and exceptions. Longer applicable requirements control. |
The retention periods above apply only to records needed for the identified purposes. MSA Section 14.3 requires relevant assignment, timekeeping, supervisor verification, training, inspection, incident, and billing records to be retained for at least four years from creation or receipt, or a later legally required trigger. A legal hold can require relevant information to remain until the hold ends. We retain identifying information only as needed to maintain usable required records, restrict access to authorized personnel, and delete retained personal information when the applicable retention purpose and period end. Account deletion does not restart a retention clock.
Providers and backups
The 48-hour closure period describes our account closure and active-database process. It is not a promise that every provider-held record or backup copy is erased within 48 hours. Records maintained by payroll, identity-verification, payment, and other providers may be subject to separate legal obligations, service arrangements, and retention periods. Backup copies may also have a separate deletion cycle. Retention remains subject to the purposes and limits described in this section. Contact us for information about provider-held records or backup handling relevant to your request.
Closing an account does not eliminate rights to employment or other records that applicable law requires to remain available. Contact CrewSolutions for assistance with retained records.
10. Security
We use reasonable administrative and technical safeguards designed to protect personal information. No system or transmission method is completely secure. Users should protect account credentials and promptly report suspected unauthorized access. This policy does not promise that a security incident can never occur or limit any notification obligation imposed by law.
11. Privacy requests and California residents
Depending on the applicable law and CrewSolutions' obligations, you may have rights to know or access information about collection, use, and disclosure; receive a copy; correct inaccurate information; request deletion; and exercise applicable limits on sensitive-information use or opt-outs from sale or advertising sharing. Where these rights apply, you may exercise them without unlawful discrimination or retaliation and may use an authorized agent as permitted by law.
Personal information addressed here includes identifiers, contact records, birth dates, employment and transaction records, analytics and diagnostics, precise geolocation, uploaded documents, communications, and verification results. Verification also involves ID images and selfies accessible in the Veriff portal, with facial-data processing by Veriff as described in Section 2. Sensitive information can include precise geolocation, biometric information used to identify someone, and sensitive identifiers or health details in submitted records.
Sections 2 through 7 explain the information, sources, purposes, recipients, and automated processes; Section 9 addresses retention and deletion. Contact us using the details below to make a privacy request. We may verify identity in a manner appropriate to the request without asking for unnecessary sensitive information. Where a request is denied or limited, the response will identify the applicable reason to the extent required by law.
12. Age limits and third-party services
The Services are intended for adults aged 18 or older. If we learn that someone under 18 has provided personal information for an account or application, we will review it and take appropriate steps consistent with applicable law and any required record preservation. Contact us if you believe this has occurred.
Third-party websites and services can have their own notices. An embedded service can still process information independently or for CrewSolutions; being displayed inside our app does not by itself determine the provider's role. This policy covers CrewSolutions' practices, and provider notices describe the practices for which those providers are responsible.
13. Policy changes
We will update this policy when appropriate and show the applicable revision date. For a material change, we will provide notice reasonably suited to the change, such as through the Services or email, and obtain any consent or provide any additional choices required by law. Posting an update or continued use alone does not replace a consent or authorization that the law separately requires.
14. Contact
Crew Solutions LLC
Email: support@crewsolutions.work
Mailing address: 2247 Cumming Rd, Brentwood, California 94513, United States
Website: https://crewsolutions.work

