How Blacklight handles personal information

Scope

This Privacy Policy applies to the Blacklight Resumes public website, direct resume requests, partner-hosted or partner-referred Blacklight flows, special-event and sponsored-program review paths, status and delivery pages, support/privacy workflows, and partner portal access.

It covers public visitors, direct customers, partner-referred end users, partner contacts, and partner portal users.

What We Collect

• Contact information such as name, email, phone number, and location details
• Resume uploads, intake responses, portfolio links, LinkedIn links, education, experience, project, and certification information
• Job-target information such as job titles, company names, and job descriptions
• Generated resumes, draft versions, cover letters, extras, quality scores and decisions, refund evidence, and analysis connected to a request
• Payment, invoice, and transaction metadata needed to process purchases, refunds, partner billing, and account administration
• Billing records such as invoice copies, invoice status history, billing contacts, PO details, and contract-linked commercial terms where applicable
• Billing-dispute information such as the charge and amount at issue, discovery time, written claim, identity-provider alerts, device or session findings, employment or access changes, and internal investigation details supplied by the organization
• Support, privacy, trust, procurement, meeting-booking, and contact-request information
• Special-event review and operating details such as event type and name, sponsor, dates, expected attendees, participating employers, expected resume submissions, audience, delivery format, reporting preference, participant-access setting, access window, cap preference, invoice contact, turnaround requirements, and confidentiality notes
• Event-agreement evidence such as the accepting organizer representative’s name, work email, title, acceptance method and time, quote or order reference, terms version, and the accepted commercial and participant-access terms
• Partner Service Agreement and Order Form evidence such as the organization legal name, accepting Organization administrator’s name, work email and title, acceptance statement and time, agreement and policy versions, package fingerprint, and the accepted service, implementation, contract, pricing, invoice, and purchase-order terms
• Partner agreement billing-operation evidence such as the agreement and contract linkage, initiating administrator identifier, immutable invoice or subscription intent, bounded payment-provider references and status, reconciliation result, error code, and timestamps
• Partner account, role, location, hosted-link, embed, and reporting metadata used to operate partner programs
• Email-only eligibility-code distribution lists, preflight classifications, delivery status, and suppression or bounce information when an Organization administrator asks Blacklight to send participant invitations
• Technical, security, and operational event data such as IP address, browser details, request status, and authentication events

How We Use Information

• Generate and deliver resume packages and related materials
• Create and compare a limited number of draft versions, apply quality and consistency checks, choose the version that best passes those checks, and administer an applicable refund or partner-plan adjustment
• Operate request status pages, delivery links, resend tools, and support
• Process payments, refunds, partner billing, and account administration
• Investigate billing disputes and suspected account compromise, contain further exposure, compare organization-supplied evidence with Blacklight records, communicate review status, and determine or apply an appropriate billing outcome
• Support partner-hosted and partner-referred requests, including hosted links, website embeds, and trust or commercial review
• Authenticate users and enforce role-based access in partner and admin areas
• Prepare partner reports and workbook exports using combined totals or access limited by role and location
• Improve output quality, service reliability, abuse prevention, and platform security
• Comply with legal obligations and preserve required operational or compliance records

Partner-Hosted Requests

Some requests are submitted through a partner such as a library system, workforce organization, college, university, job fair, hiring event, or other adult-serving institution.

In those cases, Blacklight still processes the request, generates the materials, and operates the status and delivery flow. The partner may have limited visibility into request activity associated with its own program, subject to role and location-based access controls.

When a partner provides participant support, authorized staff may receive limited access to participant names, email addresses, delivery status, target summaries, and support activity. Reporting-only users do not receive participant records or contact information.

Special events start with aggregate-only organizer reporting. Event sponsors do not receive participant names, contact information, resumes, or request logs merely because they funded an event. Any future recruiting follow-up requires a separate participant choice and is not created by the sponsorship itself.

Special-event and sponsored-program requests require review before launch. Submitting event details can create a review record or support ticket, but it does not automatically create an event account, approve billing, change limits, or open a standard trial.

When a partner enables a participant package limit, Blacklight derives a keyed identifier scoped to that partner from the verified email or single-use eligibility code. The identifier is used to count accepted packages within the displayed program period, prevent link or location changes from resetting the allowance, support exception review, and produce aggregate program reporting. It is not used to correlate a person across unrelated partner organizations.

Verified-email limits mean per verified email, not verified unique person. Eligibility-code programs store a protected one-way version of the code rather than the readable code after generation, and Blacklight does not ask partners to send library-card, student, employee, or government identifier values for this feature. Cookies, browser storage, device signals, and IP addresses are not used as the participant eligibility identity, although limited network or device signals may still support abuse prevention and security.

