Data Processing Agreement

How Codified processes personal data on behalf of VoucherVerse customers, under the GDPR, UK GDPR, POPIA, CCPA and other data protection laws.

Last updated 21 October 2026

About this agreement

This Data Processing Agreement ("DPA") forms part of the Terms of Service (the "Agreement") between the business that uses VoucherVerse ("Customer") and Codified Holdings, Inc. ("Codified"). It applies whenever Codified processes Customer Personal Data to provide VoucherVerse, and takes effect when Customer accepts the Agreement, with no separate signature. If Customer needs a countersigned copy, email privacy@codified-holdings.com.

1. Definitions

  • Data Protection Laws: all laws on personal data that apply to the processing, including the EU General Data Protection Regulation 2016/679 ("GDPR"), the GDPR as it applies in the United Kingdom ("UK GDPR") and the UK Data Protection Act 2018, the Swiss Federal Act on Data Protection, South Africa's Protection of Personal Information Act 2013 ("POPIA"), and the California Consumer Privacy Act as amended ("CCPA") and similar US state laws.
  • Customer Personal Data: personal data that Customer, its users or the systems it connects put into VoucherVerse, or that VoucherVerse generates for Customer, described in Annex I.
  • Subprocessor: a third party Codified engages to process Customer Personal Data.
  • Security Incident: a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data.
  • SCCs: the standard contractual clauses approved by European Commission Implementing Decision (EU) 2021/914.
  • "Controller", "processor", "data subject", "processing" and "supervisory authority" have the meanings in the GDPR; under POPIA they include "responsible party" and "operator", and under the CCPA "business" and "service provider".

2. Roles

Customer is the controller of Customer Personal Data (or a processor acting for its own controllers, in which case Customer confirms it has their authority to engage Codified). Codified is Customer's processor, operator under POPIA and service provider under the CCPA. Codified is a controller only for the data described in its Privacy Policy, such as account, billing and security data.

3. Customer's instructions

Codified processes Customer Personal Data only on Customer's documented instructions, which are: the Agreement and this DPA; Customer's and its users' use and settings of VoucherVerse; and any other written instruction both parties agree. Codified will tell Customer if it believes an instruction breaks Data Protection Laws, and may then decline it. If a law requires Codified to process data otherwise, Codified will tell Customer first unless that law forbids it.

4. Customer's responsibilities

  • Customer is responsible for having a lawful basis for the processing, giving data subjects the notices the law requires (including the terms of its vouchers), and for the accuracy of Customer Personal Data.
  • Customer sends vouchers to its recipients with its own tools and is responsible for that communication, including any consent it needs.
  • Customer will not put special categories of personal data (such as health, biometric or financial account data), government ID numbers or data about children under 16 into VoucherVerse. Recipient IDs should be Customer's own reference numbers.
  • Customer keeps its users' credentials and its campaign API keys confidential and is responsible for activity under them.

5. Confidentiality

Codified ensures that everyone it authorises to process Customer Personal Data is bound by confidentiality and only has access needed for their role.

6. Security

Codified implements and maintains the technical and organisational measures in Annex II. Codified may update them, provided the update does not reduce the overall protection of Customer Personal Data.

Subprocessors

7.1 Authorisation. Customer gives general authorisation for Codified to engage Subprocessors. The current Subprocessors are listed in Annex III and at /legal/subprocessors.

7.2 Changes. Codified will publish a new Subprocessor on that page, and email Customer's account admins, at least 30 days before it processes Customer Personal Data. Customer may object in writing to privacy@codified-holdings.com within that period on reasonable data protection grounds. The parties will discuss the objection in good faith; if they cannot resolve it, Customer may terminate the affected part of the Agreement and receive a refund of fees prepaid for the period after termination.

7.3 Obligations. Codified imposes on each Subprocessor, by written contract, data protection obligations no less protective than this DPA, and remains liable to Customer for its Subprocessors' performance.

7.4 Not Subprocessors. Services Customer connects or uses itself, such as its own Infobip account and chatbots, its systems that call the Codes API, or Apple Wallet on a recipient's device, act for Customer or the recipient and are not Codified's Subprocessors.

8. Data subject requests

