Public summary

Data handling summary

What partner and end-user data enters the system, where it flows, and how it stays constrained to the service path.

Focused summaryReview-ready languageFormal follow-up available

Back to trust center Open trust packet Start partner review

Why this matters

Partners should not have to guess what Blacklight collects, who touches it, or whether a hidden ad-tech stack is following their users around. This summary explains the actual data path in plain language.

Data handling summary · Current public summary

Current summary

The main points a reviewer should actually take away

These points are written to be shareable and review-friendly. They give the reviewer a direct answer in plain language before the conversation turns into a longer procurement or questionnaire exchange. If the question has already turned into a real rollout decision, move into partner review instead of treating it like document-only follow-up.

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.

Delivered resume and cover-letter DOCX files stay plain-text and single-column for ATS compatibility while also adding semantic Word headings, list structure, language metadata, and document properties for better assistive-technology handling.

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

The main points a reviewer should actually take away

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 operational detail.

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

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