Legal
Privacy Policy
This policy explains how VisualiseO Limited(“Visualiseo”, “we”, “us”) handles personal data when you use our website, our dashboard, or the visualisation widget we provide to retailers. It is written to meet our obligations under the UK GDPR, the Data Protection Act 2018, and the Data (Use and Access) Act 2025.
VisualiseO Limited is a company registered in England and Wales (company number 17171606) with its registered office at 27 Beverley Close, Normanton, WF6 1BU.
Last updated: 9 November 2026
1. Who this policy applies to
There are three groups of people whose data we may process:
- Retailers and other business customers who hold an account with us and subscribe to our service.
- End userswho interact with the Visualiseo widget embedded on a retailer's website — for example, to upload a photo of a space and generate a product visualisation.
- Website visitors who browse visualiseo.co.uk without signing up.
The rules that apply to you depend on which of these you are.
2. Our role: controller, joint controller, or processor
Data protection law treats the person who decides why data is collected (the controller) differently from the person who processes it on their instructions (the processor). Where two organisations jointly decide the why and how, they are joint controllers under Article 26 UK GDPR. Our role changes depending on the context:
- For retailer account data (your name, email, company, payment records) we are the controller.
- For photos uploaded by end users through a retailer's widget in order to generate a render, the retailer is the controller and we are the processor acting under a Data Processing Agreement (see /dpa).
- For the public gallery at visualiseo.co.uk, we are the sole controller. Sharing to the gallery stopped on 9 November 2026 and retailers no longer run their own galleries; renders shared before then are shown only in our gallery. Where a render was shared through a retailer's widget, we and the retailer were joint controllers while its gallery ran (see /legal/joint-controller-summary).
- For the Save feature on the result screen — where an end user leaves an email address or phone number so the retailer can send them their render, and those details and the render are passed to the retailer as a sales lead — the retailer is the controller and we are the processor acting on their behalf (see section 6).
- For the chat and quote assistantthat a retailer embeds on their own website — the conversation itself, any name, email address or phone number you give, and your answers to the retailer's quote questions — the retailer is the controller and we are the processor, acting under the same Data Processing Agreement. The retailer receives the conversation as a sales enquiry and handles it under their own privacy notice.
- For a quote you ask for on our own pages, we are the sole controller — there is no retailer behind it. If you consent, we pass your details to worktop companies who buy the enquiry as a lead. Each of those companies is an independent controller from the moment they receive your details: they are not our joint controllers and not our processors, and they answer to you separately under their own privacy notice. See section 6.
- For our own server logs, security telemetry, and aggregate usage statistics about the widget, we are the controller.
- For renders generated through a demo or free visualiser that we host on our own site(for example the “try it” tool on our homepage or our free flooring and worktop visualiser pages), there is no retailer involved — so we are the sole controllerof everything you do there, including the photo upload and render, the short-lived rate-limit counters and the pseudonymous session analytics. The data we handle and our legal bases are exactly the same as described elsewhere in this policy; only our role differs. Where this policy says the retailer is the controller, or refers to “the retailer's privacy notice”, that does not apply to our own hosted demos — for those, we are the controller you exercise your rights against, at privacy@visualiseo.co.uk.
3. What information we collect
From retailer account holders
- Your name, email address, and a password (stored only as a bcrypt hash — never in plain text).
- Your company name and website URL.
- Billing identifiers generated by Stripe. We never see or store your card number, CVV, or bank details.
- API keys and allowed installation domains you configure.
- Product images and custom prompts you upload to the dashboard.
- Monthly render counts and telemetry about renders generated through your account.
From end users of the widget
- Any photo you upload to generate a render (including your space photo and any custom product or material reference image). Uploaded photos are sent to our AI sub-processors to produce the output; they are not stored on our servers. Photos of people are automatically rejected before they are processed (see section 11 below).
- The generated render, which is shown to you in your browser. We hold it only so it can be shown to you, and delete it when you close the visualiser, unless you choose to keep it: by pressing Save and leaving your details (below), or by attaching it to a quote you send. The render is not downloaded to your device or emailed to you by us. Sharing a render to the public gallery is no longer offered; renders shared before 9 November 2026 stay in our gallery until withdrawn.
- Your email address and/or phone number, only if you press Save on the result screen and enter them. We keep them with a copy of the render and share them — together with the render and the product visualised — with the retailer whose widget you used, so the retailer can send you the image and follow up about that product (see section 6). We do not send you the image ourselves. Receiving ongoing marketing from the retailer is a separate, optional opt-in shown under those fields and is never ticked by default. We do not use your details for our own marketing and we never sell them.
- What you type into the chat or quote assistant.Where a retailer has switched it on, we store the conversation — every message you, the assistant and the retailer's team send — together with any name, email address or phone number you choose to give, your answers to the retailer's quote questions, and the product or render the conversation relates to. If a question asks for photos — a kitchen plan, a drawing, or the room itself — we store the ones you attach (up to three per question, and you can skip the question). We remove the hidden location data cameras add to photos before storing them, and photos are never sent to an AI. Your messages are sent to our AI sub-processor to produce the assistant's replies, and the retailer can read the whole conversation in their dashboard. We do this for the retailer, as their processor. Please do not put anything into the chat that you would not say to the retailer directly. Section 8 says how long we keep it.
- Pseudonymous session timestamps (when you opened, uploaded, generated, or closed the widget), identified only by a random session ID. They are tied to the retailer's account, not to you personally. Each session also stores a one-way hash of your network address (not the address itself) so the retailer can see how many distinct visitors return — never used to identify you.
Collected automatically
- IP address, browser, and device type — contained in our standard server logs for security and fraud prevention.
- Short-lived rate-limit counters— to protect retailers' render allowances and our service from abuse, we briefly store a counter keyed to your IP and the retailer you are using, so we can tell when a single visitor has exceeded a fair-use threshold (typically 10 renders per hour / 20 per day; retailers may adjust this). These counters are automatically deleted within 48 hours and are never used for analytics, profiling, or marketing. Lawful basis: Art. 6(1)(f) legitimate interest — documented LIA.
- Technical metadata on the images you upload (dimensions, file size). Before anything is sent to an AI provider or stored, we strip EXIF, GPS, and other embedded metadata from every image.
- Approximate location and marketing-page analytics.When you visit our own pages (not a retailer's widget), we record cookieless analytics — the page, referrer, device type, scroll depth, and time on page — together with an approximate location (city and country) derived from your IP address at the moment you load the page. We do notstore your IP address; only the resolved coarse location (e.g. “London, United Kingdom”) is kept. No cookie or browser storage is used — the visit identifier exists only in your browser's memory and is discarded when you reload — so no consent banner is required. Lawful basis: Art. 6(1)(f) legitimate interest in understanding how our marketing pages perform; you can object at any time at privacy@visualiseo.co.uk.
Sponsored product clicks on our website
Products labelled as ads may link to a retailer's product page. Clicking that button creates a billing record containing the product, retailer, destination, agreed credit price, time and a reference to the generated result. A short-lived result token prevents the same request being charged twice. This feature does not set a visitor-tracking cookie, store a persistent browser identifier or attempt to identify unique visitors.
We use the approximate country supplied by our hosting provider to show promoted product-page buttons only when it matches the retailer's selected country, and check it again before click charging. Visitors with unknown or unmatched countries can still browse and visualise these products, without a product-page button. This does not require a new visitor cookie or precise device location.
Retailers see their product click charges, without visitor identities or uploaded photos in that report. When you open a retailer's website, its own privacy notice applies.
Indirectly
In some cases a retailer may pass us metadata about an end user's session (for example, a product ID) that the retailer has gathered on their own site. Where this is the case, the retailer is responsible for telling you about that collection in their own privacy notice.
4. How we use your information, and our legal basis
| Purpose | Legal basis (UK GDPR Art. 6) |
|---|---|
| Create and administer your account, deliver the service | Art. 6(1)(b) — contract |
| Process payments and maintain billing records | Art. 6(1)(b) contract + Art. 6(1)(c) legal obligation (HMRC) |
| Send transactional emails (welcome, password reset, billing notices) | Art. 6(1)(b) — contract |
| Generate renders from end-user uploads | We process on behalf of the retailer as their processor; the retailer's own legal basis (typically Art. 6(1)(f) legitimate interest in offering a visualisation tool) applies. See the retailer's privacy notice. |
| Run a retailer's chat and quote assistant and store the conversation so the retailer can reply and follow up | We process on behalf of the retailer as their processor; the retailer's own legal basis applies — typically Art. 6(1)(f) legitimate interest in answering a sales enquiry, or Art. 6(1)(b) steps taken at your request before entering a contract. See the retailer's privacy notice. |
| Generate the assistant's replies with an AI language model | Same processor role and the same retailer legal basis as above. The conversation text is sent to Google (Gemini) as our sub-processor under a paid contract that prohibits training on it. |
| Keep showing renders shared to the public gallery before 9 November 2026 | Art. 6(1)(a) explicit consent of the end user; Art. 9(2)(a) explicit consent for any special-category data that may incidentally be revealed. |
| Keep a render an end user saved, with the email address or phone number they gave (the Save popup) | Art. 6(1)(b) / Art. 6(1)(a) — the end user's own request. We act as the retailer's processor for this. |
| Share those details + the render with the retailer so they can send the image and follow up about the product | The retailer's Art. 6(1)(f) legitimate interest in responding to a product enquiry. We act as the retailer's processor. |
| Send the end user ongoing marketing about the retailer's products and offers | Art. 6(1)(a) — separate, optional opt-in, never pre-ticked, withdrawable at any time. |
| Show your quote enquiry from visualiseo.co.uk to worktop companies with your name, email and phone removed, so they can decide whether to quote | Art. 6(1)(a) — your consent, given when you ask for the quote. See section 6. |
| Give your name, email and phone to a worktop company that buys your enquiry, so they can contact you about the job | Art. 6(1)(a) — your consent, given when you ask for the quote. Not pre-ticked, and the quote is not sent without it. See section 6. |
| Detect fraud, abuse, and keep the service secure | Art. 6(1)(f) legitimate interest — documented LIA |
| Monitor usage against your plan limits | Art. 6(1)(b) — contract |
| Improve the service (aggregate, non-identifying metrics) | Art. 6(1)(f) legitimate interest — documented LIA |
Automated decision-making. We do not carry out automated decision-making that produces legal or similarly significant effects on you within the meaning of Articles 22 / 22A–22D UK GDPR. Render generation is automated but produces a visual preview, not a decision about you. You have the right to contest any automated processing and to request human intervention; contact privacy@visualiseo.co.uk.
We never use your uploaded images to train AI models. Every AI provider we use is engaged under a paid commercial contract that contractually prohibits training on customer inputs.
5. Special-category data
A photograph is not automatically special-category data under UK law; it becomes so only where it is processed for biometric identification (Art. 9 UK GDPR). We do not carry out biometric identification and our AI providers have confirmed contractually that inputs are not used for face-matching or identification.
However, a photograph of a space may incidentally reveal information that is special-category data under Art. 9 (for example, religious markers in the home, visible mobility aids, or details that suggest ethnicity). We minimise this risk by prohibiting and rejecting photos of people before any AI processing occurs and by stripping EXIF / GPS metadata from every upload.
For the render itself (the processing that happens even if you never publish to the gallery), we rely on your explicit consent under Art. 9(2)(a) UK GDPR, captured at the widget's pre-flight notice — the consent tick covers Article 6(1)(a) and Article 9(2)(a) and is the basis we use for any special-category information that might incidentally appear in the photo of your space.
For gallery publication, we rely on a separate, more granular explicit consent under Art. 6(1)(a) and Art. 9(2)(a) — given at the Save popup while that option was offered (until 9 November 2026), and withdrawable via the tokenised link shown on the widget result screen at the moment of publication for you to copy and keep.
You may withdraw either consent at any time. Withdrawal stops future processing — it does not make past processing unlawful. The provider's file-API copy of your photo is deleted automatically within 48 hours regardless.
6. Who we share data with
We rely on a small set of trusted sub-processors to run the service:
| Provider | Purpose | Location |
|---|---|---|
| Google (Gemini API) | AI image generation (primary) and generating the retailer chat and quote assistant's replies | United States |
| Google Cloud Vertex AI | AI image and video generation (alternate model chain, Gemini Enterprise) | United States / European Union |
| OpenAI | AI image generation (alternate model chain) | United States |
| Google Cloud Storage | Product and gallery image storage | European Union |
| Neon | PostgreSQL database hosting | European Union |
| Vercel | Web application hosting | United States / global edge |
| Stripe, Inc. | Payment processing | United States / Ireland |
| Resend | Transactional email delivery | United States |
| Pusher | Real-time delivery of chat messages — both our own support chat and conversations between a visitor and a retailer | United States |
The canonical list is published at /sub-processors. We give retailers at least 30 days' email notice of any material addition or replacement of a sub-processor, and retailers can object on reasonable data-protection grounds.
Saved renders. Separately from the sub-processors above, when you press Save and leave your details we share your email address and/or phone number, the render, and the product visualised with the retailer whose widget you used, so they can follow up about that product. The retailer is an independent controller of that lead and handles it under their own privacy notice. We pass it to them as their processor; we do not use it for our own purposes.
Quote enquiries made on visualiseo.co.uk. This applies only if you asked for a worktop quote on one of our ownpages — not to a quote form on a retailer's own website, which is covered above. When you ask for a quote here, you are asked to confirm that you are happy for worktop companies to contact you about the job. If you do not agree, the enquiry is not sent and none of the following happens.
- Your enquiry is shown to worktop companies who subscribe to Visualiseo, with your name, email address and phone number removed. They see what you asked for, any photos or visualisation you attached, and your town or postcode — enough to decide whether the job is in their area.
- A company can then pay us to receive your name, email address and phone number so they can contact you. This is how the service is funded, and it is the only circumstance in which we are paid for passing on personal data.
- More than one company can buy the same enquiry — up to a fixed limit, so you may hear from several. Each of them becomes an independent controller of your details from that point and handles them under their own privacy notice. They are contractually required to contact you only about this job and never to sell your details on.
- You can withdraw your consent at any time by emailing privacy@visualiseo.co.uk. That stops any further company being given your details and removes the enquiry from the board. It cannot undo a disclosure already made — a company that has already bought your details keeps them, and you would need to ask that company directly. You can also ask any of them to stop contacting you.
Apart from the lead sale described immediately above, we do not trade or monetise personal data. We do not share it with advertisers. We do not use third-party analytics, cross-site tracking pixels, or behavioural advertising cookies.
We may disclose data where we are legally required to (for example, a court order) or where it is necessary to investigate fraud, abuse, or a threat to safety.
7. International transfers
Some of our sub-processors are based outside the UK and EEA. Where this is the case we rely on safeguards recognised by UK data protection law, in particular:
- The UK-US Data Bridge (UK extension to the EU-US Data Privacy Framework) for providers that are DPF-certified.
- Standard Contractual Clauses together with the UK International Data Transfer Addendum.
- Adequacy decisions issued by the UK government, where available.
We have completed a Transfer Risk Assessment for each international sub-processor. A summary is available on request from privacy@visualiseo.co.uk.
8. How long we keep your data
| Data | Retention |
|---|---|
| Uploaded photos (before render) | Not stored by us. Held briefly by the AI provider and automatically deleted within 48 hours under the provider's file-API retention policy. |
| Generated render (not shared) | Returned to your browser. Not stored by us. |
| Render saved on your device | Kept in your browser's IndexedDB until you clear browser data or remove it from the widget's recent-renders panel. Never sent to our servers. |
| Gallery submissions (public) | Until you withdraw consent or we remove them. |
| Saved renders (email address and/or phone number, a copy of the render, marketing opt-in status) | Kept for the retailer to action the enquiry while their subscription is active, and in any event no longer than 24 months. Deleted sooner if you or the retailer ask. Deleted in full when the retailer closes their account. |
| Visitor conversation with a retailer (no contact details given) | 90 days from your last message, then deleted together with the full transcript. This is any conversation where you did not give an email address or phone number and did not complete a quote request. |
| Visitor conversation with a retailer (contact details given, or quote completed) | Kept for the retailer to action while their subscription is active, and in any event no longer than 24 months from your last message. Deleted sooner if you or the retailer ask. Deleted in full when the retailer closes their account. |
| Quote enquiry made on visualiseo.co.uk (available as a lead) | Kept on the board while it is still worth quoting for and in any event no longer than 24 months from your last message, on the same schedule as any other quote enquiry. Removed from the board immediately if you withdraw consent, and we then hold it only as a record that you did. |
| Record of which companies bought your enquiry | Kept while it is needed to bill, refund and audit the sale, and in any event no longer than 24 months. This record is how we can tell you who was given your details. |
| Retailer account | Until you close the account, then 30 days, then deleted or anonymised. To close your account, email privacy@visualiseo.co.uk. In-dashboard self-serve account closure is planned but not yet available. |
| Payment and invoice records | 6 years (UK tax law). |
| Render metadata and analytics | 24 months. |
| Marketing-page analytics (incl. approximate location, no IP) | 24 months. |
| Widget session logs | 12 months. |
| Support chat conversations (closed) | 12 months from the last message, then deleted with all messages. Open conversations are not auto-deleted. |
| Security and server logs | 30 days. |
| Complaint records | 6 years (to evidence our handling of your right to complain). |
9. Your rights
You have the following rights under UK data protection law:
- Access the personal data we hold about you.
- Correct inaccurate or incomplete data.
- Ask us to delete your data (“right to be forgotten”).
- Restrict or object to processing based on legitimate interest.
- Receive your data in a portable format.
- Withdraw consent you have given. For gallery publication, a self-serve withdrawal link was shown on the widget result screen at the moment you shared your render, for you to copy and keep. You can use that link at any time without contacting us. You can also email us at privacy@visualiseo.co.uk, use the complaints form, or use the retailer's own channel.
- Complain directly to us using our electronic complaints form at /complaints. This is a statutory right under the DUAA 2025 (amended Art. 77 UK GDPR). We will acknowledge your complaint within 30 days and inform you of the outcome without undue delay.
- Complain to the Information Commissioner's Office at ico.org.uk.
If you used the widget on a retailer's website for a render, the retailer is the controller for that upload. You can contact either them or us. For a render shown in our public gallery, contact us: we are its sole controller.
If you are an account holder, email privacy@visualiseo.co.uk or use /complaints. We will respond within one calendar month.
10. Cookies and browser storage
We only use first-party storage. We do not use advertising, analytics, or cross-site tracking cookies, so no cookie banner is shown. Our marketing-page analytics are cookieless and run server-side (see §1).
| What | Why | Basis | Lifetime |
|---|---|---|---|
| NextAuth session cookie | Keeps you signed in to the dashboard | Strictly necessary (PECR reg. 6 exemption) | Up to 30 days. If you don't tick "Remember me" the session inside the cookie expires after 24 hours; the cookie itself may persist until you clear browser data. |
| NextAuth CSRF cookie | Protects sign-in against cross-site attacks | Strictly necessary (PECR reg. 6 exemption) | Session |
| Widget consent flag (localStorage) | Remembers you accepted the widget safety notice so you don't see it every time | Strictly necessary to deliver the service in line with the pre-flight notice requirement | 7 days |
| Chat session (localStorage, inside the chat frame) | Remembers which conversation is yours — a random visitor ID, the conversation ID and an access token — so you can pick up where you left off | Strictly necessary to deliver the chat you started (PECR reg. 6(4) exemption). Only written once you send your first message; nothing is stored if you never use the chat. | Until you clear browser data |
You can clear any of these at any time through your browser's privacy settings.
11. Children and age assurance
Visualiseo is not directed at children. You must be 18 or over to hold an account or to use the widget. We do not knowingly collect data from anyone under 18.
The widget accepts photographs of spaces and product/material references only. An automated check rejects any image that appears to contain a person before it is sent to any AI provider. We believe this restriction, combined with the age statement in the pre-flight notice, removes the material risks that the Children's Code and Online Safety Act 2023 are designed to address.
We have carried out a Children's Access Assessment (under the ICO Children's Code and the Online Safety Act 2023) and have concluded that the service is not likely to be accessed by children in significant numbers. Even so, we apply relevant standards — data minimisation, opt-in publication, no profiling, no dark patterns — as data protection by design.
If you believe a child has used our service, contact privacy@visualiseo.co.uk and we will delete their data.
12. AI-generated content (transparency)
Every render produced by the widget is AI-generated. In line with Article 50 of the EU AI Act (which applies to us when we serve EU users) and our own transparency commitments:
- Every image displayed in our public gallery carries a visible “AI-generated” label.
- The widget discloses before you upload that the final image is produced by AI and may not exactly match the product's real colour or finish.
- We do not use synthetic media to impersonate real people; photographs of people are rejected before any AI processing.
13. How we protect your data
- All traffic to and from our servers uses TLS encryption.
- Data stored by our providers (Google Cloud Storage, Neon, Vercel) is encrypted at rest using provider-managed keys.
- Passwords are stored as bcrypt hashes, never in plain text.
- API keys are unique per account and can be rotated by you at any time.
- Each retailer's widget installation is restricted to domains they allowlist.
- EXIF, GPS, and other embedded metadata are stripped from every uploaded image before it is processed or stored.
- Access to production data is restricted to the minimum number of people needed to operate the service.
- We operate an incident-response process with 72-hour ICO notification per Article 33 UK GDPR.
- We carry out Data Protection Impact Assessments for new processing and review them annually.
14. Changes to this policy
If we make a material change to this policy we will email account holders and update the “Last updated” date at the top of this page. Continuing to use the service after the change means you accept the updated policy.
15. Contact us
- Privacy questions and data subject requests: privacy@visualiseo.co.uk
- Electronic complaints form: /complaints
- General support: hello@visualiseo.co.uk
You can also reach us by post at our registered office:
VisualiseO Limited27 Beverley Close
Normanton
WF6 1BU
United Kingdom