Instnt Print

Privacy policy

11 September 2026

Instnt Print prints labels and receipts on behalf of the businesses that use it. That means personal data reaches us in two very different ways, and this policy keeps them apart, because your rights differ per case. We process personal data under the General Data Protection Regulation (GDPR).

1.Who is responsible

Instnt Print, registered with the Dutch Chamber of Commerce under number 59580577, is the controller for the data described under “Your account” below. You can reach us at hallo@instntprint.com for any question about privacy; we answer within one month.

Statutory name and registered address: to be completed.

2.Two roles, kept apart

For your account — your name, your e-mail address, your company details — we decide what happens, so we are the controller.

For what you print we are not. A shipping label carries the name and address of your customer; we never asked for that data and we do nothing with it beyond turning it into ink. There we are a processor, working on your instruction. If someone whose address is on one of your labels asks us a question, we refer them to you — we are not allowed to answer for you.

3.The website

  • Visit counts. One message per page view: which page, and which site sent you here. No cookie, nothing in your browser, nothing that sets you apart. Deleted after 90 days.
  • Google Analytics, only with your consent (art. 6(1)(a) GDPR), with IP anonymisation. Withdraw it at any time via cookie preferences.
  • Server logs. Our hosting keeps short technical logs — address, time, requested page — for security and stability. They are not used to profile visitors.

4.Your account

To use the service you need an account. We store your name and e-mail address, your password as a hash we cannot read back, which team you belong to and what you are allowed to do there. Alongside that, whatever you fill in under “My company” — address, VAT and Chamber of Commerce number, IBAN — which exists so it can be printed on your own receipts and invoices.

The basis is the performance of our agreement with you (art. 6(1)(b) GDPR), and for the invoicing details our legal obligation to keep records (art. 6(1)(c)).

5.What you print

A print job holds the values you send, the bytes that went to the printer and a small picture of the result. That is there so you can see afterwards what actually came out — not what the template says today, but what was on the paper then.

Remove a job from your list and exactly those three parts are deleted: the values, the picture and the print bytes. The row itself stays, without content, because your invoice is counted from it — a cleanup that quietly lowered your own usage would be a different kind of problem.

6.Printers, bridges and keys

We store which bridges and printers belong to your team, their serial numbers and when they were last seen, so the dashboard can tell you something is offline. API keys are stored so calls can be attributed to your team. Saved Wi-Fi networks contain a network name and a password that is meant to be printed on a card for guests — see the note in the dashboard: that field is not a place for a password that actually protects something.

7.How long we keep things

  • Visit counts: 90 days.
  • Analytics data at Google: at most 14 months.
  • Your cookie choice: 12 months, in your own browser.
  • Account and company details: as long as you have an account, and after that only what the tax authority requires us to keep (7 years for invoicing records).
  • Print job content: until you remove the job, or until you close your account.

8.Who else sees it

We do not sell data, and we do not trade it. We share it only with parties that carry out a necessary part of the service for us, under a processing agreement: our hosting provider, the service that sends our e-mail (password resets, invoices), and — only with your consent — Google Ireland Ltd. for Analytics. Where Google processes data outside the European Economic Area, that happens under the EU-US Data Privacy Framework.

We can see your data ourselves, but not casually. A small, named group of our own people has a support screen that looks across teams: which accounts exist, which organisation they belong to, when someone last signed in, and which bridges and printers are attached. We need that to answer the question that comes in most often — "I cannot sign in any more." What you print is not in it.

Three things bound it. Who may use that screen is set in the server configuration, not in a setting anyone can switch on. Every query is recorded with the name of the person who made it. And signing in as you is not possible — the most we can do is send you a link to your own address, so you set your own password and we never see it.

Hosting provider and e-mail service by name: to be completed.

9.How it is secured

  • Everything travels over an encrypted connection (TLS).
  • Passwords are stored as a hash, never as text, and cannot be read back by us.
  • Every query is limited to your own team. That is not a setting but the shape of the code, and there are tests that check a second team sees nothing of the first. The one exception is our own support screen, described above.
  • What a person may do is tied to their role: reading, printing, designing and managing are separate.

10.Your rights

You have the right to see what we hold about you, to have it corrected or deleted, to limit or object to processing, to receive it in a common format, and to withdraw a consent you gave earlier. Write to hallo@instntprint.com and we answer within one month.

If your data reached us because a business printed a label — an address on a parcel, a name on a badge — then that business decides, not us. We will point you to them, and help them answer you.

You can also lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

11.Changes to this policy

When the service changes, this page changes with it, and the date at the top says when. If a change means we would do something with your data that you have not agreed to, we ask you first.

cookie policy