Privacy & Data Protection Policy · version 2026.1.0

Your data, and exactly what we do with it .

Written under the Digital Personal Data Protection Act, 2023 and the Information Technology Act, 2000, with the RBI and NPCI master directions that govern how payment data is routed. Everything we collect, everywhere it goes, and the rights you hold over it — all of it is on this page.

What we never collect
256-bit
TLS on every connection
8
Categories of data collected
5
Things never collected, ever
6
Rights you hold under the DPDP Act
0
Data sold to brokers or advertisers
12h
Support, every day of the week
The life of your data

Six stages, from collected to deleted

Processing means the whole automated lifecycle — collection, recording, compilation, organisation, cloud storage, logical updating, institutional sharing, and secure deletion. Here is that lifecycle, stage by stage.

Stage 1

Collected, with your consent

By installing the app, logging in or routing funds, you give explicit consent under the DPDP Act, 2023 for us to process your information to deliver the services you asked for. You confirm the information you supply is authentic, current and yours.

Stage 2

Processed for a stated purpose

Account management, payment processing, utility delivery, identity verification, customer service, risk mitigation, tax invoice generation, loyalty tracking, and compliance with statutory obligations under Indian law. Nothing outside that list.

Stage 3

Shared only where a transaction needs it

Payment gateways, banking nodes, the Bharat Connect network, utility aggregators, transport operators and government authorities — each receiving the minimum the job requires. Never sold, rented or traded to brokers or marketing agencies.

Stage 4

Secured in transit and at rest

256-bit TLS on every connection, firewalled network architecture, role-based access with multi-factor authentication on admin dashboards, continuous event logging, and mirrored geographical backups.

Stage 5

Retained as long as the law requires

Profile details for the active life of the account. Financial records and transaction logs for the longer windows that corporate tax law, banking rules and statutory audits demand.

Stage 6

Purged or anonymised

Once the legal retention window expires, records are permanently purged or completely anonymised using secure digital deletion methods. Anything held back for statutory reasons moves out of production into restricted offline vaults.

How we govern data

Four pillars from the DPDP Act

The technical architecture is built on these, and every collection decision is measured against them.

Purpose limitation

We collect data strictly required to clear financial transactions or manage customer support workflows.

Data minimisation

We refrain from harvesting secondary user details or data assets that do not directly improve service delivery or satisfy KYC compliance rules.

Security and resilience

Data assets are locked inside highly protected cloud facilities, using automated continuous monitoring to counter external vulnerabilities.

Accuracy guarantee

We provide simple tools to review, update and fix errors in your profile information.

Words used here

Five terms, defined

These carry specific legal meanings throughout the policy.

AccountA uniquely assigned, cryptographically authenticated customer ledger entry matching a verified mobile identifier.
Personal dataAny information that, directly or indirectly, can isolate, pinpoint, identify or describe a unique natural individual.
Sensitive personal dataFinancial balances, KYC documents, transactional histories and authentication payloads, as designated under current Indian privacy laws.
ProcessingThe systematic automated lifecycle applied to data: collection, recording, compilation, organisation, cloud storage, logical updating, institutional sharing and absolute secure deletion.
Payment partnerScheduled commercial banks, NPCI networks, payment gateways and clearing house APIs linked to the Anpay ecosystem.
What we collect

Eight categories, and why each one exists

Collected to provide seamless payment routing and to fulfil legal compliance rules — nothing is gathered without one of those two reasons behind it.

A

Direct profile information

Full legal name, verified mobile number, email address, date of birth, gender, full physical address including state, district, city and PIN code, and language preferences.

B

Identity and KYC information

PAN details and verification markers, Officially Valid Documents such as passports, voter IDs or driving licences, and verification status from approved central providers. Aadhaar-based authentication, where lawfully and voluntarily used, runs through authorised masking gateways — no raw identification digits are ever printed, shared or displayed in clear text.

C

Transactional history

Transaction ID, internal order ID, service type, biller details, Bharat Connect transaction signatures, operator reference numbers, payment volumes, cashback records and Anpay Coin balances.

D

Payment and routing payloads

The payment method selected — UPI, debit card, credit card, net banking or Anpay Coins — bank reference strings, UPI reference tags and clearing-house status responses. Under PCI DSS, our structures never store complete card numbers, CVV codes, card PINs, net banking passwords or UPI PINs.

E

Security and account activity

Registration timestamp, successful login and logout markers, failed login attempts, password reset history, active MPIN status and referral codes — tracked to prevent account takeovers.

F

