Legal

Terms of service

Version 1.0, in force from 2026-10-13. These terms are the regulamin under art. 8 of the Polish Act on providing services by electronic means (ustawa o świadczeniu usług drogą elektroniczną). They are available free of charge, before a contract is made, in a form that can be saved and printed.

1. Provider

w3center.pl Daniel Miedzik (a sole proprietorship), Ośno 28b, 87-100 Toruń, Poland, VAT number PL7231586096 (NIP 723-158-60-96), e-mail contact@tillcast.com (“Tillcast”, “we”).

2. The service

Tillcast is a print API for receipt printers. Your software sends a print job to our API, and a printer in your venue that is connected to Tillcast prints it. No VPN and no local server are needed. The service has these parts:

  • the printer connection: a printer is set to a web address we issue, and fetches its jobs from us over HTTPS (Star CloudPRNT and Epson Server Direct Print are supported; the Star mC-Print3 and the Epson TM-m30III are the devices a test page has been printed on so far). The current list of supported models is in the documentation; a model not on it may work, with no guarantee;
  • the public API and its keys, and the connection of apps and AI assistants that people of an organization allow (section 5a);
  • the dashboard for people who manage an organization;
  • the documentation and a status page, and SDKs for TypeScript and Python, which exist as pre-1.0 versions (method names can still change before 1.0).

The service is for businesses only. It is not offered to consumers. When it creates the organization, the person declares that it acts as a business (przedsiębiorca) and uses the service for its business.

An organization may build Tillcast into its own product and offer that product to its own customers (for example a software vendor for hotels). It answers to its own customers, and for us it is one organization (see the DPA for the processing roles).

3. Who may use it, and technical requirements

You must be a business or other organization, acting through a person who may bind it. To use the service you need an internet connection, a current web browser for the dashboard, software that can call an HTTPS API, a printer of a supported model, and a network that lets the printer reach *.print.tillcast.com on port 443. The printer must be set to HTTPS; port 80 is not served.

4. Accounts and organizations

  1. A person signs in with an e-mail address that they prove with a code (and with Google, whose address is proven with a code that we send to it). One proven address is one account.
  2. A person can create an organization (up to 3 per person). A new organization is active at once: it can create keys and invite people from its first minute, and no operator checks it first. By creating the organization the person accepts these terms and the DPA for it, and our records keep who created it and when. We may suspend or end an organization under sections 11 and 12.
  3. The organization is the customer. The person who creates it, and each owner, declares that they may bind it to these terms.
  4. Roles are owner, developer and viewer. An owner invites and removes people and sets roles; the last owner cannot leave, be removed or be demoted. The organization answers for what its members do.
  5. Keep sign-in details safe. Tell us at once about any misuse. We may disable an account that is compromised.
  6. We may refuse or end an account that gives false information or breaks section 7.

5. API keys and printer addresses

  • API keys are restricted: each lists its scopes, and no key gives full access. Keys are created in the dashboard, by a person whose role allows those scopes. Live keys need a fresh confirmation, a code sent by e-mail, before they are created. A key is shown once; we keep only its hash.
  • The web address of a printer contains a secret path. It is shown when it is issued and we keep only its hash. Treat keys, addresses and webhook secrets (webhooks planned) as passwords. The organization is responsible for what is done with them. Revoke or replace one that leaks.
  • We may refuse a request that does not carry a valid key, the token of a connected app or a valid printer address, with no explanation beyond the error.

