Privacy Policy

1. Information we collect

Candidate information

Candidates may provide names, email addresses, phone numbers, work history, trades, role level, years of experience, skills, certifications, availability, travel and shift preferences, relocation preferences, pay information, screening answers, union status and union local, work-limits text, and other profile details.

Candidates may also upload profile photos and intro videos, create voice recordings for transcription and drafting, save jobs, apply to jobs, message employers, contact support, report accounts or content, and block accounts.

Employer and company information

Employers may provide a contact name, email address, phone number, company name, city, logo, company category and size, trades and roles hired, market focus, union status and union local, company description, and team member or invitee names and email addresses. Job posts may include titles, locations, pay information, trade, travel, schedule, and description.

We also process plan selection, billing status, trial and cancellation dates, Stripe customer and subscription identifiers, candidate favorites, applicant activity, and candidate contact usage.

Account, communication, and technical information

Both account types receive a Firebase user identifier. If you use Google Sign-In, Google provides the account details needed to authenticate you, such as your identifier, name, email address, and profile photo. If you use Sign in with Apple, Apple provides an identifier and, if you choose to share them, your name and an email address, which may be an Apple private relay address. We process messages, applications, reports, block lists, notification preferences, support requests, and related timestamps.

Our hosting, authentication, update, and security providers may process technical information such as IP address, browser or device type, operating system, app version, request time, and diagnostic or security events when your device communicates with the Service.

On the website, we use LogRocket to record how visitors use our pages, such as the pages viewed, clicks, scrolling, browser and device type, the site that referred the visit, and campaign tags in the link. On public pages, such as the home page, the job board, and the sign-up and log-in pages, the recording includes the text and images shown there. Inside an account, page text and images are masked before the recording leaves your browser. What you type is always masked, and the recording does not include network requests, console messages, or your IP address. LogRocket keeps small identifiers in your browser to connect the pages of one visit. The mobile apps do not use session recording.

Voice transcription and drafting

When a candidate chooses a voice feature, the recording is sent to OpenAI for transcription. The transcript is then used to draft profile fields, which may include contact, experience, pay, screening, union, and work-limits information. The candidate reviews the draft before saving it. Our server treats the recording and transcript as pass-through data and does not write them to Firestore. The mobile app removes its temporary recording after a successful request and retains a failed recording only for a retry or until the screen closes. OpenAI processes the request under its own terms and the settings on our OpenAI account. We do not promise a vendor zero-retention setting.

2. How we use information

• Create, authenticate, secure, and support candidate and employer accounts.
• Build profiles, publish job posts, match candidates with employers, and manage applications.
• Enable employer review, candidate search, messaging, team access, reporting, and blocking.
• Transcribe voice recordings and draft profile answers requested by the candidate.
• Process Stripe billing, maintain plan access, prevent duplicate charges, and keep accounting records.
• Send team invitations and, when enabled, optional job or talent emails through Resend.
• Moderate user content, investigate reports, prevent abuse, enforce our Terms, and protect the Service.
• Answer support requests, troubleshoot errors, comply with law, and defend legal rights.

3. Who receives information

We disclose information only as needed to operate the Service, provide a feature you request, protect users and the Service, complete a business transaction, or comply with a valid legal requirement. The recipients include:

Candidates and employers receive information from each other when needed for profiles, job posts, applications, and messages. Administrators may access reports, support conversations, and account information to operate and protect the Service. A successor may receive information as part of a merger, financing, acquisition, reorganization, or sale, subject to applicable law.

4. Private media, messages, and moderation

Candidate photos, intro videos, and company logos are stored in access-controlled Firebase Storage. Authorized views use short-lived signed URLs. These signed URLs normally expire within 10 minutes, but a person who receives a valid URL may use it until it expires. Hiding a candidate profile stops the Service from issuing new candidate-media URLs. Existing signed URLs may remain usable until expiration.

Messages are available to the participants and authorized company team members. Users can report content or accounts and block another account. We apply automated and rule-based moderation to user-authored messages, profiles, company descriptions, and job posts. Administrators may review reports and take action under the Terms of Service.

5. Retention and account deletion

We keep information for the time needed to provide the Service, protect users, maintain required records, and meet legal obligations. The following schedules are configured in the current source. Firestore TTL and Cloud Storage lifecycle deletion are asynchronous. Production verification is pending for those automated controls.

Account deletion removes the profile, owned job posts, applications tied to the candidate or owned jobs, conversations, support messages, wallet, candidate-contact record, stored profile media, pending invites, matching delivery logs, and Firebase login. For an account that uses Sign in with Apple, we also ask Apple to revoke the app's access. Company team members keep their own login but lose the deleted company role. We cancel local billing access and ask Stripe to cancel an active subscription and delete the Stripe customer when identifiers are available.

Reports, admin audit entries, and accounting events may be retained after account deletion, but the deletion process replaces the account identifier and removes names, report detail, thread links, and audit detail as applicable. Because some deletion work is distributed across service providers, contact us if you believe information remains after a completed request.

6. Your choices and privacy rights

• Review and update profile and company information in account settings.
• Control profile visibility, saved jobs, block lists, and available notification preferences.
• Use an unsubscribe link in an optional commercial email or turn off the matching preference. Product notification delivery is currently disabled during rollout. Team invitations and required account or transaction messages may still be sent.
• Delete a signed-in account through Settings or More. The public account deletion page explains the steps. If you cannot sign in, email us from the address on the account.

Depending on where you live, applicable law may give you rights to know, access, correct, delete, or receive a copy of personal information, and to limit or object to certain processing. We will evaluate verified requests under the law that applies. Send a request by email or postal mail using the contact information below. We may ask for information needed to verify the account and request.

Do Not Track

The website does not currently respond to browser Do Not Track signals because there is no uniform technical standard for them. The Service does not include advertising SDKs. The website uses LogRocket for session recording as described above. You may still use the account, email, and privacy choices described in this policy.

7. Security and age limit

We use access controls, authentication, private storage rules, short-lived media links, rate limits, and other technical and organizational measures designed to protect information. No transmission or storage method is completely secure, so we cannot guarantee absolute security.

The Service is intended for people who are at least 18 years old. We do not knowingly invite a person under 18 to create a candidate or employer account. Contact us if you believe a person under 18 has provided personal information.

8. Changes to this policy

We may update this policy when the Service or our practices change. We will post the updated policy here, change the effective date, and provide any additional notice required by law.

9. Contact us

Send privacy questions or requests to: