Data Processing Agreement

Last updated November 11, 2026
In short: when a hosted Casazium account holds personal data about your customers, you control that data and we process it only for you. This agreement sets out how: the security measures we keep, the sub-processors we use, how fast we tell you about a breach (72 hours at most), what happens to the data when you leave, and the transfer terms for the EU, the UK and Switzerland. It is part of our Terms of Service; there is nothing to sign. This summary isn't part of the agreement.

1. Parties and scope

This Data Processing Agreement ("DPA") is between Bob Casazza, doing business as Casazium, a sole proprietorship in Merrimack, New Hampshire, USA ("Casazium", the processor) and the customer that holds a hosted Casazium License Server account ("Customer", the controller).

  1. 1.1 What it covers. Personal data that Casazium processes for the Customer through the hosted License Server and Console: data about the Customer's own buyers and end users. It does not cover self-hosted installations: Casazium receives no personal data about a self-hosted licensee's buyers or end users, who are the data subjects this agreement is about.
  2. 1.2 How it applies. This DPA forms part of the Casazium Terms of Service and applies from the day the Customer creates an account. No signature is needed. A Customer who wants a countersigned copy can email bob@casazium.com.
  3. 1.3 Order of precedence. For personal data, this DPA prevails over the Terms of Service where they conflict. Where the Standard Contractual Clauses apply (section 4), they prevail over this DPA.

2. Definitions and roles

Terms such as "personal data", "processing", "controller", "processor", "data subject" and "personal data breach" mean what they mean in the GDPR (Regulation (EU) 2016/679) and the UK GDPR.

  1. 2.1 Customer as controller. The Customer decides why and how its buyers' data is processed: which licenses to issue, to whom, with what terms, and which storefront to connect.
  2. 2.2 Casazium as processor. Casazium processes that data only to run the hosted service for the Customer, as described in Annex I.
  3. 2.3 Casazium as controller of its own data. Casazium is a controller, not a processor, for the data of the Customer's own account users (sign-in email, billing, support), which its Privacy Policy covers. This DPA does not cover that data.
  4. 2.4 US state laws. Where the California Consumer Privacy Act or a similar law applies, Casazium acts as a "service provider" or "processor". It will not sell or share the Customer's personal data, or use it outside the direct business relationship with the Customer. It will tell the Customer if it can no longer meet these obligations, and the Customer may then take reasonable steps to stop unauthorized use.

3. Casazium's obligations

Casazium commits to the following for as long as it processes the Customer's personal data.

  1. 3.1 Instructions. Casazium processes the data only on the Customer's documented instructions. Those instructions are this DPA, the Terms of Service, and what the Customer does in the Console and API. If Casazium believes an instruction breaks data protection law, it tells the Customer immediately. If Union or Member State law to which Casazium is subject requires other processing, Casazium tells the Customer first, unless that law forbids it. Requests from public authorities elsewhere are handled under section 4.
  2. 3.2 Purpose. Casazium uses the data only for the purposes in Annex I. It does not sell it or use it for advertising. The one cross-account use is abuse prevention: Casazium counts license emails per recipient across accounts, using a one-way hash of the address, so no account can flood one person's inbox.
  3. 3.3 Confidentiality. Only people who need access to run, support or secure the service have it, and they are bound by confidentiality. Operator actions on a Customer's account are recorded in a tamper-evident audit log (Annex II).
  4. 3.4 Security. Casazium maintains the technical and organizational measures in Annex II, and reviews them as the service changes. It may improve them, but will not lower the overall level of protection.
  5. 3.5 Subprocessors. The Customer gives general authorization for the subprocessors in Annex III. Casazium will announce any addition or replacement at least 30 days before it takes effect, by email to the account owner naming the subprocessor and what it will do, and on its subprocessor page. The Customer may object in writing within that period on reasonable data protection grounds. While the objection is open, Casazium does not use the new subprocessor for the Customer's data; if the parties can't resolve it, the Customer may terminate before the change takes effect, with the export period in section 3.9 and a pro-rated refund of prepaid fees. Casazium binds each subprocessor by contract to data protection obligations that are in substance the same as these (with one exception today: the mailbox that receives email sent to casazium.com addresses is a personal Google account, which is not covered by a data processing agreement; Annex III), and remains responsible for them. On request, Casazium gives the Customer a copy of each subprocessor agreement, with commercial terms removed.
  6. 3.6 Data subject requests. The Console and API let the Customer find, export and delete its buyers' data itself. To correct a licensee name, the Customer deletes the license and issues a new one. Casazium supplies, on request, anything the export does not include. If a buyer contacts Casazium directly, Casazium passes the request promptly, normally within 2 working days, to each Customer it concerns (each only the part that concerns it), tells the buyer it has done so, and does not answer the request itself.
  7. 3.7 Personal data breaches. Casazium notifies the Customer without undue delay, and in any case within 72 hours, after becoming aware of a personal data breach affecting the Customer's data (a confirmed breach, not an unsuccessful attempt). The notice goes by email to the account owner, from security@casazium.com. It says what happened, the data and number of people likely affected, the likely consequences, and what Casazium has done. Information not yet known follows as it becomes available. Notifying a breach is not an admission of fault.
  8. 3.8 Assistance. Casazium gives reasonable help with the Customer's own obligations on security (GDPR Article 32), breach notification to authorities and data subjects (Articles 33 and 34), data protection impact assessments and consultations with supervisory authorities, as far as they concern the hosted service.
  9. 3.9 Deletion at the end. When the Customer deletes its account, Casazium deletes the Customer's personal data at once from the live service, as described in Annex I; copies in backups expire within the periods stated there. If the service ends for any other reason, the Customer has 30 days to export its data and to choose whether Casazium returns or deletes it; Casazium then deletes it, sooner if the Customer asks. Casazium keeps data after that only where law requires it or as listed in Annex I, and only for that purpose. On request, Casazium confirms the deletion in writing.
  10. 3.10 Information and audits. Casazium makes available the information needed to show it meets this DPA, starting with this document, its annexes and the security documentation. If that is not enough, the Customer may audit Casazium's processing of its data once a year on 30 days' notice, and at any time on reasonable notice after a personal data breach, when a supervisory authority asks, or where there are indications of non-compliance. The Customer chooses the auditor, who must be bound by confidentiality and must not be a competitor of Casazium. Audits are remote by default; an inspection in person takes place at a location Casazium designates. Subprocessors' facilities are covered by their own audit reports. Each party bears its own costs.

