Legal

Privacy Policy

How personal data is handled across Dropify Checkout, merchant services and our website.

Last updated: 3 October 2026

This version applies from its publication on the Dropify Checkout website.

Business: Dropify Plaza, provider of Dropify Checkout.

Owner/operator: Aayush Garg

Business address: 904/34, Vijay Nagar, Barak Gali No. 2, Rohtak, Haryana 124001, India

Complaints telephone: +91 9315620335

Website: checkout.dropifyplaza.com

Privacy contact: checkout@dropifyplaza.com

1. Purpose and scope

This Privacy Policy explains how Dropify Plaza ("Dropify", "we", "us" or "our") collects, uses, discloses, retains and protects personal data in connection with Dropify Checkout, our website, merchant onboarding, account administration and support. Personal data means information about an identifiable individual.

Dropify Checkout provides checkout technology for participating online stores. Features may include mobile verification, eligible saved addresses, merchant-configured offers, cash on delivery (COD), Partial COD advances, online payments and order information exchange with Shopify. The features available in a particular checkout depend on the merchant's configuration and connected services.

Our Services are offered to merchants in India. This policy applies to website visitors, merchant representatives and shoppers whose information we process in connection with those Services. It does not replace the merchant's own privacy notice, sales terms, or the notices of payment gateways and other independent providers. Please read the notices shown by the store and by the provider handling your payment.

This policy is a transparency notice. Merely reading it or visiting our website does not amount to consent for every processing activity described here. Where consent is required, it must be obtained through the relevant choice or permission request.

2. Our role and the merchant's role

A "merchant" is the business selling products or services through a store using Dropify Checkout. A "shopper" is an individual interacting with that checkout. For order handling and checkout activities carried out on a merchant's instructions, the merchant generally determines why customer data is used and Dropify processes that data to provide the agreed service.

We determine the purposes of processing for our own business enquiries, merchant relationships, billing, platform administration, security and applicable legal obligations. A shopper-facing saved-address feature is governed by the notice and choices applicable to that feature. Where Dropify independently determines the purposes of that processing, it is responsible for the corresponding obligations; a merchant's installation of Dropify does not itself provide permission on behalf of every shopper.

A merchant does not receive a shopper's saved addresses merely because it uses Dropify. When the shopper places an order with that merchant, the relevant delivery details are shared to complete and support that order, as explained in Section 7.

When a merchant controls the information covered by your request, we may refer the request to that merchant or assist them with it. We remain responsible for processing that we independently control and for our obligations as a service provider.

3. Information we process

We limit processing to information relevant to enabled features and the purposes explained below. Not every category is collected in every interaction.

Do not send us card security codes, UPI PINs, internet-banking passwords, one-time passwords or unnecessary identity documents in emails or support messages. If an investigation requires proof of identity, we will seek information proportionate to the request rather than unrestricted access to your accounts.

Merchant identity and business verification

During paid merchant onboarding, we collect a masked Aadhaar copy and PAN document, along with the business and contact information you provide. GST information is optional in this onboarding flow. These documents are used to assess the application, verify the business relationship, resolve verification issues and maintain relevant review records. They are not shopper checkout requirements and are not used for unrelated advertising.

Upload documents only through the signed-in onboarding form and submit a masked Aadhaar copy. Do not send unmasked identity documents, passwords or OTPs through email or support messages. The document upload flow requests your authorization for review. Our review is a business onboarding assessment, not a claim of government Aadhaar authentication.

Uploaded documents are encrypted and stored in private Cloudflare object storage. Access is restricted to authorized platform reviewers through authenticated controls. They are not made available to other merchants or shoppers. Necessary infrastructure processing and any legally required disclosure remain subject to Sections 11–14. For access, correction or deletion requests, contact checkout@dropifyplaza.com with the subject “Privacy request”; do not attach identity documents unless securely requested.

4. Sources of information

