Available on request
Our Data Processing Agreement (DPA) is a contract between your organisation and us, so we issue it to you directly, before you buy, during procurement or at any point in your subscription. This page summarises what it commits us to. The signed DPA is what binds us; this summary is not the agreement.
1. When it applies
The DPA applies whenever Serverstock Datacenter Private Limited processes personal data on your behalf in providing Satkosh. Under the Digital Personal Data Protection Act, 2023, you are the Data Fiduciary and Serverstock is a Data Processor, acting only on your documented instructions.
You decide what is backed up and are responsible for having a lawful basis for it. On personal data, the DPA prevails over the Terms of Service, the End User Licence Agreement and any commercial agreement between us.
2. What we process
Your backups are encrypted on your machines and written to the storage you choose; we do not inspect their contents. In running the Service, our systems hold:
| Category | What it includes |
|---|---|
| Console accounts | Name, designation, email address, credentials and sign-in times |
| Device records | Hostname, operating system, device identifier, agent version, last-seen time and hardware details |
| Backup operations | Job status, start and finish times, data volumes, snapshot identifiers and error messages |
| File and folder names | Shown only while a user browses a backup, and not stored |
| Alerts and notifications | Alert text, and the email addresses chosen to receive them |
| Audit records | Who did what, to which object, when, and from which IP address |
| Storage credentials | The credentials for your storage location, held encrypted |
We use this data only to schedule and run backups and restores, report their results, send alerts, control access and keep an audit trail. We do not need financial account data, health data, biometrics or government identifiers in our systems. Such data may exist inside your backups, which we do not process for any other purpose.
3. Encryption
- Backups are encrypted on your machine before they leave it. Traffic to our systems uses TLS, and our systems store data encrypted at rest.
- Managed encryption, the default: we generate and store the encryption key for you, encrypted, and use it only to run your backups and restores and to help you recover if you lose access.
- Zero-knowledge encryption: you hold the key alone, and nobody else can read your backups, including us. If you need us to be unable to access your backups, choose this option. If the key is lost, those backups cannot be recovered by anyone.
4. What we commit to
- Process personal data only on your documented instructions, and tell you if an instruction appears to breach the DPDP Act.
- Bind everyone who handles it to confidentiality.
- Keep the security measures in section 5 in place.
- Use sub-processors only as the DPA lists, and give you 30 days' written notice before adding or replacing one. You may object on reasonable data-protection grounds and, if we cannot resolve it, end the subscription without penalty.
- Notify your designated administrator of a personal data breach affecting our systems without undue delay, and in any event within 72 hours of becoming aware of it.
- Help you, as far as the Service allows, answer requests from individuals and enquiries from the Data Protection Board.
- Delete personal data as section 8 describes.
5. Security measures
- Encryption: backups encrypted on the source machine; TLS for all console, API and agent traffic; secrets encrypted at rest; passwords and recovery codes stored hashed.
- Access control: roles, with each customer's data kept to its own account; time-limited sessions ended when a password changes; two-factor sign-in for every user; limits on repeated sign-in and enrolment attempts. Restoring one machine's data onto another asks for sign-in again, raises an alert and emails you.
- Software integrity: the agent is code-signed, and every update is verified before it installs.
- Auditing and monitoring: security-relevant actions recorded with who, what, when and IP address; secrets kept out of logs; failed, overdue and offline backups raise alerts by email.
- Enrolment: enrolment tokens are limited to your account, in use and in time, and replaced by a per-device credential.
- Organisational: confidentiality obligations on staff, and production access only for those who need it.
The Security page describes these in more detail.
6. Sub-processors
| Provider | What for | Where |
|---|---|---|
| Cloud hosting provider | Hosting our systems, their database and its backups | India, Mumbai region |
| Email delivery provider | Alert, notification and account emails | India, Mumbai region |
| Our storage provider | Holding backups for customers who buy Satkosh storage | Currently India |
The signed DPA names each provider. Storage you own is not a sub-processor: you contract with that provider, and we only give the agent the credentials to write to it.
7. Where data is held
- Our systems are in India. We do not move that data outside India without your prior written consent, and we follow any restriction the Central Government sets under section 16 of the DPDP Act.
- Your backups are wherever the storage you choose is, inside or outside India. If they must stay in India, choose storage in India. Satkosh storage is currently in India.
8. Retention and deletion
- We keep the data in section 2 for as long as your subscription runs.
- When it ends, we delete your account, devices, policies, job history, alerts, notification settings and stored storage credentials within 30 days, and confirm it in writing.
- Audit records are kept for 365 days. They survive that deletion with the link to your organisation removed, and on written request we purge them within 90 days of the end.
- Backups in storage you own are not affected; deleting them is your decision. If you use managed encryption, ask us for the key before your account is deleted, or those backups can no longer be opened. Backups on Satkosh storage follow the Terms of Service.
- Locked copies cannot be deleted until their lock ends, whatever the instruction, and keep incurring storage charges until then.
9. What the DPA asks of you
- Have a lawful basis for the personal data you back up, and give any notice the DPDP Act requires.
- Set backup policies so that only data you mean to protect is backed up: the agent can read any file a policy covers.
- Manage your own console users, remove access when people leave, and turn on two-factor sign-in.
- Keep personal data out of free-text fields, such as policy names and device labels, where it is not needed.
- Choose your storage location, and take responsibility for where it is.
10. Audit, liability and changes
- Audit: once a year, on reasonable notice, we provide the information you need to check we meet the DPA, and answer a reasonable security questionnaire. On-site audits are by agreement on scope, timing and cost. Details that could weaken the security of the Service are shared under a mutual non-disclosure agreement.
- Liability: as limited in your agreement with us, except liability the DPDP Act does not allow to be limited.
- Law: the laws of India, with the courts at Nashik, Maharashtra.
- Changes: we give 30 days' written notice of changes to the DPA. If a change materially reduces your protection, you may end the subscription without penalty within that time.
11. How to get the DPA
Email legal@satkosh.com and we will send the current version, normally the same working day. Tell us if your procurement team needs it in a particular format, or countersigned. If your review needs more, such as a security questionnaire or detail on a specific control, ask in the same email.
Data Processing Agreement requests
Related documents
- Privacy Policy: how we handle personal data, published in full.
- Terms of Service: the terms the DPA sits alongside.
- Cookie Policy: the cookies and browser storage the website and console use.
- The End User Licence Agreement, presented when the Satkosh agent is installed.