Scout & Sentry

Privacy policy

Last updated: July 31, 2026

What we process

We process account data, the professional profile chosen by the candidate, job briefs, introduction interactions, meetings, and security records necessary to provide the service. Protected attributes are not used for matching.

Optional LinkedIn import

If you connect LinkedIn, you authorize Scout & Sentry to retrieve and store the portability data you select: profile, experience, education, skills, and languages. LinkedIn limits this feature to eligible EEA and Swiss members and requires approval of our application. Imported data prefills a private draft and is never published without your review. OAuth tokens are encrypted and raw LinkedIn responses are not retained. You can disconnect LinkedIn without changing your profile, or use the privacy center to delete import sources and values that remain unchanged.

Why

We use this data to build profiles, calculate explainable professional matches, arrange consented introductions, secure access, and meet legal obligations. The legal basis depends on the operation: performance of the service, explicit consent to disclose identity, documented legitimate interests for security, or a legal obligation.

Visibility and recipients

A profile remains private until it is published. Before an introduction, only authorized anonymized projections are visible. Identity and contact details are disclosed only to the named organization after candidate approval, through limited and audited access.

Retention and rights

Quarantined files are deleted after processing or within 24 hours after a failure. Introduction access expires or is revoked according to its lifecycle. In the privacy center, you can export your data, delete data imported from LinkedIn, request account deletion, correct your profile, and revoke future access. Legally necessary audit evidence is minimized and pseudonymized.

Contact

For a data question or request, contact privacy@scoutandsentry.com. A copy already received by an organization cannot technically be recalled; revocation blocks future access and updates.