Information may come directly from you, from the store where you are shopping, from an authorised merchant account user, from Shopify integrations, from the selected payment gateway, and from technical events generated while the service operates. Verification providers may return delivery and verification results needed to complete an OTP flow.

Where an authorised merchant connects existing customer or order records, the import must be limited to the agreed purpose and necessary fields. The merchant must have authority to provide those records. An import does not automatically authorise advertising use, creation of a cross-store customer profile, or disclosure of that merchant's customer list to other stores.

If you provide another person's delivery details, you should have an appropriate reason and authority to provide them. Use accurate information and avoid including sensitive personal details in address labels or free-text fields.

We use relevant information to provide requested checkout functionality, verify mobile access, display delivery details, apply merchant rules, communicate with integrated systems, record payment outcomes, investigate technical issues, support merchants and shoppers, and protect against misuse. We also use tracking and analytics to understand use of our website and checkout, assess performance and identify areas for improvement. We process business contact and account data to manage our relationship with merchants and comply with obligations that apply to us.

The legal ground depends on the activity, our role, and the law applicable at that time. This may involve consent where required, processing necessary for a requested transaction where permitted, an applicable legal obligation, or another ground specifically available under the relevant law. We do not treat a broad reference to business interests as permission to override consent requirements.

Required fields will be identified in the relevant flow. Without information necessary for verification, payment or delivery, the requested feature or checkout may not be available. Any permission required for a merchant’s optional marketing, and any optional reuse of a saved profile, are separate from providing information necessary for the current purchase. Permission for one purpose does not automatically authorise an unrelated purpose.

If we propose a materially different use that needs new permission, we will provide an appropriate notice and obtain that permission before beginning the new use.

6. Mobile verification and transactional messages

Where enabled, we use a mobile number to initiate and validate a one-time password or another supported verification process. Related attempt records and technical signals may be used to prevent abuse and troubleshoot delivery failures.

Successful OTP verification indicates access to the mobile number at that time. It is not a guarantee of legal identity, age, creditworthiness, delivery acceptance or the correctness of an address. A recycled, shared or compromised number can create risks, so appropriate access controls remain necessary.

Verification messages and essential checkout or support communications are operational messages. Permission to receive an OTP is not permission for unrelated promotions. Report suspected unauthorised access to the contact in Section 19; do not forward the OTP itself.

7. Saved addresses and returning-customer recognition

Dropify Checkout supports saved delivery addresses to reduce repeated entry during checkout. After the required verification, a shopper may review an eligible saved address and choose the details for the current purchase. The shopper can edit or delete their saved addresses using the controls provided in Dropify Checkout. If a control does not work as expected, contact checkout@dropifyplaza.com for assistance.

Saved addresses are not made available to another merchant merely because that merchant uses Dropify Checkout. The shopper's selection and use of a saved address in their own checkout flow does not grant the merchant general access to the shopper's saved profile. Relevant delivery details are shared with the merchant when the shopper places an order with that merchant, for the purpose of processing, fulfilling and supporting that order.

An order does not give a merchant access to unrelated saved addresses, another store's customer database or the shopper's purchase history at other stores. Any separate disclosure needed for payment, verification or another enabled checkout function is limited to that function and must follow the relevant notice and permission requirements.

The shopper should check the recipient name, address and contact details before submitting each order. Mobile verification does not guarantee that a stored address is current or that the holder of a recycled or shared number is entitled to every previously linked detail.

Deleting or changing a saved address affects the reusable address record; it does not necessarily change a delivery address already submitted with an order or delete a completed-order record that must be retained for a lawful purpose. Contact the selling merchant promptly to request changes to an order already placed. For other correction, erasure or permission-withdrawal requests, use the process in Section 15.

8. Payment processing and Partial COD

Payments are handled through the payment provider selected and configured by the merchant. Supported integrations include Razorpay, Paytm, PhonePe, Cashfree, PayU and Easebuzz, subject to availability and merchant eligibility. A list of supported integrations does not mean that all of them receive your information for every order.

