Your data
Where your data lives, and what happens to it.
FloorLogik holds your customers' names, addresses and telephone numbers, photographs your fitters take in their homes, and what every one of them paid. That is not data to be vague about, so this page says where it sits, who else can reach it and how long we keep it.
LAST REVIEWED 8 SEPTEMBER 2026
Whose data is whose
Your customer list is yours. We just hold it.
You decide who goes into FloorLogik and what you record about them. We hold it on your behalf and act on your instructions. In the language of UK data protection law you are the controller of your customer records and we are the processor.
Your own account is the other way round. Your staff's names and logins, what you pay us and what you have emailed us about are ours to look after and ours to explain, and that is the second half of this page.
WE NEVER DO THIS
Sell your data, share it with another retailer, use your customer records to train anything, or use them for our own marketing. Your list is not a product we have.
AND NOR DOES THIS WEBSITE
No analytics, no advertising pixels, no tracking cookies, no cookie banner to click away. The only third party this page reaches is Google Fonts, for two typefaces.
Where it is stored
On one server, in London.
Not spread across a dozen cloud services. FloorLogik runs on a single dedicated server in a London data centre, managed by us rather than rented from somebody else, with the database on the same machine. It never leaves the United Kingdom, every connection to it is encrypted, and it is backed up every day.
| What we hold | Where it sits | For example |
|---|---|---|
| Your customer records | Database, London | Names, addresses, telephone numbers, email, your notes on the job |
| Quotes, orders, invoices and payments | Database, London | What was sold, what it cost, what has been paid |
| Photographs and documents | Disk on the same server | Job photographs, product images, your logo on a quote |
| Your staff's accounts | Database, London | Name, email, telephone, scrambled password, when they last logged in |
| An audit trail | Database, London | Who changed a record, what it said before, and the address they did it from |
| Enquiries from this website | Database, London | What you typed into the contact form, and the address you sent it from |
Who else touches it
Four companies, each doing one job.
Nothing else. Where a specialist does something better and more safely than we could ourselves, we use one, and this is the whole list.
| Who | What they do | What reaches them |
|---|---|---|
| Stripe | Card payments, both your subscription to us and, if you switch it on, your own customers paying you | The amount, the reference and the payer's email. Card numbers are typed on Stripe's own page and never reach us |
| SMTP2GO | Sends the email the system sends for you | Anything in that email - a quote, an invoice, a payment link, and the address it goes to |
| OpenAI | The product assistant, if your staff use it | The question typed and the product information it needs to answer. Your customer records are not sent to it |
| Slack | Alerts us when something breaks | The technical detail of the error, which can quote part of the record being worked on at the time |
IF WE EVER ADD A FIFTH, THIS PAGE CHANGES BEFORE IT GOES LIVE.
How it is protected
Separated in code, not by good intentions.
ONE SHOP CANNOT SEE ANOTHER
Every question the system asks the database is narrowed to your business before it runs, by the framework itself rather than by each screen remembering to. A screen that forgot would still return nothing.
PASSWORDS
Stored scrambled, one way, so nobody here can read yours - including us. A reset sends a single-use link that expires.
NOT EVERYONE SEES EVERYTHING
A fitter on site sees the job and the address. Cost prices, margins and the customer's account are for the people you give those permissions to.
EVERY CHANGE IS RECORDED
Who changed a record, when, and what it said before. Useful when a price is queried, and the only honest way to answer "who deleted that".
ENCRYPTED IN TRANSIT
Everything between your browser and the server, and everything the system emails on your behalf, travels over an encrypted connection.
BACKED UP EVERY DAY
A daily copy, so a failed disk or a bad afternoon is an inconvenience rather than the end of your customer list.
How long we keep it
Kept while it is useful. Deleted when it is not.
Nothing here is kept "just in case" for ever. Where the law sets the clock, we say so.
| What | How long | Why that long |
|---|---|---|
| Your customer records, quotes, orders and photographs | WHILE YOU SUBSCRIBE | They are your working records. Deleting a customer in the app hides them first and keeps their history, so a wrong click is not permanent |
| Everything, after you leave | 30 DAYS | Long enough to change your mind or ask us for a copy. Then permanently deleted |
| Our invoices to you, and what you paid us | 6 YEARS | UK company and tax law requires it, and it applies to us whether you stay or go |
| Enquiries sent through this website | 12 MONTHS | A sales conversation that has gone nowhere in a year is over |
| Technical logs and error reports | 30 DAYS | Long enough to find the cause of a fault, short enough that they are not a second copy of your data |
What you can ask for
Any of this, by email, and we do it.
Email hello@floorlogik.com and we answer within a month, usually the same week.
If one of your own customers asks you for their data, the answer lives in your account and you can send it yourself. If you would rather we pulled it out, ask.
Yours, your staff's, or your whole database as a file.
Anything wrong, put right.
Of a record, or of everything. We will tell you what we are legally required to keep.
To us first, and to the Information Commissioner's Office at ico.org.uk if we have not put it right.