Privacy Policy

Effective 8 November 2026. This describes what Kiptos actually does today, not what it may do later.

This document is not final.

The registered company name, address and grievance officer have not been filled in yet, so this page does not name the entity responsible for your data. It should not be relied on until it does.

Who we are

Kiptos is a people and work platform for businesses in India. The registered name and address of the company operating it are still to be added to this page. For anything in this policy, write to support@kiptos.com.

Kiptos is used by an organisation to manage its own employees. Your employer decides what goes into Kiptos and who inside the company can see it — they are the data fiduciary for that content, and we process it on their instructions. If you are an employee asking why a particular record exists, your employer is the right first stop; we will still help.

What we collect

  • Account details — name, email address, and a password stored only as a hash. We never see your password. When you create an account we record which version of these terms you agreed to, and when.
  • Employment records — designation, department, reporting manager, employment type and status, joining date, employee number and work location, as entered by your organisation.
  • Attendance — check-in and check-out times, breaks, expected shift timings, and regularisation requests.
  • Attendance location — see the dedicated section below.
  • Leave — requests, dates, type, any reason you write, approvals and balances.
  • Compensation and payroll — salary records, including how your pay is split into parts such as basic and allowances, payroll periods and the figures calculated from attendance, leave and approved overtime, where your organisation uses these features.
  • Work — projects, tasks, comments, time logs, uploaded files and documents.
  • Communication — channel and direct messages, reactions and mentions.
  • Activity log — a record of significant changes, kept so an organisation can audit who changed what and when.
  • Error reports — when a page fails, the error, the page's address and the browser type, so we can fix it. No names, emails or record contents.
  • Support reports — when you use Report a problem: what you write, any screenshots you add, and what the form shows it will send (the page you were on, your browser, screen size, app version, organisation and role). Your name and email are kept with it so we can reply.
  • Signed-in devices — for each browser where you're signed in: the browser and system it reports, its IP address, when it signed in and when it was last used. We use it to keep you signed in and to let you see and end your sessions in My Account. It's kept until that device signs out, or until you sign it out there.

We do not collect biometric data. Kiptos has no facial recognition, no selfie capture, and no liveness check.

If your employer added you before you joined

An administrator in your organisation can add you to Kiptos before you sign in, one person at a time or by importing a spreadsheet. Until you accept their invitation, Kiptos holds only what they entered: your name, work email, role, department, reporting manager, designation, employment type, joining date and employee number. A spreadsheet is read in their browser and is never uploaded to Kiptos.

You receive an invitation email that names the organisation and the person who added you. If you were added by mistake, or do not want to join, ask that organisation's administrators to remove you: until you join, removing you deletes these details completely.

Attendance location, specifically

When you mark attendance, Kiptos may record your device's reported latitude, longitude and accuracy at that moment. This matters enough to be precise about:

  • It is a single point at check-in and a single point at check-out. There is no trail, no continuous collection, and nothing is recorded while the app is closed or in the background.
  • Your browser asks your permission first, and declining does not stop you marking attendance — the record is simply saved without a location.
  • The coordinate is reported by your device and is not verified by us. It is context for your organisation, not proof of where you were.
  • It is visible only to people who can already see your attendance record under your organisation's permission settings — typically you, your reporting manager, and administrators.
  • Kiptos does not enforce a geofence and does not block attendance based on where you are.

Why we process it

To provide the service your organisation asked for: recording attendance and leave, running approvals, managing projects and tasks, enabling communication between colleagues, producing reports, and keeping the platform secure and available. We do not sell personal data, and we do not use your organisation's content to train machine-learning models.

Who processes it for us

  • Supabase — database, authentication and file storage.
  • Vercel — application hosting and delivery.
  • Resend — sending email: invitations, sign-in and password emails, and the notices Kiptos sends you. It receives the recipient's address and the message.

These providers operate infrastructure outside India, so your data may be stored or processed abroad under contractual protections with each provider.

Ask Kiptos answers from your organisation's records inside Kiptos. Your question and your data are not sent to any AI provider or other outside service.

How it is kept separate and secure

Every record in Kiptos belongs to one organisation, either directly or through the record it sits under, and is protected by database-level row security, so one organisation cannot read another's records — the boundary is enforced by the database itself, not only by application code. Access inside an organisation is further limited by role and by the permission matrix your administrator controls. Data is encrypted in transit and at rest.

A support report is read by you and by the Kiptos support team, not by anyone else in your organisation. Sending one gives our team that report, not access to your organisation's other records.

Your employer may give its accountant read-only access to its payroll records: pay runs once they are locked, salary heads and payroll settings, paid and unpaid days, paid leave and approved overtime as counts, and names, designations, joining and exit dates. The accountant never sees leave reasons, check-in times or locations, contact details, or anything outside payroll. Only the organisation's owner can give this access; it has an end date, can be ended at any time, needs two-step sign-in, and everything the accountant opens or downloads is logged for the owner. If your employer does this, My pay says so.

No system is perfectly secure, and we do not claim any certification we have not obtained.

How long we keep it

Records stay for as long as your organisation's account is active, because they are the organisation's operating history. We do not delete them on a timer.

Support reports are the exception. Their screenshots are deleted 30 days after the problem is marked solved, and the report itself 24 months after it is solved.

An accountant's access log, and the record of their access, are deleted 12 months after that access ends.

Projects and documents you delete inside Kiptos are held for at least 30 days before being purged, so an accidental deletion can be recovered.

An owner of an organisation can delete it from its settings. It is held for 30 days, so a mistake can be undone, and then deleted permanently along with its stored files. Before deleting, they can download everything as files.

An owner can also erase a person's personal details, for example after they leave. Their name, contact details, photo, personal documents and login are removed. Work records other people rely on, such as tasks and approvals, stay under a placeholder name.

You can also write to support@kiptos.com and we will help. We may retain something longer only where the law requires it, such as wage records.

Your rights

Under India's Digital Personal Data Protection Act, 2023, you may ask for access to your personal data, correction of anything inaccurate, erasure, and information about who it has been shared with. You may also nominate someone to exercise these rights on your behalf.

Because your employer controls the content in their workspace, please raise these requests with them first. Write to support@kiptos.com and we will help, or act directly where the request concerns data we control. Owners and administrators can export all of their organisation's data at any time from its settings.

Grievances

The name and contact details of our grievance officer are still to be added to this page. Until then, write to support@kiptos.com. If you are not satisfied with the response, you may complain to the Data Protection Board of India.

Changes

If we change this policy we will update the effective date above and, for anything material, tell organisation administrators directly.

Contact

Questions, requests or complaints: support@kiptos.com. See also our Terms of Service, the Data Processing Agreement that covers how we handle your organisation's data, and our Contact page.