Who is responsible
DockCount decides how the data described here is handled. Questions, requests and complaints go to privacy@dockcount.com, and a person reads them.
For the records your team creates inside the product, the relationship runs the other way: your business decides what goes in, and we act on your instructions.
What we hold about people
- Account details. Name, work email address, and a one-way scramble of the password. We never store the password itself and cannot recover it.
- Who did what. Which user signed for which delivery, and when. That attribution is the point of a receiving log, so it stays on the record.
- What you upload. Photographs of packing slips and of damaged goods. A slip sometimes carries a driver's name or signature, which means a photograph of it can carry personal data.
- Billing. Whether the account is paid, which plan it is on, and when it renews. Card numbers go to Lemon Squeezy at checkout and never reach us.
Counting visits: Google Analytics and Microsoft Clarity
Pages here load Google Tag Manager, which loads Google Analytics and Microsoft Clarity. We use them to see which pages people read, which buttons they press, and where signing up gets stuck, so we can make the site easier to use.
Google Analytics records the pages you visit, how you arrived, your rough location from your IP address, your device and browser, and the actions this site reports to it: a click on a main button, how far down a page you scrolled, starting the sign-up form, a form that was refused, creating an account, signing in, and opening or completing a plan checkout. It never receives your name, email address, phone number or anything you typed.
Microsoft Clarity records how pages are used: clicks, taps, scrolling and mouse movement, which it can play back as a recording of the page. The sign-in and sign-up forms and everything behind the sign-in are hidden from it, so a recording shows the shape of the screen and none of what it holds.
If you are in the European Economic Area, the United Kingdom or Switzerland, none of this loads unless you press Accept on the banner. Everywhere else it loads by default. The cookie policy lists exactly what each one stores.
Why we are allowed to hold it
To run the service you asked us to run, which is the contract between us. To keep the service secure and working, which is our legitimate interest and yours. To keep the records the law requires us to keep, which mostly means invoices.
The photograph, and what reads it
On plans that include slip reading, the photograph you upload is sent to Anthropic, which returns the text on it. Anthropic processes it to answer that one request. The image is not used to train a model, and nothing else is sent with it.
On plans without slip reading, the photograph is stored and shown to your team and goes nowhere else. If you would rather no image ever left our systems, say so and we will turn slip reading off for your account.
Who else touches it
Five companies, each doing one job, each named on the subprocessor page with what they do and where they are. All of them are in the United States, so data about your team leaves its home country to reach them.
We do not sell data, and we do not share it with anyone outside that list, except where a court or the law requires it. If that ever happens and we are allowed to tell you, we will.
How long we keep it
Receiving records stay for as long as the account is open, because a receiving log with a hole in it is worse than no log. Close the account and we delete everything within thirty days, apart from invoices, which tax rules make us keep for longer.
Ask us to delete something sooner and we will, unless the law says we cannot.
What you can ask for
These are your rights over your own information, and none of them cost anything to use.
- A copy of it. An admin can download everything their company holds from the settings page, at any hour, without asking us. Ask us instead if you would rather.
- A correction. Most of it you can edit yourself. Tell us about anything you cannot.
- Deletion. An admin can delete the whole company and everything under it from the settings page. It goes; we cannot put it back.
- To object, or to have us stop for a while. Tell us what you object to and why, and we will stop unless the law requires otherwise.
- To take it elsewhere. The download is a machine-readable file, so it can go into whatever you move to.
Write to privacy@dockcount.com and we will answer within thirty days. There is no charge. If our answer does not satisfy you, you can complain to the data protection authority where you live.
Keeping it safe
Passwords are hashed with bcrypt. The session cookie cannot be read by scripts in your browser, and outside local development it only travels over an encrypted connection. Every query is scoped to your organisation at the point it runs, so one business cannot reach another's records even by guessing an address. Uploaded photographs are served only to people signed in to the account that owns them.
If we ever have a breach that puts people at risk, we will tell the affected accounts and the relevant authority, and we will say what happened rather than what we wish had happened.
Children
This is a tool for warehouses. It is not for anyone under 16, and we do not knowingly hold data about children.
Changes
If this policy changes in a way that affects you, we will email the account admins before it takes effect. The date at the top always says which version you are reading.