What this site collects, who it goes to, and how to get it deleted.

There are two forms on this site: the quote form, which sits on most pages and on the contact page, and an older enquiry form on the quote page and one advertising landing page. When you submit either, what you typed is written to a file on the server and emailed to me, and a copy is saved in the database I use to read enquiries (Supabase, described in section 4). No advertising network receives it, in any form, hashed or otherwise. I do not build a profile of you, and nothing you send is sold or shared with anyone else.

• Your nameYou type it
• Your WhatsApp numberYou type it. This is how I reply
• An email addressOptional
• What you need, and a short noteOptional
• Which page you sent it fromRecorded automatically

The older enquiry form asks for your name, your brand or business, your site, ad account or listing and what is not working, anything else you want to add (optional), and a WhatsApp number or email address. If what you type in the site, ad account or listing box starts with http:// or https://, everything after the page address (the tracking query and any fragment) is cut off in your browser before it is sent.

Each form also carries one field you never see: an empty box that only an automated script would fill in. If it arrives with anything in it, the submission is discarded and nothing is stored. That box is the only reason this site does not need a CAPTCHA.

If you message the WhatsApp number or the email address instead of using a form, nothing is written to that file. WhatsApp is Meta's service and their own terms apply to the conversation; email sits with my mail provider. Messages to the WhatsApp number may be answered by the same automated assistant described in section 4. When they are, your message and the reply are stored in the same database, filed under the WhatsApp number you wrote from; up to ten earlier messages of that conversation, plus the new one, are sent to Google's Gemini to write the reply, and the reply comes back through WhatsApp.

How you arrived is stored alongside what you sent, so I can tell which links and which pages actually bring anyone here. None of it is bought from anywhere and none of it identifies you beyond what you typed yourself.

• utm_source, utm_medium, utm_campaign, utm_contentWhich link or ad brought you here. utm_term is read by your browser but is not written to the file
• gclidGoogle Ads click identifier, if you arrived from a Google ad
• fbclidMeta click identifier, if you arrived from a Facebook or Instagram ad
• Referring pageThe site you came from, if any
• The first page you landed onHeld for the browser session only
• Browser user-agent stringWhich browser and device, recorded by the server

Those first-touch details live in your browser's own session storage under the key zaiv_first_touch and are gone when you close the tab. A copy is attached to your enquiry only if you actually send one.

This site loads Google Analytics 4 and, since 14 September 2026, Google Ads conversion tracking — nothing else of that kind. Neither loads the moment you arrive: the script is held back until the page is idle and you have scrolled, tapped or typed, or about four seconds have passed. If you read a page and leave without interacting, it may never load at all. Both are destinations of the same Google tag, so the Ads half adds no second download. The Meta pixel was removed on 11 September 2026 and does not run here.

• Google Analytics 4Page views, which buttons are clicked, and how far the two long pages are read. Used to see which pages do anything at all
• Google Ads conversion trackingFires once, on a confirmed enquiry, so a paid click can be matched to the enquiry it produced. It sends the fact that an enquiry happened, never its content
• Hostinger, MumbaiHosts the site and stores the enquiry file. Standard server logs, including IP addresses, sit with them
• Demo pages onlyThe sample pages under /demo/ send us one message when you leave: which page, how many seconds you stayed, and how far down you scrolled. No cookie, no IP, nothing that identifies you. They also load Google Analytics, as every page here does

Two things worth naming, because they are easy to miss. Google Analytics itself contacts two Google advertising domains — stats.g.doubleclick.net and google.co.in/ads/ga-audiences — which is a Google Analytics setting called Google Signals rather than a separate tag here. And the conversion, when one fires, is sent to googleadservices.com and googleads.g.doubleclick.net. Those are the advertising requests this site makes; there are no others.

Apart from the chat assistant in section 4, there are no other embeds on this site: no font served from a third party at page load, no video player, and no advertising or social pixel of any kind.

The chat button on every page opens an automated assistant. It is software, not a person: its answers are written by Google's Gemini model from a fixed brief of what this site says. The chat loads a few seconds after the page does, and nothing is sent anywhere until you send a message, by typing one or by tapping one of the suggested questions.