5a. Connected apps and AI assistants

  1. An owner or a developer of an organization can connect an app or an AI assistant to it, so that the app can use the organization’s account without an API key. A viewer cannot. The person who connects it may be asked to confirm with a code sent to their e-mail address, and chooses what the app may do: only from the permissions of an API key that the person holds themselves, optionally for one customer only, and for the time they pick. An app never gets more than the person who connected it could do.
  2. The connection belongs to the organization. It lasts until it expires or is ended. An owner or a developer can end any connection of the organization at any time, by disconnecting it on the Connected apps page of the dashboard. If the person who connected an app is removed from the organization, or their account is disabled or deleted, the connection stays, until it expires or is ended. If that person’s role is lowered, the permissions of the connection are lowered with it, and a later rise of the role does not give them back.
  3. The organization answers for the apps and AI assistants it connects and for what they do with the permissions they were given, including the jobs they send and the paper they use, as it does for its API keys (sections 5 and 6). It should review the Connected apps page from time to time and disconnect any app it no longer uses or does not recognize. An AI assistant sends what it reads from the account, such as the names of its customers, locations and printers and the details of its jobs, to the company that runs it: the organization chooses the assistant and answers for that choice.
  4. An app and its vendor are not ours. We do not make, check, recommend or supervise an app, and we have no contract with its vendor for the organization’s use of it; the vendor’s own terms and privacy policy apply to what the app does. The name and the label that the consent screen shows for an app do not mean that we vouch for it.
  5. We may refuse to register an app or to connect it, disconnect it, or switch it off for every organization, at once where needed, if it abuses the service, endangers security or breaks section 7. We limit how often apps can register and ask for tokens.
  6. Jobs that an app sends are jobs like any other: the limits of section 7 and the trial limit of section 8a apply to them.

6. What the organization is responsible for

  • The content of what it prints, including whether it meets law on receipts, invoices, fiscal devices and personal data. Tillcast does not make fiscal receipts and does not check content.
  • Not putting personal data in fields marked as not for it (for example the client_reference_id of a job).
  • Receipts can show personal data, including data of special categories (Art. 9 GDPR, such as health or religion, for example a diet or an accessible room). The organization decides what it prints and is responsible for having a legal basis. We recommend that it prints only what the receipt needs, and that, where it needs to describe the payment method, it prints no more than the last 4 digits of a card number. This is a recommendation and good practice, not a prohibition.
  • Having the right to give us the data it sends. The data processing agreement applies to personal data in receipts.
  • Setting up its printers and its network.

7. Acceptable use

You must not: break the law or send unlawful content (the supply of unlawful content is prohibited); attack, scan or overload the service or other customers; try to reach data or addresses that are not yours; get around limits, authentication or suspension; resell the service as a stand-alone product of printing capacity without adding your own software; use it where a failure could endanger life or health.

Limits in force: a document is at most 256 KB; a printer has at most 50 waiting jobs; a job waits for its printer at most 7 days (24 hours by default); the default poll interval is 5 seconds; all the printers of an organization in its free trial print at most 250 jobs in total, for the whole trial, as section 8a says. Limits may change with notice (section 17).

Fair use of prints. Prints are unlimited under fair use: up to 10,000 prints per billable printer per month, pooled across the organization. Printing is never stopped; above that we agree a custom offer. Only jobs that were printed count; the welcome print and test prints do not. There is no automatic charge for prints above that number.

8. Prices

List prices in euro (EUR), net; VAT is added where the law requires it. They are per billable printer per calendar month, counted per organization across all its customers, and graduated: each printer is charged at the price of its band.

Billable printers of the organization in the month Price per printer per month
1 to 4 6.00 EUR
5 to 19 5.75 EUR
20 to 100 5.25 EUR
more than 100 individual offer

Example: 20 printers cost 4 × 6.00 + 15 × 5.75 + 1 × 5.25 = 115.50 EUR, net.

Above 100 printers, each additional printer is charged at the price of the last band (5.25 EUR net), unless an individual offer is agreed.

Billing starts on the day the paid plan starts, which is the day a card is added, during or after the free trial (section 8a). An organization without a card is not billed.

A printer is billable from the day billing starts for it until the end of that calendar month (UTC), or until the day it is deleted if that comes first. In the month the card is added, billing of a printer starts on the later of the day the card is added and the day of its first contact with Tillcast in that month. In later months, it starts on the day of its first contact in that month. The first billable day and the deletion day both count: a printer first contacted on the 10th and deleted on the 20th of a 30-day month is billable for 11 days, if the card was added on or before that 10th. A printer that has no contact with us in a month is not billable in that month. No printer of an organization is billable while its free trial runs (section 8a). Removing a printer is the organization’s duty.