The selected payment provider processes the payment and settles it directly to the merchant’s designated account under its provider agreement. Dropify does not receive or hold shopper payment funds on the merchant’s behalf. Dropify uses payment references, amounts and status information to connect a payment to a checkout and support order reconciliation. Enter card, UPI or banking credentials only in the payment interface provided for that transaction. The selected payment provider’s privacy and security terms explain its processing of those credentials. Dropify support does not need your card security code, UPI PIN, banking password or OTP to investigate a payment reference.

For Partial COD, the checkout may display an advance collected online and a remaining balance payable on delivery. Relevant split amounts and transaction references are shared with the merchant and selected provider as needed. The merchant and provider may retain their own payment and refund records under their separate obligations.

For Dropify's own merchant plan payments, Razorpay processes the payment. Dropify receives the payment and order references, amount, currency, status and relevant refund information to reconcile your plan, review activation and handle billing support. These records are separate from your shoppers' store payments. Raw card details and payment authentication secrets are not required in Dropify's onboarding form.

9. Tracking, cookies, local storage and similar technologies

We use tracking and analytics in connection with our website and checkout. Depending on the tools and features in use, this may involve information about visits, pages or checkout steps used, interactions, device or browser details and related session or event identifiers. We use this information to understand service use, assess checkout performance and identify areas for improvement. Tracking and analytics are distinct from sending promotional messages.

The website or checkout may also use cookies, browser storage or comparable identifiers for sessions, security, preferences and continuity between checkout steps. Third-party payment components and merchant-configured tools may use their own technologies, subject to their respective purposes, notices and responsibilities.

Where applicable law requires notice, consent or a choice for non-essential tracking, the relevant processing is subject to those requirements. An analytics or advertising identifier does not become essential merely because it is useful to a business. Our use of analytics does not itself provide permission for unrelated advertising, retargeting or sharing information with advertising audiences; any such use requires the applicable disclosures and authority.

You can manage stored cookies through your browser settings and use any preference controls presented in the relevant flow. Blocking necessary storage may prevent part of a checkout from working. Browser cookie controls do not necessarily stop every form of tracking or remove information already held on a server, and deleting browser storage does not itself delete a saved profile or a completed order record.

For information about a tracking tool, cookie, provider or related choice, contact checkout@dropifyplaza.com with the website or checkout URL and, where possible, the name of the item. Requests to withdraw permission or erase information are handled as explained in Section 15.

10. Communications and merchant marketing

Dropify does not send its own promotional SMS, WhatsApp messages or marketing emails to shoppers. Tracking and analytics use does not mean that a shopper has subscribed to promotional messages from Dropify.

We may send or facilitate operational communications needed for mobile verification, the requested checkout, account administration, service changes, security, billing or support. These communications are separate from advertising. Receiving an OTP or using Dropify Checkout does not by itself grant permission for unrelated promotions.

The merchant or brand from which you shop may send its own marketing messages under its own privacy notice, communication preferences and applicable permission requirements. The merchant is responsible for its promotional content and for any required consent, sender identification and unsubscribe or opt-out process. Placing an order does not provide blanket consent for every promotional use of your information.

To stop a merchant’s promotional messages, use the unsubscribe or opt-out method it provides or contact that merchant directly. A request to Dropify does not automatically change a merchant’s separate communication preferences. If a message appears to have been sent by Dropify, or you need help identifying our involvement, contact checkout@dropifyplaza.com with the sender details and a description of the message; do not include an OTP or payment secret.

An operational disclosure to a merchant, payment provider or other service provider does not grant permission for unrelated advertising or other secondary use. Applicable privacy requests concerning our processing remain available under Section 15.

11. When information is shared

We may disclose relevant information to the merchant involved in your checkout; to Shopify or another authorised commerce integration; and to the chosen payment or verification provider when needed for that feature. We use Cloudflare for hosting. In that role, Cloudflare may process relevant network, request and technical information needed to deliver and protect the hosted service. We may also use contracted infrastructure, analytics, security, communications and support providers to operate the service. Naming Cloudflare does not mean that every backend, database or messaging function is provided by Cloudflare; processing locations are addressed in Section 12.

