roomvelo
Back to the site
Legal · Privacy

Privacy Policy

Last updated 22 September 2026 · GDPR-aligned

Sections
  1. Who we are
  2. Controller or processor
  3. What we process
  4. Why, and on what basis
  5. Who processes it with us
  6. How long we keep it
  7. Your rights
  8. Cookies
  9. Contact
01

Who we are

RoomVelo is an independent software project in Lithuania. We build a widget for furniture retailers: a shopper uploads a photo of their room and sees the retailer's product placed in it at its catalogue dimensions. This policy describes what that actually involves — not a finished company. You can reach us at info@roomvelo.lt.

02

Controller or processor

Which role we hold depends on whose data it is, and it changes what you can ask of us:

  • Our own site — for anything you send us through this website, RoomVelo is the controller. That is the demo-request form, and the analytics and cookies described below.
  • The widget on a retailer's site — when a shopper uses RoomVelo on a retailer's product page, the retailer is the controller and RoomVelo acts as their processor. We process shopper photos only on that retailer's instructions, under a data processing agreement. If you are that shopper, direct your requests to the shop whose site you used; we will support them in answering.
03

What we process

From this website — the only personal data we collect here:

  • Demo request — the company or shop address, work email, the interest you pick and anything you write in the message field. It reaches our shared mailbox and nowhere else.
  • Shop dashboard accounts — for shop staff we invite to their shop's dashboard: the email address used to sign in. It is kept while they have access and deleted when access is removed. Sign-in is handled by Clerk.
  • Language and consent — your language choice and your cookie decision, stored in your browser, not on our servers.
  • Analytics — aggregate page views via Vercel Analytics. No cross-site tracking, no advertising profiles.

Through the widget, for a retailer — when a shop deploys RoomVelo:

  • The room photo a shopper uploads, plus the spot they mark on it. A photo of someone's home can reveal more than furniture, which is why it is treated as the sensitive part of this product. If the camera recorded where the photo was taken, that location is deleted as the photo arrives.
  • The generated render and what was worked out from the photo to make it: estimated dimensions, camera height, and a short written description of the furniture in the room, made by an AI model.
  • Product context already public on the retailer's page: item code, price, dimensions.
  • A random visitor ID that the widget makes and keeps in the browser storage of the shop's site on your device, under the name “roomvelo_vid”. It is not a cookie and says nothing about who you are; it lets the shop's report count visitors rather than page loads.
  • Your rooms and results — if you use the try-on, the widget also keeps a list of your room photos and results in the same browser storage: their IDs, the spot you marked and the product names, so you can try other products on the same photo. It is kept for up to 30 days, and “Forget my photos” removes it from your device.
  • The page and the steps — the address of the product page, and what happened in the widget: opened or closed, a photo uploaded, a render started, the result downloaded, the add-to-cart button pressed. The same steps, without the photo, are passed to the shop's own page analytics if it runs any. The widget also counts how many times its button was shown: one number per shop per day, with nothing that identifies the page or you.
  • Your device type — when the photo is uploaded, we read your browser's description of your device to tell which phone took it, because the phone's lens sets the scale. We keep only the resulting lens estimate, or your answer if the widget asks which phone you have.
  • Your IP address — used to cap how many photos and renders one visitor can make in a day, so the service cannot be abused. We store only a hashed code of it next to that day's count, never the address itself.

We never use shopper photos to train models, never sell them, and share them with no one outside the processors listed below.

04

Why, and on what basis

  • Demo requests — to reply to you. Legitimate interest in responding to a business enquiry you initiated (Art. 6(1)(f)); you can ask us to delete it at any time.
  • Shopper photos — to produce the render requested. Processed on the retailer's legal basis, on their documented instructions (Art. 28).
  • Visitor ID, page and steps — to give the shop its usage report and to invoice it for renders, on the shop's instructions.
  • Analytics and limits — legitimate interest in keeping the service working and knowing which pages are read. In the widget, this is done for the shop.
05

Who processes it with us

We use a small number of sub-processors. We name them because a vague list is not a disclosure:

  • Vercel — hosting and analytics for this site.
  • Resend — delivery of the demo-request email.
  • Microsoft 365 — the mailbox that receives it.
  • Clerk — authentication, only if you create an account.
  • Amazon Web Services — the widget's server, database and file storage in Stockholm, Sweden, and the network that delivers its files. AWS also runs Claude, Anthropic's AI model, for us in the USA (Amazon Bedrock): it reads the room photo to describe the furniture in it.
  • Replicate (USA) — runs the image models that outline the furniture, remove the old piece and draw the new one. The models come from Meta (SAM 3), Google (Nano Banana), ByteDance (Seedream) and, as a backup, OpenAI (gpt-image); when one of the last three is used, the photo can reach its maker through Replicate.
  • RunPod (USA) — runs the model that measures depth in the room photo.

The widget's server, database and stored files are in the EU. The AI models that read the photo run in the USA, and other services above may process data outside the European Economic Area too. Those transfers rely on the European Commission's standard contractual clauses. We are naming this plainly rather than claiming everything stays in the EU, because it does not.

We do not sell personal data and we run no third-party advertising.

06

How long we keep it

  • Demo requests — kept while we are in contact and for up to 24 months afterwards, so we remember a conversation we already had. Ask and we delete it sooner.
  • Room photos and renders — the photo, the render and the working files made from them are deleted 30 days after the photo is uploaded, from our server and from our storage. A retailer can set a shorter window in their agreement with us.
  • Daily limit counts — the hashed IP code and its counts are deleted after 30 days.
  • Usage records — the visitor ID, page, steps and a record of each render (which product, when, and what was measured and described, never the photo) are kept for the shop's reports and invoices, for at most 24 months.
  • Backups — copies of our database are kept for 30 days, then deleted.
  • Site analytics — aggregate, with no identifier that points back to you.
07

Your rights

Under the GDPR you can ask for access to your data, correction, deletion, restriction, portability, and you can object to processing based on legitimate interest. Write to us and we will answer within one month.

If you used the widget on a shop's website, send the request to that shop — they are the controller. We will help them fulfil it.

You can also complain to the Lithuanian State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija).

08

Cookies

We use the smallest set that makes the site work: your cookie decision, your language, and a session cookie if you sign in. Analytics is aggregate. There is no advertising or cross-site tracking, so there is nothing here to opt out of beyond the banner.

The widget on a shop's site sets no cookies. It keeps the random visitor ID and your list of rooms and results described above in the browser storage of the shop's site and, for the open tab only, where you are in the try-on, so a reload does not send you back to the start.

09

Contact

Questions, requests, or a data processing agreement to review: info@roomvelo.lt. A postal address is available on request.

© 2026 RoomVeloPrivacy policyTermsinfo@roomvelo.lt