LEGAL

PeopleBind Privacy Policy

Last updated: 13 October 2026

This policy explains what personal data PeopleBind collects, why, who it's shared with, how long it's kept, and the choices you have. It covers the PeopleBind web application (app.peoplebind.com / peoplebind.com), its employee portal, the public careers/job-application pages, the PeopleBind API, and the PeopleBind MCP connector.

PeopleBind is operated by 1x1labs, 21, Sector-B, DHA-1, Islamabad, Pakistan ("PeopleBind", "we", "us"). PeopleBind is offered to businesses in Pakistan.

1. Who is responsible for your data

PeopleBind is an HR platform that companies ("Customers") use to manage their own employees and job applicants. That gives us two different roles:

If you're an employee or a job applicant, your employer (or the hiring company) decides what information about you is recorded in PeopleBind and who in that company can see it. Questions or requests about that data — access, correction, deletion — should go to them first; we will help them respond (§10).

2. What we collect

2.1 Data Customers enter about their employees

Depending on which modules a Customer uses and what they choose to record:

• Identity & contact: full name, employee code, work and personal email, phone number, photo, gender, date of birth, national ID number (CNIC), father's name, marital status, home address, emergency contact name and phone.
• Employment: department, designation, branch, manager, employment type and status, joining, confirmation and exit dates, employment history, shift.
• Pay & banking: basic salary, salary level and components, allowances, deductions, loans and repayments, tax withholding, payslips, bank name, account number and IBAN, final settlements.
• Time & attendance: check-in/check-out times, work sessions, overtime, timesheets, attendance corrections, scheduled shifts (dates, times, branch, role and any shift notes) where the Customer uses shift scheduling, and — only if the Customer turns it on — the location (latitude/longitude and accuracy) and a photo captured at check-in/out, plus whether it fell outside the office geofence.
• Leave: leave balances, requests, dates, and the reason given (which can include health information if the employee chooses to write it).
• Performance & development: goals, KPI scores, review comments, feedback notes, training and course records, kudos, survey responses (some surveys are anonymous — no link to the employee is stored).
• Expenses & assets: expense claims and receipt images, company assets assigned.
• Documents: contracts, ID copies, certificates and any other files the Customer uploads, with expiry dates.
• Onboarding: checklist tasks and their completion.

2.2 Job applicants

Name, contact details, CV/resume file, the answers given on the application form, the job applied for, interview notes, stage in the hiring process, and offer details. We also briefly record the network address of each application submission to prevent spam (deleted automatically — §9).

2.3 Account and usage data

