Legal
Privacy policy
Effective date: 11 October 2026
This policy explains what personal data Artiz Studio handles, why, where it is kept, for how long, and what control you have over it. The short version:
• Your original photo files stay on your own computer unless your studio turns on cloud backup of originals. • Our photo analysis (culling, face grouping, retouching) runs on your own computer or phone. We never send photos to outside AI services and never use anyone's photos to train AI models. • Face recognition is off until a studio turns it on, and a guest's face is searched only after the guest agrees. • We don't sell personal data, show adverts or use third-party analytics or tracking. • Our database and app server are in Bangalore, India. Photos are stored with Cloudflare R2, which does not guarantee that the files stay in India. • For photography studios we are the Data Fiduciary of their account data. For a studio's clients and guests, the studio decides how their photos are used and we act only on its behalf, as its Data Processor.
Who we are
Artiz Studio is a product of NEW.E AI Solutions, with its office at Madurai, Tamil Nadu, India ("we", "us", "our"). The "Service" means our website (https://artizz.in), our web app (https://app.artizz.in), the Windows desktop app, and everything studios share through them: client galleries, selection and album-approval pages, guest "My photos" pages, the photo-booth kiosk, event devices, the live event wall, the frame shop, the studio directory and referral pages.
Who this policy covers
• Studios and their team members: photographers and staff with an account. • Clients and guests: couples, families, event guests and anyone else who opens a link a studio shares, picks photos, reviews an album, uses the kiosk or "Find my photos", orders frames or appears in a studio's photos. They don't need an account. • Couples who use the studio directory or a referral page to contact a studio. • Website visitors.
Our two roles
India's Digital Personal Data Protection Act, 2023 (the "DPDP Act") separates the Data Fiduciary, who decides why and how personal data is used, from a Data Processor, who processes it on the fiduciary's behalf.
We are the Data Fiduciary for:
• studio accounts, team members, sign-in and security records, two-step verification settings and billing; • the studio directory (listings, verification details and the enquiry form); • ratings of Artiz Studio that guests give inside a gallery; • our website, its contact and early-access forms, and our server logs; and • the rules of a guest's "Find my photos" enrolment that we set (the longest time a face signature may be kept, and the "Delete my data" button). The studio decides whether face search is used at its event and is responsible for that choice.
We are a Data Processor, acting for the studio, for:
• photos, previews, retouched images, albums and deliveries the studio puts in the cloud; • client records, selections, comments, reviewer names and album approval records; • face signatures of people in the studio's photos, when the studio uses cloud face search; • booth photos, frame orders, reminder e-mails and messages the studio sends to its clients; and • enquiries once they reach the studio's client list.
If you are a client or guest, please contact the studio first about your photos: to remove a photo, close a gallery, get a copy of your data or ask how it is used. If you can't reach the studio, or need help, contact our Grievance Officer (details at the end). We will pass your request to the studio and help it respond. Studios can ask us for our Data Processing Addendum.
What we collect, and why
Each item below says what we collect, why, and our basis under the DPDP Act. "Legitimate use" means a use the DPDP Act allows without separate consent, mainly under section 7(a), where you gave us the data for that purpose (for example, to run your account). "Consent" means we ask you first, and you can withdraw it at any time.
Studio account. The studio name, the account holder's name and e-mail address, and a password, which we store only as a salted scrypt hash. If you use "Sign in with Google", Google tells us your name, e-mail address and Google account ID; we never see your Google password. Team members' names, e-mail addresses and roles. Studio branding you add (logo, colour, phone, e-mail, website, social links). Why: to run your account and the Service. Basis: legitimate use (you gave it to use the Service).
Two-step verification. If you turn it on: the method you chose, your mobile number for SMS codes, an authenticator secret (stored encrypted), backup codes (stored hashed) and the devices you chose to trust for 30 days. Platform administrators must use two-step verification. Why: to protect accounts. Basis: legitimate use.
Billing. Your plan, billing cycle, amounts, dates, payment status and method type, and Razorpay's subscription, mandate and payment references. Card numbers, CVV, UPI PINs and banking passwords go straight to Razorpay or your bank; we never see or store them. Why: to charge for and manage your subscription, and to keep the accounting and tax records the law requires. Basis: legitimate use and legal obligation.
Studio content in the cloud. When a project is synced to the cloud: smart previews (smaller copies of photos), thumbnails, retouched images, album designs, full-size delivery copies the studio chooses to share, booth photos, photos from event devices waiting to reach the event computer, and, only if the studio turns on cloud backup of originals (a paid add-on), copies of the original camera files. Why: to show galleries, sync the studio's computers and deliver photos. Basis: we process this on the studio's instructions; the studio is responsible for its own basis.
Client and guest records. What the studio enters about its clients (for example names, phone numbers, e-mail addresses and event dates), and what clients and guests do on a shared link: favourites, notes, comments, change requests, the name a family member types to review, and downloads. Why: to provide selection, review and delivery for the studio. Basis: processed on the studio's instructions.
Album approval records. When a client approves an album design, we record the typed name, the confirmation that they agree, the date and time, the browser and device details (user-agent), the IP address, and a fingerprint (SHA-256 hash) of the exact album version approved. This is an approval record: a valid electronic record of the client's agreement. It is not an "electronic signature" as the Information Technology Act, 2000 defines that term. Why: so the studio and the client have reliable proof of what was approved. Basis: processed on the studio's instructions.
Face signatures in a studio's photos. A face signature is a list of numbers describing a face. It is biometric data, which we treat as sensitive. Face recognition is off until the studio chooses to turn it on in the app; face grouping then runs on the studio's own computer. Face signatures, and the names a studio gives to people (for example "bride"), are kept in our cloud only while face search (guest "Find my photos" or kiosk search) is switched on for at least one open link of that project. When face search is off on every link, or the links close (for example because the project is cleaned up from the cloud or deleted), we delete that project's face signatures from the cloud. The studio's own computers keep their copy. Face signatures are used only to find people within that one project, never compared across projects or studios, and never used for any other purpose. Why: to let guests find their own photos. Basis: processed on the studio's instructions; the studio is responsible for its client's consent and for telling guests.
Guest selfies ("Find my photos"). A guest can take a selfie to find photos they appear in. Before the camera opens, we explain what will happen and ask the guest to confirm that they are 18 or older, or that a parent or guardian agrees. Then:
• On a guest's own phone, the phone turns the selfie into a face signature. The selfie never leaves the phone. Only the face signature is sent, used once to search that event's photos, and then discarded. It is not stored. • At a photo-booth kiosk on the event laptop, the selfie is processed on the laptop and deleted as soon as the search ends. • At a kiosk phone or tablet paired over the venue's local network, the selfie is sent over that network to the event laptop, searched there, and deleted before the results are shown. Over the internet, the kiosk device makes the face signature itself and sends only that, for a one-off search.
Basis: the guest's consent, collected on the studio's behalf. A guest who says no can still see the event's public photos.
"Keep finding me" enrolments. If a guest asks to be told about new photos, we keep their face signature and an optional first name, linked to that one event, plus, if they choose, an e-mail address and the push-notification address of their "My photos" page, and a record of the consent (whether an adult or a parent agreed, when, and which version of the wording). We use them only to find and notify the guest about new photos from that event. They are deleted automatically after the period shown on the consent screen (by default 30 days after the event day), or immediately when the guest taps "Delete my data" on their page. Basis: the guest's consent (or a parent's or guardian's, for a child). Withdraw it at any time with "Delete my data".
Notifications. Push notifications go through the push service of the guest's browser maker (Google, Mozilla, Apple or Microsoft). We send them an empty message; the phone then fetches the text from us, so no names, photos or face data pass through those services. E-mail notices to guests (at most two) are sent in the studio's name.
Booth photos and the live wall. Photos taken at a studio's photo booth are stored with the project and can be shown on the event screen if the studio turns that on; the studio can hide any photo. A guest receives their booth photos through a QR-code link.
Event devices. When a studio pairs a phone, tablet or TV for an event, we keep the device's label and status (battery, charging, network quality and clock difference) so the studio can see that its devices are working.
Frame orders. If a studio runs a frame shop, a couple who orders frames gives their name, phone number and an optional note. The order goes to the studio. Payment goes directly from the couple to the studio's own UPI account; Artiz never receives or handles that money. The studio is the seller. Basis: processed on the studio's instructions.
Reminder e-mails. If a studio sets a selection or approval deadline with reminders, we e-mail its client, in the studio's name, at the address the studio gave. Every reminder has a link to stop reminders for that gallery. Basis: processed on the studio's instructions.
Studio directory. Studios that choose to be listed give a public profile (name, city, area, contact details, services, photos) and verification details: the owner's name and a GSTIN, Udyam or PAN number. We use them only to check that the business is real. When we approve a listing, we delete the owner's name and the number at once and keep only the type of number, its last four digits and the date. For a rejected listing, we delete the details 90 days after the decision. Why: to run an honest directory. Basis: legitimate use (given to us to be listed).
Directory and referral enquiries. When a couple contacts a studio through the directory or a referral page, we collect their name, phone number and/or e-mail address, event details and message, and deliver them to that studio's client list. We send them only to the studio you chose. Basis: legitimate use (given to us to contact that studio). After delivery, the studio is responsible for its copy.
Ratings of Artiz Studio. After downloading a photo, a guest may be asked to rate the experience of getting their photos. We store the stars, an optional comment, which studio's gallery it came from, and a short one-way code made from the IP address and browser details, used only to limit repeat ratings. Everyone who rates is offered the same link to leave a public review, whatever their rating. Basis: legitimate use (given voluntarily for that purpose).
Website forms. When you ask for early access, a demo or to contact us: your name, e-mail address and, if you give them, phone number, studio name, city and message. Basis: legitimate use (you gave them so we can reply).
How you found us. Our website remembers in your browser's local storage how you first arrived (a campaign tag in the link, or the referring website) and the first page you opened. If you create a studio account, this is sent with your sign-up so we know which channels bring us studios. It is never shared and never used to follow you across other websites.
Security and server records. Sign-in sessions (time, IP address and browser details), an audit log of important account and administrator actions (with the IP address), and our web server's access logs (time, IP address, address requested, response and browser details; share tokens and PINs are removed from the logged addresses). We also keep daily usage counters per studio (requests, storage and bandwidth). Why: to secure the Service, investigate misuse and incidents, keep the logs the law requires, and apply plan limits. Basis: legitimate use and legal obligation.
Messages. If you write to us, we keep the correspondence so we can help you.
What we don't do:
• No third-party analytics, advertising cookies or trackers. The desktop app has a setting for anonymous usage statistics; it is off by default, and today nothing is sent even when it is on. • We don't sell personal data, build advertising profiles or use anyone's photos or face data to train AI models. • We don't use a studio's client and guest data for our own purposes.
Who we share data with (sub-processors)
We share personal data only with the service providers below, only as needed to run the Service, under contracts or terms that require them to protect it.
• DigitalOcean (DigitalOcean, LLC): our server, database, server logs and daily database snapshots, in its Bangalore (BLR1) data centre, India. • Cloudflare R2 (Cloudflare, Inc.): storage of photos and files (previews, thumbnails, retouched images, deliveries, booth photos, logos, device photos in transit and cloud backups of originals). Cloudflare chooses the storage region; it is not guaranteed to be in India. • Zoho ZeptoMail (Zoho Corporation Private Limited): sending our service e-mails (sign-in and verification codes, receipts, notices, reminders). It receives the recipient's address and the message. India. • Razorpay (Razorpay Software Private Limited): subscription payments and UPI AutoPay mandates. India. • Google (Google LLC): "Sign in with Google", if you use it. Outside India. • Web push services: Google Firebase Cloud Messaging, Mozilla Push Service, Apple Push Notification service and Microsoft Windows Push Notification Services, which deliver guests' notifications. They receive only an empty message and the push address. Outside India. • MSG91 (Walkover Web Solutions Private Limited), only if SMS sign-in codes are switched on: your mobile number and the code. India. • Meta's WhatsApp Business Platform, only if WhatsApp sending is switched on (it is off today): the phone number and the message.
We keep this list up to date on this page. Studios get notice of new sub-processors as described in our Data Processing Addendum.
Inside the Service, data is shared as the studio decides: clients see what the studio shares with them, and the studio sees its clients' selections, comments, approvals, orders and enquiries. Model files for on-device analysis are downloaded from public hosts (such as Hugging Face and Google's storage); those hosts see only the device's IP address.
We may also disclose information when the law requires it: a court order, a lawful request from a government agency, or a direction under the Information Technology Act, 2000. We may also disclose it to protect the rights, safety or property of our users, the public or ourselves. If our business is transferred, for example when NEW.E AI Solutions becomes a private limited company, personal data moves to the new owner under this policy or one offering equal protection, and we will tell studios first.
Where data is stored
• Database, app server, logs and daily snapshots: DigitalOcean, Bangalore, India. • Photos and files: Cloudflare R2. Cloudflare picks the location, which may be outside India. • Some providers above (Google and the push services) process limited data outside India.
Transfers outside India are made as the DPDP Act allows, and will follow any restrictions the Government of India notifies.
How long we keep data
• Studio accounts and content: while the account is active. • After a subscription ends: the account becomes read-only and we keep its data for 60 days, so you can renew or export it. After that we may delete it, after e-mailing the owner. • When you delete your account: you have 7 days to change your mind, then we erase the cloud data. Database snapshots that still contain it are overwritten within 7 more days. • Projects in the cloud: each studio sets a cleanup policy (by default 90 days after delivery, or after 365 days without activity). Cleanup deletes previews, retouched images, originals, booth photos and cached files, and closes the project's links, which also deletes its cloud face signatures. Thumbnails, album snapshots and approval records stay until the studio deletes the project. • Deleted projects: they stay in Trash for 30 days, then everything is deleted. • Face signatures of people in a studio's photos (cloud copy): only while face search is on for an open link of the project, as described above. • A guest's selfie: not stored (see above). • "Keep finding me" enrolments (face signature, first name, e-mail address, push address): deleted automatically after the period shown to the guest (by default 30 days after the event day), or straight away with "Delete my data". • Frame orders: kept with the project, and deleted with it. • Directory verification details (owner's name, GSTIN, Udyam or PAN number): reduced to the type of number, its last four digits and the date as soon as a listing is approved; deleted 90 days after a listing is rejected. • Directory and referral enquiries: deleted 2 years after the last activity, unless the studio has made the enquirer a client with a project, or sooner if the studio deletes them. • Ratings of Artiz Studio: comments and the repeat-rating code for 2 years; star counts without personal data may be kept longer. • Website form submissions: 2 years. • Sign-in sessions (IP address and browser details): deleted 30 days after they expire. Each sign-in is also recorded in the audit log (below). • Audit log and server access logs: one year, as the law requires, then deleted, unless an incident or a legal claim needs them for longer. • Billing, payment and tax records: 8 years, as Indian tax law requires, even after an account is deleted.
How we protect data
• Encrypted connections (HTTPS, TLS 1.2 or higher) for the website, the web app and our APIs. • Passwords stored only as salted scrypt hashes; session tokens, reset codes and backup codes stored only as hashes; authenticator secrets encrypted. • Two-step verification for studios who turn it on, and required for platform administrators. • Unguessable share links, plus the optional PINs, expiry dates, watermarks and download controls each studio sets. • Access limited by role, rate limits on sign-in and public pages, and an audit log of sensitive actions. • A server firewall that admits only web traffic and key-only administrator access, with automatic security updates. • Daily database snapshots, kept on the server for 7 days.
No system is completely secure. Please use a strong, unique password, turn on two-step verification and keep your own backups of your original photos.
If there is a data breach
If a personal data breach happens, we will contain it, investigate it and:
• for data where we are the Data Fiduciary, tell each affected person without delay, in plain language, what happened, what it means for them and what they can do, and inform the Data Protection Board of India without delay, with a detailed report within 72 hours, as the DPDP Rules require; • for data we process for a studio, tell the studio within 24 hours of becoming aware of the breach, and help it inform its clients, guests and the Board; and • report cyber security incidents to CERT-In within 6 hours, as its directions require.
Cookies and local storage
We don't use advertising or third-party tracking cookies. The web app keeps your studio's projects and your sign-in token in your browser's local storage and IndexedDB; the desktop app keeps the same in its data folder on your computer. A guest's "My photos" page and a kiosk keep their own settings, and any enrolment still waiting to be sent, in the browser. Clearing browser data or uninstalling the app removes these local copies, so make sure your work is synced first. The only cookie we set is a short-lived security cookie during "Sign in with Google".
Your rights
Under the DPDP Act, subject to its conditions and timelines, you can:
• get a summary of the personal data we process about you and what we do with it, and the names of those we have shared it with; • correct, complete or update it; • have it erased when it is no longer needed, unless the law requires us to keep it; • withdraw consent as easily as you gave it (guests: "Delete my data" on your "My photos" page); • nominate someone to exercise your rights if you die or become unable to; and • have your complaint handled by us and, if you are not satisfied, complain to the Data Protection Board of India.
How to use them:
• Studios: update account details on the Account page, and download your data or delete your account in the app. For anything else, write to our Grievance Officer from the e-mail address on the account. • Clients and guests: ask the studio first. Guests can delete their "Find my photos" data themselves at any time. If you can't reach the studio, write to our Grievance Officer. • To nominate someone, write to our Grievance Officer with the nominee's name and contact details.
We may need to confirm your identity before acting on a request. We aim to respond within 15 days, and in any case within the time the law allows. We keep a record of each request and how we handled it.
Children
Only adults (18 or older) can open a studio account. Wedding and event photos often include children, so:
• The studio is responsible for getting verifiable consent from a parent or lawful guardian, where the law requires it, before processing children's photos through the Service. • Before a guest's face is searched or kept, we ask the guest to confirm that they are 18 or older, or that a parent or guardian agrees. For a child, the parent or guardian confirms that they consent on the child's behalf. • Kiosk screens say: "Under 18? Please ask a parent." • We don't use children's data for tracking, behavioural monitoring or targeted advertising, or in ways likely to harm them.
Changes to this policy
We will post any update here with a new effective date. For significant changes, we will tell studios by e-mail or in the app before the change takes effect.
Grievance Officer and contact
For any question, request or complaint about privacy, about content on the Service or about how we handle personal data, contact our Grievance Officer:
• Name: to be appointed — contact hello@artizz.in • Designation: Grievance Officer, NEW.E AI Solutions • Address: Madurai, Tamil Nadu, India • E-mail: hello@artizz.in
We acknowledge every complaint within 24 hours and aim to resolve it within 15 days, and in any case within the time the law allows. Our Grievance page (https://artizz.in/grievance) explains what to include in a complaint.
If you are not satisfied with how we handled a complaint about your personal data, you can complain to the Data Protection Board of India through its online platform (see https://www.meity.gov.in for the current address). The Board generally expects you to raise the complaint with us first.