Support and grievance records

Support ticket reference codes, email transcripts, WhatsApp chat threads, file attachments, system error screenshots and case resolution histories.

G

Device technical data

Device type, manufacturer, model, operating system variant and version, Anpay app version, screen resolution, system time zone and interface language — logged to detect device spoofing and confirm app safety.

H

Network telemetry and diagnostics

IP address, internet service provider identity, approximate location, session duration markers, background system error exceptions and application crash reports.

What we never collect

Five things our systems are blocked from touching

These are systemic blocks, not policy promises — the platform cannot harvest or track any of them under any scenario.

Never collected, under any scenario

To protect your financial security, Anpay maintains strict systemic blocks that prevent the platform from harvesting or tracking these highly sensitive credentials:

  • Card PINs — your confidential debit or credit card personal identification numbers.
  • CVV codes — the three-digit card verification value.
  • Banking passwords and UPI PINs — internet banking passwords or transaction UPI PINs.
  • Raw OTPs — one-time passwords are not retained after verification completes.
  • Biometrics — fingerprints and face geometry stay inside your device's secure hardware layer.
Cookies and device permissions

What runs in the browser, and what the app asks for

Industry-standard cookies, web beacons and tracking pixels help recognise your browser on a future visit. The app asks for device permissions only where a feature needs them.

Cookies deployed

Used to enhance the experience, protect account sessions, optimise performance and analyse service usage.

  • Essential and operationalEnable core website functionality, maintain secure sessions, prevent unauthorised access and protect against fraudulent activity.
  • Performance and latencyMeasure performance, optimise page loading speed, analyse interaction maps and identify underlying technical issues.
  • Preference and interfaceSave language selections, retain interface settings and remember login setup configurations.
  • AnalyticsMeasure aggregated traffic, analyse behavioural trends and optimise platform scalability.

App permissions

Requested under rigorous structural protocols, each tied to a specific feature.

  • CameraSecure KYC verification, uploading validation documents and scanning retail dynamic QR codes.
  • Storage and filesSaving tax invoices, downloading transaction receipts and uploading verification proof.
  • Push notificationsReal-time top-up alerts, bill confirmations, instant security warnings and authorised promotional campaigns.
  • ContactsStrictly opt-in, only if you choose a feature that needs contact selection — such as sharing a referral code.
  • LocationDetecting anomalies, looking for location fraud, and complying with regional Indian financial regulations.
Collected while you use a service

What each service records

Depending on which utility you use, these are the structural strings our databases store.

Recharge services

CLAUSE 14

Target mobile numbers, cellular operator identity, network circles, selected plans and transaction status codes.

Bharat Connect

CLAUSE 14

Consumer account numbers, biller identities, billing volumes, due dates, Bharat Connect transaction IDs and operator reference strings.

Travel booking

CLAUSE 14

Full passenger names, ages, booking reference markers, travel routes, PNR statuses, cancellation requests and refund tracks.

Digital gift cards

CLAUSE 14

Selected merchant brands, exact voucher face values, order reference codes and redemption status indicators.

Anpay Coin and rewards

CLAUSE 14

Loyalty tokens accrued, coins redeemed per transaction loop, live coin balances and token expiration timelines.

Automated technical logging

CLAUSE 12

On every access: originating IP address, login and logout timestamps, browser variant, device category, OS version, Anpay software version, network type (Wi-Fi or cellular), error exceptions and crash diagnostics.

Analytics

CLAUSE 13

Session volumes, interaction durations, most-used services, navigation loops, error rates and regional trends. All datasets are permanently aggregated and anonymised, completely decoupled from individual profiles.

Fraud prevention monitoring

CLAUSE 16

Account logs screened for multiple failed logins, abnormal high-value patterns, concurrent device hijacking and access from compromised networks. Anpay may delay, hold or decline any transaction pending verification.

How it is used

Lawful purposes, and one thing you can switch off

1

What the data is used for

Account management, payment processing, utility delivery, identity verification, customer service, risk mitigation, tax invoice generation, loyalty tracking, and compliance with statutory legal obligations under Indian law. By using our services you grant explicit consent for processing as described here, and you remain responsible for keeping the identifiers you supply accurate — incorrect data causes transaction failures and delivery delays.

2

Marketing you can opt out of

With your voluntary consent we may send updates about promotional cashbacks, campaigns and referral rewards over email, SMS, push notification or WhatsApp. You keep the full right to opt out of promotional alerts at any time. Essential transactional notices — recharge confirmations, refund updates and security warnings — cannot be disabled.

