Data Processing Terms
1. Roles
For the employee and position data a Customer uploads to Sklton ("Organisation Data"), the Customer is the Data Fiduciary and [[registered company name]] ("Reward.AI") is its Data Processor, within the meaning of the Digital Personal Data Protection Act, 2023 and its rules ("DPDP Act").
2. What is processed
| Item | Detail |
|---|---|
| People concerned | The Customer's employees, contractors and vacant positions included in its upload |
| Data fields | As chosen by the Customer, typically: employee ID, name, business unit, department, position title, manager, level, age, annual cost, snapshot date, utilisation, location, employment status, market benchmark and pay band |
| Purpose | Producing organisation structure, cost analysis, findings, reports, notes and projects for the Customer inside Sklton |
| Duration | While the Customer's organisation exists in Sklton, then deletion as in section 8 |
3. Reward.AI's commitments
- Process Organisation Data only to provide Sklton to the Customer and on the Customer's documented instructions, which are these terms and the Customer's use of the product.
- Not sell it, use it for advertising, combine it with other customers' data, or use it to train AI models.
- Make sure staff who can access it are bound by confidentiality, and limit access to what is needed to support the Customer and run the service.
- Apply the security measures in section 5.
- Help the Customer respond to requests from the people concerned (access, correction, erasure, grievance), mainly through the product's own export, edit and delete features.
- Give the Customer reasonable information to show compliance with these terms.
4. Sub-processors
The Customer authorises these sub-processors. Reward.AI binds each to data protection obligations no weaker than these terms, and remains responsible for them.
| Sub-processor | Purpose | Location of Organisation Data |
|---|---|---|
| Supabase, Inc., on Amazon Web Services | Database, authentication, server functions | Mumbai, India (ap-south-1) |
Netlify (website files), jsDelivr (software library) and Hostinger (account emails) do not receive Organisation Data. Reward.AI will give at least 30 days' email notice before adding or replacing a sub-processor of Organisation Data; the Customer may object and, if no solution is found, cancel and receive a refund of unused prepaid fees.
5. Security measures
- Encryption in transit (TLS/HTTPS) and at rest.
- Tenant isolation enforced by database row-level security: users only access the organisation they belong to; dataset changes, invitations and member removal are limited to the CEO and admins.
- Passwords stored only as salted hashes; email confirmation required to join an organisation.
- Secret keys kept server-side only; the browser uses a publishable key bound by the database rules.
- Audit log of dataset uploads, approvals and archival in each workspace.
- Automated security checks of database configuration after each change; access security tests that verify one organisation cannot read another's data.
- Database backups by the hosting provider, retained for up to [[30]] days.
6. Personal data breach
Reward.AI will tell the Customer without undue delay, and in any case within 72 hours, after becoming aware of a breach affecting Organisation Data. It will describe what happened, the data and people likely affected, the steps taken, and a contact person, so the Customer can meet its own duty to inform the Data Protection Board and affected people. Reward.AI will cooperate with the Customer's investigation.
7. Location and transfer
Organisation Data is stored in India. Reward.AI will not transfer it outside India except as allowed by the DPDP Act, and with notice under section 4.
8. Return and deletion
The Customer can download its Organisation Data at any time (Data → Your data → Download all data). When the Customer's CEO deletes the organisation, Organisation Data is deleted from the live database immediately, and from backups within [[30]] days, unless the law requires Reward.AI to keep it.
9. Customer responsibilities
The Customer is responsible for having a lawful basis and giving the required notices to the people whose data it uploads, for the accuracy of that data, for limiting uploads to what the analysis needs, and for managing who in its organisation has access.
10. Contact
Data protection questions and breach contact: contact@sklton.cloud · Grievance Officer: [[Name]], [[address]].