Legal

Privacy notice

Version 1.3, in force from 2026-10-21. This notice is given under Article 13 of the GDPR (Regulation (EU) 2016/679) to visitors of the Tillcast website and to people who use the Tillcast dashboard.

1. Who is the controller

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. This is also the contact for all privacy requests. There is no data protection officer.

2. What this notice covers, and what it does not

It covers:

  • the website tillcast.com and www.tillcast.com;
  • the dashboard dashboard.tillcast.com: the sign-in screens and the pages where people manage an organization, its members, its API keys and the apps connected to it, and the page where a person allows an app to connect;
  • invitations to join an organization (section 9);
  • e-mail you send us;
  • the requests that the printers of an organization make to our servers, as far as they say something about a person: the network address of the place where a printer is, and what a printer says about itself (section 3, “What a printer sends first”).

It does not cover receipt data that an organization sends to print. For that data the organization is the controller and Tillcast is its processor under the data processing agreement. If you are a guest, a customer or an employee of an organization that uses Tillcast, contact that organization first.

The documentation site docs.tillcast.com is hosted by Fern, which runs its own usage analytics there and sets a cookie in your browser for it.

3. What we process, why, and on what basis

Data Purpose Legal basis
Website visit. Your IP address and the technical details of your request reach Amazon CloudFront, which serves the site. We do not store access logs of the website at the moment; CloudFront access logs (with the IP address) are planned and will be kept 90 days. Delivering the page; security of the service Art. 6(1)(f), our interest in a working and secure site
Account. Name, e-mail address (proven by a code), the sign-in method (password, or Google; if you use Google, also the identifier that Google gives your Google account, which our sign-in provider keeps as part of your user name), multi-factor settings (an authenticator app, optional; passkeys (planned); never a phone number), the date of creation and the day you were last seen. Your password is handled by our sign-in provider (AWS); our own database does not hold it. Creating and running your account; signing you in Art. 6(1)(b), the contract for the account
Membership. The organizations you belong to and your role (owner, developer, viewer); who invited you; the API keys you created (their record, never their secret). Access control inside an organization Art. 6(1)(b)
Connected apps. When a person allows an app or an AI assistant to use an organization’s account, we keep a record of the connection: the name under which the app was shown, the host it returns to, the permissions and the customer limit that were allowed, the organization, the expiry, the user id of the person and a copy of their e-mail address, and the time. Later the record also holds when the app was last used, how many print jobs it made and, if the connection ends, when, by whom and why. The tokens of the app are kept only as hashes. When the app takes an action in the account (for example it creates a customer), the audit entry of the organization names the app and the person who allowed it. An app that registers itself leaves a registration (the name it chose, the addresses it returns to and the permissions it may ask for: no personal data), and we count the registrations that come from one IP address in each hour, to stop abuse: the counter holds the address. Beyond what the API keeps for any call, we keep nothing of what an app sends or reads. Letting an organization connect apps to its account and see and end each connection; security; proving who allowed what; stopping abuse of the registration Art. 6(1)(b) for the connection you ask for; Art. 6(1)(f) for security, accountability and the counter
E-mail codes. For a password account, the sign-up code is sent and held by our sign-in provider (AWS). For a Google profile, and for approving a sensitive action such as creating a live API key or connecting an app, we send a 6-digit code to your address. The address on a Google profile is one that can be edited, so Google’s word does not prove it; the code we send to that address does, once you type it. We keep no code and no address in the clear, only keyed hashes and counters: a keyed hash of the code (it works for 15 minutes and once, and is deleted when it is used), a keyed hash that records which Google profile proved which address (it works for 1 hour and is deleted when your account is set up), counters of attempts and of codes sent for the profile, the times of the codes sent to a mailbox (as a keyed hash of the mailbox) and a count of the codes of the day. A hash that is not used stays in the record of the profile until that record ends (section 7). Someone else can make us send a code to your address by typing it into their own profile; the e-mail says to ignore a code you did not ask for, and never to share one. Proving that the address is yours; preventing abuse Art. 6(1)(b) and (f)
Audit entries of an organization (members, roles, invitations, API keys, connected apps, suspension) and a security log of your own account (e-mail proven, failed codes, lockouts, deletion): the time, the action, your IP address, your browser’s user agent, a request id and, in audit entries, a snapshot of your e-mail address. Security, investigating abuse, proving who did what Art. 6(1)(f)
Application logs. Request ids and error lines of our servers. They do not hold e-mail addresses in the clear (only keyed hashes), tokens, codes or receipt content. For a printer that does not work we can switch on, for a limited time, a detailed log of the requests that the printers of one maker make: while it is on, the headers and the bodies of those requests (what section 3 describes under “What a printer sends first”) are written to the log as well, and kept as long as the log is. Operating and fixing the service Art. 6(1)(f)
Analytics. On the website: the address of the page with the campaign parameters (utm_...) of the link you followed, the page you came from, the browser’s user-agent text and language, the screen and window size, the time zone, the time, random identifiers of the visit that live only in the memory of the page, and a click on the buttons “Sign up” and “Sign in”. In the dashboard: the same for the page on which you open it, and, once you are signed in, your account id (never your name or e-mail address), the id of the organization you work in, and that you created an account, an organization, an API key or a printer, that a printer came online or that a job was printed. Never: receipt content, a name, an e-mail address, a printer’s address, an API key or a label. Section 4 says how. Knowing where visits come from and whether they lead to an account, and whether setting up a printer works Art. 6(1)(f), our interest in understanding and improving how the service is found and used
What a printer sends first. For every printer that an organization connects, the first request of each kind that the printer makes to our servers: its greeting when it first connects, 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 the job. There are at most seven kinds, so at most seven requests are kept per printer, and a later request of the same kind is not kept. Each one is kept as the printer sent it: its headers (among them the public network address of the internet connection of the place where the printer is, as our load balancer reports it, the name the printer gives itself, and the host name it called, which carries the code of the organization’s customer), its query (the part of the address after the question mark: in a request for a job or a confirmation it carries the number of the job, the hardware address of the printer and the result code), its body (a printer may state in it its model, its firmware, its serial number, its hardware address and its status), the time, and the status and the size of our answer. The number of a job named in a kept request stays with that request after the job itself is gone. Never kept in it: the secret in the printer’s web address (it is replaced before anything is stored), the content of any receipt or any message or document of a customer (a printer’s greeting and polls carry none), and the content of our answers to the printer. To recognise what kind of printer it is, which model, and which protocol it uses, and to help the organization when the printer does not work Art. 6(1)(f), our interest in a service that works with the printers customers connect, and in helping them when one does not
E-mail sent by Tillcast. Sign-in codes, invitations, security notices, and notices to the owners of an organization about the apps connected to it. Invitations and our own notices are sent through our e-mail provider (AWS); the sign-in and password-reset e-mails are written and triggered by the sign-in provider (AWS) and are sent through the same e-mail provider, from the same sender address. Providing the service Art. 6(1)(b)
Your e-mail to us. The message, your address and any details you send. Answering you Art. 6(1)(f), or Art. 6(1)(b) if you ask about a contract
Invoices and accounting records of the organization you act for (names and contact details of the people on the invoice) (invoices issued in wFirma; card payments through Stripe (planned)). Invoicing, tax and accounting duties Art. 6(1)(c) and (f)