For eligibility-code administration, Blacklight stores a non-participant batch label, batch identifier, quantity, validity dates, status counts, issuing account role, and any revocation time, authorized actor, reason category, and bounded reason note. For a downloaded batch, readable codes appear only in the one-time generation response and export. For Blacklight-assisted email distribution, each readable code is encrypted only while its message is pending, is not placed in the general email-outbox payload, and is cleared after provider acceptance or a terminal cancellation or failure.

An email-only CSV is parsed in the administrator’s browser and the raw file is not uploaded. Blacklight receives the extracted addresses needed for preflight and delivery, checks them for syntax, common domain mistakes, mail routing, duplicates, selected disposable domains, shared role addresses, and existing suppressions, and sends approved invitations through Postmark. These checks do not establish identity or guarantee inbox placement.

Participant-facing limit checks do not disclose whether an unrelated email address has used the program. Partner reporting is aggregate by default; participant support access remains limited by role and location, while reporting-only and sponsor access does not include participant identity or request detail.

Billing Disputes And Security Evidence

When an organization reports a billing dispute or suspected account compromise, we collect the claim, the invoice charge and amount at issue, when the concern was discovered, the submitting account and contact information, and supporting information the organization chooses to provide. Supporting information may include identity-provider alerts, device or session findings, employment or access changes, notification records, and internal investigation details, and it may relate to the organization’s administrators or employees.

We also record bounded workflow metadata such as the case number, invoice issue date, assigned reviewer, security-containment state, customer information requests and responses, review deadlines, escalation state, and notification history. Escalation emails are designed to contain the case number, severity, deadline, and a protected admin link rather than the organization’s evidence narrative.

We use this information to secure affected access, suspend further billable overages during review, investigate authorization and billing activity, compare organization-supplied evidence with Blacklight authentication, authorization, notification, usage, delivery, invoice, and audit records, communicate case status, determine credits, refunds, or amounts owed, prevent fraud or abuse, and preserve the decision history.

Access is limited to authorized organization billing roles and Blacklight personnel, support providers, or professional advisors who need the information for billing, security, investigation, or review. Payment providers receive only the information needed to pause collection or apply an approved adjustment. We do not use billing-dispute evidence for advertising or sell it.

Submit only information needed for the review. Do not provide passwords, recovery codes, full payment-card data, or unrelated personal information.

Adult-Serving Institution Programs

Blacklight currently supports institution-led workflows for participants age 18 or older, including colleges, universities, workforce programs, library systems, and special events.

Blacklight does not currently activate K–12 or under-18 programs. Any future teen-program pathway would remain disabled until separate program classification, contract, privacy, and legal review is complete.

How We Share Information

We do not use a hidden data-sale or advertising-tracking model. We share information only as needed to operate the service, work with service providers, comply with law, protect the service, or support partner-originated request workflows.

• Infrastructure, hosting, storage, and authentication providers
• Payment processors and transactional email providers
• Model and AI providers used for request generation and processing
• Professional advisors, auditors, and service providers working on our behalf
• Law enforcement, regulators, courts, or other parties where disclosure is legally required or reasonably necessary
• Authorized operational partners associated with partner-originated requests, within the disclosed role, location, and program limits

Core Providers

Blacklight currently relies on core providers such as Stripe for payments, Postmark for transactional email, Supabase for database, storage, and authentication infrastructure, Cloudflare for hosting and edge delivery, Zoho for business email, CRM-linked outreach logging, and meeting scheduling where used, and OpenAI and related model tooling where needed for generation and processing.

For direct payments, Stripe receives the transaction amount and currency, an internal request reference, the selected package code, and the receipt email needed for the transaction. Blacklight does not send the target job role in PaymentIntent metadata.

AI And Automated Processing

Blacklight uses AI-assisted and automated processing to analyze request inputs, create and compare a limited number of draft versions, score or evaluate results, and check for missing or inconsistent content before release. AI-assisted output still requires user review and judgment before use.

Blacklight does not rely on a persistent external chat history as the official record of the service. OpenAI API requests are sent from the server-side queue with response storage turned off (`store: false`). OpenAI states that API data is not used to train its models by default, and Blacklight’s account sharing controls for inputs, outputs, feedback, evaluation, and fine-tuning data are disabled.

Under OpenAI’s standard API handling, limited API data may still be retained for abuse monitoring for up to 30 days unless a different retention arrangement or legal exception applies. Blacklight does not currently have Zero Data Retention. Blacklight’s own request records, outputs, and retention/deletion rules remain the primary business record for the service.

Cookies And Similar Technologies

The public site is designed to avoid advertising cookies and third-party tracking pixels as a business model. We may still use limited session handling, local storage, and internal analytics or event logging needed to operate, secure, and improve the service.

Public search-indexing signals such as crawler hints or IndexNow URL notifications are limited to public website URLs and do not add advertising cookies or browser-side tracking pixels.

Retention And Deletion

We do not intend to keep request-linked personal information forever. Different record types have different retention and minimization rules.

