COD Guard India
Merchant data processing terms
Last updated: October 9, 2026
These terms apply between Rachid Bouhmou, sole developer of COD Guard India, Brussels, Belgium (bourachid12031984@gmail.com), acting as the "Processor", and the merchant who installs COD Guard India on their Shopify store, acting as the "Merchant" or "Controller". By installing or using the app, the Merchant accepts these terms. They supplement the COD Guard India privacy policy and Shopify's Partner Program and API terms.
1. Roles
The Merchant is the controller of their customers' personal data. The Processor processes that data only on the Merchant's behalf, to provide the app. Where the GDPR applies, these terms are intended to meet Article 28 GDPR.
2. What is processed and why
- Data subjects: buyers who place cash-on-delivery (COD) orders in the Merchant's store.
- Personal data: buyer name, shipping address, phone number and email, for COD orders only, plus the order details needed to assess the order. Prepaid orders are not stored.
- Purposes (purpose limitation): scoring the risk of COD orders; applying the Merchant's rules; sending WhatsApp order confirmations, only when the Merchant turns messaging on; tracking shipments and delivery outcomes with carriers the Merchant connects; showing results to the Merchant. The data is not sold, not used for advertising or marketing, and not used for any other purpose.
- Automated decisions: the app's score only recommends. Automatic order cancellation and hiding COD at checkout are off by default, and they apply only if the Merchant turns them on and sets the rules.
3. Merchant instructions
The Processor processes personal data only on the Merchant's documented instructions. Those instructions are given through installing the app, choosing its settings, and these terms. If an instruction appears to break data protection law, the Processor will tell the Merchant.
4. Confidentiality
Only the Processor has access to production data. Any person later authorised to process the data will first be bound by a duty of confidentiality and will have access only as needed.
5. Security
The Processor applies the measures described in the COD Guard India Security and Incident Response Policy, including:
- HTTPS/TLS for all traffic;
- encryption at rest by the database provider;
- AES-256-GCM encryption of stored integration tokens;
- access limited to the Processor, with strong unique passwords and two-factor authentication;
- an audit log of views of order data;
- point-in-time database recovery;
- separation of test and production data.
6. Sub-processors
The Merchant authorises the following sub-processors:
| Sub-processor | Role | Location | When used |
|---|---|---|---|
| Fly.io | Application hosting | Singapore | Always |
| Neon | PostgreSQL database | AWS ap-southeast-1, Singapore | Always |
| Upstash (provisioned via Fly.io) | Job queue (Redis) | Singapore | Always |
| Meta Platforms (WhatsApp Cloud API) | Sending WhatsApp confirmations | Per Meta's terms | Only when the Merchant turns on messaging |
| Shiprocket | Shipment tracking | India | Only when the Merchant connects Shiprocket |
| Delhivery | Shipment tracking | India | Only when the Merchant connects Delhivery |
The Processor will tell Merchants about any intended addition or replacement of a sub-processor by updating this list and the privacy policy at least 14 days in advance, where reasonably possible. A Merchant who objects may uninstall the app. Personal data is then deleted as described in section 9. Sub-processors are bound by data protection obligations through their own terms. Where data leaves the EEA and the GDPR applies, the transfer relies on the safeguards in those providers' terms (for example, Standard Contractual Clauses).
7. Data subject requests and consent
- The Processor honours customer requests forwarded by Shopify or the Merchant. It responds to customers/data_request webhooks with the data held for that customer, and it erases data on customers/redact.
- The Processor follows consent decisions that Shopify or the Merchant passes on. For example, WhatsApp messages are sent only when the Merchant has turned messaging on, and the Merchant is responsible for having the buyer's consent to be contacted where the law requires it.
- The Processor assists the Merchant, within reason, with requests, data protection impact assessments and regulator enquiries about the app.
8. Personal data breaches
The Processor notifies affected Merchants without undue delay after becoming aware of a personal data breach affecting their data. The target is within 72 hours where the GDPR applies. The notice describes what happened, the data and approximate number of people concerned, likely consequences, and the measures taken. The Processor also informs Shopify.
9. Retention and deletion
- Customer personal fields are deleted (nulled) after the Merchant's retention period. The default is 365 days, and the Merchant can change it in the app settings.
- When the Merchant uninstalls the app, Shopify sends a shop/redact request, and the Processor deletes that shop's data in response.
- Provider backups expire according to the providers' own schedules. Neon states a 30-day backup retention, and the point-in-time restore history is limited to the configured window.
10. Audits and information
On request, the Processor gives the Merchant the information reasonably needed to show compliance with these terms. This includes the security policy and the sub-processor list.
11. Contact
Rachid Bouhmou, bourachid12031984@gmail.com