Privacy Policy

This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use Paymorz services.

1. Introduction and Scope

1.1. Introduction

This Privacy Policy ("Policy") explains how QUANTUMCONA LLP, operating as Paymorz™ ("Company," "we," "our," "us"), collects, uses, and protects your personal information through our website, mobile application, and related services (collectively, the "Platform").

Paymorz™ is a vendor management and payment enablement platform developed by QUANTUMCONA LLP. The Platform enables businesses, startups, and enterprise clients to onboard vendors, verify their KYC details, manage invoices, and process secure payments in compliance with Indian regulatory requirements.

We respect your privacy and comply with applicable data protection laws, including the Digital Personal Data Protection Act, 2023 (DPDP Act), Information Technology Rules, 2011, Intermediary Guidelines, 2021, and Reserve Bank of India (RBI) regulations.

By using the Platform, you acknowledge that you have read, understood, and agree to this Policy. If you do not consent to this Policy, please discontinue use of our services immediately.

1.2. Scope

This Policy applies to all users of Paymorz™, including:

  • Freelancers and service providers utilizing invoicing services on the Platform
  • Vendors, service providers, and business entities interacting with the Platform
  • Visitors accessing the Platform or communicating with us

This Policy covers personal and sensitive data (including KYC, financial, and transactional details) collected through our website, mobile application, customer support channels, and authorized third-party tools.

This Policy does not apply to:

  • External websites or applications linked to Paymorz™
  • Independent vendors or partners collecting data outside our systems
  • Services not operated or controlled by QUANTUMCONA LLP

We encourage users to review third-party privacy practices before sharing their data with external services.

1.3. Governing Law

This Policy shall be governed by and construed in accordance with the laws of India, with exclusive jurisdiction in the courts of Hyderabad, Telangana, unless otherwise required by applicable law.

Terms used in this Policy have the same meaning as defined in the Paymorz™ Terms of Service.

1.4. Objective

This Policy aims to:

  • Clearly inform users about the categories of data we collect and the purposes for such collection
  • Explain how we use, store, and protect your personal data
  • Define your privacy rights under applicable data protection laws
  • Demonstrate our accountability as a responsible data fiduciary in compliance with the DPDP Act, 2023

2. Data We Collect

2.1. Overview

When you use Paymorz™, we collect and process certain personal and sensitive data to operate the Platform, verify users, process payments, and comply with legal obligations. We only collect information that is necessary, lawful, and proportionate, as required under Section 6 of the DPDP Act, 2023.

2.2. Categories of Data Collected

2.2.1. Identification and Contact Data

Data Categories: Name, business name, email address, phone number, physical address, and login credentials.

Purpose: Account creation, identity verification, communication, and registration compliance.

2.2.2. Financial and Payment Data

Data Categories: Bank account details, UPI ID, transaction references, and invoice details (processed via PCI-DSS–compliant partners such as Razorpay and similar payment aggregators).

Purpose: Secure payment processing, settlements, and financial compliance.

Important Note: Paymorz™ does not store card details or CVV information.

2.2.3. KYC and Compliance Data

Data Categories: Permanent Account Number (PAN), Aadhaar details, business registration documents, Goods and Services Tax Identification Number (GSTIN), and proof of address.

Purpose: Identity verification, anti-fraud checks, and compliance with Reserve Bank of India (RBI) and Prevention of Money Laundering Act (PMLA) obligations.

Security: All sensitive data is encrypted and transmitted securely through secure channels.

2.2.4. Transactional and Platform Activity Data

Data Categories: Invoices generated, payments made to service providers, transaction and settlement details, communication records related to vendor onboarding or payments, and feedback history.

Purpose: To maintain transaction integrity, enable payment reconciliation, and support dispute resolution or audit compliance.

2.2.5. Technical and Device Data

Data Categories: IP address, device ID, operating system type, browser information, performance logs, and approximate location (non-precise).

Collection Method: Collected via cookies, software development kits (SDKs), and analytics tools (e.g., Google Analytics, Mixpanel, and Sentry).

Purpose: Security monitoring, performance diagnostics, error tracking, and improving platform stability and user experience.

2.2.6. Communication and Support Data

Data Categories: Messages, support tickets, attachments, and timestamps when you contact us.

Purpose: Customer support, issue tracking, and service quality improvement.

2.2.7. Marketing and Preference Data

Data Categories: Subscription preferences, engagement metrics, and referral participation (collected only with your explicit consent).

Purpose: Sending product updates, promotional offers, and reward notifications.

2.2.8. Sensitive Personal Data

Data Categories: Financial details, official identification documents, passwords, and biometric data (if utilized).

Purpose: Used exclusively for KYC verification, fraud prevention, or as legally required, with encryption and restricted access controls.

2.3. Data Collection Methods

  • Voluntary Data: Information you provide directly (e.g., during registration, KYC submission, or communication with our support team)
  • Automatic Data: Information collected automatically via cookies, SDKs, or analytics tools while using the Platform

All data is processed lawfully under contractual necessity, legitimate interest, or user consent, in accordance with the DPDP Act, 2023.

2.4. Data from Third Parties