Our current operational approach includes a limited recoverable case-file window for request content, redaction of older messaging content, minimization of older audit and site network fields, deletion or trimming of aged queue records, and cleanup of older support attachments and tickets.

Request-scoped candidate text and sensitive quality issue or evidence details follow the recoverable case-file window. After that window, Blacklight may retain limited non-content operational evidence such as candidate counts, scores, outcomes, prompt versions, hashes, compensation state, and timestamps for service accountability and aggregate reporting.

Participant-access verification sessions, partner-scoped enforcement keys, eligibility-code batches and hashes, exception records, and reservation links are scheduled for deletion after the applicable program period plus 120 days. Blacklight may retain deidentified aggregate totals and the limited policy or audit history needed to show which rule, period, role, code issuance or revocation, exception, or allowance release applied.

Eligibility-code recipient addresses are minimized to masked values after thirty days, while bounded delivery state may remain with the related batch until the program period plus 120-day deletion point. General email-outbox recipient and message content follows the existing thirty-day redaction schedule.

Billing records, including invoice copies and invoice/payment status history, may be retained longer than resume-request artifacts for accounting, audit, tax, contract-enforcement, collections, legal-hold, fraud-review, and dispute-resolution purposes.

For a closed billing dispute, we generally keep the full claim, evidence narratives, actor identifiers, investigation details, and provider-response details for one year after the latest final decision, adjustment, or collection activity. We then minimize that content and retain a limited financial and outcome record for up to seven years from that activity before deleting or irreversibly deidentifying the dispute-specific record.

An active legal hold, unresolved balance, continuing fraud or security investigation, or documented retention requirement may pause those steps. Active holds are scheduled for review at least every ninety days, and information such as passwords, recovery codes, full payment-card data, or unrelated personal information should not be submitted and may be redacted sooner if discovered.

If you submit a validated privacy deletion request, Blacklight may delete generated artifacts, delete or scrub uploaded files and request-linked content where supported, scrub applicant-linked PII in structured records, and preserve only limited records needed for compliance, disputes, legal holds, fraud review, or security.

Where a billing, collections, or legal need applies, limited billing and contract records may remain after account closure or privacy deletion even if resume artifacts and other operational content are removed on a shorter schedule.

Partner Account Closure And Deletion Requests

Closing a partner account and deleting partner data are not the same workflow. Account closure can end service access while billing, contract, audit, or dispute records are still retained.

If an authorized partner representative asks us to delete partner data, we may verify authority first, close or disable service access if needed, and then remove or minimize service data such as generated resumes, uploaded source files, support attachments, and bulky intake content where supported.

We may refuse or limit deletion where records must be retained for unpaid invoices, tax/accounting, fraud review, legal obligations, legal holds, collections activity, contract enforcement, security, or disputes. In those cases, we keep the minimum record set we reasonably need for those purposes.

Your Choices And Rights

Depending on where you live, you may have rights to request access to, correction of, deletion of, or information about personal information we hold about you.

You can use the contact/privacy path on the website to ask privacy questions or submit a privacy request. We may need to verify your identity before fulfilling certain requests.

Partner Portal Users

If you use the partner portal, we collect account and role information such as email, role, authentication linkage, scope, and related partner or location metadata. We use that information to manage access, enforce role restrictions, route notifications, operate hosted links and embeds, prepare scoped reporting, and support account administration.

Partner portal activity can also include billing-state changes, plan-change confirmations, support tickets, trust/commercial review requests, special-event support requests, event-agreement evidence, and meeting-booking context when those workflows are used.

Partner portal billing activity can include dispute claims, supporting evidence, case communications, review outcomes, and related collection or adjustment history.

If a partner account later closes or submits a deletion request, we may disable partner-user access quickly while retaining limited billing, contract, audit, or legal records that still apply to the institution account.

Security

We use administrative, technical, and organizational measures designed to protect personal information, including access controls, authentication requirements for protected areas, audit logging for sensitive administrative actions, hashed token handling for status and campaign access, and role-based and location-based access controls for partner access.

Billing records and invoice copies are treated as sensitive business records and are intended to be limited to billing, admin, finance, support, legal, or similarly authorized personnel with a legitimate operational need.

No system is completely secure, and we cannot guarantee absolute security.

Age Eligibility

Blacklight Resumes’ currently available service is for people age 18 or older. We do not knowingly offer the current public or partner intake to people under 18.

A future teen-program proposal would require a separate review and activation decision before any under-18 participant intake could be enabled.

International Users

Blacklight operates from the United States. If you use the service from outside the United States, you understand that information may be processed and stored in the United States or other jurisdictions used by our service providers.

Changes To This Policy

We may update this Privacy Policy from time to time. If we make material changes, we may update the date on this page and take additional steps where appropriate.

Contact

For privacy questions or requests, use the contact page and select the privacy path so we can route the issue correctly.