Privacy policy
In force from 21 November 2026.
The short version
- Chhaya is a tool for photography studios. A studio uses it to share photos with its clients, let them choose photos for their albums, and run its enquiries, quotations and calendar.
- Two kinds of data, two roles. For a studio's account, sign-in, our bills and how our apps behave, we decide what happens to the data, so we are its data fiduciary. For everything a studio keeps about its own clients and work (galleries, photos, the people in them, enquiries, quotations, its client list and calendar), the studio decides and we only process it for them, as their data processor. Questions about that data go to the studio first; we help them answer.
- Photos stay in India. Your photos, galleries and records are stored in Amazon Web Services' Mumbai region. A few services we use run outside India; they are listed in Who else handles data.
- We don't sell data, don't show ads and don't train AI on your photos. Face grouping (People) runs on our own servers, inside one project, and anyone in the photos can ask to be removed from it.
- Galleries are private. Only people the studio invites, signed in with the invited address, can open a gallery. Studio pages on
chhaya.pageare public by design. - You can ask to see, correct or delete your data, or complain, at privacy@chhaya.app. Our Grievance Officer answers within the times in Your rights.
Who we are
Chhaya ("Chhaya", "we", "us") is a service run from India. Its websites are chhaya.app, its subdomains (such as app.chhaya.app and <handle>.on.chhaya.app) and the studio pages on <handle>.chhaya.page.
| For | Write to |
|---|---|
| Privacy questions, requests, grievances | privacy@chhaya.app |
| Security problems | security@chhaya.app |
| Abuse, takedown and copyright notices | abuse@chhaya.app |
| Anything else | support@chhaya.app |
Grievance Officer: Prashanth Banda, privacy@chhaya.app (write "Grievance" in the subject).
Who this policy is for
| You are | What this policy covers for you |
|---|---|
| A studio owner or studio member | Everything: we are the fiduciary for your account, and we process your studio's client data on your studio's instructions (see the Data processing addendum). |
| A client a studio invited to a gallery, or who received a quotation from a studio | Your Chhaya account and sign-in, which are ours. Your gallery, your favourites, your album choices and your details on the studio's quotation are the studio's: the studio is your fiduciary for them. |
| Someone in a studio's photos, or who sent a studio an enquiry | The studio is your fiduciary. This policy tells you how we handle that data for the studio, and how to reach the studio or us. |
A visitor to chhaya.app or a studio page |
The little we learn from your visit (see Cookies and similar storage). |
Data we are responsible for
We decide why and how this data is used.
| Data | Why | Basis |
|---|---|---|
| Your account: your name, email address, profile picture and handle, from your Google account or the address you sign in with by code | To make and run your account and show who did what | Your consent when you create an account (DPDP Act s.6), and the contract (our Terms) |
| Sign-in: your Google account's identifier, the time you signed in, sessions and the device names you see in Your account | To keep you signed in and your account safe | Consent; security is part of the service you asked for |
| Your agreement: which version of our terms and this policy you agreed to, and when | To prove what you agreed to | Legal obligation and the contract |
| Studio details: the studio's name, handle, contact email and phone, logo, branding, its members and their roles | To run the studio's account | The contract |
| Billing: the studio's plan, subscription, invoices and receipts, payment references (such as a UPI or bank transfer reference), seller and buyer details on invoices | To bill, keep accounts and meet tax law | The contract and legal obligation (books of account) |
| Messages we send you: emails about your account, sign-in codes, billing reminders and notices of changes | To run the service | The contract |
| Support: what you write to us and what we did | To help you | Consent (you wrote to us) |
| Technical data: error reports, performance timings, page addresses with private parts removed, request logs, IP addresses in security logs | To keep Chhaya working and secure, and to find faults | Consent at sign-up for account holders; legal obligation for security logs (CERT-In directions) |
| Analytics (Microsoft Clarity): how you move through our pages, with photos masked | To learn where our pages confuse people | Only with your separate "yes"; you can change it any time in Your account › Privacy |
| Audit records: who changed what in a studio, and every time our staff open a studio | To keep a reliable record and protect studios | Legal obligation and the contract |
We don't use this data for advertising, and we don't sell or rent it to anyone.
Data we process for studios
Each studio is the data fiduciary for what it keeps on Chhaya about its clients and its work. We process it only to provide Chhaya to that studio, under the Data processing addendum. This includes:
- Photos and films the studio uploads, the viewing copies made from them, and, if the studio keeps them, originals and RAW files. Photos can carry details from the camera (EXIF), including when and where they were taken (location) and the camera's serial number. Galleries keep these details in the photos clients see and download; public studio pages never do (we strip them).
- Clients and contacts: names, phone numbers and email addresses a studio enters or collects, the studio's notes about them, and which enquiries, quotations and projects they're linked to.
- Enquiries sent to a studio through its Contact us form, its enquiry link or the form embedded on its own website: the sender's name, contact details, the date and kind of work, their message, how they found the studio, and the website the form was on.
- Quotations: what the studio offers, the client's contact, and, when a client accepts online, a record of the acceptance (the account, the time, the IP address and browser). This record is evidence for the studio; it is not an electronic signature under the IT Act.
- Bookings, events and the calendar: dates, venues, the team on each event. A calendar feed is a private address your calendar app reads; anyone who has it can read that calendar, so keep it private, and reset it if it leaks.
- What clients do in a gallery: favourites, the photos added to each album, album submissions, change requests on a quotation and, later, comments on photos.
- Payments a client made to the studio, which the studio records by hand. Chhaya never takes money from clients.
- People in photos (face grouping). See below.
If you are a client, an enquirer or someone in a studio's photos, the studio is the one to ask about this data: what it holds, correcting it, or deleting it. If you write to us instead, we pass your request to the studio within 7 days and help it answer. We may also act directly where the law requires us to, for example on a court order.
People in photos (face grouping)
Chhaya's People groups a project's photos by the faces in them, so clients can find the photos they're in. It is part of the plans that include it. The studio decides for each project whether People is on; it is on unless the studio turns it off.
- What it does. Our software finds faces in a project's photos and turns each into a set of numbers (a face template) that lets it group the same person's photos together. People on the project can name a group and correct it.
- What it doesn't do. It doesn't guess age, gender, ethnicity, mood or anything else about a person. It never compares faces across projects or studios, keeps no list of known faces, and isn't used to identify anyone outside the project. We don't use face data for our own purposes and don't train any model on it.
- Where it runs. On our own servers in AWS Mumbai, with open models we run ourselves. No outside face-recognition service sees the photos.
- Who sees it. People the studio gave access to the project see the groups (each person only in the photos they're allowed to see), the face thumbnails and the names. Nobody sees the face templates. Our staff can't open People, even when supporting a studio.
- When it's deleted. A project's face data (templates, thumbnails, groups and names) is deleted when a photo is deleted for good, when the project is closed, and when the studio is deleted. If the studio turns People off for a project, People is hidden at once and its face data is deleted after 180 days, unless the studio turns it back on before then; the studio can also delete it at once.
- Your say. The studio tells its clients, in its own agreement with them, that it uses Chhaya and that Chhaya groups faces, and gets their agreement (a parent's, for a child). If you are in a studio's photos and don't want to be grouped, ask the studio to turn People off for the project or to remove you; or write to privacy@chhaya.app, and we'll remove you from People in that project.
Face templates are biometric information, which the IT Act's SPDI Rules 2011 treat as sensitive personal data until the DPDP Act replaces them. We protect them as such.
Children
- A studio's team must be 18 or over, because only an adult can make the contract a studio's account needs.
- Clients can be any age. Galleries hold event photos and are family-friendly, so a studio may invite a younger family member. If you're under 18, a parent or guardian must agree before you create an account, and they can ask us about, correct or delete your data.
- Children appear in photos of weddings, family events and school functions. The studio is the fiduciary for those photos, and under the DPDP Act it must have a parent's or guardian's verifiable consent for processing a child's personal data. That consent should cover People, since children appear in event photos and are grouped like everyone else.
- We never track children's behaviour, profile them or show them advertising.
Where your data is stored
Your account, your studio's records, and every photo, film and file a studio uploads are stored in AWS's Mumbai region (ap-south-1), in India. Backups the studio buys (the Backup add-on, in S3 Glacier Deep Archive) are in Mumbai too.
Some data leaves India:
- Photos you view abroad. Our content delivery network (Amazon CloudFront) serves photos from its location nearest the viewer, so someone opening a gallery outside India receives copies from a server near them. Only people allowed to see a photo can fetch it.
- The services listed below that run outside India.
The DPDP Act lets the government restrict transfers to particular countries (s.16). None of our transfers goes to a restricted country today; if one ever did, we would stop it.
Who else handles data
We use these companies to run Chhaya. Each handles only what it needs, under its own terms with us. The Data processing addendum has the same list for studios.
| Service | What for | What it sees | Where |
|---|---|---|---|
| Amazon Web Services | Hosting, database, photo storage, processing, email (Amazon SES), backups | Everything stored in Chhaya | Mumbai, India; CloudFront worldwide |
| "Sign in with Google" | That you are signing in to Chhaya; your name, email and picture come back to us | Worldwide | |
| Grafana Labs (Grafana Cloud) | Error reports, performance data, logs and alerts | Technical data with names, emails, phone numbers and private links removed | Mumbai, India |
| Microsoft (Clarity) | Page analytics, only after you say yes | How you use our pages; photos, typing, numbers and email addresses masked | United States |
| Cloudflare | Domain names (DNS) and forwarding mail sent to our addresses | Our domain records; emails you send to @chhaya.app addresses pass through it |
Worldwide |
| Google (Gmail) | Our support, privacy and security mailboxes | Emails you send us | Worldwide |
| Slack | Alerts to our team about faults and staff access to a studio | Technical alerts; which studio a staff member opened, never its content | United States |
| Meta (WhatsApp), when we offer it | WhatsApp messages you agreed to receive, such as enquiry alerts | Your phone number and the message | Worldwide |
| Razorpay, when we offer online payment | Taking subscription payments from studios | The studio's payment details | India |
We'll update this list before we add a service that handles personal data. Studios are told in advance (see the addendum).
We may also disclose data when the law requires it (a court order, or a lawful request from a government agency under the IT Act or other law), to protect people from harm, or to a buyer of our business, which would be bound by this policy.
Cookies and similar storage
We use few cookies and no advertising cookies.
| Name | What for | How long | Needs your consent |
|---|---|---|---|
__Host-chhaya_session |
Keeps you signed in | Until you sign out, 30 days unused, or 400 days at most | No (essential) |
__Host-chhaya_sign_in and sign-in cookies |
Protect a sign-in while it happens | Minutes | No (essential) |
| Photo access cookies (on our media address) | Let your browser load only the photos you're allowed to see | 12 hours, renewed while you use Chhaya | No (essential) |
sidebar_state |
Remembers whether the side menu is open | 1 week | No (essential) |
_clck, _clsk (Microsoft Clarity) |
Page analytics | Up to a year; removed when you say no | Yes |
Our apps also keep things in your browser's storage: your theme and recent places, the last studio you opened, your analytics choice, and a copy of a project's photo list so it opens quickly (kept up to 30 days unopened and cleared when you sign out). None of it is sent to anyone else.
Clarity never runs on galleries, on sign-in pages, or before you say yes. You choose in the banner, and can change your mind in Your account › Privacy.
How long we keep data
We keep data only as long as we need it, then delete it. Where a studio decides (its own data), these are the defaults Chhaya applies.
| Data | Kept |
|---|---|
| Your account | Until you delete it |
| Sessions | Until they end, then 30 days |
| Photos and films in a project | Until the studio deletes them or closes the project |
| The Trash | 30 days, then deleted for good |
| A closed project | Its files are deleted (viewing copies, films, originals, RAW, face data, its Trash); its records (album choices, client names, quotations) stay with the studio until the studio is deleted |
| Face data | While the photo exists and People is on; 180 days after People is turned off |
| Enquiries never quoted | 12 months after the last change, unless the studio deletes them sooner; enquiries caught as spam, 7 days |
| Quotations | Never accepted: 12 months after they lapse. Accepted: while the project lasts, and the proof of acceptance for 3 years after |
| A studio's client list | While linked to an enquiry, quotation or project; 24 months after the last link goes |
| Content of emails and messages we send | 30 days after delivery; a record that a message was sent, 12 months |
| Notifications in the app | 90 days |
| Studio exports | 7 days after they're ready |
| Invoices, receipts and billing records | 8 years, as tax and company law require |
| Audit records and records of staff access to a studio | 3 years |
| Security logs | 1 year |
| Other technical logs and error reports | 14 to 90 days |
| Database backups | Daily copies kept 7 days and weekly copies kept 4 weeks, so at most 35 days, then deleted |
When a deleted photo is really gone. A photo deleted for good is removed from storage. Copies our content network has cached can be served for a while longer, but only to someone already allowed to see that photo.
When a studio ends
- If a studio stops paying, it keeps full use for 7 days. Then it is read-only for 7 more days and its galleries are paused; it can still export. If it still hasn't paid, it is deleted as below. Owners are emailed before each step.
- If a studio cancels, it keeps working until the end of the period it paid for. Then it is suspended, and its projects, photos, galleries, quotations, enquiries, studio page and client data are deleted within 7 days. Owners are emailed before this happens.
- If an owner deletes the studio, the deletion starts about 24 hours later (any owner can cancel it until then) and is finished within 7 days.
- What stays after a studio is deleted: its name and handle, plan and payment history, invoices and receipts, the list of who was on its team, and usage totals, kept for 8 years to meet accounting law. None of it is anyone else's personal data. The studio's handle can't be taken by anyone for one year.
- Accounts outlive studios. Deleting a studio doesn't delete its members' or clients' Chhaya accounts.
- Before deleting, a studio's owners can export its photos and records.
Your rights
Under the Digital Personal Data Protection Act, 2023 you have the right to:
- access a summary of your personal data and how it's used, and who it was shared with (s.11);
- correct, complete, update and erase it (s.12);
- withdraw consent at any time, as easily as you gave it (s.6(4)); withdrawing doesn't undo what was done before, and some features may stop working;
- have a grievance answered (s.13);
- nominate someone to exercise your rights if you die or can't (s.14).
How to use them:
- Your account: in Your account you can see and correct your details, download your data, change your analytics choice and delete your account. For anything else, write to privacy@chhaya.app.
- Data a studio holds about you (galleries, photos, enquiries, quotations): ask the studio. If it doesn't help, write to us.
- Nomination: write to privacy@chhaya.app with your nominee's name and contact details.
We may need to confirm it's you before acting. We acknowledge a request or grievance within 24 hours and answer it within 15 days. Some data we must keep even if you ask us to delete it, such as invoices (for tax law) and proof that a quotation was accepted (for the studio's contract); we'll tell you what and why.
If you're not satisfied with our answer, you may complain to the Data Protection Board of India.
Deleting your account removes your name, email, picture, sessions and favourites. Your comments, if any, stay as "Former member", and album choices you made stay with the studio, without your name, while its project lasts. Studios you owned must be handed to another owner or deleted first.
Security
- All traffic is encrypted (HTTPS, with HSTS). Data is encrypted at rest by AWS.
- Galleries and photos are reachable only by people the studio invited; every request is checked on the server.
- Sign-in uses Google or a one-time code; we never store passwords.
- Logs leave out names, emails, phone numbers, message contents and private links.
- Our staff work from separate staff accounts, can see studio and account details needed for support and billing, and can't see photos or galleries. To fix a problem a studio can't, a staff member may open that studio as "Chhaya support" for at most an hour, for a recorded reason; every such access is logged, and staff can never open People, billing, downloads or exports this way.
If a breach affects your personal data, we tell you and the Data Protection Board as the DPDP Act requires, and report it to CERT-In within 6 hours of noticing it. If it affects data we process for a studio, we tell the studio without delay so it can tell its clients.
To report a security problem, write to security@chhaya.app.
Emails and messages
- We email account holders about their account, sign-in, billing and changes to Chhaya. These aren't optional while you have an account.
- We send studios' messages to their clients on the studio's behalf: gallery invitations, quotations, sign-in codes and enquiry confirmations. They come from Chhaya's address with the studio's name. A studio chooses who on its team gets its notifications.
- Every message we send today is about your account, your studio or your galleries; we send no marketing. If we ever do, it will be occasional, only with your consent, and easy to stop. WhatsApp messages, when we offer them, are sent only if you turn them on, and you can stop them any time.
Changes to this policy
We'll update this policy when Chhaya changes. If a change matters, we'll tell account holders by email or in the app at least 30 days before it takes effect, and ask again for your consent where the law needs it. Previous versions stay available.
Law
This policy is written for the Digital Personal Data Protection Act, 2023 and its Rules, the Information Technology Act, 2000 and the rules under it. If a studio's client lives outside India, the studio is responsible for any further duties its client's law gives it; we help as the Data processing addendum describes.