Who it is shared with

Never sold. Shared only where the transaction requires it.

We do not sell, rent, trade or unconstitutionally traffic your personal data to third-party brokers or external marketing agencies. Every party below is contractually and legally bound to safeguard your information under applicable Indian laws and strict non-disclosure mandates.

Security infrastructure

What stands between your data and an attacker

Administrative, technical and physical measures together. We apply industry-best solutions — while being clear that no method of transmission over the internet can be guaranteed 100% secure.

DPDP Act 2023Data protection
IT Act 2000Digital records
PCI DSSCard data handling
256-bit TLSEvery connection
Regulators and networks this sits under
Reserve Bank of India NPCI Bharat Connect CERT-In Companies Act 2013
All consumer payment databases, transaction logs and profile records are hosted in secure local cloud zones inside India
  • Transport layer encryption

    All sensitive data and transactional payloads moving between your app or browser and our cloud servers use 256-bit TLS, shielding packets from interception, sniffing and man-in-the-middle attacks in transit.

  • Role-based internal access

    Internal access is limited to staff who need the data to manage support, resolve transaction errors or handle compliance. Multi-factor authentication is enforced on administrative dashboards, and detailed audit logs are kept for every data query event — reducing the risk of internal misuse or unauthorised data handling.

  • Network defence and backups

    Secure architecture behind firewalls, role-based controls, continuous security event logging, system patch management and automated geographical backup facilities.

  • Business continuity

    Redundant mirrored database cloud architectures, regular disaster recovery exercises and automated operational health checks, so an infrastructure disruption does not become data loss.

  • Continuous monitoring

    A security operations centre runs automated monitoring to flag and neutralise anomalies before they reach users: real-time login pattern tracking, API payload inspection, database error trend checks and centralised event logging.

  • Incident response

    On detecting a breach or unauthorised security event, the incident response team takes immediate containment steps, secures vulnerable access points and cooperates with agencies such as CERT-In. Affected users and authorities are notified promptly where the law requires it.

  • Data integrity

    We take reasonable steps to keep records accurate and relevant, and encourage you to update your profile whenever something changes — it keeps delivery fast and disputes short.

Your rights

Six rights you hold under the DPDP Act

Enforceable legal data rights, subject to verification protocols and local legal limitations. Exercise any of them through the form below or the grievance desk.

Access and inspection

Request deep visibility into the exact categories of personal profile, banking reference and transactional records currently held in our cloud architecture.

Rectification and correction

Request immediate modification or updating of any inaccurate or outdated information associated with your profile.

Consent withdrawal

Reverse or withdraw your consent for future data processing operations at any time.

Secure deletion and erasure

Ask for deletion of your personal records once the data is no longer required to deliver the services you requested.

Processing inquiry

Demand detailed reports explaining how your data is shared, which banking gateways it is routed through, and the purposes behind our internal governance processes.

Lodging formal disputes

File data privacy complaints directly through our dedicated grievance desks.

Where erasure cannot be granted

Fulfilment of erasure or consent-withdrawal requests is restricted by statute. Anpay cannot execute deletion where legal mandates require retention for corporate taxation, systemic audit tracking, ongoing fraud investigations, or active banking network dispute resolutions.

Where a lawful deletion request is approved, secure purges run across all active operational servers. Records retained for the statutory reasons above are moved out of active production and stored inside highly restricted, offline cloud vaults, still protected under the same security standards.

Managing your own account

Updating, closing, and what closure does not do

Depending on which utility you use, these are the structural strings our databases store.

Keeping details current

CLAUSE 40

You are responsible for keeping profile data, utility account numbers, cellular identifiers and email endpoints accurate, authentic and complete. Details can be changed instantly through the self-service dashboard in the app, or by lodging a verification ticket with support. Incorrect or outdated contact data disrupts payment delivery, triggers failures on external billing networks, and limits what support can do for you.

Account closure

CLAUSE 41

File a closure request through support@anpay.in. Strict identity verification runs first, to prevent malicious takeovers and unauthorised profile manipulation. Closure cannot be executed while there are active pending transactions, unresolved refund cycles, open disputes with external billers, ongoing fraud investigations, or unfulfilled accounting tracking loops.

What deletion cannot reach

CLAUSE 42

Closing a profile does not immediately delete the underlying financial files — corporate and banking laws require preservation for fixed multi-year audit windows. Anpay retains specific transactional records for taxation and financial reporting, anti-money-laundering and security investigation requirements, corporate audits and enforcement of user agreements.

