Cravme
Back to Legal Hub

Data Processing Addendum

Last updated: November 14, 2026

This Data Processing Addendum ("DPA") forms part of the Merchant Terms of Service between Cravme LLP ("Cravme") and the business using Cravme ("Merchant"). It applies whenever Cravme processes personal data on the Merchant's behalf, and sets out the contract that section 8(2) of the Digital Personal Data Protection Act, 2023 ("DPDP Act") requires between a Data Fiduciary and a Data Processor. It applies automatically; no separate signature is needed. Merchants who need a countersigned copy can request one at legal@cravme.com.

1. Roles

  1. For Merchant Personal Data (defined below), the Merchant is the Data Fiduciary and Cravme is the Data Processor.
  2. For data about customers' Cravme accounts and Marketplace orders, and for data about the Merchant's own owners and users, Cravme acts as an independent Data Fiduciary under its own privacy policies, and this DPA does not apply.

2. What data this covers

"Merchant Personal Data" means personal data that the Merchant collects, uploads or manages through the Services, including:

  • the Merchant's customers: names, phone numbers, emails, addresses, order and visit history, loyalty points, feedback, table bookings and marketing preferences collected through the POS, QR ordering, the Merchant's website or imports;
  • the Merchant's staff: names, contact details, roles, shifts, attendance, leave, salary, deductions, payslips, bank details and, where face clock-in is used, face images and face templates used to mark attendance;
  • the Merchant's suppliers and other contacts stored in the Services.

3. Cravme's commitments

Cravme will:

  1. process Merchant Personal Data only on the Merchant's documented instructions, which are these Terms, this DPA and the Merchant's use and configuration of the Services, and not for its own purposes, except where Indian law requires (in which case Cravme will tell the Merchant unless the law forbids it);
  2. ensure that its staff and contractors who can access the data are bound by confidentiality;
  3. protect the data with reasonable security safeguards, including those set out in the DPDP Rules: encryption, access control, logging and monitoring of access, backups, and measures to keep the Services available;
  4. notify the Merchant without undue delay, and in any case within 48 hours of becoming aware, of a personal data breach affecting Merchant Personal Data, with the information the Merchant needs to inform the Data Protection Board of India and affected individuals, and help the Merchant do so;
  5. help the Merchant respond to requests from individuals exercising their rights (access, correction, erasure, grievance and nomination), mostly through self-service tools in the dashboard, and pass on any request it receives directly;
  6. not sell Merchant Personal Data or use it to market Cravme's or anyone else's services to the Merchant's customers or staff;
  7. keep logs for at least one year as the DPDP Rules require, and make available the information reasonably needed to show compliance with this DPA.

Audits. Once a year, or after a personal data breach affecting Merchant Personal Data, the Merchant may ask Cravme to answer a reasonable written security questionnaire and share summaries of relevant third-party certifications of its hosting providers. An on-site audit is available only where required by a regulator or court, on at least 30 days' notice, during business hours, at the Merchant's cost, and without access to other customers' data.

4. Sub-processors

  1. The Merchant authorises Cravme to use the sub-processors listed below. Cravme imposes data protection terms on each that are no less protective than this DPA, and remains responsible for them.
  2. Cravme will give at least 30 days' notice in the dashboard or by email before adding or replacing a sub-processor. If the Merchant reasonably objects on data protection grounds and we cannot resolve it, the Merchant may terminate the affected Services and receive a refund of prepaid fees for them.

Current sub-processors

  • Google Cloud and Firebase: hosting, databases, authentication, file storage, notifications (India: Mumbai for core services)
  • Vercel: website hosting and delivery (global)
  • Cloudinary: image storage and processing (global)
  • Razorpay, Cashfree, PhonePe and Juspay: payment processing (India)
  • MSG91: SMS and OTP (India)
  • Meta Platforms (WhatsApp Business): WhatsApp messages (global)
  • Amazon Web Services (SES): email delivery (India: Mumbai)
  • Google Maps Platform: addresses and maps (global)
  • PostHog, Sentry, Google Analytics and LogRocket: analytics and error monitoring, only where enabled (United States / global)
  • Google (Gemini): AI image and text features, only when the Merchant uses them (global)

5. The Merchant's commitments

The Merchant will:

  1. have a lawful basis, and where needed valid consent, for every piece of Merchant Personal Data it collects and asks Cravme to process, and give individuals the notices the DPDP Act requires;
  2. obtain staff consent before using face clock-in, explain how face data is used, and offer an alternative way to record attendance;
  3. send marketing only to people who have agreed to receive it and honour opt-outs;
  4. not upload data it does not need, and not upload children's data except where the law allows and verifiable parental consent has been obtained;
  5. handle requests and grievances from its customers and staff, and publish its own contact details for them; and
  6. keep its users' logins secure and remove access for people who leave.

6. Face data

Face clock-in captures a face image on the device to detect and match the employee's face when marking attendance. Face templates and images are used only for attendance for that Merchant, are never used to identify people for any other purpose, are never shared with other Merchants, and are deleted when the employee is removed or the Merchant closes the account (subject to any legal hold).

7. International transfers

Merchant Personal Data is primarily stored in India. Where a sub-processor processes it elsewhere, Cravme will only transfer it to countries not restricted by the Government of India under section 16 of the DPDP Act.

8. Deletion and return

During the subscription, the Merchant can export and delete Merchant Personal Data through the dashboard. Within 30 days after the account closes, Cravme will delete Merchant Personal Data, unless the law requires it to be kept (for example tax invoices the Merchant issued through the POS). Deletion from backups happens as backups expire. On request, Cravme will confirm the deletion in writing.

9. Liability and term

This DPA lasts as long as Cravme processes Merchant Personal Data. Liability under it is governed by the Merchant Terms of Service. If this DPA conflicts with the Terms on data protection, this DPA wins.

10. Contact

Data protection questions and breach contacts: legal@cravme.com. Grievance Officer: D. Sai Kiran, legal@cravme.com.

Questions about this policy?

We'll explain anything that isn't clear, or help you use your rights over your data.

legal@cravme.com