GetPruf
Create your account
Company Name
Your Name
Email
Password
Where should we store candidate data?
πΊπΈ United States
AWS S3 us-east-1. General-purpose. Pick this if you have no regulatory reason to pick something else.
π¨π¦ Canada (PIPEDA)
AWS S3 ca-central-1. Personal Information Protection and Electronic Documents Act (Canada).
πͺπΊ European Union (GDPR, EU AI Act)
AWS S3 eu-central-1 (Frankfurt). GDPR + EU AI Act compliant. Required for EU candidates.
π·πΊ Russia (152-Π€Π)
Yandex Object Storage ru-central1. Federal Law 152-FZ compliant. Required for Russian Federation candidates.
Required by EU AI Act, GDPR, PIPEDA, and 152-FZ. Pick the region that covers your candidates' jurisdiction.
How will you obtain candidate consent?
Notify candidate and offer opt-out (recommended)
Each analysed candidate receives a short email naming your organisation and a 72-hour opt-out link. Safer default; no DPIA required.
Legitimate interest (requires published DPIA)
No candidate notification. Requires you to publish a Data Protection Impact Assessment at /dpia on your site. Only pick this if counsel has signed off.
GDPR Article 6 / 152-FZ Art. 9 lawful-basis. Affects whether the candidate is notified about the screening.
I agree to the
Terms of Service
and
Privacy Policy
I consent to GetPruf storing the raw resume files I upload (PDF, DOCX, image) on its infrastructure for the analysis purpose. Files are retained for up to 2 years from the upload date, after which they are automatically deleted from object storage; I can extend retention to 5 years in Settings, or delete files earlier from the dashboard. Legal basis: GDPR Art. 6(1)(a) - explicit consent.
Optional: I additionally consent to GetPruf using the raw resumes I upload to train and improve its detection models. This consent is separate, voluntary, and can be revoked at any time in Settings. Revocation applies only to future uploads - files already incorporated into a training corpus cannot be retracted.
Create account
Already have an account?
Sign in