The boundaries

Consent, eligibility, and the edges of our control

CLAUSE 5

Consent and acceptance

Installing the app, logging in or routing funds confirms you have read and understood this document, and grants unconditional explicit consent under the DPDP Act, 2023 for processing to deliver requested services. If you do not accept these terms, discontinue use and request account closure immediately.

CLAUSE 6

Legal eligibility

You represent that you are of sound mind, legally competent under the Indian Contract Act, 1872, and authorised to act for any entity you register. Minor interactions require explicit validation from a parental guardian, and any detected use of synthetic or fraudulent IDs triggers instant account termination.

CLAUSE 43

Third-party links

Our interfaces may contain links to external portals, banking interfaces or partner developer platforms. Anpay disclaims liability for the privacy practices, tracking cookies, security measures or content of third-party platforms. Once you follow an external link you are governed by that platform's privacy conditions — review them.

CLAUSE 44

Children's data

Our products are designed for individuals legally capable of entering binding contracts under the Indian Contract Act, 1872. We do not intentionally gather, index or process details from individuals under the age of majority without parental consent. Where risk tracking identifies an unverified minor's account, the system locks the profile and purges the associated data fields from active systems.

CLAUSE 45

Cross-border transfers

Anpay operates entirely within the sovereign boundaries of the Republic of India, and all payment databases, transaction logs and profile records are hosted in secure local cloud zones. Should future expansion or international travel partner features require routing data across borders, such movement will match strict data security laws using robust contractual safeguards.

CLAUSE 46

Automated decisions and risk scoring

Automated algorithms evaluate security states in real time: detecting suspicious volume spikes or unusual location shifts, blocking brute-force login attempts and device hijacking, and intercepting transactions that deviate from your baseline. Where an automated decision affects your account status, you retain the full right to file an evaluation request with our compliance division for manual review.

The legal terms

Liability, changes and jurisdiction

Where this policy applies

Every interface, every product, every pipeline

It applies universally to all individuals, consumers, merchants, corporate partners, system administrators and third-party nodes that access the digital products hosted by Anpay.

Anpay mobile application
Official web portals
B2B merchant systems
Admin dashboards
Mobile network recharges
Satellite TV top-ups
Bharat Connect utility clearings
Flight, hotel and bus tickets
Brand e-gift cards
Automated SMS networks
Corporate emails
Push notification servers
Accountability

Who is answerable for your data

VD
Vaskar Das
Founder & Director

Sets the product direction and the technical standard, and signs off on how customer money is handled.

"The shortest privacy policy would be the most flattering one. This is the accurate one instead."

At Anpay, your data security is our ultimate corporate responsibility. We continually audit our technology stacks, train our operations teams and evaluate our infrastructure security systems to promote highly responsible data governance.

The ongoing goal is a secure, completely reliable and deeply rewarding digital payment experience for every citizen and merchant we serve across the country — which starts with being precise about what we hold and honest about what we cannot delete.

Version 2026.1.0 DPDP Act 2023 IT Act 2000 RBI & NPCI directions Companies Act 2013
Data privacy enquiries

Exercise a right, or ask a question

In compliance with the DPDP Act, 2023, this is the dedicated channel for data privacy concerns. We make reasonable efforts to investigate and respond within a reasonable time, depending on the technical complexity of the case.

Corporate identity ledger

Legal entityAnpay Ventures Private Limited
CINU63990WB2024PTC272006
GSTIN19ABBCA0218R1ZH
Registered office1st Floor, Narayanpur, Kumarganj, Balurghat, Dakshin Dinajpur, India
Policy version2026.1.0
JurisdictionCourts at Dakshin Dinajpur, West Bengal

Communications directory

General corporateinfo@anpay.in
Customer helpdesksupport@anpay.in
Alliances and APIbusiness@anpay.in
Grievance and disputesdispute@anpay.in
Voice helpline011 6929 0388
WhatsApp gateway+91 94341 16115
Active hours11:00 AM to 11:00 PM IST, all seven days
Tell us your name as registered
Enter the 10-digit number on your account
Enter an email we can reply to
Pick the right you want to exercise
0 / 1000
A few lines, please — enough for us to act on

Identity verification runs before any request is actioned. Never send your OTP, MPIN, card CVV, full card number or UPI PIN — we never ask for them.

Questions about your data?

The compliance desk answers data rights inquiries and privacy complaints directly. Call, message, or use the form above.

="_blank">+91 94341 16115 · 11:00 AM to 11:00 PM IST, every day