4. International transfers

Casazium is based in the United States, and some subprocessors store data there (Annex III), so data from EU, EEA and UK Customers is transferred outside those regions.

  1. 4.1 EU and EEA. Where the Customer is in the EU or EEA, or the GDPR otherwise applies to the transfer, the parties agree to Module 2 (controller to processor) of the EU Standard Contractual Clauses (Decision (EU) 2021/914), incorporated by reference. Clause 7 (docking) applies; Clause 9 option 2 (general authorization, with the notice in section 3.5); the Clause 11 option is not used; Clause 13: the supervisory authority competent for the Customer under Clause 13(a), as the Customer identifies it. Clauses 17 and 18: Clause 17 Option 1, the law of Ireland, and Clause 18(b), the courts of Ireland. Annexes I to III of this DPA complete the SCCs' annexes.
  2. 4.2 UK. For UK Customers, the UK Information Commissioner's International Data Transfer Addendum to the EU SCCs (version B1.0, in force 21 March 2022, as revised under its Section 18) applies. Table 1: the parties as in section 1 and Annex I. Table 2: the EU SCCs as chosen in section 4.1. Table 3: Annexes I to III of this DPA. Table 4: neither party may end the Addendum when the Approved Addendum changes (its Section 19). For UK transfers the Addendum's mandatory clauses replace Clauses 13, 17 and 18 with the Information Commissioner and the law and courts of England and Wales.
  3. 4.3 Switzerland. For transfers subject to the Swiss Federal Act on Data Protection (FADP), the EU SCCs apply with these adjustments: the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for those transfers (alongside the authority under Clause 13 where the GDPR also applies); "Member State" in Clause 18(c) does not stop data subjects habitually resident in Switzerland from bringing claims there; and references to the GDPR are read as references to the FADP where only the FADP applies. Clauses 17 and 18 otherwise apply as in section 4.1.
  4. 4.4 Onward transfers. Casazium transfers data to subprocessors outside the EU, EEA or UK only under an adequacy decision, the SCCs, or another valid mechanism, with the exception noted in section 3.5.
  5. 4.5 Transfer assessment. Casazium will provide the information a Customer needs for its transfer impact assessment, including whether Casazium has received government requests for Customer data. As of November 8, 2026, Casazium has not received any request or order from a public authority, including law-enforcement and national-security authorities, for disclosure of personal data processed under this DPA. Any future request will be handled under SCC Clause 15.