We may receive limited data from the following sources:

  • Payment and KYC partners (for verification purposes)
  • Banks and financial institutions
  • Public or government databases (Ministry of Corporate Affairs (MCA), Goods and Services Tax Network (GSTN))
  • Referral or integration partners

All such data sharing is governed by Data Processing Agreements (DPAs) ensuring equivalent protection standards as required under the DPDP Act, 2023.

2.5. Accuracy and User Responsibility

You are responsible for ensuring that all information you provide is accurate and up to date. Incorrect or false data may lead to account suspension or service restrictions. To update or correct your data, please contact support@paymorz.com.

2.6. Optional Data Sharing

You may choose not to provide certain data; however, this may restrict access to key features such as KYC verification, payment processing, or referral rewards.

3. How We Use Your Data

3.1. Purpose of Processing

Paymorz™ processes your personal and sensitive data only for lawful, necessary, and defined purposes, in accordance with Section 4(1)(b) of the DPDP Act, 2023. We never sell, rent, or use personal data for unrelated or unauthorized purposes.

3.2. Core Data Uses

3.2.1. Account and Identity Management

Purpose: To register and maintain your account, authenticate identity, and verify contact details.

Legal Basis: Contractual necessity; legitimate interest.

3.2.2. KYC and Compliance Verification

Purpose: To verify authenticity under Reserve Bank of India (RBI), Prevention of Money Laundering Act (PMLA), and KYC regulations using PAN, Aadhaar, GSTIN, or equivalent identification documents.

Legal Basis: Legal obligation; legitimate interest (fraud prevention).

3.2.3. Payment and Transaction Processing

Purpose: To process, reconcile, and record payments through PCI-DSS–compliant partners (e.g., Razorpay).

Legal Basis: Contractual necessity; legitimate interest (financial audit).

3.2.4. Service Delivery and Communication

Purpose: To facilitate vendor onboarding, service provider engagement, invoice management, payment requests, and exchange of compliance documents.

Legal Basis: Contractual necessity.

3.2.5. Customer Support and Dispute Resolution

Purpose: To assist users, log issues, and track resolutions for transparency and audit purposes.

Legal Basis: Contractual necessity; legitimate interest.

3.2.6. Security and Fraud Prevention

Purpose: To monitor activity, detect anomalies, and prevent unauthorized or suspicious behavior using automated and manual checks.

Legal Basis: Legal obligation; legitimate interest.

3.2.7. Legal and Regulatory Compliance

Purpose: To fulfill obligations under applicable laws, court orders, or regulator directives (e.g., RBI, Financial Intelligence Unit - India (FIU-IND), Tax authorities).

Legal Basis: Legal obligation.

3.2.8. Analytics and Product Improvement

Purpose: To analyze anonymized usage patterns, fix errors, and enhance platform performance.

Legal Basis: Legitimate interest; user consent (for non-essential analytics cookies).

3.2.9. Marketing and Optional Communication

Purpose: To send product updates, promotions, or referral offers only with explicit consent.

User Control: Users may withdraw consent at any time through account settings or unsubscribe links.

Legal Basis: Consent.

3.2.10. Policy Enforcement and Recordkeeping

Purpose: To enforce our Terms of Service, resolve violations, and maintain records for audits and investigations.

Legal Basis: Legal obligation; legitimate interest.

3.3. Automated and Derived Data Use

Paymorz™ does not engage in fully automated decision-making or profiling that produces legal effects without human oversight. Aggregated, anonymized insights (e.g., usage trends, fraud patterns, uptime metrics) may be used internally for analytics but never identify individuals.

3.4. Data Minimization and Future Services

We collect and retain only data necessary for the purposes outlined above. If Paymorz™ introduces new integrations or features, we will conduct a Data Protection Impact Assessment (DPIA) and inform users before processing any new data category or use. New purposes will always be supported by either a lawful basis or fresh consent.

3.5. Prohibited Uses

Paymorz™ expressly forbids the following:

  • Selling or monetizing personal data
  • Using KYC or financial data for marketing purposes
  • Cross-linking data between users without explicit consent
  • Automated profiling for employment or credit scoring
  • Behaviour-based or retargeted advertising without explicit consent

4.1. Overview

Paymorz™ processes personal data only when there is a clear and lawful basis, in line with Sections 4 and 7 of the DPDP Act, 2023. We process your data when:

  • You have given explicit consent
  • Processing is necessary for a contract or to deliver requested services
  • Processing is required by law or regulation
  • It serves legitimate business interests that do not override your rights
  • It is required to fulfill legal or public duties under applicable law

We do not sell, lease, or process data for unrelated or unauthorized purposes.

4.2. Lawful Bases Explained

4.2.1. Consent

Application: Used for non-essential or optional processing, such as:

  • Marketing or promotional emails
  • Analytics cookies
  • Surveys or testimonials

Consent Management: Consent is obtained through clear, affirmative action and may be withdrawn at any time via account settings or email to support@paymorz.com. Withdrawal does not affect processing completed before revocation.

4.2.2. Contractual Necessity

