# Privacy policy — changes needed before the Meta Pixel goes live

Your live policy at `/privacy` currently contains **two statements that become false**
the moment the Pixel starts firing:

> "We do not sell your personal information to anyone. **We do not use your data for
> advertising or share it with marketers.**"

> "**We don't use cookies for third-party advertising.**"

Running the Pixel while the policy says this is worse than having no policy at all —
it's a documented contradiction, and it's the first thing a regulator or a complaining
visitor would point at.

I can't edit `privacy.php` directly because that file isn't in the folder I can see.
Below are the exact replacement sections. Find each heading in your `privacy.php`
and swap the content underneath it.

Three other things I noticed while reading it, flagged at the bottom.

---

## REPLACE — Section 1, last bullet ("Automatically")

```html
<li><strong>Automatically.</strong> Basic technical information about your visit —
which pages you view, roughly where you are (city and country, derived from your
IP address), which site referred you, and your browser and device type. This is
collected through Google Analytics, our own first-party visitor counter, and
(where you have consented, or where consent is not legally required) the Meta
Pixel. We also record your IP address itself for security and fraud prevention.</li>
```

---

## REPLACE — Section 2, the closing paragraph

Replace this:

> "We do not sell your personal information to anyone. We do not use your data for
> advertising or share it with marketers."

With this:

```html
<p><strong>We do not sell your personal information to anyone, ever.</strong></p>

<p>We do use limited data for advertising measurement. When you visit our website
we may share a securely hashed version of your email address or phone number, along
with the fact that a booking took place and its value, with Meta (Facebook and
Instagram). This lets us understand which of our advertisements actually lead to
bookings, so we do not waste money showing ads to people who do not want them.
The information is hashed before it leaves our servers, meaning Meta receives a
scrambled value rather than your actual email or phone number.</p>

<p>We never share the details of your trip, your itinerary, your travel dates, or
anything you tell us about your family or your reasons for visiting Varanasi with
any advertising platform.</p>
```

---

## REPLACE — Section 3, the sharing table

Add these two rows to the existing table:

```html
<tr>
  <td>Razorpay (payment processor)</td>
  <td>To take payment securely when you book online. They receive your name,
      email, phone number and the amount. We never see or store your card details.</td>
</tr>
<tr>
  <td>Meta (Facebook / Instagram)</td>
  <td>Advertising measurement only, and only where you have consented or where
      consent is not legally required. Receives hashed identifiers and the value
      of a completed booking — never your itinerary or trip details.</td>
</tr>
```

---

## REPLACE — Section 6, "Cookies" (whole section)

```html
<h2>6. Cookies and tracking</h2>

<p>We use three kinds of cookie:</p>

<ul>
  <li><strong>Essential.</strong> To keep you signed in and to remember what is in
      your cart. The site cannot work without these.</li>
  <li><strong>Analytics.</strong> Google Analytics, plus our own first-party counter,
      to understand how many people visit and which pages are useful. We also keep a
      short-term record of visits, including IP address, which is automatically
      deleted after 30 days.</li>
  <li><strong>Advertising.</strong> The Meta Pixel, which lets us measure whether our
      Facebook and Instagram advertisements lead to real bookings.</li>
</ul>

<p><strong>If you are visiting from the UK, the EU, or the EEA</strong>, no advertising
cookie is set until you accept it. You will see a banner on your first visit, and
declining costs you nothing — the site works identically either way. You can change
your mind at any time by clearing this site's data in your browser.</p>

<p>Visitors elsewhere can opt out of our own analytics at any time by emailing us,
and can control Meta's advertising tracking through their Facebook or Instagram
account settings.</p>
```

---

## ADD — a new section, after Section 7 ("Your rights")

India's Digital Personal Data Protection Act requires a named contact for
data grievances. You currently have no such section.

```html
<h2>7a. If you are in India</h2>

<p>Under India's Digital Personal Data Protection Act, 2023, you have the right to
access, correct, and erase the personal data we hold about you, to nominate someone
to exercise those rights on your behalf, and to raise a grievance about how we have
handled your data.</p>

<p>Our Grievance Officer is <strong>[YOUR NAME]</strong>, contactable at
<a href="mailto:namaste@kashiandkin.com">namaste@kashiandkin.com</a>. We aim to
respond to any grievance within 30 days.</p>

<p>If you are not satisfied with our response, you may escalate the matter to the
Data Protection Board of India.</p>
```

**You must put a real name in that placeholder.** A grievance officer with no name
does not satisfy the requirement.

---

## Three other things worth fixing while you are in there

1. **Section 11 has a placeholder phone number** — `+91 00000 00000`. Your real
   number is +91 90443 99595, which is already correct in the footer. This one has
   been live since 12 July.

2. **Section 1 says "once installed, Google Analytics"** — it *is* installed, and
   has been for a while. Drop the "once installed".

3. **Update the "Last updated" date** at the top to the day you publish these
   changes. An unchanged date next to changed terms is the detail people notice.

---

## One thing I am not qualified to give you

I am not a lawyer, and this is not legal advice. The wording above is written to
describe accurately what your website actually does, which is the part I can verify
from the code. Whether it fully satisfies GDPR, UK GDPR, or the DPDP Act for your
specific business is a question for someone qualified — worth an hour of a lawyer's
time before you spend money driving traffic to the site.