5. Liability, term and law

  1. 5.1 Liability. Each party's liability under this DPA is subject to the cap in the Terms of Service, except that: liability to data subjects, including under SCC Clause 12(b) and GDPR Article 82, is not limited by this DPA or the Terms; and each party's liability to the other for breach of the Standard Contractual Clauses or the UK Addendum is not capped. Nothing limits liability that law does not allow to be limited, or either party's liability to data subjects under GDPR Article 82.
  2. 5.2 Term. This DPA lasts as long as Casazium processes personal data for the Customer, and its deletion and confidentiality commitments continue after that.
  3. 5.3 Changes. Casazium may update this DPA to reflect changes in law or in the service, with at least 30 days' notice by email; a change required by law may take effect sooner. A change never modifies the Standard Contractual Clauses and never reduces the protection this DPA gives the Customer's data; changes of subprocessor follow section 3.5. If a change materially affects the Customer, it may terminate before the change takes effect.
  4. 5.4 Governing law. New Hampshire law, with the courts of Hillsborough County, New Hampshire, as in the Terms of Service, except where the Standard Contractual Clauses require the law of an EU member state or the UK.

Annex I: Description of the processing

Data subjects. The Customer's buyers and end users: people and organizations the Customer issues licenses to, and people who use the licensed software on their machines.

Categories of personal data.

  • License records: the license key; the licensee name or email the Customer enters ("issued to"); notes and custom fields the Customer enters; license terms, dates and status.
  • Activations: the machine identifier the Customer's software sends (its content is set by the Customer's software, which may include a hostname), activation and check-in times, and the time a license or machine last called the service (recorded at most hourly, without an IP address).
  • Seat history: for each license, when a machine took a seat, was refused because the license was full, or had its seat freed (and, for a freed seat, by whom: the buyer's app, the buyer portal, the Customer, Casazium support, or an expired seat lease). Machines appear only as a code derived one-way from the license key and the machine identifier, not the identifier itself. No IP address is recorded.
  • Purchases: when the Customer connects a storefront (Stripe, Lemon Squeezy or Paddle), the storefront's order, checkout, customer, payment and subscription identifiers, with amounts. The buyer's email address is used to issue and email the license, and is usually what the license's "issued to" holds; the purchase record itself holds no email address. For Paddle, Casazium fetches the buyer's email from Paddle with an API key the Customer provides.
  • Email delivery: the buyer's email address and the license email's content, including the license key, sent through the email subprocessor. Casazium's own send logs keep a one-way hash of the address, not the address.
  • Buyer portal: sign-in links (stored as hashes) and the machines shown to the buyer.
  • Technical logs: IP addresses of requests to the service (including the Customer's apps fetching the server's signing keys, which carries no license data), in rotating server logs; and the Console proxy's access log, which records page addresses (including license keys in license page addresses) and IP addresses.
  • Console email log: the Console's record of the expiry and quota emails it sent the Customer, whose entries contain license keys.
  • Support notes: notes Casazium writes on the account while giving support, which may name a buyer.

The Customer should not put special category data (GDPR Article 9) in free-text fields. The service does not need it.

Purpose and nature. Issuing, validating, activating and revoking licenses; fulfilling storefront purchases; emailing license keys to buyers; running the buyer portal; showing the Customer each license's seat history and flagging licenses that look shared (a flag only: the service takes no action on it); preventing abuse; backing up the service; and fixing errors. Processing is continuous while the Customer's account is open.

Retention.

DataKept for
License, activation and portal recordsUntil the Customer deletes them or the account
Purchase records400 days, then deleted automatically; deleted with the account
Seat history90 days, then deleted automatically; deleted with the license or the account
Email send records (hashed address)8 days
Email delivery feedback30 days
Buyer reports of unwanted email90 days
Email subprocessor's own logsUp to 30 days
Daily backups14 days, then permanently deleted
Continuous database replicaAbout 3 days at most: snapshots are kept 24 hours, then the backup provider deletes them within about a day
Server request logs (IP addresses)Overwritten by size (three 10 MB files per container) and cleared on every redeploy; in practice a few days. Console proxy log about a week
Error reportsContain no personal data; samples 30 days
Record of support actions on the accountAbout 13 months, also after account deletion; it holds identifiers, not buyer contact details. Support notes are kept until the account is deleted

Account deletion. Deleting the account removes all of the above except the record of support actions from the live service at once, including the Console email log, in a single step with no undo. Leftover payment records clear within about 8 days. Copies in backups expire within 14 days, and from the database replica within about 3 days.

Annex II: Security measures

These are the measures in place as of License Server 1.36.0 and Console 1.22.0.

AreaMeasure
Encryption in transitTLS on every public endpoint, with HSTS.
CredentialsAPI keys, activation tokens and portal links are stored as SHA-256 hashes. Console passwords use scrypt. Storefront webhook secrets and storefront API keys are encrypted with AES-256-GCM, bound to their record.
Encryption at restBackups and the database replica are encrypted at rest by the backup provider (AES-256, with keys the provider manages); copies written before the provider turned this on in September 2026 are replaced as backups expire. License keys in the License Server's database have been stored encrypted with AES-256-GCM since 11 November 2026, under a key kept in the server's configuration, not in the database or its backups; each key is found by a one-way value, and its first and last four characters are kept unencrypted for search and display. Backups taken before that date hold the keys in plain form until they are deleted. The Console's record of the expiry emails it sent contains license keys in plain form (Annex I). Licensee names and emails, and the rest of the license data, are stored unencrypted, because the service must read them to show them in the Console, put them in license files and send emails. The servers' disks are not encrypted; data on them relies on the hosting provider's data-center security, and secrets and credentials are protected as described above.
Tenant isolationEvery Customer API request is scoped to that Customer's account, so one Customer's API key cannot read another's data. Only the operator's support tools work across accounts (see Operator access).
Secrets out of logsLicense keys, portal tokens and licensee searches are redacted from logs. Current API routes take keys in headers or request bodies; older routes that put a key in the URL are deprecated, and those URLs are redacted in the service's logs. The API's proxy keeps no access log. The Console's proxy keeps a size-rotated access log of about a week, which includes page addresses (a license's Console page address contains its key) and IP addresses. Error reports carry no identifiers, emails, keys or IP addresses.
Abuse protectionRate limits on API and sign-in routes; per-recipient limits on license emails.
Operator accessCasazium's support tools are reachable only over a private network, with passkey sign-in and short sessions. The deployment panel, through which the operator can reach server logs and the database, is reachable over the internet through Cloudflare and requires the operator's sign-in. Buyer emails are masked by default, and showing one is recorded. Every operator action is written to a hash-chained audit log whose integrity can be verified.
License integrityOffline license files and release manifests are signed, so they cannot be altered without detection. Each server publishes its signing keys in a key set signed by root keys kept offline, so a signing key can be replaced after a suspected leak, and apps using the key-set setup follow without a new build.
AvailabilityDaily backups kept 14 days off-site, plus a continuous database replica.
DeletionAccount and license deletion take effect immediately on the live service; backups expire on schedule (Annex I).
PeopleOne operator has production access. Any future staff or contractors with access will be bound by a written confidentiality undertaking.
Incident responseA written incident and breach procedure: evidence is preserved first, each kind of leaked secret has its own containment steps, Customers are notified within the deadline in section 3.7, and every personal data breach is recorded in a register kept outside the service.