When we engage service providers to process personal data on our behalf, we require processing to be limited to the agreed purpose and subject to appropriate confidentiality, security and processing obligations. Some recipients, including merchants and payment providers, may independently determine certain uses and have their own legal responsibilities.

We may disclose information where necessary to meet a binding legal requirement, respond to a valid request, protect rights or safety, or investigate misuse. We assess such requests for lawful authority and scope before making the relevant disclosure, subject to applicable law. In a proposed merger, acquisition or business transfer, necessary information may be shared subject to appropriate safeguards and notice where required.

You may request information about the recipients or service-provider categories relevant to your data through our privacy contact. We will provide the information required by applicable law, taking account of the particular service, our role and lawful confidentiality or security restrictions.

12. Processing locations and international transfers

Information may be processed where our authorised providers and personnel operate. The locations must reflect the actual infrastructure and support arrangements, not just the location of a merchant or the website domain.

You may contact us for information about the processing locations relevant to your interaction. We will assess the specific service and providers involved when responding. The use of an Indian domain, mobile number or merchant does not by itself mean that every processing operation takes place in India.

Where a transfer is subject to legal restrictions, we will apply the arrangements required by the law in force, including contractual safeguards or restrictions on particular destinations where applicable. We do not represent that all information stays in India unless the verified architecture and all relevant providers support that commitment.

13. Retention and deletion

We retain personal data only for as long as it is needed for the purpose for which it was collected, or for a further period justified by applicable recordkeeping requirements, dispute handling, security or the establishment and defence of legal claims. The duration depends on the record category, our role and any applicable legal requirement.

Ending a merchant's use of Dropify does not automatically erase every record associated with that relationship. Certain records may remain after termination, but a continuing purpose or applicable legal obligation must justify the particular information retained. We do not treat merchant departure, an unspecified future use or a general promise not to misuse data as an unlimited retention right.

Where genuinely relevant to an existing transaction, obligation or issue, post-termination retention may be needed to reconcile payments or service invoices; assist with an outstanding refund, chargeback or customer complaint; investigate a specific security incident or misuse; comply with required records or a lawful request; or establish, exercise or defend a legal claim. Each reason applies only to the records needed for that purpose. For example, retaining an invoice does not automatically justify keeping every shopper's full address book.

An independently maintained shopper profile may continue only while its disclosed purpose, applicable permission and other lawful conditions remain valid, and is subject to the shopper's available deletion and correction choices. Ending one merchant relationship does not by itself authorise reuse for unrelated marketing or disclosure to another merchant.

The following criteria explain how retention is determined. Where the law prescribes a particular minimum or maximum period, that requirement takes precedence over a general operational criterion.

There is no single retention period for every category of data. A particular record must not be kept indefinitely without a continuing lawful basis. You may ask us for the retention criteria applicable to a particular record or request its deletion. We will explain any specific legal or operational reason for retaining information rather than treating a general reference to this policy as sufficient by itself.

When a valid deletion request applies, we will delete, anonymise or restrict relevant information as appropriate. A legal hold or mandatory retention requirement may prevent immediate deletion of specific records. Retained exceptions will be limited to the relevant lawful purpose. Deletion from our systems does not automatically delete independent merchant or gateway records, and removal from active systems may precede expiry of restricted backup copies.

14. Security and incidents

The service is designed to use access controls, merchant account separation, protected integration credentials and server-side checks of relevant payment responses. We select and maintain safeguards for transmission, storage, administrative access and provider access according to the nature of the information and the risks of the relevant processing.

No internet service can promise absolute security. Merchants must protect their users and integration credentials, and shoppers should avoid sharing verification codes or payment secrets. Report suspected exposure promptly without including further sensitive data in the report.