• Each message you sendSent to a server function of mine on Supabase, a hosted database service, which passes it to Google's Gemini API together with up to the last 20 messages of the same conversation, so the reply makes sense. Your message and the reply are stored in my Supabase database
• Which page you were onThe path of the page, for example /services/, stored with the conversation
• A random conversation IDMade in your browser when the chat loads and stored with the conversation so its messages stay together. Your browser keeps it, with the messages so far, in the tab's session storage under zaiv-chat-v1, and drops both when the tab closes
• Your IP addressRead by the server function to stop abuse: no more than 30 requests in 10 minutes from one address. It is kept as its own counter in a separate table, not linked to the conversation. A second counter, kept against the conversation ID, allows 200 requests a day per conversation
• A WhatsApp number or emailOnly if you type one into the box the chat offers after its second reply. It is stored with the conversation and saved as an enquiry, and it is not sent to Gemini

Google's terms for the free tier of the Gemini API let Google use what is sent to improve its products, and say people at Google may read it. So please do not type into the chat anything you would not want read: no passwords, no bank details, no customer data. To leave a contact detail, use the box the chat offers, which does not go to Gemini, or one of the forms.

Where it is kept: the database is on Supabase, in its Seoul, South Korea region. Only my own server functions and my passphrase-protected dashboard can read these tables; they are closed to the public.

How long it is kept: each message and its reply are deleted automatically once they are 90 days old (the deletion runs once a day). The record of a conversation (the page path, the conversation ID and any contact detail and note you left in the chat) is deleted once its last message is 90 days old, and the abuse counter for an address is deleted 90 days after its window started. The same applies to conversations on WhatsApp. A contact detail you leave in the chat is also saved as an enquiry, and that copy follows the enquiry rules in section 9. What Google keeps on its side is governed by Google's Gemini API terms.

To have a conversation deleted, write to support@zaivdigital.com and say roughly when you chatted and from which page, because the website chat does not know who you are unless you left a contact detail. For WhatsApp, the number you wrote from is enough. It is done within thirty days.

Until 11 September 2026 the contact detail you typed was hashed in your browser and the hash was handed to Meta's pixel, so that Meta could match your enquiry to an advert. The Meta pixel is gone and that no longer happens at all — not the hash, and not the value. Google Ads conversion tracking, added on 14 September 2026, is not given your contact detail either, hashed or otherwise: it is told that an enquiry was completed, and nothing about who completed it.

Google Analytics is still here, and it is worth being exact about what it does and does not get: it records that a button was clicked, not what you typed into the form. Your name, your brand, the site, ad account or listing you name and your contact detail are never passed to it.

So your contact detail reaches exactly three places: the enquiry file on the server, the copy in my Supabase database, and my inbox. That is the whole list, and it is how I reply to you. If you type it into a chat message rather than the box the chat offers, it also goes to Gemini, as section 4 explains.

If you would rather not be counted in the analytics at all, message the WhatsApp number or the email address directly instead of using the form.

This site sets no cookie of its own. Google Analytics sets its own when, and only when, it loads.

• _ga and _ga_<property>Google Analytics. Tells one browser from another so a visit is not counted five times
• _gcl_auGoogle Ads. Written only if you arrive from a Google ad, so that a click and a later enquiry can be matched
• zaiv_first_touchNot a cookie. Session storage, set by this site, holding the attribution details in section 2. Deleted when the tab closes
• zaiv-chat-v1Not a cookie. Session storage, set by the chat assistant, holding the conversation ID and the messages so far. Deleted when the tab closes

Blocking all of these costs you nothing: the site works normally without them and the form still reaches me. An ad blocker, a browser that blocks trackers, or Google's own opt-out add-on will all do it.

Ads, sites and listings are worked on inside your own accounts, not ours. You add us as a user with the permissions you choose, and you remove us with one click whenever you want. We never need your password, we will never ask for it, and we will never ask you to email us one.

What I look at while that access is open is your listing and your Business Reports — sessions, unit session percentage, units ordered and ordered product sales for the product we agreed on. I take screenshots of those four numbers so both of us are reading the same figures at the start and at the end.

Your Business Reports contain your commercial data, not personal data about your customers, and I do not download, export or ask for customer names, addresses or order details. If a report I open happens to contain any, it is not copied out of Seller Central.

I will not name your brand publicly, publish your numbers, or use the work in a case study without your written permission. If we stop working together, you remove my access and I delete the screenshots on request.

This free tool, at /tools/aplus-builder.html, works differently from the rest of the site and is documented separately here because it is the one place on zaivdigital.com that reads an outside webpage on your behalf.

