Data processing addendum
This addendum is part of the Terms of use for every studio; there's nothing separate to sign.
1. Who does what
1.1. This addendum is between the studio (the data fiduciary, or under the GDPR the controller) and Chhaya ("we"), its data processor.
1.2. It covers the personal data in the studio's content: photos, films, originals and RAW (and the people in them, including face data from People), its clients and their contacts, enquiries, quotations and their acceptances, bookings, events and the calendar, client payments the studio records, and what clients do in galleries (favourites, album choices, change requests, comments).
1.3. It doesn't cover the data we decide about ourselves: the accounts of the studio's team and clients, sign-in, billing, our own messages, technical data and analytics. Our Privacy policy covers that.
2. Instructions
2.1. We process the studio's personal data only to provide Chhaya to the studio, as the studio uses and configures it (who it invites, what it uploads, whether People is on for each project, what clients may download), within the features of its plan, and as these terms describe. Those are the studio's instructions.
2.2. If we think an instruction breaks the law, we tell the studio and may decline it. If the law requires us to process data in another way, we tell the studio first, unless the law forbids it.
2.3. We don't sell the studio's data, use it for advertising, combine it with other studios' data, or use it to train AI models.
3. The studio's part
The studio:
- has a lawful basis for the data it puts on Chhaya, and gives the people concerned (clients, enquirers, guests, the people in its photos) the notice the DPDP Act s.5 requires, including that it uses Chhaya;
- has verifiable consent from a parent or guardian before processing a child's data (DPDP Act s.9), covering People;
- decides for each project whether People is on (biometric data under the SPDI Rules, 2011, rule 3); where it is on, tells its clients in its own agreement with them and has their agreement; and turns People off, or asks us to remove a person, when someone asks;
- answers the requests of the people whose data it holds (access, correction, erasure, grievance, nomination), and keeps its own retention rules;
- decides whether clients may download full size, knowing originals keep their location and camera details;
- tells us at once if it learns of a misuse of its account.
4. Our people
Everyone working on Chhaya who can reach the studio's data is bound to keep it confidential. Our staff can't see photos, galleries or People in the normal course. A staff member may open the studio as "Chhaya support" only to fix a problem or recover data, for a recorded reason, for at most an hour, and every access is logged and kept for 3 years.
5. Security
We keep reasonable security safeguards (DPDP Act s.8(5); IT Act s.43A and SPDI rule 8 while they apply), including:
- encryption in transit (HTTPS with HSTS) and at rest (AWS-managed encryption);
- access checked on the server for every request; galleries open only to the invited address, signed in;
- photos served through short-lived cookies scoped to what each person may see;
- face data in per-project storage that only the analysing service can read, never served to browsers;
- separate staff accounts with step-up sign-in, permissions held as roles, and an audit log;
- logs that leave out names, emails, phone numbers, message contents and private links;
- security logs kept for 1 year in India;
- backups of the database and, for studios with the Backup add-on, of their chosen originals and RAW.
6. Sub-processors
6.1. The studio authorises us to use these sub-processors. Each is bound by terms at least as protective as this addendum.
| Sub-processor | Service | Studio data it handles | Location |
|---|---|---|---|
| Amazon Web Services India / AWS | Hosting, database (Aurora DSQL), storage (S3), processing (Lambda, SQS), content delivery (CloudFront), email (SES), Deep Archive backups | All | Mumbai, India; CloudFront edges worldwide |
| Grafana Labs | Error reports, logs, traces | Technical data only, with personal details removed | Mumbai, India |
| Meta Platforms (WhatsApp), when offered | Notifications the recipient turned on | Phone number, message | Worldwide |
6.2. Changes. We publish the list in Who else handles data, in our Privacy policy, and tell the studio's owners at least 30 days before adding or replacing a sub-processor of studio data. If the studio objects on reasonable data-protection grounds and we can't resolve it, the studio may cancel and get a refund of the unused part of its paid period.
7. Where data is
The studio's data is stored in India (AWS Mumbai). Photos are delivered to viewers through CloudFront locations near them, which can be outside India. We won't move the studio's stored data out of India without 30 days' notice, and never to a country the government has restricted under DPDP Act s.16.
8. Breaches
8.1. If we become aware of a breach affecting the studio's personal data, we tell the studio's owners without undue delay, and within 24 hours, with what we know: what happened, what data and how many people, the likely effect, what we've done, and who to contact. We send more as we learn it.
8.2. We help the studio meet its own duties to inform the Data Protection Board and the people affected (DPDP Act s.8(6) and its Rules), and we report to CERT-In within 6 hours as its 2022 directions require.
9. Helping with requests
9.1. Most requests the studio can answer itself in Chhaya: finding a client's records, correcting them, deleting photos, removing a client from a gallery, erasing a client from Clients, turning People off for a project (its face data is deleted 180 days later, or at once if the studio chooses), and exporting data. We remove one person from People in a project when the studio asks.
9.2. Where it can't, we help, at no charge for reasonable requests, within 15 days. If a person asks us directly about the studio's data, we send the request to the studio within 7 days and don't answer it ourselves unless the studio asks or the law requires.
9.3. We give the studio the information it reasonably needs to show it meets its duties, and answer reasonable written questions about our safeguards once a year.
10. Deletion and return
10.1. During the subscription the studio can delete data any time; deleted photos go to the Trash for 30 days, then are deleted for good.
10.2. Before its subscription ends or it is deleted, the studio can export its data (photos, files and records, as ZIP files kept 7 days).
10.3. When a studio is deleted, or 7 days after its subscription ends following a cancellation, we delete its content and personal data, within 7 days. Copies in database backups are deleted within 35 days (daily backups are kept 7 days, weekly ones 4 weeks); photo copies cached by CloudFront are served only to people allowed to see them and expire. We keep only what the law requires: invoices, receipts and the studio's business record for 8 years, and acceptance records and audit records for the periods in the Privacy policy.
11. Foreign clients
If a studio's client or a person in its photos is in the European Union, the United Kingdom or another place whose law applies to the studio, the studio tells us, and we'll agree any further terms that law requires (for example standard contractual clauses under the GDPR, Art. 28 and 46). We don't promise that Chhaya meets every foreign law by default.
12. Order of precedence
If this addendum and the Terms of use conflict about personal data the studio puts on Chhaya, this addendum wins. Liability under it is subject to the limits in the Terms of use.