Legal

Data processing agreement

Version 1.0, in force from 2026-10-13. This agreement is part of the terms of service between w3center.pl Daniel Miedzik, Ośno 28b, 87-100 Toruń, Poland, VAT PL7231586096 (“Tillcast”, the processor) and the organization that accepted the terms (“the Customer”, the controller). If the Customer is itself a processor for its own customers (for example a software vendor for hotels), it acts for them, and Tillcast is a sub-processor. The Customer confirms it is authorized to instruct Tillcast for them.

1. Scope and roles

  1. This agreement covers personal data in the content that the Customer or its software sends to Tillcast to print (“Customer Data”), and personal data in the settings and records that Tillcast keeps for the Customer.
  2. For Customer Data the Customer is the controller and Tillcast is the processor.
  3. For the personal data of people who sign in to the dashboard (their name, e-mail, sign-in and audit data) Tillcast is an independent controller; see the privacy notice. This agreement does not cover that data.

2. Subject matter and duration

The subject matter is the printing service of the terms. The agreement lasts as long as Tillcast holds Customer Data, which includes the periods in Annex 1 after the contract ends.

3. Nature and purpose of processing

Tillcast receives print jobs from the Customer through its API (once the API is released), stores them until the target printer fetches them, hands them to the printer over HTTPS, records the result, and deletes the content. The purpose is to deliver the Customer’s receipts, tickets and reports to its printers, to bill the service, and to secure and support it. Tillcast does not read the content except as the service needs (rendering, size checks) and does not use it for any other purpose. It also lets an application or an AI agent that the Customer has authorized use the Customer’s account through the API, within the permissions the Customer gave it (section 5, point 4).

4. Types of data and data subjects

See Annex 1. Receipt content is sensitive in practice: it can show a guest’s name, room, the items bought and amounts. The Customer decides what it sends and is responsible for the legal basis, including for special categories of data (Art. 9 GDPR). Tillcast recommends that the Customer prints only what the receipt needs and, where it describes the payment method, no more than the last 4 digits of a card number. This is a recommendation, not a prohibition.

5. Instructions

  1. Tillcast processes Customer Data only on the Customer’s documented instructions: the terms, this agreement, the Customer’s use of the API and dashboard, and written instructions that fit the service. The Customer’s API calls are an instruction.
  2. Tillcast tells the Customer without delay if it thinks an instruction breaks the GDPR or other law.
  3. If law requires Tillcast to process the data otherwise, it tells the Customer first, unless the law forbids that.
  4. An application or an AI agent that the Customer connects to its account (by allowing it on the consent screen of the dashboard) acts on the Customer’s instruction, within the permissions the Customer gave it, as the Customer’s own API call does (point 1). It acts for the Customer, as the Customer’s own processor or as the Customer’s own system, under the Customer’s own arrangements with its provider. It is not a sub-processor of Tillcast: Tillcast does not engage it, and the Customer decides what it may do through the permissions it gives. Data that Tillcast gives to such an application or agent on that instruction, for example the names of customers, locations and printers and the details of jobs, is then handled by it and by its provider, and the Customer answers for the choice and for what is done with that data.

6. Sub-processors

  1. The Customer gives general authorization for the sub-processors in the list and in Annex 3.
  2. Tillcast tells the Customer’s owners by e-mail of a new sub-processor of Customer Data or a replacement at least 30 days before it starts. The Customer may object within 14 days on reasonable data protection grounds. If the parties cannot agree, the Customer may end the contract before the change takes effect, without penalty for the part not used.
  3. Tillcast imposes on each sub-processor the same data protection duties as in this agreement, by contract, and remains responsible to the Customer for them.

7. Confidentiality and personnel

Everyone at Tillcast who may reach Customer Data is bound to confidentiality. Access to production is limited: at the date of this version, only the owner has it. Tillcast operators will have access to organizations’ records through a separate operator sign-in with mandatory multi-factor.

8. Security

Tillcast takes the measures in Annex 2, which the security overview describes, appropriate to the risk (Art. 32). It may change them if the level of protection is not lowered. It reviews them as the service changes.

9. Assistance

Tillcast helps the Customer, with regard to the nature of processing and the information it has:

  1. Data subject requests. Tillcast passes on any request it receives about Customer Data to the Customer without delay and does not answer it itself, unless the Customer asks. Because receipt content is deleted soon after printing and is not searchable by person, Tillcast usually cannot find a person’s data; the Customer holds the original.
  2. Security, breach notification, impact assessments and consultations (Art. 32 to 36).
  3. Evidence. The information needed to show compliance (section 13).

10. Personal data breach

Tillcast tells the Customer’s owners by e-mail without undue delay after it becomes aware of a breach affecting Customer Data, with what it knows: the nature, the data and records concerned, likely consequences, and the measures taken or proposed. It adds details as it finds them. It helps the Customer in notifying the authority and the data subjects.

11. Location and transfers

Customer Data is stored and processed in Ireland. The website’s content delivery network uses locations in North America and Europe but carries no Customer Data. Tillcast does not transfer Customer Data outside the EEA except as the sub-processor list shows, and only with the safeguards of Chapter V of the GDPR.

