Data Processing Addendum
Last updated: October 2026
The short version
For personal data inside your receipts, customer lists, feedback, and loyalty records, you are the data controller and we are your data processor under Malaysia's PDPA.
We process that data only to run the service, only on your documented instructions, and we tell you promptly if we learn of a breach so you can meet your own 72-hour notification duty.
Our providers are listed on the subprocessors page; you can object if we add a new one.
What this addendum is
This Data Processing Addendum ("DPA") is between Polaris Technologies (SSM registration 202603066744 · AS0511535-P) ("ezResit", the processor) and the merchant whose order confirmation or pilot agreement references the ezResit Terms of Service (the data controller). It applies whenever we process personal data on the merchant's behalf in providing the service, and it forms part of the Terms. If this DPA and the rest of the Terms conflict on a data-protection matter, this DPA wins.
Terms like "personal data", "processing", "data controller", "data processor", "data subject", and "personal data breach" have the meanings in the Personal Data Protection Act 2010 (Malaysia) as amended ("PDPA").
Roles and scope
Merchant = data controller. You decide what your POS prints, which customers you market to, and what you collect through the service. You are responsible for having a lawful basis for that data, including any notice or consent your customers need.
ezResit = data processor. We process that personal data only to provide, secure, and improve the service, and only on your documented instructions, including the instructions you give by configuring the dashboard, enabling features (loyalty, review routing, OCR indexing), or asking support for help.
ezResit = independent controller for its own operational data: merchant account emails, staff invitations, billing records, device credentials, security logs, and the public status feed. The privacy notice governs that processing, not this DPA.
Data covered
Personal data that may appear in: receipt content produced by your POS; customers' feedback ratings and comments; wallet customers' phone numbers and loyalty records where your customers have linked or consented through your outlet; and consented customer lists shown in your dashboard.
Duration
For the term of your merchant account, plus the retention periods in the privacy notice (consent records are append-only history; receipt links live up to 180 days; deletion follows section 7 below).
Our obligations as processor
We will:
- process personal data only on your documented instructions, including this DPA and your use of the service's features, unless the law requires otherwise, and then we will tell you first where the law allows;
- ensure people under our control who handle personal data are bound to confidentiality;
- keep in place the technical and organisational measures in Annex A below;
- not use your customer personal data for our own purposes: no profiling, advertising, or sale;
- tell you promptly if we believe an instruction would breach the PDPA.
Subprocessors
You authorise us to use the providers listed on our subprocessors page to run the service (hosting, database, storage, message delivery, payment). Each is engaged under a written contract requiring protections no weaker than this DPA.
If we add or replace a subprocessor in a way that expands who touches merchant-controlled personal data, we will update that page and flag the change before it takes effect. You may object in writing within 14 days; if the objection is reasonable and we cannot offer an alternative, you may end the affected part of the service and we will refund the unused prepaid period for it.
Personal data breaches
If we confirm a personal data breach affecting personal data we process for you, we will notify you without undue delay and aim to do so within 24 hours of confirming it, so you can meet your own obligation under section 12B PDPA to notify the Commissioner within 72 hours and affected data subjects where significant harm is likely.
The notice will describe, to the extent known: what happened, what data and how many subjects are likely affected, likely consequences, and the measures taken or proposed. We will keep you updated as more is known and give reasonable assistance for your own notifications. You are responsible for assessing your reporting duty as controller; a breach notification from us is not itself an admission of fault or liability.
Helping you with data-subject requests
Where a data subject asks you (or asks us about data you control) for access, correction, deletion, withdrawal of consent, or portability, we will give reasonable assistance so you can respond, noting that much of the data is available to you directly in the dashboard and CSV exports. We will not answer a data-subject request about data you control except to point the requester to you or to act on your instruction.
Cross-border processing
The service stores merchant data in Singapore (primary database and object storage) and uses delivery providers whose networks span other countries, as listed on our subprocessors page. You instruct us to make these transfers as needed to run the service; for transfers of personal data you control, our transfer is performed on your behalf and you are responsible for your own section 129 PDPA basis. For data where we are controller, the basis is described in the privacy notice.
Deletion and return
- While your account is active you can export receipt history and consented customer lists from the dashboard (CSV) at any time.
- On termination we hold your data available for export for 30 days where practicable, then delete or anonymise it within a further 90 days, except where the law or the integrity of shared records requires retention (for example, append-only consent history, which is retained in anonymised form).
- Already-issued receipt links keep working until their normal expiry; deleting the merchant account does not pull receipts out of customers' hands. To kill a specific link before expiry, use the revoke function in the dashboard or ask us.
Assurance
To demonstrate compliance with this DPA we will: maintain the measures in Annex A; answer reasonable written security questionnaires once per year; and, where a serious incident or a regulator reasonably requires it, provide further information about the relevant processing. On-site audits are not practical at our size; the questionnaire route plus the public status page and security contact (security.txt) are the intended assurance channel.
Liability and order of terms
Liability under this DPA is subject to the limitation of liability in the Terms. Order of precedence for data-protection matters: this DPA, then the order confirmation, then the Terms, then the privacy notice as background only.
Annex A: Technical and organisational measures
The measures the service maintains, in summary:
- Encryption in transit for all connections; object storage access via short-lived signed URLs only, never public buckets.
- Device, account, and session credentials stored only as hashes; credentials bound to tenant, device, location, and station.
- Public receipt access via high-entropy bearer tokens (at least 128 random bits); no internal identifiers exposed publicly.
- Row-level tenant isolation in the database; browser-facing roles denied direct table access; all privileged access via audited service paths.
- Append-only audit ledger for operator actions, including support "view as merchant" sessions.
- Append-only consent records (purpose- and channel-specific) that cannot be silently overwritten.
- Per-IP throttling and header hardening on public surfaces; no-store caching on all receipt, wallet, and API responses.
- Retention sweep jobs that expire artifacts and data on schedule; rendered receipt artifacts deleted with their source.
- Encrypted backups held off the primary provider (cold recovery path).
- Access to production systems restricted to named operator credentials; operator actions logged.