Application: Required to perform Paymorz™'s contractual and operational obligations, including:

  • Vendor registration, verification, and onboarding
  • Payment initiation, settlement, and reconciliation
  • Invoice processing and transaction record maintenance
  • Customer support and compliance management

Importance: Without this data, Paymorz™ cannot deliver its essential vendor management and payment processing services.

4.2.3. Legal and Regulatory Obligation

Application: We process and retain data as required by:

  • Reserve Bank of India (RBI), Financial Intelligence Unit - India (FIU-IND), and Prevention of Money Laundering Act (PMLA) for KYC and Anti-Money Laundering (AML) compliance
  • Tax and audit requirements
  • Court or law enforcement orders

Note: These obligations may continue even after consent withdrawal or account closure.

4.2.4. Legitimate Business Interests

Application: We process limited data to ensure operational integrity and service improvement, such as:

  • Preventing fraud or misuse
  • Maintaining network security
  • Enhancing user experience and functionality
  • Conducting internal audits or risk management

Safeguards: We apply strict safeguards to ensure such processing never overrides user rights.

4.2.5. Legal or Public Duties

Application: In rare cases, Paymorz™ may process data to assist lawful investigations or fulfill public mandates (e.g., fraud detection, AML compliance), under authorized supervision.

4.2.6. Employment and Partner Data (Internal Use)

Application: For internal staff, consultants, or verified vendors, data is processed for onboarding, payroll, and compliance with labor and tax obligations.

4.3. Automated Decision-Making

Paymorz™ does not engage in automated decisions or profiling that produce legal or significant effects without human oversight. Automated tools (e.g., fraud detection) operate under supervision and regular review.

4.4. Compatibility and Future Use

Before processing data for a new or secondary purpose, Paymorz™ will:

  • Assess legal compatibility
  • Notify affected users
  • Obtain fresh consent, where required

No new purpose is introduced without a valid lawful basis and transparency update.

4.5. Documentation and Accountability

Paymorz™ maintains internal Records of Processing Activities (RoPA) detailing:

  • Each data category and purpose
  • Lawful basis
  • Retention timelines
  • Applied safeguards

These records are periodically reviewed by the Data Protection Officer (DPO) for ongoing compliance.

5. Data Sharing and Disclosure

5.1. Overview

Paymorz™ does not sell or trade user data. Information may be shared only with trusted partners that help us operate the Platform or meet legal obligations. Each disclosure is limited, documented, and protected by confidentiality agreements and Data Processing Agreements (DPAs) that require equivalent safeguards under the DPDP Act, 2023, and Information Technology Rules, 2011.

5.2. Categories of Authorized Recipients

5.2.1. Payment and Financial Partners

Partners: Razorpay and similar licensed payment aggregators.

Purpose: Process and reconcile transactions, prevent fraud, and comply with Reserve Bank of India (RBI) KYC and record-keeping norms.

5.2.2. Cloud and Infrastructure Providers

Partners: Google Cloud, Supabase, Amazon Web Services (AWS), or equivalent secure hosts certified under ISO 27001 or SOC 2.

Purpose: Reliable storage, uptime, and scalability of Platform data.

5.2.3. Analytics and Diagnostics Partners

Partners: Mixpanel, Google Analytics, or comparable analytics SDKs.

Purpose: Understand usage trends and improve functionality using anonymized or pseudonymized data.

5.2.4. Authentication and Communication Vendors

Partners: Clerk.dev (for login), SendGrid / Twilio (for OTPs and emails), and similar future providers.

Purpose: Account access, alerts, and verification.

5.2.5. KYC and Compliance Vendors

Partners: Independent verification or background-check agencies.

Purpose: Fulfill Reserve Bank of India (RBI) and Financial Intelligence Unit - India (FIU-IND) KYC-AML obligations.

5.2.6. Professional and Legal Advisors

Partners: Law firms, auditors, and tax consultants.

Purpose: Legal defense, contract enforcement, and statutory audit.

5.2.7. Government and Regulatory Authorities

Recipients: Courts, regulators, or law-enforcement bodies—only on lawful request or statutory compulsion.

Purpose: Legal compliance and prevention of unlawful activity.

5.2.8. Affiliates and Business Successors

Circumstances: In mergers or acquisitions, data may transfer to a successor entity with equal safeguards.

Purpose: Business continuity.

5.2.9. Internal Teams

Access Control: Access is role-based and limited to trained staff in support, compliance, or engineering departments.

Purpose: Secure internal operations.

5.3. Principles for All Disclosures

  • Purpose Limitation: Data is shared only for stated, lawful reasons
  • Minimal Disclosure: Only data necessary for the specific task is disclosed
  • Confidentiality & Security: Mandatory contractual safeguards are enforced
  • Compliance Assurance: Vendors must meet DPDP Act and RBI standards
  • Audit Trail: Every disclosure is logged and reviewed by the Data Protection Officer (DPO)

5.4. Vendor Due Diligence and Future Partners

Each vendor is screened for certifications (ISO 27001, SOC 2, PCI DSS), localization compliance, and past security record. All future or replacement providers—known or unknown—will meet equivalent protection standards, and material additions will be disclosed through policy updates.

5.5. Prohibited and Aggregate Sharing