12. Deletion and return

  1. During the contract. Receipt content is deleted when its job reaches a final state (printed, failed, cancelled or expired). A job is offered for at most 7 days (24 hours by default), plus up to 1 hour while a printer’s confirmation is awaited. As a safety net, the content also expires automatically at the end of that period; the database may carry out this deletion with a delay of some days. Receipt content is not part of backups. Job records without content are no longer returned 7 days after the final state and are then deleted, typically within a few days, and from backups as in point 4.
  2. After the contract. Tillcast keeps the Customer’s data 3 months in case the Customer returns, then deletes it, except the records that back invoices (Annex 1), which Tillcast keeps for its own legal duty as a controller of accounting data.
  3. Return. Customer Data is not stored beyond the periods above. Records the Customer wants can be read through the API while the contract lasts. On request within the 3 months Tillcast will give an export of the Customer’s records in a common format.
  4. Deleted records may remain in backups until the backup window (up to 35 days) ends. Receipt content is not backed up.

13. Audits and information

Tillcast makes available the information needed to show it meets Art. 28: written answers to the Customer’s reasonable questions, the security overview and, for the hosting, the reports that the hosting provider publishes. Tillcast does not offer on-site audits. If the Customer’s supervisory authority requires an inspection, Tillcast cooperates as the law requires. Tillcast holds no security certification of its own at the date of this version.

14. Liability

The liability clause of the terms applies, including its cap.

15. Order of precedence, law

If this agreement and the terms conflict about personal data, this agreement prevails. Polish law applies and the courts named in the terms are competent.


Annex 1: Details of the processing

Item Description
Controller The Customer
Processor w3center.pl Daniel Miedzik (contact: contact@tillcast.com)
Data subjects Whoever the Customer chooses to name on a print: for example hotel guests, restaurant customers, the Customer’s staff, vehicle owners (registration numbers). The Customer decides what is printed; Tillcast, like an e-mail provider, does not control or restrict the subject matter of what its customers write.
Content Receipt documents and print data (text, images, QR codes and barcodes as the Customer composes them) up to 256 KB per job. In practice: names, room or table numbers, order lines, amounts, dates, reference numbers. Special categories of data (Art. 9) are possible incidentally; full card numbers are discouraged (the recommendation is the last 4 digits at most).
Records without content Job id, printer, customer and location ids, media type, size in bytes, status, the printer’s result code, the Customer’s own client_reference_id of a customer, a location, a printer or a job (at most 128 characters, which must not contain personal data), a hash of the idempotency key, and times. Names of customers, locations and printers as the Customer enters them. Printer connection state and hardware status; the printer’s MAC address and user agent; the location’s address and time zone; optional job metadata (up to 10 keys and 1 KB, which must not contain personal data) and warnings; the id of the API key or of the connected application used. For each application that the Customer connected: its name as it was shown, the permissions and the customer limit allowed, the expiry, the times it was allowed, last used and ended, the number of jobs it made, and which person allowed it (the data of that person as a user of the dashboard is dealt with in section 1, point 3). Webhook endpoint addresses (planned). For each printer, the first request of each kind that it makes to Tillcast (its greeting, the way it asks for work, the result it reports, the request in which it asks for a job and the one in which it confirms it; at most seven per printer), as the printer sent it: its headers (among them the public network address of the printer’s internet connection and the host name it called, which carries the code of the Customer’s customer), its query (the number of the job, the printer’s hardware address, the result code) and its body (the model, firmware, serial number, hardware address and status that the printer states), with the time and the status and size of Tillcast’s answer; never the content of a receipt, the content of the answer, or the secret in the printer’s address.
Frequency Continuous, as the Customer sends jobs
Retention of content Until the job is final: printed, failed, cancelled or expired; offered for at most 7 days (default 24 hours) plus up to 1 hour; backstop deletion by database time-to-live as in section 12.1
Retention of records Job records and job events: 7 days after the final state. Printer state events: 3 months. Lifecycle events (printer created, installed, moved, deleted, billable): 1 year. Daily statistics: 90 days; weekly: 1 year; then monthly. Monthly usage records, month closes and monthly statistics (they name printers with their MAC address, customers, locations and the organization, as the Customer typed the names, not people): 7 years from the end of the calendar year of the month. Webhook delivery log (planned): 30 days. Audit log: 90 days. Records of connected applications: while the connection is active, and after it ends 90 days if it was revoked and 30 days if it ran out; a connection with no end date is kept until someone disconnects it, even after the application stops using it. The printer’s first requests of each kind: as long as the printer exists in the Customer’s account; deleted when the printer is deleted (copies in backups as in section 12, point 4). Data of an organization that left: 3 months after offboarding, except the records above.
Location Ireland

Annex 2: Technical and organizational measures

The security overview is part of this annex. In summary: data in the EU, encrypted at rest and in transit; receipt content kept apart, not backed up, deleted when the job is final and never logged; secrets stored only as hashes; isolation between customers; least-privilege access; restricted API keys, roles and an audit trail (planned); strong sign-in with multi-factor for staff; monitoring and alarms; changes only through a tested, automated pipeline.

Annex 3: Sub-processors

See subprocessors.md. For Customer Data: Amazon Web Services (hosting, Ireland).