Legal
Privacy Policy
What we collect, why, where it lives, how long we keep it, and what you can ask of us. Written for the people whose details end up in a Corepilott workspace as much as for the company that runs it.
Draft prepared 23 September 2026 — for review by counsel before publication.
Effective date: [to fill: effective date]
1.Two roles, so read the right part
For this website and for your company’s account with us, we decide what is collected and why: we are the Data Fiduciary under the Digital Personal Data Protection Act, 2023. Clauses 2, 4 and 10 cover that.
For everything inside a workspace — employee records, candidates, client contacts, payroll — your company decides. It is the Data Fiduciary, and we process on its instructions as its Data Processor. Clauses 3, 5, 6 and 7 cover that. If you are an employee or portal user with a question about your own record, start with your company’s administrator; clause 9 explains how we help.
2.What this website collects
- Enquiry and demo forms: the name, email, company, company size and message you type. No identifier is attached and nothing is read from your browser that you did not enter.
- Sign-up: your name, work email, company name and a password. The password is stored only as an argon2id hash; we cannot read it back. A verification token is sent to the email address to prove it is yours.
- Sign-in on this site: the workspace name and email you enter, and a session token kept in your browser for that tab only.
- Server logs: the address, browser and time of each request, kept for security and fault-finding and rotated within 30 days.
3.What a workspace holds on your company’s behalf
Only what your company’s users enter or upload. Depending on the modules in use, that can include:
- Employees: name, contact details, date of birth, address, PAN, bank account for salary, statutory numbers, employment history, attendance and clock-ins including the device used, leave, timesheets, expense claims, payroll figures and payslips, grievances, learning records, and issued documents with the signature, IP address and browser recorded when one is signed.
- Candidates: the application, résumé, form answers, interview notes and scorecards.
- Clients and vendors: company details, GSTIN, contacts, quotations, purchase orders, invoices, bills, tickets and the messages exchanged through a portal.
- Call records: for telecalling, the number dialled, the outcome and the notes taken — not a recording.
- The audit trail: who changed what and when, which the application itself cannot edit or delete.
4.Why we process it
- To provide the Service your company subscribed to, including sending the mail it asks us to send.
- To bill your company and issue GST invoices.
- To keep the Service secure, investigate abuse and fix faults.
- To answer support requests — only with the access described in clause 6.
- To meet legal obligations, such as keeping tax records.
We do not sell personal data, use it for advertising, share one customer’s data with another, or use it to train models.
5.Where it is stored
Structured data lives in a PostgreSQL database in which every table is separated by customer using row-level security enforced by the database itself. Files live in one Cloudflare R2 bucket, in a separate folder per customer; no bucket is public and every download goes through the application, which checks who is asking. Both are hosted in the region configured for the deployment, which we state in the sub-processor table below. Data is encrypted in transit. Backups are taken nightly and we practise restoring them.
6.Who can see it
Inside a workspace, the roles and scopes your company’s administrators assign. Our own staff can look inside a workspace only if an administrator turns on support access, which is off by default, needs a stated reason, is read-only, expires after 60 minutes and is recorded in your company’s own audit trail.
We disclose personal data to a court, regulator or law-enforcement body only where the law compels us, and we tell your company first unless the law forbids it.
7.Sub-processors
The providers that handle data on our behalf. We give customers 30 days’ notice by email before adding one.
| Purpose | Provider | Location |
|---|---|---|
| File storage (attachments, PDFs, résumés, logos) | Cloudflare, Inc. — R2 object storage | Region as configured for the deployment |
| Application and database hosting | [to fill: hosting provider] | [to fill: region] |
| Transactional email delivery | [to fill: mail transport provider] | [to fill: region] |
| Payment collection and subscription invoices | [to fill: payment gateway] | India |
| Error monitoring and uptime checks | [to fill: monitoring provider, or “none”] | [to fill: region] |
Table to be completed before publication.
8.How long we keep it
- Workspace data: for as long as the subscription runs, then a 30-day window for your company to export it, then deletion within 60 days; backups roll off within 30 days after that.
- Enquiry and demo forms: 12 months from the last contact, unless a subscription follows.
- Our invoices to your company and our own audit records: for as long as tax and company law require, typically up to eight years.
- Server logs: 30 days.
9.Your rights
Under the Digital Personal Data Protection Act, 2023 you may ask for a summary of the personal data held about you and how it has been used; ask for it to be corrected, completed or updated; ask for it to be erased where it is no longer needed for the purpose it was collected; nominate a person to exercise these rights if you cannot; and have a grievance heard.
If the data sits in a workspace, your company answers the request and we assist it: correction and erasure are tools its administrator already has. If the data is ours — an enquiry, an account with us — write to the grievance officer below. We reply within 30 days. If you are not satisfied, you may complain to the Data Protection Board of India.
Grievance officer: [to fill: name], [to fill: email address], [to fill: postal address].
10.Cookies and browser storage
This website sets no cookies. It uses no third-party analytics, tracking script or advertising integration, and its fonts are served from our own server rather than fetched from a font service. Two things are kept in your browser, by you, for you:
corepilot.theme— whether you chose light or dark, in local storage, until you clear it.corepilot.token— your sign-in session, in session storage, gone when the tab closes.
If analytics are ever added, this clause changes first and a notice appears on the site before anything is set.
11.Changes and contact
When this policy changes we update the effective date above and, for a material change, email every account. Questions go to hello@corepilott.com; a signed data processing agreement is available on request.
Questions about this document: hello@corepilott.com
Terms of ServiceRefunds and cancellationData processing agreementHow the isolation model works