This notice stands on its own. It describes personal data the website code collects, and the purpose that code uses it for. It is not a certificate of compliance, and it is not legal advice.
The Digital Personal Data Protection Rules, 2025 were notified on 13 November 2025. Rules about notices, security, erasure, children, and grievances are scheduled to start on 13 May 2027. Consent Manager registration is scheduled to start on 13 November 2026. Those dates had not been changed by the sources checked on 25 October 2026, including the Digital Personal Data Protection (Removal of Difficulties) Order, 2026.
Questions, withdrawal, access, correction, erasure, nomination, and grievances: privacy rights page. You can also email hi@brandmen.io. That address is the published business contact. [Data Protection Officer: not appointed in this repository. Appoint one only if the business is notified as a Significant Data Fiduciary or otherwise decides it needs one.]
A complaint to the Data Protection Board is a separate step. The Board was established by a MeitY notification dated 13 November 2025. [Board complaint link: not confirmed in the sources checked on 25 October 2026. Use the means the Board publishes.]
1. Enquiries
Forms on the contact page and landing pages ask for this data:
- Name, email, Indian mobile number, company, service, budget range, and message
- The page address, campaign parameters already in the link, time to submit, and device type
- IP address, browser identifier, and an approximate city taken from the hosting request headers
- The country value is set to IN by the form code
- A Cloudflare Turnstile result, used to reject automated submissions
Purpose: reply to the enquiry and prepare a project response. The checkbox for this purpose starts unchecked.
Optional and separate: emails about BrandMen Studio services. That box also starts unchecked. Enquiry emails are not added to that list unless the box is checked. Withdraw it on the privacy rights page.
When configured, the same enquiry is emailed to the studio inbox, notified in Telegram, and sent to Twenty CRM. [Whether each of those providers is a Data Processor, and the contract terms, are legal decisions. They are not in this repository.]
Stored in the Supabase table contact_submissions. [Database region: not recorded in this repository.]
[Lawful ground: not decided here. Review consent and the Act's legitimate use for data a person voluntarily gives for a specified purpose.]
[Retention period: not enforced by the website code. A business and legal decision is required.]
2. Newsletter
The newsletter form collects a name and email address, plus a Turnstile result.
Purpose: send the newsletter until the person unsubscribes or withdraws. A confirmation link is emailed and expires after 48 hours. Only a verified subscriber is eligible for the newsletter recipient group.
Stored in newsletter_subscribers. [Retention period: not enforced.]
3. Bookings and payments
Booking forms collect the name, email, phone if entered, answers to the questions configured for that event, the chosen time, and the timezone. Paid events open Razorpay checkout. The website stores the Razorpay order id and payment status on the booking.
Purpose: schedule the appointment, send booking messages, and take payment when the event has a price.
A confirmed booking can create a Google Calendar event when that integration is configured. [Calendar account and region: not recorded here.]
Erasure of a booking flags the row for a person to review. The code does not delete payment records, because tax or payment-provider duties are [a legal decision, not confirmed in code].
4. Chat
The chat assistant sends the conversation to DeepSeek when DEEPSEEK_API_KEY is set. If you share a name, Indian mobile number, or email in the chat, the transcript can be stored in chat_transcripts, emailed to the studio, and sent to Telegram.
This privacy notice is where that chat use is described. The chat does not show a separate notice or checkbox, because the details are taken from the messages themselves. [Whether that is an acceptable consent or legitimate-use design is a legal decision.]
5. Job applications
Applications collect name, email, Indian mobile number, city, experience, cover letter, LinkedIn URL, portfolio URL, and a resume file. The file is stored in object storage under job-applications. A copy of the application email goes to brandmenstudio@gmail.com when email delivery is configured.
Purpose: consider the application for the selected role.
An erasure request flags the application. The resume file is not deleted automatically. [How long hiring records must be kept is a legal decision.] The form does not ask for age or date of birth.
6. Accounts, invoices, and staff tools
Client and admin sign-in uses Supabase Auth. Session cookies are set for the portal. Client profiles, messages, support tickets, invoices, and files are stored for the account. Staff, attendance, payroll-related, and finance screens exist in the admin area.
Those areas are not erased automatically from the public privacy form. A matching client account is flagged for a person to review. [Employment, tax, and contract retention periods are legal decisions.]
7. Analytics and advertising
Analytics and advertising are on by default. Each choice is stored on its own, and you can turn either one off in Cookie Settings, which is also linked from the cookie icon on every page. Switching a choice off reloads the page so a script that already loaded during that visit stops. This notice does not say the Act requires a particular banner, and it does not say the site is compliant.
Analytics:
- Google Analytics, measurement id G-4KZQ1VWXC7. The site loads gtag.js and sends page measurements, plus events this code already defines for traffic source and, when those signals are in the link, an AI Overview click. Purpose: measure site visits and interactions. Vendor: Google.
- Microsoft Clarity, project id vsg7yhxlhb. The site loads the standard Clarity tag. Purpose: measure site visits and interactions. That product can record a session. Vendor: Microsoft.
The Clarity snippet in this repository does not turn input masking on or off, and it does not unmask any field. [Those settings are in the Clarity project, not in this code. Check project vsg7yhxlhb before treating any field as masked. This page does not confirm that masking is on.]
Advertising:
- Google Ads, conversion id AW-18002859423. The site loads the Google tag for this Ads account, and after a lead form is submitted successfully it sends one "Submit lead form" conversion event. Purpose: measure ad performance. Vendor: Google.
- Meta Pixel, id 924254049165800. The site loads Meta's script and sends a page view. Purpose: measure ad performance. Vendor: Meta.
Google Tag Manager container GTM-5FK8R28T is named in the source. No export of that container is in this repository, so the site does not load it. Tags that exist only inside the container do not run. [Manual action: export container GTM-5FK8R28T from the Google Tag Manager account, list every tag that collects or sends visitor data, and only then decide whether this site should load it. This paragraph is not that list.]
The choice is stored in this browser and, when the database migration is applied, as a privacy_consent_events row tied to a random key rather than your name. [Retention periods at Google, Microsoft, and Meta are not stated in this repository.] [Processor contracts for those vendors are not in this repository.]
[Lawful ground used in the code for these tools: they run unless you switch them off, so the code does not wait for a consent choice. Confirm the ground and this notice wording with counsel. The Act does not, by itself, require a cookie banner.]
8. Other tools that can receive technical data
- Cloudflare Turnstile on forms that show the security check
- Google Maps, only after you choose Load Google Map on the contact page. The address is also written in text
- Google Translate, only after you choose a language other than English from the language menu. The visible page text is sent to Google so the page can be shown in that language. English does not load it
- Sanity, for published site content. Visitor accounts are not created there by the pages reviewed
- Resend, Gmail SMTP, or another configured mail transport for messages the site sends
- The host that serves the site, including Vercel request headers such as city when those headers are present
- Cloudflare R2 when object storage is configured for files such as resumes
[Where each provider stores data, and the processor contract, are not in this repository.]
An earlier version of this page said the Supabase database was in Singapore. This repository does not record the project region. [Confirm the region in the Supabase project settings.]
9. Withdrawal, rights, and grievances
Use the privacy rights page for access, correction, erasure, withdrawal, nomination, a privacy question, or a grievance. The same page is the withdrawal route for newsletter and service-email consent. Cookie withdrawal is in Cookie Settings. Neither choice is pre-ticked.
Email confirmation is required before the site changes or discloses records, so a request cannot be completed by someone who only knows the address. The link expires after 48 hours.
Erasure anonymises matching enquiries and chat transcripts that contain the email. It unsubscribes the newsletter. It asks Twenty CRM to delete a linked opportunity when that integration is configured. It does not delete emails already sent, Telegram messages, Razorpay records, Google Calendar events, advertising audiences, resumes, invoices, or staff records. Those are listed for a person to review.
The grievance page names the published grievance contact for customer complaints. [Grievance response period under the Rules, once they commence: not more than 90 days. The 15-business-day aim on the grievance page is the studio's existing statement, not a finding that the legal period has started.]
10. Children and people with a lawful guardian
The public forms reviewed do not ask for age or date of birth, so the site cannot tell from those forms whether the person is a child. There is no verifiable parent or guardian consent flow. An earlier line on this page said the services are not directed at people under 18. That sentence is not enforced by the code.
[Product decision required before building an age check or parental-consent flow. The October 2026 Removal of Difficulties Order clarifies that section 9 covers a child or a person with disability who has a lawful guardian. It does not create an age-check design for this website.]
11. Security and breaches
The site uses access control on admin and client routes, httpOnly session cookies, and server-side service credentials. [Whether those measures meet the Rule 6 list — encryption or equivalent, access control, access logs, backups, a one-year log retention minimum, and processor contract clauses — has not been audited as a completed control set.]
[Breach response: there is no coded workflow that notifies affected people and the Data Protection Board. That process needs an owner, a contact, and a runbook. Do not treat this page as that runbook.]
12. What this notice does not decide
- [Whether BrandMen Studio is a Significant Data Fiduciary.]
- [A Data Protection Officer, independent data auditor, or data protection impact assessment.]
- [Cross-border transfer conditions. The Act allows transfer outside India unless the Central Government restricts it. No such order was found in the sources checked.]
- [Retention periods, including the one-year minimum for certain logs once Rule 8 applies, and any longer period required by tax or employment law.]
- [Signed processor contracts for Supabase, Cloudflare, Google, Meta, Microsoft, DeepSeek, Resend, Razorpay, Telegram, Twenty, and the site host.]