Contact RoleSift support.
Reach the RoleSift team during the private beta. This page covers what to include — and what to leave out — when you write in.
How to reach us
During the beta, email RoleSift at sebcolliedog@gmail.com for access, account, extension, billing, privacy, or security support. Do not include passwords, card numbers, API keys, national ID numbers, or unnecessary CV details in support messages.
Where to send what
Use these subject lines so we can triage faster. Include only the details listed — no secrets, no full CVs.
Use subject RoleSift private beta access request. Include the email you want to use, whether you have an invite code, and whether you are testing on desktop Google Chrome.
Include your RoleSift account email, the page you were on, and the exact login or access-code issue. Do not send passwords or authentication tokens.
Include Chrome version, RoleSift extension version, affected job site URL, expected result, and actual result. Redact screenshots before sending them.
For checkout, subscription, or refund questions, include your RoleSift account email and approximate charge date. Stripe handles card details, so never send card numbers.
Report suspicious behavior, unexpected redirects, permission concerns, or privacy requests. Redact CV details, passwords, tokens, and employer-confidential material.
Support messages are not a place for secrets
Keep secrets out of support email.
RoleSift support can investigate account, extension, billing, privacy, and security issues without passwords, bank details, national ID numbers, API keys, medical data, or full unredacted CVs.