Privacy policy

Who we are

Centra (centra.studio) is software for photography and event studios. It runs a studio’s enquiries, bookings, team, money and deliveries in one place, through three apps: one for the studio, one for its team members and one for its clients.

Centra is operated by [Registered company name — to be added on incorporation], [Registered office address — to be added]. In this policy “Centra”, “we” and “us” mean that company. Questions about this policy go to support@centra.studio or to our grievance officer (see Grievances and complaints).

Who decides what

Studios are our customers. A studio uses Centra to work with its own clients (couples, families and companies) and its own team. Under India’s Digital Personal Data Protection Act 2023 (the “DPDP Act”), that gives two different roles:

• Centra decides (we are the data fiduciary, or controller) for the accounts of studio owners and studio staff, for the billing records between Centra and a studio, and for visitors to this site.
• The studio decides (we are its data processor) for everything about the studio’s clients and team members: enquiries, events, people, files, messages, payments and deliveries. Centra processes this only on the studio’s instructions and only to run the service for that studio.

When a studio turns on WhatsApp messaging (planned, not available yet), Meta processes those messages through its WhatsApp Cloud API as a further processor, and ODIV Engage passes them between Centra and Meta.

If you are a studio’s client, or a person who filled in a studio’s enquiry form, please contact your studio first: it decides what is kept about you. If you write to us instead, we pass your request to the studio and help it respond.

What we collect, and why

We do not use advertising or tracking cookies. The apps use cookies only to keep you signed in.

Data from Google

Centra uses Google in two ways. Each is described here exactly: what we access, what we store, and who it goes to.

Google sign-in (name, email address, profile picture)

Studio owners, team members and studio clients can sign in with Google. We receive your name, email address and profile picture from your Google account and use them only to create your account, sign you in and show your name to the people you work with in Centra.

Google Calendar (the calendar.events permission)

• Anyone signed in to a studio’s app (usually the owner) can choose to connect their own Google Calendar. We ask for the calendar.events permission only when that person clicks Connect, never at sign-in.
• Centra then writes the studio’s shoot days and calls into that person’s primary Google Calendar, and updates them when they change in Centra.
• Each event Centra writes carries a private tag. Centra looks up only events carrying its own tag, so it can update them without making duplicates. It does not read, copy or store any other calendar events, and it keeps no list of the events it wrote.
• We store the refresh token Google issues, the Google account email it belongs to, and the time of the last sync. They are stored in our database (Supabase, Mumbai, India). The token can be read only by our servers, never from a browser, not even by the person who connected the calendar. The account email and the last sync time are shown to the studio’s owners on the Integrations screen. Centra also records, against each shoot or call, when it was last synced.
• Disconnecting Google Calendar in Centra (Integrations) revokes the token at Google and permanently deletes it from our database. You can also remove Centra’s access at any time at myaccount.google.com/permissions: the token then stops working at once and Centra can no longer write to your calendar, but the stored token stays in our database until you disconnect in Centra or ask us to delete it. Events Centra already wrote stay in your calendar until you delete them.

How Google data is used, and how it is not

• Google data is used only to provide the sign-in and calendar features described above, which you can see and control.
• It is shared only with the service providers that host Centra (Supabase and Vercel, below), and only to run those features. We would otherwise share it only with your consent, for security, to comply with the law, or as part of a merger or sale of Centra after asking for your consent first.
• We do not sell Google data, use it for advertising (including retargeting or personalised ads), pass it to advertising platforms or data brokers, or use it to judge creditworthiness or for lending.
• Our people do not read Google data unless you ask us to (for example in a support request), to investigate a security problem or a bug, or to comply with the law.
• Google data, whether raw, aggregated, anonymised or derived, is never used to create, train or improve generalised or foundational AI or machine-learning models. Centra does not read calendar events, so calendar data never reaches Centra’s AI features.
• Anyone who handles Google data for us is bound by these same rules. If we ever want to use Google data in a new way, we will ask for your consent first.

Centra’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Data from Meta: WhatsApp and lead forms

WhatsApp messaging and lead forms are planned and are not available yet. When they launch, they will be off until a studio turns them on, and this section describes how they will work.

Before then. A few places in Centra already offer WhatsApp as a channel, for example for the one-time code sent before signing an agreement. Until WhatsApp sending is switched on, such a message is not delivered, so choose email instead. The message text, any code or link in it, and the full phone number are never written to our logs: we keep only a record that a message was attempted, with its type, a partly hidden phone number and a reference number.

• WhatsApp. When a studio turns this on, its WhatsApp messages travel through ODIV Engage (a WhatsApp business solution provider) and Meta’s WhatsApp Cloud API. Centra will hold the message content, phone numbers, delivery and read statuses, and the record of when and how each person agreed to receive messages, only to run that studio’s conversations.
• Facebook and Instagram lead forms. When a studio connects its lead forms, Centra will receive the answers submitted on the form and the form, page and ad identifiers, only to place the enquiry in that studio’s list of enquiries. The studio’s own privacy policy, linked from its form, governs what the studio does with it.
• We do not sell, license or buy Meta Platform Data.
• Meta data stays inside the studio’s own account in Centra and is never passed to another studio. We do not use it to build or add to profiles of people, to track people, to make eligibility decisions about them, or to discriminate against them.
• Centra does not use WhatsApp or Meta data to create, develop, train or improve AI models.
• Meta processes WhatsApp Cloud API messages in its own data centres, which may be outside India. Meta keeps messages for up to 30 days to deliver them, deletes the identifiers tied to a message within 30 days of its last status update, and keeps no backups. Centra does not control Meta’s copy.
• The studio sending WhatsApp messages or running lead forms is responsible for its own privacy notice and for each person’s agreement to be contacted.
• To stop Centra receiving your Meta data, remove Centra in Facebook under Settings, then Business Integrations; to stop a studio’s WhatsApp messages, tell the studio or block its number. A studio can disconnect its WhatsApp number or lead forms at any time. The steps are on the data deletion page.

