e-Paper

PRIVACY POLICY

Privacy Policy

Privacy Policy

Daily ePaper · localhost:8080/mandali_epaper · Last updated: 8 September 2026

This Privacy Policy explains, in detail, how Daily ePaper (“we”, “us”, “our”) collects, uses, stores, shares, and protects information when you visit localhost:8080/mandali_epaper, read our digital ePaper, create an account, subscribe, clip pages, download PDFs, set a reading location, or enable notifications. By using the website and related services, you agree to this policy together with our Terms & Conditions.

Who we are

Daily ePaper publishes digital newspaper editions (ePaper) at localhost:8080/mandali_epaper. This policy covers the public website, the ePaper reader, archive, search, subscription pages, clip/share features, and related admin-operated services that process reader information.

This document is an explanation of our practices. It is not legal advice. If a court or regulator requires a different standard, we will follow applicable law.

Information we collect

We collect only what we need to run the ePaper. Depending on how you use the site, this may include:

  • Account details when you sign in with Google: name, email address, and a profile image URL provided by Google. We do not receive your Google password.
  • Contact details you type into Contact Us or other forms (name, email, message).
  • Subscription and billing records such as plan, status, dates, and payment references from the payment partner. Full card numbers are handled by the payment provider, not stored as raw card data on our servers.
  • Reading location if you allow it: district, state, country, optional locality/area label, and (when GPS is used) approximate coordinates used to match your district. This is stored in a browser cookie and may be recorded for matching editions.
  • Notification subscription if you allow browser push: a push endpoint and encryption keys stored so we can send edition alerts. We do not get the contents of other sites’ notifications.
  • Clips and shares: cropped page images you create, share links, and related metadata (edition, page).
  • Technical data: IP address, browser type, device type, language, referring page, and approximate network location used for security, diagnostics, and (when GPS is off) a rough location guess.
  • Usage data: pages viewed, edition opened, feature clicks (for example clip, archive, PDF download attempts) as needed to operate and improve the service.

We do not require you to create an account only to browse public pages. Some features (PDF download, some personalisation) need sign-in and an active publisher subscription.

How we use your information

We use information to:

  • Show ePaper pages, archives, search, and the correct edition for your area when location is available.
  • Keep you signed in and recognise returning readers.
  • Process subscriptions, renewals, invoices, and payment status.
  • Send service messages and, if you opted in, web push alerts when an edition is published.
  • Let you clip, download, print, or share a portion of a page you selected.
  • Protect the site against abuse, fraud, spam, and unauthorised access.
  • Measure performance (page load, errors) and improve layout and features.
  • Comply with law, respond to lawful requests, and enforce our Terms.

We do not sell your personal information. We do not rent reader lists to unrelated advertisers as a data product.

Location and editions

If location features are enabled, we may detect or remember your area so that editions tagged with the same district (for example Khammam or Hyderabad) can be ranked first in lists and the edition menu. Detection can use:

  • Your browser’s location permission (GPS), then map matching to a district/area;
  • A location you choose yourself in the location panel;
  • A short-lived network/IP estimate when GPS is not available (this is less precise).

You can change or clear the saved location from the location chip. Turning location off or blocking permission means we will not use GPS; edition lists then follow default/manual order instead of your district.

Google sign-in and accounts

Reader sign-in uses Google Sign-In (OAuth). Google authenticates you. We store the identity Google shares with us (typically name, email, photo URL) so we can recognise you, apply download permissions, and show your profile. You can stop this by signing out and, if you wish, revoking Daily ePaper access in your Google account settings. Deleting our stored reader record can be requested via Contact Us.

Browser notifications

If you tap Allow on notifications, your browser stores a subscription on your device and we keep the corresponding push endpoint so we can send alerts (for example when a new edition is published). You can revoke this any time in the browser site settings or using unsubscribe on the site if shown. We do not use push to send unrelated advertising without a separate, clear opt-in.

Subscriptions and payments

Paid plans are processed through a payment partner (for example Razorpay). The partner collects payment instrument details under its own privacy policy. We keep transaction references, amount, status, and plan dates so we can activate or renew access. Queries about a charge should include the transaction reference shown in your history or email.

Clips, sharing, and PDF downloads

When you clip a region of a page, we generate an image of that region so you can download or share a link. Shared clip pages may be viewable by anyone who has the link. Do not clip or share content you are not allowed to redistribute.

Edition PDF download, where offered, is limited to signed-in readers while the publisher subscription is active. Download attempts may be logged (edition, time, IP) for security and abuse prevention. PDF files are not meant to be a public, unauthenticated download.

Cookies and similar technologies

We use cookies and similar storage to:

  • Keep a login session;
  • Remember your chosen reading location;
  • Remember display preferences where applicable;
  • Support security (for example CSRF protection) and basic analytics.

On first visit we show a cookie notice. Continue means you are happy to receive the cookies described in our Cookie Policy.

You can block or delete cookies in your browser. If you do, sign-in, location ranking, and some forms may stop working until cookies are allowed again.

Third-party services

We use trusted processors to run the product, which may include:

  • Google (sign-in);
  • Payment gateways;
  • Map/geocoding providers used only to turn coordinates or place names into a district/area;
  • Hosting, CDN, and object storage so page images load quickly;
  • Email or notification infrastructure.

Those parties process data under their own terms. We require them to use data only to provide their service to us, except where they independently provide a service to you (for example Google Account).

Pages may link to other websites. Their privacy practices are their own. Review those policies before you share information there.

Security and storage

We use reasonable technical and organisational measures: HTTPS where configured, access controls on administration, private storage for edition PDFs, and least-privilege access for staff tools. No method of transmission or storage is 100% secure. You should protect your Google account and avoid sharing clip links that contain private material.

Newspaper page images shown in the reader are part of a published edition and may be cached on a content network so the paper loads quickly. That is distribution of published content, not a sale of your personal profile.

How long we keep data

We keep information for as long as needed to provide the service, keep accounts and payments accurate, resolve disputes, and meet legal or audit duties. Location cookies may expire sooner (hours for a rough IP guess, longer for a location you saved). Push subscriptions are kept until you unsubscribe or the browser invalidates them. Clip files and share links remain until deleted by us or by retention rules set by the publisher.

Your rights

Subject to Indian law (including applicable IT and data protection rules), you may request to:

  • Know what personal data we hold about you;
  • Correct inaccurate account or contact information;
  • Withdraw consent for location, cookies, or notifications (via browser/site controls, or by asking us);
  • Ask for deletion of your reader account data where we are not required to keep it (for example payment records);
  • Complain to us first via Contact Us, and to a competent authority if you remain unsatisfied.

We may need to verify that the request comes from the account holder before we change or delete data.

Children’s privacy

The ePaper is a general news product. We do not knowingly collect personal information from children under 13. If you believe a child has submitted personal data, contact us and we will take reasonable steps to delete it. Parents and schools should supervise use of the site.

Changes to this policy

We may update this page when features, law, or processors change. The “Last updated” date at the top will change. Continued use of localhost:8080/mandali_epaper after an update means you accept the revised policy. Material changes may also be announced on the site.

Contact

Questions, access requests, or complaints about privacy: use our Contact Us page. Please mention “Privacy Policy” in the subject and include the email you use to sign in, if any.

Related documents: Terms & Conditions · Cookie Policy