Paymorz™ never:

  • Shares data with advertisers or unrelated businesses
  • Cross-links freelancer and client data without consent

We may share only aggregated or anonymized statistics (e.g., usage or performance trends) that cannot identify individuals.

6. Data Security and Protection Measures

6.1. Our Security Commitment

At Paymorz™, protecting your personal and financial data is fundamental to our operations. We apply multi-layered administrative, technical, and organizational safeguards to preserve confidentiality, integrity, and availability throughout the data lifecycle.

Our security framework aligns with:

  • Digital Personal Data Protection Act, 2023 (DPDP Act) - Section 8(5)
  • Information Technology Rules, 2011 (IT Rules) - Rule 8
  • Reserve Bank of India (RBI) Master Directions (2020)
  • ISO/IEC 27001:2022, ISO/IEC 27701:2019, and NIST Cybersecurity Framework

6.2. Core Security Principles

  • Confidentiality: Data access is restricted to authorized personnel using role-based access controls
  • Integrity: Information is protected against unauthorized alteration or loss
  • Availability: Systems are redundant and fault-tolerant for continuous operation
  • Accountability: All data access and activity are logged and monitored
  • Proportionality: Controls are scaled to data sensitivity and operational risk

6.3. Technical Safeguards

  • Encryption: All personal and financial data is encrypted in transit (TLS 1.3+) and at rest (AES-256)
  • Tokenization: Sensitive identifiers (bank, UPI, card tokens) are masked; payment data is processed only by PCI DSS–certified partners
  • Network Protection: Firewalls, Intrusion Detection Systems (IDS)/Intrusion Prevention Systems (IPS), and Distributed Denial of Service (DDoS) protection secure network traffic
  • Access Control: Multi-factor authentication (MFA) and least-privilege access are enforced
  • Secure Development: OWASP Top 10 principles, code reviews, and quarterly Vulnerability Assessment and Penetration Testing (VAPT) by certified firms
  • Data Segmentation: Vendor, enterprise client, and admin data are stored in separate logical environments

6.4. Organizational and Administrative Controls

  • Data Protection Officer (DPO): Oversees DPDP Act and IT Rules compliance
  • Employee Training: Annual mandatory programs on data security, phishing prevention, and incident response
  • NDAs and Screening: All personnel and vendors sign Non-Disclosure Agreements (NDAs) and undergo background checks before access
  • Vendor Audits: Annual reviews of all third-party vendors for compliance and data security standards

6.5. Infrastructure and Physical Security

  • Data Hosting: Data is hosted in Tier IV facilities (Google Cloud, AWS, Supabase, or equivalents)
  • Physical Controls: Data centers use biometric access, 24×7 surveillance, and environmental controls
  • Resilience: Redundant data centers and encrypted backups ensure resilience and disaster recovery capabilities

6.6. Incident Detection and Response

Paymorz™ maintains a 24×7 Incident Response Framework (IRF) to detect, assess, and resolve security incidents:

  • Detection: Real-time monitoring for anomalies or unauthorized access
  • Containment: Compromised systems are isolated, credentials revoked, and forensic review initiated
  • Notification: Affected users and regulators (Data Protection Board (DPB), Reserve Bank of India (RBI)) are informed within 72 hours, as required under DPDP Act Section 8(9)
  • Review: Every incident triggers a root-cause analysis and system improvement plan approved by the DPO/Chief Information Security Officer (CISO)

6.7. User Responsibilities

Users share responsibility for securing their accounts. We recommend:

  • Using strong, unique passwords
  • Enabling two-factor authentication (2FA)
  • Avoiding credential sharing
  • Logging out after use
  • Reporting suspicious activity to security@paymorz.com

Negligence in account hygiene may limit Paymorz™'s ability to prevent misuse.

6.8. Data Integrity and Accuracy

Automated validation and audit logs ensure information remains accurate and up to date, in compliance with DPDP Act Section 9(1).

6.9. Audits and Certifications

Security measures are independently reviewed through:

  • ISO 27001 audits (annual)
  • PCI DSS verification (payment gateways)
  • SOC 2 Type II reports (cloud partners)
  • RBI-mandated system audits

All findings are reviewed and tracked by the DPO and Executive Security Committee.

6.10. Continuous Improvement

We maintain a proactive cybersecurity culture through:

  • Regular vulnerability testing and code reviews
  • Updates to cryptographic standards and dependencies
  • Participation in Indian Computer Emergency Response Team (CERT-In) programs
  • An internal bug bounty and responsible disclosure system

7. Your Rights as a Data Principal

7.1. Overview

As a user ("Data Principal") under the Digital Personal Data Protection Act, 2023 (DPDP Act), you have specific rights regarding your personal data. Paymorz™ ensures full transparency and compliance with:

  • DPDP Act, Sections 11–13
  • Information Technology Rules, 2011 (Rule 5(7))

You can exercise your rights at any time by writing to support@paymorz.com or contacting our Grievance Officer (see Section 12).

7.2. Your Rights

7.2.1. Right to Access

What You Can Request:

  • What data we hold about you
  • Why and how we use it
  • Who it has been shared with