If a personal-data incident occurs, we will investigate, take appropriate containment and remediation measures, and notify affected parties or authorities where required by applicable law and our contractual obligations.

15. Your choices and requests

Depending on applicable law, our role and the relevant provisions in force, you may be able to request information about processing, access or a summary of your personal data, correction or updating, erasure, withdrawal of consent, and grievance redressal. Additional rights, including nomination where applicable, will be handled in accordance with the requirements that apply.

Send a request to checkout@dropifyplaza.com with the subject "Privacy request". Describe the request and provide the store name or another relevant reference. We may verify your authority using proportionate information to avoid disclosing data to the wrong person. Do not include an OTP, password or full payment credentials.

We will explain whether we can act directly or need to coordinate with the merchant. We will respond within the legally applicable period and explain any lawful limitation or necessary additional information. Requests will not be refused merely because they concern a completed order, although particular records may need to be retained.

Withdrawing consent does not make earlier lawful processing unlawful. It may affect a feature that depends on the withdrawn permission, and it does not override another valid legal requirement to retain limited records. Marketing or optional saved-profile choices should not be confused with cancellation or refund of an order.

16. Children and persons requiring authorised representation

Merchant accounts are intended for adults legally capable of entering the relevant agreement. We do not intend to solicit children's personal data through our business website. A merchant's customer base may nevertheless include children, and an OTP alone does not verify age or parental authority.

Where processing involves a child under applicable law, any required verified parental or lawful guardian consent and other safeguards must be in place before the relevant processing. Merchants must not use the service to bypass those requirements. We will not treat access to a mobile number as proof of age or parental authority, and we may restrict an affected feature while a concern is investigated.

A parent, guardian or authorised representative may contact us about suspected improper processing. We will assess the request, verify authority proportionately and take the action required for our role.

Stores, gateways and other websites linked from our service operate under their own notices. When you leave our service or interact directly with their components, their practices may apply in addition to this policy. Linking to a provider or displaying its logo does not mean that Dropify controls all of that provider's processing.

For product delivery, cancellation, returns and merchant invoices, contact the selling merchant. For our handling of personal data, use our privacy contact. We will help identify the appropriate route where reasonably possible.

18. Changes to this policy

We may update this policy to reflect changes in the service, actual processing arrangements or applicable law. The published version will identify its effective date. For material changes, we will provide an appropriate notice and seek fresh consent where required before applying a new consent-dependent use.

A policy update does not authorise retroactive use of information for an incompatible purpose. Previous versions and the date of a relevant change can be requested through our privacy contact.

19. Privacy contact and grievance escalation

For privacy questions, rights requests or complaints, contact:

  • Business: Dropify Plaza — Dropify Checkout
  • Owner/operator: Aayush Garg
  • Business address: 904/34, Vijay Nagar, Barak Gali No. 2, Rohtak, Haryana 124001, India
  • Email: checkout@dropifyplaza.com
  • Complaints telephone: +91 9315620335

Use the subject “Privacy request” for access, correction, erasure or consent-related requests, and “Privacy grievance” for a complaint about our handling of personal data. Include your store name or relevant reference and a short explanation of the issue. We will route the request to the person responsible for the relevant matter. Do not include passwords, OTPs or complete payment credentials.

We will assess the request, seek proportionate verification where necessary and respond within the period required by the law applicable to the request. If a concern remains unresolved, reply to the same correspondence with the subject “Privacy grievance — escalation”, quoting the earlier reference or message date. We will review the earlier handling and explain the outcome or any further steps required.

Formal correspondence may be sent to the business address or email above, subject to any service requirements prescribed by applicable law. The contracting-party details in an accepted Merchant agreement continue to apply to that relationship.

If our response does not resolve your concern, you may use the complaint or other remedies available under applicable law. Where a law provides a specific regulator or authority route and requires an initial grievance process, those procedures apply. This policy does not restrict a mandatory privacy or consumer right. Related service conditions appear in the Terms of ServiceRefund & Cancellation.