Annex III: Subprocessors

The Customer authorizes these subprocessors; the same list is kept on the subprocessor page. Stripe, Lemon Squeezy and Paddle are not on the list when the Customer connects them as its own storefront: the Customer contracts with them directly, and Casazium only receives their webhooks and, for Paddle, looks up the buyer's email with the Customer's key.

SubprocessorWhat it doesPersonal dataLocation
Contabo GmbHServers that run the hosted serviceAll data in Annex I of the DPAGermany (EU)
Backblaze, Inc.Off-site backups and the database replicaAll data in Annex I of the DPA, as backupsUnited States (us-east-005)
Resend, Inc.Sends license emails to buyersBuyer email address, license key and email contentUnited States (us-east-1)
Cloudflare, Inc.DNS for casazium.com; proxy and TLS termination for the error-report endpoint and Casazium's deployment panelData in transit only. Error reports carry none; through the deployment panel the operator views server logs (with IP addresses) and the databaseGlobal
SimpleLogin (Proton AG)Receives email sent to casazium.com addresses and forwards it to Casazium's mailboxWhatever people email Casazium, including buyer requests and vendors' support messagesGermany, Switzerland, the Netherlands and France
Google LLC (Gmail)Hosts the mailbox that email to casazium.com addresses is forwarded toWhatever people email Casazium, including buyer requests and vendors' support messages. A personal Google account, not yet covered by a data processing agreement (DPA section 3.5)United States and other Google data centers

Casazium's own billing provider (Stripe) and its operator notifications (Discord) receive no buyer personal data, so they are not listed.