Privacy policy
What we store, and what we do with it
You are about to tell a website where you have been and, if you choose to, the number on your passport. This page says exactly what happens to that — in the same plain English as the rest of the site, and with no paragraph designed to be skipped.
The short version
- We do not sell your data, and we never will. There is nobody to sell it to who would not make this a worse product.
- There are no trackers on this site. No analytics, no advertising pixels, no third-party fonts or scripts of any kind. Three cookies: the one that keeps you signed in, the one that keeps you signed in between visits if you ask for it, and the one that remembers what you chose about cookies.
- Passport and document numbers are encrypted before they are written down, with a key that is not stored in the database. A copy of the database on its own does not contain them.
- You can have all of it back, or all of it deleted. Ask, and we do it. There is no retention clause designed to keep you here.
Who is responsible for it
MicroWizard operates MyStayDays and is the data controller for everything described on this page.
Anything on this page — a question, a request, or a complaint — reaches a person through the contact form. Choose "my data" on it and it goes to whoever handles that.
What we store, and why
Your account
Your email address, a bcrypt hash of your password, the name you chose to be called, what you named your workspace, your time zone, your role in that workspace, and the time you last signed in. The email address is how you sign in and how we reach you about your own account. We store a hash of your password and never the password itself, which means we cannot tell you what it is — only help you set a new one.
The people you are tracking
For each traveller: their name, the nationalities they hold, optionally their date of birth, and any note you add. Nationality is not decoration — it is what decides whether the 90/180 limit binds that person at all, so the answer cannot be produced without it. Date of birth is optional and only used by rules that depend on age.
Passports and travel documents
The issuing country, the issue and expiry dates, the document's status, and — only if you enter one — the document number. Dates are what let us warn you that a passport will be too old for a trip you have already booked. The number is stored because some people want their records in one place; nothing in the calculation needs it, and leaving it blank costs you no accuracy at all.
Your travel
For each trip: the country, the dates you arrived and left, whether it is completed, booked, planned or cancelled, and optionally why you went. This is the input to every figure the product produces.
Records kept to keep the service safe
We record the IP address behind failed sign-in attempts, new registrations and password reset requests, so that those three things can be rate-limited. Without it, the sign-in form is a free guessing machine and the reset form is a way to flood somebody's inbox. These records are about the request, not about you, and they are not used for anything else.
Messages you send us
When you write to us through the contact form we keep your name, your email address, what you wrote and the IP address it came from, so that we can reply and so that the form cannot be used to flood us. It is also emailed to whoever handles that kind of question. We keep it for twelve months and then delete it, and you can ask us to delete it sooner. Writing to us does not create an account and does not sign you up to anything.
Payment
If you buy the paid plan, the payment itself happens on Stripe's own pages. We never see or store your card number. What we keep is the customer and subscription reference Stripe gives us, and the invoices it issues, so that your account knows which plan it is on and you can find your receipts.
How a passport number is stored
This is the part worth being specific about, because it is the part you would want to know before typing one in.
A document number is encrypted with AES-256-GCM before it reaches the database, using a key held in the application's configuration and not in the database itself. Somebody who obtains a copy of the database — a stolen backup, a dump from a compromised host — has the encrypted bytes and no way to read them.
The last four digits are kept in the clear, deliberately, so that the interface can show you which document it is talking about without decrypting anything. Nothing in the compliance engine ever decrypts a number; it works entirely from countries and dates.
You do not have to give us one. Every figure MyStayDays produces is identical whether the number field is filled in or blank. It is there for people who want their documents recorded in one place, and for nothing else.
Why we are allowed to hold it
- To provide what you asked for. Your account, your travellers, your trips and your documents exist because you entered them so that we could answer a question about them. That is the contract between us.
- To keep the service secure. The rate-limiting records above are kept because running a sign-in form without them would be negligent. This is our legitimate interest, and it is narrow.
- Because the law requires it. Records of payments have to be kept for accounting purposes for as long as tax law says.
Where a traveller you have added is somebody other than you — a family member, a colleague, a client — you are the one who decided to record their details, and you are responsible for having a reason to. We hold that data on your instructions.
Who else can see it
People you share a workspace with
Everyone signed in to your workspace can read the travellers and trips in it. What they can change depends on the role you give them. Nobody outside your workspace can see any of it.
Us, when we are supporting you
Our operators can open a customer's travellers and trips from an internal console. We would rather tell you that plainly than let you discover it. Every such view writes an entry into that account's own audit trail — we cannot look at your travel without leaving a record in your account that we did.
Three suppliers, and no others
The company that hosts the servers, the company that delivers our email — which is only ever password reset messages and messages about your own account — and Stripe, if you pay us. Each of them sees only what their job requires. There is no analytics provider, no advertising network and no data broker in this list, because there is none anywhere in this product.
Your data is stored in the United Kingdom and the European Economic Area.
How long we keep it
Your travel records stay in your account until you delete them or ask us to close the account. We do not expire them on a schedule, because a 180-day window looks backwards and a product that quietly discarded last winter would start giving wrong answers.
Rate-limiting records are kept for as long as the limit they enforce needs them, which is measured in hours. Payment records are kept for as long as accounting rules require. Messages sent through the contact form are deleted after twelve months, which is long enough to find the thread again if the same question comes back and short enough that a support mailbox is not a permanent archive of everybody who ever wrote in.
Closing an account is not yet a button. It is on the list and it is not built, so today you ask us and a person does it — properly, including the travellers, trips and documents, not just the login. We would rather say that than imply a self-service control that does not exist.
What you can ask us to do
Under UK and EU data protection law you have the right to see the personal data we hold about you, to have it corrected, to have it deleted, to receive a copy in a portable form, to restrict what we do with it, and to object to us processing it. You can exercise any of them through the contact form — choose "my data" and say which of them you want.
We will not charge you for it and we will not ask why. We aim to answer within a few days and are required to answer within one month.
If you think we have handled your data badly, please tell us first — but you are entitled to complain to a data protection regulator without doing so. In the UK that is the Information Commissioner's Office.
Cookies, children, and changes
Cookies. One, and it exists to keep you signed in. The cookie page lists it in full and explains why there is no consent banner on this site.
Children. MyStayDays is for adults managing travel. We do not knowingly create accounts for under-16s. A traveller recorded in an account may of course be a child — a family tracking a household will have one — and that record belongs to the adult who created it.
Changes. If we change this policy in a way that affects what happens to your data, we will email the address on your account before it takes effect rather than quietly reposting the page.
This version took effect on .
Still want to ask something?
A real person reads every message the contact form sends. Questions about what we store are the ones we most want to be asked.