Response Time: We will respond within 15 business days. Certain information (e.g., trade secrets or other users' data) may be redacted for security reasons.

Legal Reference: DPDP Act Section 11(2)(b).

7.2.2. Right to Correction / Update

What You Can Request: Correction or completion of inaccurate information at any time via your account settings or written request.

Response Time: Verified corrections are completed within 7 working days.

Legal Reference: DPDP Act Section 12(1)(b).

7.2.3. Right to Erasure ("Right to be Forgotten")

When You Can Request: Deletion or anonymization of data if:

  • It's no longer needed
  • You withdraw consent
  • Processing was unlawful

Response Time: Deletion occurs within 30 days, unless retention is required by Reserve Bank of India (RBI), Financial Intelligence Unit - India (FIU-IND), or tax laws, in which case data will be restricted, not erased.

Legal Reference: DPDP Act Section 12(1)(c).

7.2.4. Right to Withdraw Consent

Application: For optional data uses (e.g., marketing or analytics), you can withdraw consent at any time via:

Effect: Withdrawal takes effect within 10 business days and does not affect processing completed before withdrawal.

Legal Reference: DPDP Act Section 6(4).

7.2.5. Right to Data Portability

What You Can Request: A copy of your personal data in a structured, machine-readable format (e.g., CSV, JSON) to transfer elsewhere.

Response Time: Fulfilled within 20 business days, subject to legal and technical feasibility.

Legal Reference: DPDP Act Section 12(1)(e).

7.2.6. Right to Restrict or Object to Processing

When You Can Request: Restrict or object to processing when:

  • Accuracy is contested
  • Processing lacks a valid basis
  • It involves unauthorized marketing

Effect: Processing will be paused (except storage) until resolved.

Legal Reference: DPDP Act Section 12(1)(d).

7.2.7. Right to Nominate a Representative

What You Can Request: Nominate someone to exercise your rights if you pass away or become incapacitated.

Process: Submit a notarized authorization via support@paymorz.com. Verified requests are processed within 30 days.

Legal Reference: DPDP Act Section 13.

7.2.8. Right to Grievance Redressal

Process: Complaints to our Grievance Officer are:

  • Acknowledged within 24 hours
  • Resolved within 15 working days (extendable for legitimate reasons)

Escalation: If unresolved, you may escalate to the Data Protection Board of India (DPB).

Legal Reference: DPDP Act Section 12(2).

7.3. Verification of Requests

To protect your privacy, we may verify your identity before fulfilling a rights request. We will only ask for information necessary for verification and delete it once verification is complete. Excessive or repetitive requests may be refused or incur a nominal administrative fee.

7.4. Response Timelines

The response timelines for various requests are as follows:

  • Access Request: We will respond within 15 working days
  • Correction Request: We will respond within 7 working days
  • Deletion Request: We will respond within 30 working days
  • Consent Withdrawal: We will process within 10 working days
  • Portability Request: We will fulfill within 20 working days
  • Grievance Resolution: We will resolve within 15 working days
  • Nominee Registration: We will process within 30 working days

All timelines comply with the DPDP Act and Paymorz™'s internal service standards.

7.5. Exemptions

Certain rights may be limited when processing is necessary for:

  • Compliance with law or court orders
  • Performance of a contract
  • Fraud prevention or investigations
  • Legal claims or defenses

In such cases, users will be informed of the lawful grounds for exemption.

8. Children's Data and Age Restrictions

8.1. Overview

Paymorz™ is a professional services and vendor management platform intended exclusively for individuals aged 18 years and above. We do not knowingly collect, store, or process personal data from children or minors below this age threshold.

This restriction ensures compliance with:

  • Section 9(3) of the Digital Personal Data Protection Act, 2023 (DPDP Act), which prohibits processing of children's personal data without verifiable parental consent
  • Rule 4(1) of the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011

8.2. Age of Eligibility

To register and use the Paymorz™ Platform, users must:

  • Be at least 18 years old, or
  • Be using the Platform under the active supervision and verifiable consent of a parent or legal guardian (where applicable, e.g., for training or educational partnerships)

By accessing or registering on the Platform, you confirm that you meet the applicable age and legal capacity requirements.

8.3. Parental or Guardian Consent (If Applicable)

If Paymorz™ becomes aware that a user under 18 years has registered or transacted on the Platform, we will:

  • Suspend the account temporarily
  • Request verifiable parental or guardian consent through documented proof (such as government ID verification or signed authorization)
  • Restore access only upon receipt of such consent, if permitted by applicable law

Where consent is not obtained within 15 working days, the account and all related data will be permanently deleted in accordance with our data retention policies.

8.4. Data Processing of Minors (Restricted)

If a minor's data is lawfully processed (e.g., through guardian consent), it will be limited to:

  • Identity verification for parental oversight
  • Communication strictly necessary for account setup or educational collaboration
  • Basic account management with no access to financial or payment functions

Paymorz™ does not process sensitive personal data, financial information, or behavioral analytics of minors, even with consent.

8.5. Prohibited Activities for Minors

Paymorz™ is intended exclusively for use by registered businesses, authorized signatories, and adult representatives (aged 18 or above). Individuals below 18 years of age are not permitted to:

  • Register vendor or business accounts
  • Submit or process invoices
  • Access or manage payment or settlement information
  • Provide KYC or compliance documentation

Any account found to be operated by a minor may be suspended or terminated in accordance with the Terms of Service.

8.6. Detection and Remediation Mechanisms

To ensure compliance and prevent unauthorized use by minors, Paymorz™ employs:

  • Age confirmation during account creation
  • AI-assisted identity checks and document validation for KYC
  • System audits to flag discrepancies between declared age and verified documents
  • Manual review by the compliance team where anomalies are detected

These safeguards are designed to maintain platform integrity and minimize the risk of underage participation.

8.7. Responsibility of Parents and Guardians

Parents and guardians are encouraged to:

  • Supervise minors' online activities
  • Educate them about safe data sharing practices
  • Contact Paymorz™ immediately at grievance@paymorz.com if they believe a minor has accessed or provided personal information without consent

Paymorz™ will take prompt action to verify and delete such data as required by DPDP Act Section 9(4).

8.8. International Users and Local Age Requirements

For users in jurisdictions where the legal age of consent differs, Paymorz™ will apply the stricter applicable age threshold. Where parental consent is required under foreign law, Paymorz™ will seek documentation consistent with the relevant jurisdiction's standards before account activation.

8.9. Deletion of Unauthorized Child Data

If we discover that we have inadvertently collected personal data from a child without proper consent, we will:

  • Delete the data from all systems within 7 working days of confirmation
  • Notify the parent or guardian of the deletion
  • Document the incident in our Data Breach and Compliance Register for audit traceability

8.10. Contact for Child Data Concerns

If you believe that a minor's data has been improperly collected or used, please contact:

9. Data Storage and Localization

9.1. Overview

Paymorz™ processes and stores all user data—including financial, KYC, and transactional information—within servers located in India, in accordance with the Reserve Bank of India (RBI) Payment Aggregator and Payment Gateway Guidelines (2020) and Section 16 of the DPDP Act, 2023.

No cross-border transfers of personal or financial data are made unless required for technical hosting or performance monitoring through approved cloud infrastructure (e.g., Google Cloud, AWS, or Supabase). Any such limited transfers are subject to contractual safeguards ensuring compliance with Indian data protection standards.

9.2. Data Localization Commitment

In line with Reserve Bank of India's (RBI) Payment Aggregator/Payment Gateway (PA/PG) Guidelines (2020):

  • All payment transaction data (including customer and credential details) is stored exclusively in India
  • Backups are also maintained in India and accessible only to authorized personnel
  • Any data processed overseas (e.g., fraud analysis) is returned and deleted within RBI-prescribed timelines

This ensures full regulatory compliance and audit access under Indian jurisdiction.

9.3. Transfers of Non-Financial Data

Limited non-financial data (e.g., usage logs, analytics, communication) may be transferred to or accessed by partners such as:

  • Google Cloud, Supabase, AWS (hosting and authentication)
  • Mixpanel (analytics)
  • SendGrid, Twilio (notifications)

Such transfers are made only to:

  • Countries approved by the Government of India as providing adequate protection, or
  • Vendors bound by Data Processing Agreements (DPAs) ensuring equivalent safeguards

9.4. Safeguards for International Transfers

Paymorz™ ensures all transfers meet the following protections:

  • Adequacy or Approved Jurisdictions: Transfers only to countries with recognized data protection frameworks
  • Contractual Protections: Data Transfer Agreements (DTAs) or Standard Contractual Clauses (SCCs) mandating confidentiality, breach reporting, and audit rights
  • Encryption: All cross-border data is encrypted (TLS 1.3 in transit, AES-256 at rest)
  • Transfer Impact Assessments (TIAs): Conducted before new transfers to evaluate risk and legal adequacy

9.5. Exceptions Permitting Transfer

International transfers may occur when:

  • Explicit user consent is obtained
  • Required to perform a contract (e.g., cross-border payment)
  • Legally mandated by court or regulator
  • Necessary for public interest or legal defense

All such transfers are logged, reviewed, and overseen by the Data Protection Officer (DPO).

9.6. Retention and Deletion by Foreign Processors

When data is processed abroad:

  • Processors must delete or return all data after completion
  • Paymorz™ retains full control of deletion, retention, and modification rights
  • Processors cannot reuse or retain data beyond authorized purposes

This upholds the storage limitation principle.

9.7. Oversight and Accountability

  • All international transfers are recorded in a Data Transfer Register maintained by the DPO
  • Foreign processors undergo periodic audits and re-certifications
  • Any breach or non-compliance is reported to the Data Protection Board of India (DPB) under Section 8(9) of the DPDP Act

9.8. User Rights and Requests

Your rights (access, correction, deletion, objection, portability) remain fully enforceable even if data is processed abroad. You may request:

  • Confirmation of international transfers
  • Details of countries and safeguards applied
  • Objection to such transfers, if rights are compromised

Responses will be provided within 15 working days via support@paymorz.com.

9.9. Affiliates and Future Partnerships

If Paymorz™ expands globally or integrates with new international partners:

  • A Data Protection Impact Assessment (DPIA) will precede any new transfer
  • Updated Data Processing Agreements (DPAs) will govern all exchanges
  • Material updates will be disclosed under Section 13 (Policy Updates)

9.10. Breach Management for International Transfers

If a breach occurs involving international data:

  • The foreign processor must notify Paymorz™ immediately
  • Paymorz™ will contain and report the incident within 72 hours, per Section 6 (Data Security and Protection Measures)
  • Affected users and regulators will be informed with full remediation details

10. Data Accuracy, Integrity, and Accountability

10.1. Overview

Paymorz™ ensures that all personal and transactional data remains accurate, complete, and reliable for its intended purpose. This obligation is grounded in:

  • Section 9(1) of the DPDP Act, 2023
  • Rule 5(6) of the Information Technology Rules, 2011

Accuracy and integrity are treated as both a legal and ethical responsibility, essential for secure and transparent service delivery.

10.2. Principles of Data Accuracy

We follow clear accuracy standards:

  • Verification at Collection: Information is validated through secure forms, KYC checks, or automated validation tools
  • User Review & Updates: Users may review and update their information at any time (see Section 7 – Your Rights as a Data Principal)
  • Error Correction: Detected inaccuracies are corrected promptly and logged for audit
  • Automated Checks: Systems detect duplicates or inconsistencies and trigger correction workflows

10.3. User Responsibilities

Users must ensure all submitted information is:

  • True and current
  • Updated promptly when changes occur
  • Authorized, particularly for business or entity data

Providing false or outdated data may result in restricted access, transaction suspension, or account termination under our Terms of Service.

10.4. Internal Integrity Mechanisms

Paymorz™ maintains technical and procedural controls to protect data integrity:

  • Validation Controls: Automated field checks (email, IFSC, GSTIN, PAN)
  • Quarterly Data Audits: Identify and rectify outdated or inconsistent records
  • Reconciliation Mechanisms: Match KYC and transaction data with payment gateways
  • Change Tracking: Every edit or deletion is timestamped and auditable

10.5. Third-Party Data Quality

Partner agreements require:

  • Data validation and synchronization across systems
  • Prompt correction of detected mismatches
  • Maintenance of real-time consistency through secure APIs or data-sharing protocols

All vendors operate under Data Processing Agreements (DPAs) with built-in accuracy and reporting obligations.

10.6. Integrity and Security Synchronization

To ensure reliability:

  • Sensitive data uses cryptographic hash validation and immutable audit logs
  • Integrity verification is built into backup and recovery processes
  • Any data corruption triggers an automatic alert and remediation under Section 6 (Data Security and Protection Measures)

10.7. Accountability Framework

Paymorz™ maintains a structured governance system that includes:

  • A Data Protection Officer (DPO) responsible for oversight
  • An Internal Controls Register and audit trails of all data events
  • Quarterly compliance reports retained for eight years
  • Mandatory employee and vendor confidentiality commitments

10.8. Automated Systems and Human Oversight

For automated processing (e.g., analytics or fraud detection):

  • Datasets are cleaned and validated
  • Algorithmic bias is regularly reviewed
  • Results are verified by human reviewers before deployment

This ensures accuracy without unintended distortions.

10.9. Correction Workflow

When a mismatch or correction request is identified:

  • The record is flagged for review, verified, and corrected within 7 working days
  • Supporting documents may be required
  • Both old and new data remain in the system for 90 days for traceability

10.10. Backups, Archives, and Continuous Improvement

  • Backups are synchronized with live databases; outdated data is purged during maintenance
  • Archived data retained for regulatory reasons is read-only and tamper-evident
  • Annual data governance audits and AI-based anomaly detection help improve accuracy and staff awareness

11. Cookies, SDKs & Tracking

Paymorz™ and its service partners use cookies, SDKs, pixels, and similar tracking technologies to provide core functionality (login, payments, security), measure and improve performance, detect fraud, and—with your consent—deliver analytics and marketing.

Essential cookies required for authentication and payment cannot be disabled. For details on cookie categories, vendors, retention periods, and how to manage or withdraw consent, see our Cookie Policy and Cookie Preferences center.

We honor browser Do-Not-Track (DNT) and Global Privacy Control (GPC) signals for non-essential cookies where technically feasible.

12. Grievance Redressal, Contact & DPO

12.1. Overview

Paymorz™ maintains a transparent and time-bound grievance redressal system to address privacy and data-protection concerns in accordance with:

  • Digital Personal Data Protection Act, 2023 (DPDP Act)
  • Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011
  • Reserve Bank of India (RBI) Master Directions for Payment Aggregators and Gateways (2020)

We are committed to resolving all user complaints promptly, fairly, and lawfully.

12.2. Data Protection Officer (DPO) & Grievance Officer

Data Protection Officer: The Data Protection Officer can be contacted at support@paymorz.com. The DPO will acknowledge your request within 24 hours and provide a response within 15 working days. The DPO oversees overall compliance, internal audits, and engagement with regulators.

Grievance Officer: The Grievance Officer can be contacted at grievance@paymorz.com. The Grievance Officer will acknowledge your complaint within 24 hours and work towards resolution within 15 working days. The Grievance Officer is the first point of contact for all user complaints related to data protection, misuse, or unauthorized disclosure.

12.3. How to File a Complaint

You may raise a concern by:

QUANTUMCONA LLP Survey No. 130P & 115/1P, WeWork Rajapushpa, Nanakramguda Main Road, Medchal Malkajgiri, Telangana 500032, India

Please include:

  • Your full name and contact details
  • A clear description of the issue
  • Supporting documents (if any)

12.4. Grievance Handling Process

Our grievance handling process follows these stages:

Stage 1 - Acknowledge receipt: We will acknowledge your complaint within 24 hours of receipt.

Stage 2 - Internal investigation: We will conduct an internal investigation within 3 working days.

Stage 3 - Request for additional info / findings: We will request any additional information or share our findings within 7 working days.

Stage 4 - Final resolution / corrective action: We will provide final resolution or take corrective action within 15 working days.

Stage 5 - Closure confirmation: The entire process will be completed within 20 working days total.

If a complaint is complex or depends on third-party inputs, we'll inform you of any extended timeline.

12.5. Escalation

If unresolved or unsatisfactory:

  • Email the DPO at support@paymorz.com, quoting your case reference
  • If still unresolved, you may approach the Data Protection Board of India (DPB) under Section 11(2) of the DPDP Act
  • International users may also contact their local data-protection authority (e.g., European Data Protection Board (EDPB) or Information Commissioner's Office (ICO))

12.6. Scope of Grievances

You may raise concerns about:

  • Unauthorized access or misuse of data
  • Inaccurate or outdated records
  • Delays or denials in exercising rights
  • Breach or data-security incidents
  • Cookie or consent-management violations
  • Financial-data handling and retention issues

Operational or general service queries may be redirected to customer support.

12.7. Oversight & Record-Keeping

  • All complaints are logged in a Grievance Management Register maintained by the DPO
  • Each entry records timestamps, assigned personnel, and closure details
  • Records are retained for 8 years for audit and regulatory review
  • Periodic audits ensure compliance with response timelines and effectiveness

12.8. Protection Against Retaliation

Users who exercise their privacy rights or raise grievances in good faith are protected from any form of retaliation or discrimination. All complaints are handled confidentially and impartially.

12.9. Integration with Related Policies

This mechanism complements:

  • Section 7 – Your Rights as a Data Principal
  • Section 6 – Data Security and Protection Measures
  • Terms of Service – Dispute Resolution
  • Cancellation & Refund Policy

Together, these ensure a unified, transparent framework for user protection and accountability.

13. Policy Updates and User Notifications

13.1. Overview

Paymorz™ keeps this Privacy Policy current with applicable laws, technologies, and operations. We may update it from time to time in line with:

  • DPDP Act, 2023 – Sections 10 & 11
  • Information Technology Rules, 2011 – Rule 5(10)

No change will ever reduce the level of protection afforded to your personal data.

13.2. Review & Update Frequency

This Policy is reviewed at least annually or sooner if:

  • New laws, RBI/DPDP Board directions, or audit findings require updates
  • We introduce new data categories, vendors, or technologies
  • Grievance or contact details change

All revisions are approved by the Data Protection Officer (DPO) before publication.

13.3. Nature of Amendments

Revisions may cover:

  • Updated data-collection categories or legal bases
  • Added/replaced processors or partners
  • Modified retention periods or security controls
  • Language or structure improvements for clarity

13.4. How We Notify Users

When we make significant updates, we will inform you through one or more of the following:

  • A revised Policy posted on the Platform with a new Effective Date
  • An in-app banner or pop-up on login
  • Email or push notification for material changes
  • A note in our enterprise compliance bulletin

Users are encouraged to check this page periodically.

13.5. Version Control

Version v1.0: Effective from March 2025, reviewed by QUANTUMCONA LLP. This was the initial release of the Privacy Policy.

Version v2.0: Effective from August 2025, reviewed by Data Protection Officer. This is the current update of the Privacy Policy.

Archived versions are retained for 8 years for audit reference.

13.6. Consent to Revised Policy

By continuing to use the Platform after an updated Policy takes effect, you confirm that you have read and agree to the new terms. If any update materially alters your rights or our obligations, renewed consent will be sought as required under DPDP Act Section 6(1). You may withdraw consent or deactivate your account under Section 7 – Your Rights as a Data Principal.

13.7. Feedback & Contact

We welcome feedback or clarification requests at support@paymorz.com. Enterprise clients may also participate in periodic compliance consultations. Your input helps us strengthen data-governance standards.

13.8. Relationship to Other Documents

This Policy should be read with:

  • Terms of Service – account and platform conditions
  • Cancellation & Refund Policy – payment disputes
  • Vendor/Partner Agreements – B2B relations
  • Cookie & SDK Policy – consent and tracking

If inconsistencies arise, the provision offering greater user protection prevails.

13.9. Final Acknowledgment

By using Paymorz™, you acknowledge that you have reviewed and accepted the current version of this Privacy Policy and understand the rights, responsibilities, and protections described herein.