1. Who we are, and our role
Tankha is operated by [Registered company name] Private Limited, [Registered office address, City, State, PIN] ("we", "us").
- For employee records that a business (our customer) keeps in Tankha, the business is the Data Fiduciary and decides why and how the data is used. We are its Data Processor and process that data only on its instructions.
- For account holders (the people who sign up and manage a company account), we are the Data Fiduciary.
If you are an employee and have a question about your records, contact your employer first. We will help them answer you.
2. What we collect, and why
| Data | Why |
|---|---|
| Account: name, work email, password (stored only as a one-way hash), role | To let you sign in and to control what you can see |
| Company: name, legal name, GSTIN, PAN, TAN, PF/ESI codes, offices, logo | To run payroll, show details on payslips and bill you |
| Employee records: name, code, contact details, joining/exit dates, department, PAN, UAN, ESI number, bank account, salary, tax regime and declarations, date of birth (optional) | Payroll, statutory deductions (PF, ESI, PT, TDS), payslips and legally required registers |
| Attendance: check-in/out times and, only when the employer has turned on a check-in radius for the office, the device location at check-in | Working hours, late marks and preventing check-ins from outside the office |
| Leave requests, approvals and balances | Leave management and payroll |
| Security data: IP address, browser/device type, sign-in times | Keeping accounts secure and showing your active sessions |
We collect only what these purposes need. We don't ask for Aadhaar numbers, biometrics, health data or religion. Optional fields stay optional.
3. Consent and notice
- Account holders agree to this policy and our Terms when signing up (the boxes are never pre-ticked), and we record the version and time.
- Employers are responsible for giving their employees notice and obtaining any consent the DPDP Act requires before adding their data. Tankha reminds them when adding employees.
- You can withdraw consent at any time. Withdrawal doesn't affect processing that the law requires, such as keeping payroll records.
4. Children's data
Tankha is for businesses and adults. Accounts can only be created by people aged 18 or over. Employees under 14 cannot be added (Child and Adolescent Labour Act, 1986). For employees aged 14–17, the employer must confirm they hold verifiable consent from a parent or guardian before saving their data, and we record that confirmation. We don't track, profile or target advertising at anyone, including children.
5. Sharing
We do not sell personal data or use it for advertising. We share it only:
- with service providers who host and run the service for us (for example cloud hosting and email delivery), under contracts that require confidentiality and security. Current providers: [hosting provider, region], [email provider];
- when the law requires it, for example a lawful order from a government authority;
- within the customer's own account: for example HR and admins see employee records, and employees see only their own.
The app uses no third-party analytics, advertising or tracking code. Fonts are served from our own servers.
6. How long we keep data
- Company and employee data: for as long as the customer's account is active. After deletion of an account, it is removed from our live systems straight away, and from backups within [30] days.
- Payroll, attendance and wage records: customers are legally required to keep these for several years (for example under the Code on Wages and the Income-tax Act). Customers can anonymise employees who have left, which removes their personal details while keeping the amounts.
- Ended sign-in sessions: 30 days. Read notifications: 180 days. Closed privacy requests: 2 years.
7. Security
- Each company's data is kept separate, and every request is checked against the signed-in person's company and role.
- Passwords are salted and hashed with bcrypt. Sign-in uses short-lived tokens and an httpOnly cookie, and you can sign out of any device.
- Data is encrypted in transit (HTTPS). Changes to attendance by HR are logged with who made them and why.
If a personal data breach affects you, we will inform the Data Protection Board of India and the affected customers as the DPDP Act requires.
8. Your rights
Under the DPDP Act you can ask to access a summary of your data, correct or update it, erase it (subject to legal retention), nominate someone to act for you, and raise a grievance.
- Signed-in users can download their data and send an export or deletion request from Settings › My account.
- Account owners can export or delete the whole company account from Settings › Privacy & data.
- You can also email privacy@[your-domain]. We reply within 30 days.
9. Cookies
We use only essential cookies, needed to keep you signed in. See the Cookie Policy.
10. Where data is stored
Data is stored in [India / hosting region]. If we ever transfer data outside India, we will do so only as the DPDP Act and Government notifications permit.
11. Emails
We send account emails you need (for example security and billing). Product updates are sent only if you opt in, and every such email has a one-click unsubscribe link.
12. Grievance Officer and contact
Grievance Officer: [Grievance Officer's name], grievance@[your-domain], [Registered office address, City, State, PIN]. We acknowledge grievances within 24 hours and resolve them within 30 days. If you're not satisfied, you can complain to the Data Protection Board of India.
13. Changes
We will tell account owners by email or in the app before material changes take effect, and show the date at the top of this page.