VoucherVerse lets Customer find and export Customer Personal Data itself (search vouchers and customers, export to CSV) and delete vouchers and campaigns. A customer record (a recipient's name, email address, phone number and recipient ID) cannot yet be corrected or deleted in the service: Codified will do it on Customer's request to privacy@codified-holdings.com, in time for Customer to meet its legal deadlines. For anything else Customer cannot do through the service, Codified will help, taking into account the nature of the processing. If Codified receives a request from a data subject about Customer Personal Data, it will pass it to Customer without undue delay and not answer it except on Customer's instructions.

9. Security Incidents

Codified will notify Customer without undue delay, and in any case within 48 hours, after becoming aware of a Security Incident affecting Customer Personal Data. The notice goes to Customer's account admins by email and will describe, as far as then known, the nature of the incident, the data and data subjects concerned, its likely consequences, and the measures taken or proposed. Codified will update Customer as it learns more, take reasonable steps to contain and remedy the incident, and help Customer meet its own obligations to notify authorities and data subjects. Notifying an incident is not an admission of fault.

10. Assistance

Taking into account the nature of the processing and the information available to it, Codified will give Customer reasonable help with data protection impact assessments and prior consultations with supervisory authorities that relate to VoucherVerse.

11. Return and deletion

Customer can export its data as CSV at any time while its account exists, including after a subscription ends. Cancelling a subscription does not close the account. When the account is closed (on Customer's request to privacy@codified-holdings.com, or under the Agreement), Codified deletes Customer Personal Data within 30 days, except where the law requires it to keep some, in which case it stays protected by this DPA and is used for nothing else. Data Customer deletes in the service is removed as described in Annex I.

12. Audits

Codified will make available the information reasonably necessary to show it meets this DPA, including answering a reasonable security questionnaire once a year. If that is not enough, or a supervisory authority requires it, Customer (or an independent auditor bound by confidentiality, not a Codified competitor) may audit Codified's compliance once in any 12 months, with at least 30 days' written notice, during business hours, without disrupting Codified's operations or other customers' data, and at Customer's cost. Audits of Subprocessors rely on their own certifications and reports.

13. International transfers

EU. Where Customer Personal Data is transferred from the European Economic Area to Codified or its Subprocessors in a country without an adequacy decision, the SCCs apply and are incorporated by reference: Module Two (controller to processor) where Customer is a controller, and Module Three (processor to processor) where Customer is a processor. Clause 7 (docking) applies; in Clause 9 option 2 applies with the notice period in section 7.2; the option in Clause 11 does not apply; in Clause 13 the supervisory authority is that of Customer's EU establishment or, failing one, its EU representative, or otherwise Ireland's Data Protection Commission; Clauses 17 and 18 choose the law and courts of Ireland. Annexes I, II and III of this DPA complete the SCCs' annexes.

UK. For transfers from the United Kingdom, the International Data Transfer Addendum issued by the Information Commissioner (version B1.0) applies to the SCCs, with Table 1 completed from Annex I, Table 2 as above, Table 3 from Annexes I to III, and either party may end it as in its section 19.

Switzerland. For transfers from Switzerland, the SCCs apply with references to the GDPR read as the Swiss Federal Act on Data Protection, and the Federal Data Protection and Information Commissioner as the competent authority.

South Africa. For transfers of personal information from South Africa, this DPA provides the binding agreement required by section 72 of POPIA.

If the SCCs conflict with this DPA or the Agreement, the SCCs prevail.

14. CCPA

As a service provider, Codified will not: sell or share Customer Personal Data; retain, use or disclose it for any purpose other than providing VoucherVerse to Customer, or outside the direct business relationship with Customer; or combine it with personal information from other sources, except as the CCPA permits. Codified will comply with the CCPA, give the same level of protection it requires, and tell Customer if it can no longer meet these obligations. Customer may take reasonable steps to stop and remediate unauthorised use of Customer Personal Data.

15. General

This DPA lasts as long as Codified processes Customer Personal Data. Each party's liability under this DPA is subject to the limitations in the Agreement, except where Data Protection Laws or the SCCs do not allow them. If this DPA conflicts with the Agreement, this DPA prevails for the processing of Customer Personal Data. Codified may update this DPA to reflect changes in law or in VoucherVerse, provided the update does not reduce the protection of Customer Personal Data; it will tell Customer's admins of material changes 30 days in advance.

Annex I: Details of processing

Data exporterCustomer, as identified in its VoucherVerse account. Contact: its account admins. Role: controller (or processor).
Data importerCodified Holdings, Inc., 1111B S Governors Ave #93788, Dover, DE 19904, USA. Contact: privacy@codified-holdings.com; for the EU and the UK, craigm@codified-holdings.com. Role: processor.
Data subjectsCustomer's customers and voucher recipients; people who enter codes through Customer's chatbots or systems; Customer's authorised users (admins and staff).
Categories of dataNames, email addresses, phone numbers and Customer's own recipient IDs; voucher codes, values, campaigns and status; when, where (merchant or channel) and by whom vouchers were issued, allocated and redeemed; identifiers of people entering codes, usually phone numbers; users' names, email addresses, roles and merchant assignments; users' activity in the audit log, with IP address and browser; request logs of users' activity (IP address, browser, and the address requested including search terms, which can contain recipients' names, email addresses or phone numbers); recipients' IP address and browser when they open a wallet link; users' use of the app (pages and clicks, without on-screen text) and error reports.
Special categoriesNone. Customer must not provide them (section 4).
FrequencyContinuous, for as long as Customer uses VoucherVerse.
Nature and purposeHosting and storing data; generating, importing, allocating, validating and redeeming voucher codes; making QR images and wallet passes; answering Customer's chatbots and systems through the Codes API; analytics and exports for Customer; audit logging; error tracking; deleting data. Purpose: providing VoucherVerse to Customer under the Agreement.
RetentionWhile Customer's account exists, then deleted within 30 days of its closure (section 11). In the service: deleted campaigns and their codes are kept 30 days for restoring, then deleted; imported files, import results and exports 7 days; request logs 30 days; counts of rejected code attempts 1 hour.
Transfers to SubprocessorsAs in Annex III, for the same nature, purpose and duration.
Competent supervisory authorityAs in section 13.

Annex II: Security measures

  • Encryption. HTTPS for all traffic, with HSTS. Data at rest is encrypted by the hosting and database providers.
  • Network and edge. All traffic passes through a content delivery network and web application firewall (IP reputation lists, known-bad-input rules, rate limits on sign-in and the API). The API answers only requests that came through it.
  • Separation of customers. Every record belongs to one company, and every request is checked against the user's company and role.
  • Authentication. Accounts are tied to an email address the person proved they own. Passwords are hashed with bcrypt. Sessions expire after 24 hours. Password reset links work once, for one hour, and are rate-limited; only hashes of reset and invitation tokens are stored.
  • Access control. Roles separate admins from staff; staff can only redeem for the merchants assigned to them. A deactivated user cannot sign in again and cannot redeem from their next scan; a dashboard session already open ends within 24 hours.
  • API keys. Shown once, stored only as hashes, and rotatable at any time. Requests from Infobip are signed and checked, with a five-minute window against replay.
  • Abuse prevention. A voucher can only be redeemed once, enforced by the database. Repeated wrong codes from one participant are blocked for an hour.
  • Storage. Files and QR images are in private storage, reachable only through signed, time-limited links. Temporary files are deleted after 7 days.
  • Input handling. Every input is validated on the server; spreadsheet exports are protected against formula injection.
  • Logging and audit. Every change, export and download is recorded in an audit log that cannot be edited and that Customer's admins can review. Request logs are kept 30 days.
  • Monitoring. Health checks and alerts for downtime, error bursts and failed background jobs.
  • Infrastructure and change management. Infrastructure is defined as code. Production and development run in separate cloud accounts. Deployments run through an automated pipeline with tests and short-lived credentials, and reach production only as tested releases started by hand. Secrets are kept in a secrets manager, never in code.
  • People. Access to production is limited to staff who need it, through individual accounts, and staff are bound by confidentiality.

Annex III: Subprocessors

SubprocessorWhat it does for VoucherVersePersonal data it receivesLocation
Amazon Web Services EMEA SARL and Amazon Web Services, Inc.Cloud hosting: application servers, file storage (QR images, imports, exports), content delivery, firewall, queues, DNS, configuration secrets and logsAll Customer Personal DataIreland (EU). Content delivery and the firewall run at edge locations in Europe and North America.
MongoDB, Inc. (MongoDB Atlas)Managed databaseAll Customer Personal DataIreland (AWS eu-west-1)
Infobip Ltd.Sending service emails to Customer's users (sign-up confirmation, invitations, password resets, account notices); sign-in with Infobip for customers who use the Infobip Exchange appUsers' names and email addresses; Infobip account and user identifiersEuropean Union
PostHog, Inc.Product analytics and error trackingUsers' account, role and company IDs (only for users who accept analytics cookies); pages visited and clicks, without on-screen text; browser, device and IP address (for approximate location); error reports, whose messages can contain the data involved in the errorUnited States
Google LLCGoogle Wallet passes, only when a voucher recipient chooses to save a voucher to Google WalletThe pass: voucher code, value, campaign, recipient's name, issuing company, valid-until dateUnited States and other locations Google uses

The current list is always at /legal/subprocessors.