We do not use the data above for marketing and we do not sell it.

Required or optional. The account data is needed to create an account. Without it we cannot give you access to the dashboard.

4. Cookies, browser storage and analytics

  • Cookies. The website sets no cookies. The dashboard’s own code sets none. Analytics (below) sets none. The documentation site is hosted by Fern, which sets a cookie for its own analytics (see section 2). There is no cookie banner for the website.
  • Browser storage. The website keeps only your choice of light or dark theme and, on the blog, the code language or product you picked, in the browser’s local storage, on your device, and sends it nowhere. The dashboard keeps your sign-in tokens in localStorage of the device until you sign out or the 14-day refresh token expires, the id of the organization you are working in (per tab, and the last one used on the device so a new tab can start with it), a pending invitation token, the page to return to after sign-in, and your choice of light or dark theme. This is needed to give you the service you asked for or is a setting you chose. Tokens go to our sign-in provider and to our API; the organization id goes to our API in a header; an invitation token goes to our API when you accept. Analytics writes nothing to your device.
  • Analytics (PostHog). The website and the dashboard use PostHog, in its EU Cloud (Frankfurt), to count visits and what leads from a visit to an account (section 3 lists what is counted). The library is part of our own pages: it is not loaded from PostHog, and your browser sends the counts to PostHog’s server in the EU and to no other. It uses no cookie and writes nothing to your device (no local or session storage): it keeps what it knows in the memory of the page you have open, so a new page, or a reload, is a new visit to it. It does not read your IP address into the counts: we have switched on the setting of our PostHog project that discards it. A browser that sends “Do Not Track” is not counted. Nothing you type is sent. PostHog acts as our processor (section 5). No advertising or other tracking tool runs on the website or in the dashboard.