• Sign-in: email address, password (stored only as a one-way hash by our authentication provider — we never see it), two-factor-authentication enrolment (the secret lives with the authentication provider), and — if you sign in with Google or Microsoft — the name and email those providers return.
• Roles & permissions assigned within your company.
• Inquiries and demo bookings (our own marketing): when someone asks for a recommendation on our Pricing page, we keep their name, work email, phone, company, team size and message, plus where they came from: the outside site that sent them (if any), the page they landed on, and any campaign tags on the link. When someone books a demo through our Calendly calendar, we keep their email, the meeting time and whether it was cancelled. We use this to answer the inquiry and to see which channels bring people to us.
• Activity records: an audit log of important changes (who did what, when), notifications, approvals, and an "online now" indicator based on when you last had PeopleBind open.
• Email-sending log: when someone sends an email through PeopleBind (an invitation, a payslip, a test message), we record who sent it, the recipient's address, the subject line and the time, to detect misuse and enforce sending limits. For notices PeopleBind sends on its own (for example a reply to a support ticket) we record the recipient's address, the subject line and the time, to keep within our email provider's limits. It never includes the message body.
• Device & technical: browser type and IP address in server logs; if you turn on push notifications, your browser's push subscription endpoint.
• Support: messages and attachments you send to our support/help desk.
• Integrations a Customer connects: Google/Microsoft calendar tokens (to add approved leave to an employee's calendar), a Slack incoming-webhook URL, ClickUp tokens, a BioTime server address and login (the password stored encrypted), outbound webhook URLs, and API keys (stored only as a hash).

2.4 What we don't collect

We don't run advertising trackers, and we don't sell personal data or use it for advertising.

Our public marketing and career pages, and the login and sign-up pages, can use Ahrefs Web Analytics to count visits and see which pages and referring sites visitors come from. It runs only if a visitor clicks Allow on the banner. Until then it is not loaded, and nothing is sent to Ahrefs. The visitor's answer is kept on their device so the banner is not asked again. When it runs, it records the page address, the page the visitor came from, and basic browser details (type, operating system and device type). Pages whose address carries a token, such as invitations and password resets, are never counted. If a visitor who said yes signs in during the same visit, the first app page may be recorded, and then the app reloads, so no further app pages are recorded. Ahrefs states that its tool does not use cookies by default; see Ahrefs' own privacy policy for what it does with this data.

3. How we use it

• To provide the service the Customer signed up for: running payroll, tracking attendance and leave, storing documents, managing hiring, sending the notifications and emails the product sends (leave decisions, payslips, reminders, invites).
• To keep it secure: authentication and two-factor authentication, permission checks, audit logs, rate limiting, fraud and abuse prevention, and diagnosing errors.
• AI features (available on some plans, used only when someone in the Customer's account uses them): the in-app assistant answering questions about the company's own data, searching the company's policy documents, suggesting text for performance reviews, drafting replies to support tickets, and extracting skills from resumes and ranking applicants. AI output is always a draft or suggestion for a person to review — it never makes final decisions about hiring, pay or employment on its own.
• To support you when you contact us.
• To run our business: billing, and meeting legal, tax and accounting obligations.

We don't use Customer data for any purpose of our own beyond these (for example, we don't build profiles of employees or combine data across Customers).

4. Why we are allowed to use it

For data we process as a processor (§1), the Customer is responsible for having a legal basis — typically the employment contract, a legal obligation (tax, labour law), or legitimate interests.

For data we control:

• Contract — to provide the account and service you signed up for.
• Legitimate interests — to secure the service, prevent abuse and improve reliability.
• Legal obligation — to keep financial records and respond to lawful requests.
• Consent — for optional features such as push notifications or calendar sync; you can withdraw it at any time in the app.

5. Who can see your data inside your company

Access is controlled by the roles your company assigns. Within PeopleBind:

• Every company's data is isolated from every other company's at the database level.
• National ID, bank and salary details are only shown to the employee themselves and to people whose role specifically allows it (for example HR or payroll) — a manager does not see their team members' CNIC, bank details or salary just by being their manager.
• Anyone whose role can see this sensitive data must use two-factor authentication.
• Changes an employee makes to their own bank details don't take effect until someone in HR or payroll approves them, and the employee is emailed whenever their bank details change.

6. Who we share it with

We share personal data only:

• With the service providers in §7, who process it on our behalf under contract.
• With integrations the Customer switches on (Google or Microsoft calendar, Slack, ClickUp, the Customer's own webhooks or API clients). What's sent is set by that integration — for example, calendar sync adds approved leave as "Approved leave" without the reason given.
• When the law requires it, such as a valid court order — we'll tell the affected Customer unless we're legally prevented from doing so.
• In a business transfer (merger, acquisition), under the same protections as this policy.

We never sell personal data.

7. Service providers (sub-processors)

Anthropic and OpenAI are used under their commercial API terms, which do not allow them to use the data we send to train their models.

8. International transfers

PeopleBind's customers and their employees are in Pakistan, but the data is not stored in Pakistan: our main database and file storage are in India (Mumbai), and some providers in §7 are in the United States or operate globally. Each provider is bound by contract to protect the data and use it only to provide its service to us, and data is encrypted whenever it travels between them. If Pakistani law comes to require that certain data be kept inside Pakistan, we will update how we store it and tell Customers in advance.

9. How long we keep it

A Customer can delete individual records (an employee, an applicant, a document) at any time; how long it keeps its own employees' records is its decision as controller.

10. Your rights

We give everyone whose data is in PeopleBind the ability to access their data, correct it, ask for it to be deleted, object to a particular use, get a copy of it, and withdraw consent they've given — subject to what the law requires us or the Customer to keep (for example payroll and tax records).

• Employees and applicants: contact your employer or the hiring company — they control your data. You can already see and update much of your own profile in the employee portal (bank-detail changes go to HR for approval). If you contact us directly we'll pass your request to the right Customer.
• Account holders and website visitors: email info@peoplebind.com. We'll respond within 30 days and may need to confirm your identity first.

If you're not satisfied with how a request was handled, contact us at info@peoplebind.com and we'll review it.

11. Security

• All connections are encrypted (HTTPS, with HSTS); data is encrypted at rest by our hosting provider.
• Every company's data is isolated at the database level, and each person only sees what their role allows.
• National ID, bank and salary details have an extra layer of restriction (§5).
• Two-factor authentication is required for administrators and anyone who can view sensitive employee data, and available to everyone.
• Passwords must be at least 10 characters and are stored only as one-way hashes.
• Uploaded files are private (the exception is profile photos, which anyone holding the photo's link can load), and each is only available to people allowed to see it.
• Important changes are recorded in an audit log.

No system is perfectly secure. If we become aware of a breach affecting personal data, we will notify affected Customers without undue delay, and authorities where the law requires.

12. Cookies and local storage

PeopleBind doesn't use advertising cookies. The app stores the following in your browser, all needed for it to work (for the public website's visit counting, see section 2.4):

• your sign-in session (kept only until you close the tab if you untick "Remember me");
• a queue of actions made while offline, so they can sync when you reconnect (cleared when you sign out);
• a service worker that caches the app for speed and offline use and delivers push notifications if you enable them;
• small interface preferences (light/dark theme, a collapsed sidebar, tips you've dismissed).
• where your visit to our public website started (the first page, the site that sent you, and any campaign tags), kept for this browser tab only, so an inquiry you send from the Pricing page can say where it came from. It is cleared when the tab closes and is never sent anywhere until you submit that form.

13. Children

PeopleBind is a workplace tool and isn't intended for use by anyone under 16. If a Customer records an employee or trainee under 18, the Customer is responsible for any consent the law requires from a parent or guardian.

14. Changes, governing law and contact

We'll post changes on this page and update the "Last updated" date; for material changes we'll also notify Customer account administrators by email in advance.

This policy is governed by the laws of Pakistan, and the courts at Islamabad have jurisdiction over any dispute about it.

Contact: 1x1labs, 21, Sector-B, DHA-1, Islamabad, Pakistan — info@peoplebind.com