Public summary

Data handling summary

What partner and end-user data enters the system, where it goes, and how its use is limited to providing the service.

Updated: August 30, 2026
Scope: Public summary
Escalation: Formal follow-up available

Back to trust center Open trust packet Start partner review

Current control position

Blacklight limits collection to the service path and does not operate an advertising-profile business. Applicant content, operational records, partner configuration, and billing evidence are separated by purpose and access boundary.

Data handling summary · Current public evidence boundary

Current safeguards

What Blacklight currently does

These statements describe implemented controls and their limits in plain language. They are not a certification, legal opinion, or substitute for an institution-specific contract requirement.

Blacklight collects the information needed to generate, deliver, and support resume requests: intake details, uploaded documents, selected targets, delivery records, and support or privacy follow-up when needed.

That data stays tied to the service path rather than being reused for ad targeting, third-party tracking, or unrelated marketing profiling.

Special events default to aggregate-only organizer reporting. Sponsors do not receive participant names, contact information, resumes, request logs, portal access, or recruiting rights merely because they funded access.

The public site is intentionally cookie-light and tracking-light, so the normal assumptions people make about ad-tech stacks do not apply here.

Launch verification stores bounded operational evidence, including the authorized actor, active campaign, configuration fingerprint, and a hash of the confirmed public link rather than a reusable raw link token.

Delivered resume and cover-letter DOCX files stay plain-text and single-column for applicant tracking system (ATS) compatibility. They also use Word headings, lists, language information, and document properties to work better with assistive technology.

Next review path

Open the next document only if the review actually needs more

Start with this summary. Then move into the packet, appendix, or formal follow-up only when the reviewer needs a broader or more formal response. Move into partner review when the next useful step is rollout fit, launch scope, and trust review together.

Data handling summary

What Blacklight currently does

Open the next document only if the review actually needs more

Use the packet when the team needs one concise review document.

Use the appendix when the reviewer needs deeper technical detail.

Start the partner request when trust diligence has become a real rollout decision.

Request formal trust follow-up when the public materials are no longer enough.