• An ASIN you type into Step 1Sent to a small server function of ours, which tries to fetch the public amazon.in listing page for that ASIN and read its title, bullets, description and image links. That is the only thing sent — not your browser, your IP is only visible to that function the way it is to any server you contact, and nothing is written to a database
• Everything you type or upload from Step 2 onward — brand, title, bullets, description, and up to 8 imagesStays in that browser tab. The module images are drawn on your own device with the HTML canvas element and never uploaded anywhere. Skipping Step 1 and typing everything in yourself means nothing at all is sent to us
• The ZIP file the tool buildsAssembled and downloaded entirely in your browser. It is never seen by us unless you attach it to an email yourself
• The optional email at the end of Step 4Sent to the same `lead` function the contact form uses (see section 1), tagged with the source “aplus-builder” so I know which tool it came from. Skipping it sends nothing

The listing-fetch function is a best-effort read of a public page and can fail or be blocked by Amazon at any time; when it is, the tool says so and switches to manual entry, which works identically. If a later version of this tool is asked to check the ASIN lookup against your Amazon account for permissions, that will be written here before it ships.

The enquiry file sits outside the public part of the server, so it cannot be opened from a browser. Records are removed 24 months after the enquiry, or sooner if you ask.

Chat conversations (section 4) are deleted automatically 90 days after each message. The copy of an enquiry in the Supabase database has no automatic deletion period yet; it is deleted on request, and a fixed period will be written here when it is set.

Analytics data follows Google's own retention settings, which I do not control beyond choosing them. Emails, and WhatsApp threads in the WhatsApp app itself, are kept for as long as the conversation is useful, and deleted on request; the assistant's database copy of a WhatsApp conversation follows the 90-day rule in section 4.

This data is never sold, and it is never shared with anyone beyond the parties named in sections 3 and 4 and the mail provider that carries the notification email to me.

A copy of what is held about you, a correction to it, or its deletion. You do not need a reason and there is no form to fill in.

Email from the address you used, or message the WhatsApp number from the number you gave, and say which of the three you want. Expect a reply within seven days, and the thing itself done within thirty. For a chat conversation, say roughly when you chatted and from which page.

You can also withdraw consent for the analytics at any time by blocking it in your browser, and adjust ad personalisation inside your own Google account settings.

This site sells a business service and is not aimed at children. Nothing is knowingly collected from anyone under 18.

If this page changes, the date at the top changes with it. Anything material will be written here rather than changed quietly.

If you are not satisfied with how a request was handled, write to me first so it can be put right. Under India's Digital Personal Data Protection Act you may also complain to the Data Protection Board of India. Grievances are handled by the proprietor of the business named at the foot of this page, at the same email address.

What the Zaiv Lens extension sends. When you view an amazon.in search results page with the Zaiv Lens extension installed, the extension reads the public listings on that page and sends them to our servers automatically; there is nothing to press and no prompt. Per listing we receive the ASIN, price, star rating, number of ratings, the "bought in past month" badge text as Amazon prints it, and whether it is sponsored, plus the search text and page number. We also receive a random install ID made when the extension was installed; we store only a one-way hash of it, and we do not store it together with your name, email, account or network address (a network address is used only as a short-lived, one-way-hashed counter to limit abuse). We do not receive page HTML, page links, buyer names or anything from your Amazon account. A search text that looks like an email address, a link or a phone number is not sent. We use this data to improve Zaiv Lens; we do not sell it, and we do not use it for advertising or profiling. Anything we show to other users is a total or a typical value across many installs, never one install's listings. We keep the data for 24 months, then delete it. If you want the rows stored for your install deleted, write to support@zaivdigital.com or message +91 92208 05129 with your install ID and we will delete them. Your install ID is shown at the bottom of the Zaiv Lens panel (Install ID, with a Copy button). Uninstalling the extension stops the sending, and so does the switch "Share scan data with Zaiv Digital" at the bottom of the Zaiv Lens panel, next to the Install ID: it is on when the extension is installed, and while it is off no listing details from a search page are sent (the Search Expander's own lookups have their own switch). Counts of how many installs searched a given text on a given day carry no link to any install and are kept as totals.

The full policy for the extension, including its Zaiv Lens Cloud account and the search-volume lookups, is at /zaiv-lens/privacy/.