AI features

• AI features are off until a studio turns them on, and a studio can turn them off at any time.
• When a studio uses an AI feature, the request and the studio data needed to answer it (for example an enquiry’s details) are sent to an AI provider and the answer comes back to Centra.
• Requests go through the Vercel AI Gateway to the AI providers the studio enables. If a studio adds its own key for a provider, requests for that provider go directly to that provider under the studio’s own account instead.
• Centra does not use your data to train AI models, and does not use Google, WhatsApp or Meta data in AI features. Each AI provider’s own terms govern what it keeps from a request and whether it may use it; we have not yet signed separate no-training commitments with each provider.
• Most of what an AI writes in Centra is a draft that a person checks before using it. The exception is Iris, the studio’s enquiry and questionnaire assistant: when a studio turns on its AI follow-up questions, those questions are written by AI and shown straight to the person filling in the form. Apart from those, nothing an AI writes is sent to a studio’s clients unless a person chooses to send it.

Email

Centra sends sign-in links and codes, invitations, and messages a studio sends to its clients and team (for example an invoice or an agreement to sign). Email is delivered by Resend (Plus Five Five, Inc., USA) and sign-in emails by Supabase. Mail sent on a studio’s behalf names the studio as the sender. When the studio has set a contact email, replies go to it; otherwise the mail carries no reply address.

We do not turn on open or click tracking for mail sent from centra.studio addresses, so we do not record whether you opened an email or clicked a link in it.

Who helps us run Centra

These service providers process data for us, only as needed to run Centra and under written terms that bind them to it. Data is stored in India where we can choose the region; some providers process it in other countries, as the table shows. Section 16 of the DPDP Act allows transfers outside India unless the Government of India restricts the country.

Razorpay keys a studio adds are stored so that only our servers can read them, never a browser. Centra never sees card numbers.

What we never do

• We do not sell personal data, and we do not share it for advertising.
• We do not show ads in Centra or use studio data to target ads anywhere.
• We do not pass one studio’s data to another studio.
• We share data only with the providers above, when the law requires it, or when you or your studio direct us to.

How long we keep it

Most records in Centra change status rather than being erased, and the activity trail cannot be edited. Some things are removed for good when someone in the studio removes them: uploaded files, travel tickets, photos of people, client-portal cover images, and some entries such as items in a schedule, a team list or a proposal. Everything else is deleted when a deletion request is carried out (see Data deletion) or as the table says.

Your rights

Under the DPDP Act you can ask us:

• to tell you what personal data we hold about you and how we use it;
• to correct or complete it, or bring it up to date;
• to erase it, unless the law requires us to keep it;
• to name another person who can use these rights for you if you die or cannot act yourself.

Where we rely on your consent, you can withdraw it as easily as you gave it: write to support@centra.studio, or disconnect the feature in the app. Withdrawing consent does not affect what was done before, and some parts of the service may stop working without it.

To use any of these rights, write to support@centra.studio from the email address on your account. We reply as soon as we can, and within 90 days at most, the limit the DPDP Rules set. If the data belongs to a studio’s clients or team, we pass the request to the studio, which decides. This policy is in English; ask us if you would like it in another language listed in the Eighth Schedule to the Constitution of India.

Security

• Every connection to Centra is encrypted in transit.
• Each studio’s data is kept apart: one studio cannot see another’s.
• Payment gateway keys a studio adds can be read only by our servers, never by a browser.
• Google Calendar tokens can be read only by our servers, never by a browser, including the browser of the person who connected the calendar.
• Message text, one-time codes and sign-in links are never written to our logs. For each message we keep only its type, a partly hidden address, which provider sent it, the provider's message id and whether it was delivered (with the provider's error text if it failed).
• Security and sign-in records are kept for at least one year.
• Changes are recorded in an audit trail that cannot be edited.

If a breach affects your personal data, we will tell the people affected and the Data Protection Board of India without delay, and send the Board a detailed report within 72 hours of learning of it, as the DPDP Rules require. Where the data is a studio’s, we tell the studio without delay too. Where Meta data is involved, we will also tell Meta.

To report a security problem, write to support@centra.studio with “Security” in the subject. The same address is published in /.well-known/security.txt.

Children

Centra accounts are for adults running or working with a studio, not for anyone under 18. A studio must not add a child’s personal data without the verifiable consent of a parent or guardian, and must not aim its lead forms at children.

Grievances and complaints

Our grievance officer is [Grievance officer’s name — to be added], [Grievance officer’s designation — to be added], [Registered company name — to be added on incorporation], [Registered office address — to be added]. Email: support@centra.studio.

Please raise a complaint with us (or, for a studio’s data, with the studio) first: the DPDP Act asks you to use this route before going to the Board. If you are not satisfied with the answer, you can then complain to the Data Protection Board of India, which works as a digital office and takes complaints online. More ways to reach us are on the contact page.

Changes to this policy

When this policy changes, the date at the top changes with it, and we tell studio owners about changes that matter to them. We will ask for consent before using data in a new way that needs it.