Each day is priced separately. For each calendar day (UTC), we count the organization’s billable printers on that day and price them with the table above, as for a whole month: each printer is charged at the price of its band for that day’s number of printers. The day costs 1/(number of days in the month) of that monthly amount, and the month is the sum of its days. If the number of billable printers is the same on every day of a month, the month therefore costs exactly the table price for that number.

Only jobs that were printed count towards the fair-use number of section 7 and the trial limit of section 8a. The welcome print and test prints do not count. The 5-second poll is included. A shorter poll interval (down to 1 second) and an own printer domain are extras with a surcharge agreed individually on request.

A change of the price list applies from the first day of the next month, so a month is never priced with two price lists. A price increase also follows section 17.

8a. Free trial

  1. An organization can add and use many real printers free of charge for 1 month, counted from the day its first printer connects to Tillcast (the free trial). The trial belongs to the organization and covers its printers during that month, except as point 9 says. No payment card is needed to start. An organization that already has a card when its first printer connects has no free trial: its printers are billed as section 8 says.
  2. During the trial, the organization has one limit for all its printers together: at most 250 jobs in total, for the whole trial. Only jobs that were printed count; the welcome print and test prints do not. A job above the limit is refused, with a message that asks for a card. The fair-use rule of section 7 is for billable printers and does not apply to the organization’s printers during its trial.
  3. Every job printed in the trial, on every printer of the organization, ends with the line Test print · tillcast.com (a hyphen stands in for the dot on a printer that cannot print it). The line cannot be switched off.
  4. The trial ends after that month, or earlier on the day a card is added. An organization can add a card before the trial month ends, to start the paid plan early: the trial ends that day, the line in point 3 stops, and billing starts that day (point 7).
  5. A card is asked for only when the limit in point 2 is exceeded, when the trial month is over without a card, or in the cases of point 9. Apart from point 9, it is never asked for at the first printer or at its first print. The organization gives its company data in the same step as the card: legal name, address, country and tax ID.
  6. If the trial month is over and there is no card, printing is blocked on all the organization’s printers until a card is added.
  7. Billing starts on the day the paid plan starts, which is the day a card is added, during the trial or after it. An organization without a card is never billed: nothing accrues during the trial, after it while printing is blocked on all its printers (point 6), or after its printers are switched off (point 8). Once a card is added, each of its printers is billed like any other printer, by calendar day (section 8): in the month the card is added, from the later of that day (that day included) and the printer’s first contact in that month; in later months, from the printer’s first contact in that month.
  8. 30 days after a trial has ended without a card, we switch off each printer of the organization by disabling its web address (section 5). The dashboard tells the owners before we do.
  9. There is one free trial per organization and per person, and a printer that was already part of a trial is not covered by another one. A printer is recognised by its hardware address or serial number. If the rule on the organization or the person applies, there is no free trial: printing on the organization’s printers is blocked until a card is added. If the rule on the printer applies, that printer is not covered: printing on it is blocked until a card is added, while the organization’s other printers go on under its trial.

9. Billing and invoicing

  1. We keep a usage record for every billable printer and close each month shortly after it ends (from 00:15 UTC on the 1st). Invoices are based on these records.
  2. After the end of each month the organization’s card is charged automatically for that month. Card payments go through Stripe (planned). We issue the invoice in wFirma, our invoicing system, and send it by e-mail to the organization’s owners. Invoices are issued as the law requires.
  3. If a payment fails, we tell the owners by e-mail and retry the payment. A payment more than 7 days overdue can lead to suspension (section 11).
  4. VAT. Prices are net. For an organization in Poland, VAT is added. For a business in another EU state with an EU VAT number confirmed in the EU VAT Information Exchange System (VIES), the reverse-charge rule applies and the invoice carries no VAT. If the number cannot be confirmed, Polish VAT is added; if it is confirmed later, we issue a correcting invoice.
  5. There is no minimum fee. The organization pays only for billable printers (section 8). The free trial is in section 8a.
  6. Complaints about an invoice: section 16.

10. Availability

