ZAIV LENSby Zaiv Digital
amazon.in

Privacy Policy

Zaiv Lens · Effective 2 November 2026 · Version 3 (version 2: 4 October 2026; version 1: 19 September 2026)

The short version

Zaiv Lens reads amazon.in pages in your own browser, on pages you open yourself, and only after you click its LENS tab. It never signs in to Amazon and never asks for an Amazon password. What you choose to send to Zaiv Lens Cloud is stored in a hosted database under your workspace, readable only by your workspace's members. We never mix one customer's uploaded Amazon data into another customer's numbers. There are no advertising trackers and no analytics scripts on this app. Delete your account and everything under it is deleted.

  1. Who we are
  2. Where the reading happens
  3. What we store
  4. What we do not collect
  5. Where it is stored
  6. Who can read it
  7. Your Amazon data is never pooled
  8. How long we keep it, and deletion
  9. Cookies and browser storage
  10. Third parties
  11. The Chrome extension
  12. Your rights
  13. Children
  14. Changes to this policy
  15. Contact

1. Who we are

Zaiv Digital is a trade name of Anayza Enterprises, Kalkaji, New Delhi, India. We make Zaiv Lens: the web app at app.zaivdigital.com and the Chrome extension "ZAIV LENS". Together they are "Zaiv Lens" in this policy.

Zaiv Lens is built for sellers on amazon.in only. We are not affiliated with, endorsed by, or connected to Amazon in any way.

2. Where the reading happens

Every measurement Zaiv Lens makes of amazon.in is made in your own Chrome tab, by the extension, from a page you opened yourself. The extension requests no amazon.in page, and none of our servers ever fetch an amazon.in page, on your behalf or otherwise. Once you open its panel, the only thing it loads from Amazon is each product's thumbnail, from Amazon's image server, using the image link the search page already shows.

Concretely, the extension:

3. What we store

Everything we hold about you belongs to one workspace. A workspace is created for you when you sign up. This is what sits inside it.

DataWhat it isWhere it comes from
AccountYour email address, your name and the WhatsApp number you type on the Create account form, your plan code, and when you signed up. You sign in with a link or a six-digit code emailed to you, with a password if you set one, or with "Continue with Google" (which gives us your name and email, no number). If you set a password, the sign-in service stores a one-way hash of it, never the password itself, and the extension never sees it. We may message the WhatsApp number about your account and Zaiv Lens; reply STOP and we will not again.Sign-up.
Extension profileWhile you are signed in to the extension and it reads an amazon.in search results page: the delivery pincode amazon.in prints in its own header ("Deliver to … 110019", the area only, never a street), the extension's version number and the time of that read. Kept as the latest value on your account.The extension, each time it reads a results page signed in. Nothing is sent when you are signed out.
SearchesThe search keywords you look up on amazon.in results pages while signed in, with the day and how many times. On the free plan this is also the counter for the three search keywords a day shown with full numbers; from the fourth keyword the free view hides the same numbers as before. The counter resets at midnight IST. Signed out, no keyword is kept against any account.The extension's keyword lookup, signed in.
CapturesThe raw capture file exactly as the extension produced it (kept verbatim as evidence), plus a metadata row: capture kind, time collected, size, and counts.You press "Send to Zaiv Lens Cloud" in the extension. Nothing is captured any other way.
Extracted tablesThe same capture split into per-keyword market rows, per-ASIN product detail rows, and dated rank observations, so that tools can query them without re-reading the raw file.Computed from your capture when it arrives.
Your ASINs and keywordsThe list of distinct ASINs and search terms your captures have ever touched, with title, brand, image URL, first seen and last seen.Computed from your captures.
Derived tablesKeyword Tracker rows and Alert events. These are recomputed from your captures and can be deleted and rebuilt at any time.Computed on our edge functions, as you.
Things you createTracked keywords, the ASINs on your watch list, My List entries with tags and notes, saved filter sets, listing drafts.You, in the app.
AnchorsRows from a Brand Analytics (Top Search Terms) or Search Query Performance export you upload: the search term, its rank or volume, the source, and the month.You upload the CSV on the anchors page.
Usage metersA count per workspace, per day, per unit (captures, capture bytes, and a ten-minute burst counter). Used only to enforce plan limits and stop abuse.Incremented by our edge functions.

The web host also keeps ordinary web-server access logs (IP address, time, page requested, browser user agent) for the static files of app.zaivdigital.com, as any host does. We do not add tracking of our own on top of that.

4. What we do not collect

5. Where it is stored

Zaiv Lens Cloud's database, authentication, file storage and edge functions run on Supabase. Our Supabase project is hosted in the ap-northeast-2 region (Seoul, South Korea), so your data is stored outside India. The static app pages are served from Hostinger hosting. Raw capture files sit in a private storage bucket that is not publicly readable; the file path is not a secret and is not what protects it — the access policy is.

6. Who can read it

Only the members of your workspace. This is enforced in the database itself, not just in the app: every table that holds your data carries a workspace id, and Postgres row-level security refuses any read or write by anyone who is not a member of that workspace. The same rule applies to the storage bucket that holds raw capture files.