5. Who receives your data

Recipient Role Why
Amazon Web Services (AWS) Processor Hosting, sign-in, e-mail and delivery of the website. See the sub-processor list.
Google Independent controller for its own sign-in, and our provider of identity Only if you choose “Sign in with Google”. We receive your e-mail address, your name and the identifier that Google gives your Google account; not your picture or anything else. Google learns that you sign in to Tillcast.
Fern Processor Hosts the documentation site.
PostHog (PostHog Inc.; EU Cloud, Frankfurt) Processor Product analytics of the website and the dashboard (section 4). See the sub-processor list.
Stripe (planned) Our processor for billing, and a controller for its own payment processing Card payments.
wFirma (Web INnovative Software sp. z o.o.) Processor Issuing invoices; sees the data on invoices. Data stored in the EU. See the sub-processor list.
Our accounting office Processor Bookkeeping; sees invoices.
Google (Google Workspace) Processor Receiving e-mail that you send us at contact@tillcast.com.
Other people in your organization Recipients Members see each other’s name, e-mail and role in the member list. The people who can open the Connected apps page see each connection with the name or e-mail address of the person who allowed it and the date. Owners see the audit entries of the organization once that screen exists (planned). Tillcast operators (our staff, through a separate sign-in with mandatory multi-factor) can suspend organizations, disable people and delete accounts on request.
Authorities and courts Recipients When the law requires it.

What a printer sends first (section 3) is read only by Tillcast operators, to recognise a printer or to help with a fault, and by the hosting provider as the processor that stores it. It is not shared with anyone else.

6. Transfers outside the EEA

We store account data in Ireland. Some functions run elsewhere:

  • The website is served by a content delivery network from locations in North America and Europe, so your IP address and request are handled near you, possibly outside the EEA.
  • The events of analytics are stored in the EU, in PostHog’s EU Cloud (Frankfurt).
  • If a provider named in section 5 processes personal data outside the EEA, the transfer rests on the European Commission’s adequacy decision for the EU-US Data Privacy Framework (where the provider is certified) or on standard contractual clauses.

You can ask us for a copy of the safeguards (section 11).

7. How long we keep it