We aim to keep the service running, but we do not promise an uptime level: there is no service level agreement. Our target is 99.9% availability of the printer connection per calendar month. It is a target only; missing it gives no claim to a refund or damages. We may stop the service briefly for maintenance. Printers fetch jobs by polling, so a job reaches a printer only while the printer is switched on, connected and polling. Delivery is at least once: if the printer’s confirmation is lost, a job may print twice, because we prefer that to losing a receipt. A job that its printer does not fetch before it expires is not printed. The organization’s software should read the job status and handle the cases. The status page shows incidents.

11. Suspension

  • For non-payment: if the organization does not pay, we may suspend it. All its printers are cut off at once; the organization keeps read access to the API and access to the dashboard, but cannot create or change anything and cannot send new print jobs. When it pays, printing works again within minutes (DNS caches in the printers can delay it). Jobs waiting at that time stay until they expire, and print only if access returns first. We suspend only after the payment is 7 days overdue, and we first send an e-mail to the organization’s owners at least 3 days before. You can ask that a person reviews the suspension.
  • For a breach of section 7, or a security risk: we may suspend an account, key, connected app, printer, customer or the organization, at once where needed, and tell you why.
  • An organization can pause a single location; its printers are then refused and not billed.

12. Ending the contract, data retention and deletion

  1. The contract is for an indefinite period. The organization may end it at any time by removing its printers and asking us to close the organization. The organization may end the contract at any time with effect at the end of the calendar month. We may end it with 30 days’ notice, or at once for a serious breach.
  2. After offboarding we keep the organization’s data for 3 months in case it returns, then delete it. We keep longer only: lifecycle events (1 year); monthly usage records, month closes and monthly statistics (7 years, counted from the end of the calendar year of the month), because they back the invoices.
  3. Receipt content is kept only until the job is printed, failed, cancelled or expired (at most 7 days, plus up to 1 hour while the printer’s confirmation is awaited), and is then deleted; the database may remove the stored item physically some days later. Receipts are not part of backups. Job records without content are kept 7 days. There is no option to keep data longer, not even for a fee.
  4. Retention of other data is in the privacy notice and the DPA. On request we return the data we hold as an export in a common format.

13. Personal data

For the personal data of people who use the dashboard, we are the controller (see the privacy notice). For personal data in receipts, we are the processor, and the DPA is part of these terms. Sub-processors: list. Security measures: overview.

14. Intellectual property

The service, the documentation and the SDKs belong to us or our licensors; open-source parts keep their licences (for example Apache-2.0 for the receipt preview package, planned). You get a non-exclusive right to use the service during the contract. You keep all rights to your content and give us the right to process it to run the service.

15. Liability

  1. We answer for damage caused by our fault, under Polish law.
  2. We are not liable for lost profits.
  3. Our total liability in any period of 12 months is limited to the fees the organization paid in the 12 months before the event.
  4. We are not liable for events outside our control, for failures of the printer, the network or a third party’s service, for the content of what is printed, for what an app or AI assistant connected by the organization does with the permissions it was given, or for a print that is delayed or doubled as described in section 10.
  5. The limits do not apply where the law does not allow them, in particular for intentional fault.

16. Complaints

Send a complaint to contact@tillcast.com, with the name of the organization, the description and what you ask for. We answer within 30 days of receiving it. Disputes are not subject to consumer out-of-court schemes, because the service is for businesses.

17. Changes to the service and the terms

We may change the service and these terms for important reasons: a change of law or of the requirements of a provider we depend on, security, a change in the technology or in the cost of running the service, or the addition or removal of features. We will tell the organization’s owners by e-mail at least 30 days before the change takes effect. A price increase applies from the first month that begins after the 30-day notice. If you do not accept a change, you can end the contract before it takes effect.

Breaking changes to the REST API. A breaking change to the REST API (/v1) takes effect no earlier than 6 months after we tell the organization’s owners by e-mail, and a version date that a newer one has replaced stays available for at least 12 months. This promise covers only the REST API at /v1: the MCP server (/mcp) is not covered. For every other change, including a change of the limits in section 7 and the enforcement of a rate limit, this section keeps the 30 days above.

18. Governing law and courts

Polish law applies. The competent court is the court for the seat of the provider, in Toruń.

19. Final

If a part of these terms is void, the rest stands. Contract language: English. Contact: contact@tillcast.com.