Legal · PrivacyThe editorial site at zupeein.com collects the minimum data needed to serve the page and respond to reader letters. This page is the desk plain-English privacy policy. The operator product has its own privacy policy inside the app.
Server logs. IP address, user agent, requested path. Retained for 30 days.
Reader letters. If you write in, your email and the content of your message.
Newsletter signups. Email address, only if you sign up.
The desk does not collect your mobile number, your bank account, your PAN or any financial identifier. The operator product handles those. If anyone claiming to be the desk asks for them, it is not the desk.
The editorial site has no payment portal. Any request for financial data on this domain is a phishing attempt. Leave the page and write in.
The editorial site uses minimal cookies — session cookies and a single analytics cookie that aggregates page views. No advertising cookies and no cross-site tracking.
Server logs: 30 days. Reader letters: 12 months, then deleted. Newsletter signups: until you unsubscribe. You can request deletion of any retained data through the address on the verification desk page.
Access. Ask what data the desk holds about you.
Correction. Correct any inaccurate data.
Deletion. Delete any data the desk holds, subject to legal retention.
Write in through the editorial address listed on the verification desk page. The desk aims to respond within seven working days.
Three habits the desk has internalised. First, treat the operator published privacy policy as the superseding source for any data the operator collects. Second, treat the cookies and tracker behaviour of your own browser as your responsibility. Third, treat reader-flagged corrections as the most-valued input.
Two things the desk treats as anchor facts. First, the site does not set first-party cookies. Second, the site embeds a single font URL from Google Fonts.
Three recurring ones. First, "do you collect my KYC documents?" No. Second, "do you sell my data?" No. Third, "where is the affiliate route?" It is the single contextual affiliate URL on this domain.
Two checks. First, the operator published privacy policy on the help section. Second, the cookies and tracker behaviour of your own browser.
For the terms of use, see the terms page. For the verification habit, see the verification desk. For the operator profile, see the owner page.
Three things to look for. First, what we collect. Second, what we do not collect. Third, the affiliate disclosure. Each is short on purpose; reading them takes five minutes.
Three things. First, the operator internal policy; operator policy covers any data the operator holds. Second, third-party cookies set by web fonts or other resources. Third, any browser-side tracking the operator app carries.
Two checks. First, the operator published privacy policy on the help section. Operator policy applies to any data the operator collects. Second, the cookies and tracker behaviour of your own browser.
Two recurring ones. First, "do you collect my KYC documents?" No. Second, "do you sell my data?" No.
For the terms of use, see the terms page. For the verification habit, see the verification desk. For the operator profile, see the owner page.
Three habits the desk has internalised for reading this policy. First, treat each clause as one isolated reading. Second, treat the operator published privacy policy as the superseding source for any data the operator collects. Third, treat reader-flagged corrections as the most-valued input.
Two things the desk treats as anchor facts. First, the site does not set first-party cookies. Second, the site embeds a single font URL from Google Fonts.
For the terms of use, see the terms page. For the operator profile, see the owner page.
Three habits the desk has internalised for daily privacy reading. First, treat the operator published privacy policy as the superseding source. Second, treat the cookies and tracker behaviour of your own browser as your responsibility. Third, treat reader-flagged corrections as the most-valued input.
Two things the desk treats as anchor facts. First, the site does not set first-party cookies. Second, the site embeds a single font URL.
For the terms of use, see the terms page. For the verification habit, see the verification desk.
No. The site has no payment portal.
30 days.
Yes, any time. Each newsletter has an unsubscribe link.
Yes, subject to legal retention.
No.
The address on the verification desk page.
No. The desk is independent from the operator product.
The desk collects the reader's IP address, the reader's user-agent, the reader's referrer, and the reader's page-visited log. The desk does not collect the reader's name, the reader's email, the reader's phone number, the reader's PAN, the reader's Aadhaar, or the reader's KYC document. The desk's analytics is a private Plausible instance, and the IP address is not stored. The terms page documents the editorial scope, and the facts page documents the desk's verification method.
The reader's habit is to read the data-collected list on the privacy page, and to log the data-collected list on a private sheet. The sheet is the audit trail if the desk's analytics is reversed, and the desk's support channel honours the sheet if the audit trail is clean.
The desk's analytics is a private Plausible instance, and the Plausible instance does not set cookies. The Plausible instance does not set third-party trackers. The Plausible instance does not set cross-site identifiers. The desk's analytics is the canonical signal of the reader's page-visited log, and the desk's analytics is the canonical signal of the reader's referrer. The reader's habit is to read the cookies list on the privacy page, and to log the cookies list on a private sheet. The terms page documents the editorial scope, and the facts page documents the desk's verification method.
The reader's habit is to log the cookies list on a private sheet, and to re-check the cookies list on the morning of the first visit. The re-check is the moment the cookies list is locked.
The desk's analytics is retained for 1 year. The desk's source dossier is retained for the editorial subscription's lifetime. The desk's reader-correction channel is retained for 7 years. The retention window is the canonical signal of the desk's data-handling. The reader's habit is to read the retention window on the privacy page, and to log the retention window on a private sheet. The terms page documents the editorial scope, and the facts page documents the desk's verification method.
The reader can request the desk's view of the reader's data, the desk's deletion of the reader's data, the desk's export of the reader's data, and the desk's correction of the reader's data. The reader's habit is to write to the desk's reader-correction channel with the request, and to log the request on a private sheet. The customer-care page documents the escalation ladder if the request is unresolved.
The terms page documents the editorial scope, and the facts page documents the desk's verification method.
