Last updated: 27 September 2026
This Privacy Policy describes how the ALABTY WhatsApp Automation Chrome extension ("the Extension") handles data when used by recruiters with an ALABTY Applicant Tracking System (ATS) account. This policy applies only to the Extension, not to the ALABTY platform generally.
The Extension automates sending WhatsApp messages to candidates on behalf of a recruiter who is logged into the ALABTY ATS (recruitment.alabty.com). It detects pending outreach notifications created by the recruiter's own activity inside ALABTY, sends the corresponding message through the recruiter's own logged-in WhatsApp Web session, and reports the delivery outcome back to ALABTY.
| Data type | What it is | Where it comes from |
|---|---|---|
| Authentication token | The ALABTY session bearer token | Read from the recruiter's own authenticated requests to alabty.uat.pybex.io while they are logged in |
| Candidate contact data | Candidate name and phone number | Fetched from the ALABTY notifications API using the recruiter's own account |
| Message content | The pre-composed outreach message | Generated by ALABTY itself based on the recruiter's workflow |
| WhatsApp UI state | Whether WhatsApp Web is logged in, loading, or ready to send | Read from the DOM of web.whatsapp.com in the recruiter's own browser session |
| Send outcome | Sent / failed / invalid-number status | Determined by the Extension while sending, then written back to ALABTY |
Data is used strictly to carry out this single purpose. It is not used for advertising, analytics, profiling, or any purpose unrelated to sending the recruiter's own queued WhatsApp messages.
Queue state, counts, and settings are stored locally in the recruiter's own browser using Chrome's local storage — this data stays on the recruiter's device and is not transmitted to any server operated by the Extension developer. The only network calls the Extension makes are to:
The Extension does not sell, rent, or transfer candidate or recruiter data to any third party. Data flows only between the recruiter's browser, their own ALABTY account, and their own WhatsApp Web session — no data passes through, or is stored by, any server owned by the Extension developer.
The Extension does not retain data beyond what is needed to complete an active send queue. Local browser storage (counts, status) can be cleared at any time by removing the Extension or clearing Chrome's site/extension data. Candidate records and message history are retained according to ALABTY's own data retention practices, not the Extension's.
| Permission | Why it's needed |
|---|---|
| tabs / activeTab | Open, reuse, and focus the ALABTY and WhatsApp Web tabs |
| scripting | Run the two content scripts on ALABTY and WhatsApp Web |
| webRequest | Read the authorization header already sent to the recruiter's own ALABTY domain |
| storage | Save local queue state and settings on the recruiter's device |
| alarms | Schedule polling and queue auto-resume timing |
| notifications | Alert the recruiter when the queue needs attention |
| Host access: alabty.uat.pybex.io, web.whatsapp.com | The only two domains the Extension interacts with |
The Extension is a business tool intended for use by recruiters and is not directed at, or knowingly used by, children.
This policy may be updated if the Extension's functionality changes. The "Last updated" date at the top of this page will reflect the most recent revision.
For questions about this policy or how the Extension handles data, contact:
ALABTY Support
Email: support@alabty.com
Website: alabty.com