Data Kept
Account (name, e-mail, memberships) While the account exists. On deletion only a tombstone with the user id and the state “deleted” remains.
Sign-in identity tombstone after deletion 30 days, so that a token that is still valid cannot create the account again
Sign-up that never proved its e-mail At most 30 days after the last code; unconfirmed profiles at the sign-in provider at most 7 days
E-mail code for a Google profile (keyed hash) It works for 15 minutes; deleted when it is used. One that is not used is deleted with the record of the profile (below)
Proof that a Google profile typed the right code (keyed hash of the profile and the address) It works for 1 hour; deleted when the account is set up. One that is not used is deleted with the record of the profile (below)
Record of a Google profile that asked for codes and did not set up an account (hashes, counters, times) Until 30 days after its last code, or until its account is set up
Times of the codes sent to a mailbox and the count of a day’s codes (keyed hashes, no address) 2 days
Invitation Valid 7 days; deleted at most 7 days after it ends. A hash of the address stays for “do not invite me again” until you ask us to remove it, because it is the only way to honour that request
Audit entries of an organization (with the e-mail snapshot) 90 days, also after a member’s account is deleted (the entry then shows “Deleted user”)
Security log of your account (IP address, user agent, request id) 90 days, or until your account is deleted
Connection of an app (with the copy of your e-mail address) While it is active; 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 app stops using it. Also after your account is deleted.
Registration of an app that registered itself 30 days if no connection of it is ever made; once one is, until 90 days after the app was last used
Tokens of an app; a request to connect that nobody approves; the counters of registrations per IP address An access token works for 1 hour. A refresh token works until the connection ends or the app has not used it for 90 days, and the record of one that was replaced is kept until its own 90 days are over, so that its reuse is noticed. A request to connect works for 10 minutes and a counter covers one hour. The database removes a record an hour after the end of its time, which can take some days more
Counters of e-mail codes sent 2 days
Application logs of the printer path (the detailed log of printer requests, while we have it switched on, included) 7 days
Analytics events (section 3) 12 months
What a printer sends first (section 3) As long as the printer exists in the organization’s account. It is deleted when the printer is deleted; copies in backups go as below.
Backups Up to 35 days. Deleted personal data can remain in backups until that window ends.
Website access logs Not stored now. When CloudFront standard logs are switched on (planned): 90 days.
Your e-mail to us 3 years from the end of the matter
Monthly usage records, month closes and monthly statistics (they name printers, customers, locations and organizations as typed by the organization) 7 years, counted from the end of the calendar year of the month, also after an account or organization is gone
Invoices and accounting records 7 years, counted from the end of the calendar year

8. Automated decisions

We do not make decisions about you based solely on automated processing that produce legal or similarly significant effects, and we do not profile you (analytics, section 4, counts what people do in the service; it decides nothing about anyone). Technical limits apply automatically to protect accounts, for example a lockout after repeated wrong codes. If an organization is suspended automatically for non-payment, you can ask that a person reviews it: write to contact@tillcast.com.

9. If you were invited to an organization (Art. 14)

An owner of an organization can invite you by e-mail. We then hold your e-mail address, the role offered and the identity of the person who invited you, until the invitation is accepted, revoked or expired (section 7). The source of the address is that owner. The invitation e-mail names us as controller, links to this notice and offers “do not invite me again” (planned: the invitation e-mail does not do this yet, and the route behind it is not built). We use the address only to send and check the invitation (Art. 6(1)(f)). An invitation does not prove that the address is yours; you must confirm it when you sign in.

10. Your rights

You have the right to access your data, to have it corrected or erased, to restrict or object to processing (where we rely on legitimate interest), to data portability (where the basis is contract) and, where processing rests on consent, to withdraw it. The right to object to processing based on Art. 6(1)(f) applies for reasons relating to your situation.

11. How to exercise them

Write to contact@tillcast.com from the address of your account. To protect your account we may ask you to confirm a request with a code sent to that address. We answer within one month (Art. 12(3)); we may extend it where the law allows. Account deletion is done by us on request for now; self-service deletion is planned.

12. Complaint

You may complain to the supervisory authority: Prezes Urzędu Ochrony Danych Osobowych (UODO), ul. Stawki 2, 00-193 Warszawa, https://uodo.gov.pl. You may also complain to the authority of your own country.

13. Changes

We will publish a new version with its date. For a material change to how we use your data we will tell account holders by e-mail.