Our edge functions run as you, with your own session, so they are bound by the same row-level rule. There is one scheduled housekeeping job that runs with elevated access across all workspaces: it re-processes incomplete captures, trims history past your plan's retention window, rolls up usage counters and removes orphaned files. It is not reachable from any request, and it does not read the contents of your captures for any other purpose.

The owner of Zaiv Digital has administrator access to the database, as anyone operating a database must, and uses it to run the service, take backups and fix an account when its owner asks us to. We do not read your captures or anchors to build anyone else's answers, to build a dataset, or to sell.

7. Your Amazon data is never pooled

Anchors are the one place a seller's real Amazon numbers enter Zaiv Lens: a Brand Analytics rank or a Search Query Performance volume that Amazon published to you and to nobody else. Anchors are read per workspace and never pooled. Your upload is used for your workspace only. It is never used to improve another workspace's numbers, and another seller's upload is never used to improve yours. There is no cross-workspace read path in the schema at all; this is a property of the database, not a promise in a document.

8. How long we keep it, and deletion

Backups taken by the database provider expire on the provider's own schedule and are not read by us except to restore the service.

9. Cookies and browser storage

Zaiv Lens sets no cookies of its own. What it keeps in your browser is for your session and your own convenience:

10. Third parties

ServiceWhat it does for Zaiv LensWhat it sees
SupabaseDatabase, sign-in (emailed link/code, password, or Google), file storage, edge functions. Region ap-northeast-2 (Seoul).Everything in section 3. Sign-in emails are sent through Supabase's email service until we move them to our own mail server.
HostingerHosts the static files of app.zaivdigital.com.Ordinary access logs: IP address, time, page requested, user agent.
Google FontsServes the Nunito Sans typeface used on these pages.Your IP address and browser details when the font file is requested, as with any file fetched from Google.
Razorpay (Pro payments)Takes payment in INR on its own pages. Pro and Pro+ are paid plans (Pro ₹299 / month or ₹2,999 / year; Pro+ ₹599 / month or ₹5,999 / year), sold as Razorpay subscriptions that renew by themselves until you cancel on the Billing page.Your card or UPI details and billing name — entered on Razorpay, never on our pages. When you pay, Razorpay sends us the payment id, the amount and the email you paid with; we store those in our billing log to switch Pro on and to handle refunds. We never see your card or UPI details. A subscription creates a customer record (name and email) and a subscription at Razorpay, and we store the subscription id and its status.

We do not sell, rent or share your data with anyone else. We would disclose it only if required by a lawful order from an Indian court or authority, and we would tell you unless the order forbids it.

11. The Chrome extension

The extension's own privacy policy, the one its Chrome Web Store listing points to, is at https://zaivdigital.com/zaiv-lens/privacy/. It describes version 1.3.0 in full; this section summarises it.

Single purpose

ZAIV LENS has one purpose: research on the amazon.in search-result or product page you are viewing (a demand range taken from Amazon's own "bought in past month" badge, the Easy Ship fee and GST) and, when you press Send, saving that page's figures to your Zaiv Lens Cloud account. It reads only the page you have open. It never signs in to Amazon.

Permissions, exactly as declared in the manifest, and why

PermissionWhy it is needed
storageTo keep your session token and the email address you are connected as in the extension's own private storage (chrome.storage.local), so captures are saved to your account, plus the public address and publishable key of Zaiv Lens Cloud. It holds nothing else, and no secret of ours.
https://hfzhntkwndduxvktcplj.supabase.co/* (host)To send captures to your Zaiv Lens Cloud account and refresh your session token. The request carries your own session; no other credential exists in the extension.
Content script on https://www.amazon.in/s*, /dp/*, /*/dp/* and /gp/product/*To add the LENS tab to amazon.in pages whose address begins with /s (search results, and a few other pages such as seller-profile and store pages) and to product pages and, after you click it, read the page in front of you and show the Zaiv Lens panel on it. This is the only marketplace Zaiv Lens supports. Sign-in, checkout, payment, order and account pages, Seller Central and the advertising console are excluded in the manifest, so nothing of ours runs there.
Content script on https://app.zaivdigital.com/*To complete the one-time "Connect" handshake on our own connect page, where the app hands the extension your session token after you click Connect.

The extension requests no other permission and runs nowhere else: no tabs, no history, no cookies, no <all_urls>. The packaged extension contains the public Supabase project URL and publishable key — both are designed to be public and are already in the app's own JavaScript — and nothing else.

12. Your rights

Under the Digital Personal Data Protection Act, 2023 and as a matter of how we run the service, you can at any time:

13. Children

Zaiv Lens is a business tool for Amazon sellers. It is not directed at anyone under 18, and we do not knowingly hold data about anyone under 18. If you believe we do, email us and we will delete it.

14. Changes to this policy

If we change what we collect, where it lives or who can read it, we will update this page, change the version and effective date at the top, and email the address on your account before the change takes effect. Continuing to use Zaiv Lens after that date means you accept the updated policy.

15. Contact

Zaiv Digital (Anayza Enterprises), Kalkaji, New Delhi, India · support@zaivdigital.com

See also the Terms & Conditions and Support pages.