
Last updated: 7 October 2026 · Applies to the EmiGuard platform at emi.letzshop.co.in, the retailer app, and the customer payment portal.
The shop that sold you the device on EMI is the data controller for your customer record (it decides what is stored and can delete it). EmiGuard — the platform operated by letzshop — is the processor hosting the software that stores and processes that record on the shop's behalf. Payment collection is between you and the shop (UPI to the shop's own ID); we never store your UPI PIN, card or bank credentials.
From the customer (at the point of sale): name, mobile number, device identifiers (model, Android ID / device ID), the EMI plan you agreed to, and your written consent that the financed device may be locked when an installment is overdue and unlocked when dues are cleared.
From the device (while enrolled as an owner device): lock state, battery / SIM state, app inventory used for lock features, and location only when the shop requests it (for recovery or ownership proof — it is not tracked continuously by default). Tamper events (factory reset attempts, unauthorized SIM change) are recorded as security events.
From the shop: the shop's mobile number, name, UPI ID and helpline — shown to you on lock and payment screens so you know who to contact.
Messages: if the shop enables SMS or WhatsApp reminders, your mobile number receives due/overdue notices, lock/unlock notices and payment receipts through Twilio (SMS) or a WhatsApp business API provider. Message attempts are logged (time, number, outcome) for proof of delivery.
To enforce the EMI agreement you signed: remind you of dues, restrict the device when an installment is overdue past the grace period, and restore access once payment is recorded. The legal basis is your explicit consent captured at enrollment (consent text and timestamp are stored with your record) plus the contract between you and the shop. Aggregate, anonymised statistics (e.g. overdue counts) may be used to improve risk scoring.
The shop you bought from, its distributor/dealer chain (only customers under them), and the platform admin. Device commands and data accesses are written to an audit trail visible to the shop. We do not sell data, do not run advertising trackers, and do not share your number with third parties other than the messaging providers above and Google Firebase (push delivery).
Device and customer records are kept while your contract is active, and are deleted by the shop when the contract closes or when you request it after dues are settled. Security/audit entries are kept as a rolling log (last 200 events); message-attempt logs are kept as a rolling log (last 50). Demo accounts and their data are purged automatically at the end of the 14-day demo.
You may ask the shop for a copy of your record, corrections, or deletion (after dues are cleared). You may withdraw consent to device administration by having the shop deregister the device — the device stops being managed and its lock is released. Questions about this policy: contact the shop that sold you the device, or write to the platform at the contact address published on the shop's dashboard.
Admin and retailer traffic is served over HTTPS. Passwords are stored as salted PBKDF2 hashes. Device commands require authenticated tokens; FRP recovery secrets are server-side only and never returned. No system is perfectly secure — please contact the shop promptly if you believe your record is wrong.