Privacy choices should be as reviewable as the product.
This notice explains what the website collects, why it is processed, how long it is kept, and what the live analysis workflow deliberately does not retain.
Scope and publisher.
This notice applies to the Role Evidence website, live analysis workflow, resource tools, contact form, subscription checkout, subscription management, and assisted onboarding. The publisher is Role Evidence. A production legal notice address must be supplied through the deployment configuration before publication.
Public website use.
The public content pages can be read without creating an account. The intended analytics configuration is cookieless and limited to content-free page and funnel events. It must not include email addresses, document names, role text, resume text, evidence bindings, model output, or free-form messages.
The website does not use a non-essential cookie banner because it does not intentionally set non-essential cookies. If that implementation changes, this notice and the consent interface must change before the new processing begins.
Analysis verification records.
The analysis workflow uses an email address for operational verification. The intended record includes a normalized email, an HMAC identifier, verification status, policy version, consent timestamp, expiry, and limited abuse-prevention state.
Operational analysis records are scheduled for deletion after 30 days. A marketing record is retained only when the visitor separately chooses optional marketing consent, and remains until unsubscribe or deletion.
Candidate and job content.
Uploaded resumes, job descriptions, extracted text, redacted text, model inputs, model outputs, result data, and generated dossiers are processed only to return the requested short-lived analysis result. They are not written to a database, object storage, email, analytics event, monitoring attachment, or application cache.
Candidate data is not used for model training, fine-tuning, enrichment, background research, or cross-customer learning. The live analysis workflow uses no external enrichment source.
Contact, checkout, and onboarding records.
A contact inquiry can include name, work email, organization, inquiry category, and message. A subscription purchase creates Stripe customer and subscription identifiers, billing status, and lifecycle timestamps. Assisted onboarding can include agency name, recruiter-count band, ATS, workflow description, and scheduling preference.
Payment card details are collected by Stripe and are not submitted to Role Evidence. Onboarding access requires a server-verified paid Checkout Session or signed access token.
Service providers and disclosure.
The intended production architecture assigns limited roles to hosting, database, email, billing, abuse-prevention, private inference, analytics, and monitoring providers. A provider should appear as active only when it is configured in the deployed environment.
Information may also be disclosed when required by law, to protect the service or another person, or as part of a transaction involving the business, subject to applicable safeguards and notice requirements.
Your requests.
Depending on location and context, a person may request access, correction, deletion, restriction, portability, or information about processing. Role Evidence may need to verify the request and may retain limited information when required for security, billing, dispute, or legal obligations.
Use the contact form for general inquiries.
Security and changes.
Reasonable technical and organizational controls are used for the information the service is configured to process. No internet service can promise absolute security. Material changes to this notice should receive a new effective date and, when required, direct notice.
Review the stricter analysis boundary.
The analysis data policy describes authority consent, transient content processing, suppression, browser memory, and reset behavior.