Privacy Policy for Producer Relay

The candidate intake is a free, California-only pilot. It does not require an account or identity documents, and it asks no other screening questions. The form collects your name, email address, phone number, state, and current license status. It also asks for self-attested yes-or-no answers to whether you are at least 18 years old and authorized to work in the United States.

The qualification result depends only on the age and U.S. work-authorization answers. Current license status is recorded as profile information and does not affect that result.

Optional pilot-processing consent covers storing the profile details you submit and processing your age and U.S. work-authorization answers for the pilot. The app evaluates those two answers to return an immediate qualification result. If you do not consent to pilot processing, that submission's profile and answers are not stored. Profiles submitted with pilot-processing consent are available for administrator review.

Optional SMS consent is separate from qualification and does not change the result. When pilot-processing consent is given, the SMS choice is stored with the candidate profile, and affirmative SMS consent is recorded as a separate consent event alongside pilot-processing consent. The public form sends no follow-up message or text when you submit it.

An agency application records the company name, organization type, authorized contact name and email, selected arrangement, eligibility and authority attestation, and acceptance of the terms. For a bounty arrangement, it also records acceptance of the bounty agreement. These details are stored for application review. Submitting an application does not charge the applicant.

Checkout is available only to approved agency accounts. The approved arrangement is paid through a hosted, one-time checkout. The application itself does not take payment.

The app records the payment status and amount, arrangement, capture time, service-term start and end dates, invoice number and email status, and a candidate reference when the payment is a bounty. After a successful capture, the app creates a paid invoice and emails it to the agency contact. The invoice email includes the company and contact details, arrangement, amount, capture date, and service-term dates, plus the candidate reference for a bounty.

The current app behavior does not confirm which payment processor operates the hosted checkout or how that provider collects, handles, or retains payment-card details. Those disclosures need owner and counsel review.

When a deployment supplies the analytics app slug, the browser creates a random visitor ID and saves it in localStorage under polsia_vid. On page load, the app sends a beacon containing that app slug and visitor ID to the configured Polsia API endpoint. This description is limited to the values sent by the app code; it does not state additional analytics data or endpoint-side retention practices.

The current application does not establish retention periods for candidate, agency, payment, invoice, or visitor-ID records. Retention periods; full service-provider and payment-processor data handling; security practices; privacy rights and request handling; and any legal conclusions or jurisdiction-specific disclosures need owner and counsel review. No retention period, security guarantee, processor identity, or legal conclusion is stated here.

The current Terms of Service page lists producer-relay@polsia.app for terms and commercial-invoice questions. The owner and counsel should confirm that this address is monitored and appropriate for privacy inquiries and confirm the process for handling privacy requests. No separate privacy-request process is documented in the current app.