Last updated: 15 October 2026
In short: we look after publishers’ accounts ourselves. When a viewer uses a room, their actions trigger events we log for the publisher who sent the link, such as which sections they reached and the comments they chose to leave. There is no screen recording, video or keystroke capture. If a viewer says yes when the room asks, we also log the screens they open inside the demo and what they click there, never what they type. On this site and in the app we measure how they are used, with our own code on our own servers, and you can turn that off. We do not sell personal data, show advertising, or let any other company track you here.
1. Who we are
Roomi is a trading name of Daedalus Technology Services Ltd, a company registered in England and Wales under company number 14033663, whose registered office is at 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ. Our VAT number is GB423285900.
Write to us about anything in this policy at privacy@getroomi.com, or by post at our registered office.
2. Who is responsible for your data
If you have a Roomi account (a publisher, a member of a team, or someone who signs in to comment on the Community), we are the controller of your account data: we decide what is collected and why.
If someone sent you a link to a pitch room (a viewer), the publisher who sent it decides who receives a link, and uses the events the room logs about you for their own purposes, such as following up. They are the controller of that data, and we are their processor: we log and hold it for them, on their instructions, under our terms with them. To ask about it, contact the publisher first; if you contact us, we pass your request to them and help them answer.
On a public Community page, nobody sent you a link, and we decide what is logged there, so we are the controller of it.
We are also the controller of the little we keep to run and protect the rooms themselves: the hashed network addresses we count seats by, how many viewer-hours a workspace has used, reports of abuse, and our moderation decisions.
3. What we collect about publishers
- Your account: your name, email address and picture from Google or GitHub, whichever you sign in with, with the account id and sign-in tokens it gives us; your passkeys’ public keys (never a private key); the name you choose to be shown by, and your Community handle; your bio and any photo you upload.
- Signing in: your sessions, each with the browser it was signed in from and the network (IP) address it came from; a record of each time you sign in: when, and which way (Google, GitHub, a passkey, an emailed link or the command line tool), with no browser or network address; and the connections you make from the roomi command line tool or an AI assistant.
- Your workspaces: the workspaces you own or belong to, your role in each, invitations, and your workspace’s brand: name, colours, theme and logo.
- Your content: the demos you deploy, their builds, tours, pages and files, Community cards and covers, your notes about viewers, and your replies to them.
- Billing: your plan, its status and period, your seats and your invoices. Stripe takes your card and billing details on its own pages; we keep only its references and the amounts, never a card number.
- How you use it: deploys and how each reached us (the command line, Claude’s connector, an API token or an upload while signed in), usage such as viewer-hours, a history of the changes made to your workspace, the moderation checks run on your listings, and any feedback or report you send us.
4. What happens when a viewer opens a room
When you open a link a publisher sent you, what you do in the room triggers events that we log for that publisher. There is no screen recording, no video and no keystroke capture: we log that something happened, and keep only the words and pictures you choose to send. The events are these:
- Who you are: the name, and the email address if any, the publisher gave when they made your link. If the link was forwarded to you, the room asks your name and email address before it opens, and logs that the link reached you; it does not log who forwarded it. Nobody checks or sends anything to an address given in a room.
- If the publisher asked us to send you the link: we email it to the address they gave, once, from Roomi’s own address, naming them as the person who shared it. The email has a link to report it and a link to stop links being sent to you this way; if you use either, or the email bounces, we keep a keyed hash of your address (a scrambled form that cannot be turned back into it) so that we send you no more, and a report goes to the people who look after Roomi. Our outbox keeps the address and the email’s details for 30 days, as it does for every email.
- If the room asks you to prove your email: where the publisher has turned it on, the room asks for your work email before it opens, and we email a 6-digit code to it from Roomi’s own address, naming the publisher. We process your address to send the code, and our outbox keeps the address and the email’s details for 30 days, as it does for every email. The code itself is never stored: we keep a keyed hash of it, which works for 10 minutes and 5 tries. The room answers the same whether or not an address may open it, so nobody learns who is on the publisher’s list. Once you type the right code, the publisher sees that you proved the address, and when.
- If the room asks for a password: we never keep or show what you type. To stop guessing, we log each wrong try against your link, with a keyed hash of your browser’s session and of your network range, which cannot be turned back into either; after too many, the room asks you to wait. The publisher sees how many wrong tries each link had, never what was typed.
- Where you went: when you opened the room and left it, and whether you are in it right now; the sections of the demo and the pages you reached, and how long you spent on each; the tour steps you reached and the scenarios you tried, and whether they worked; whether you went full screen, opened it in a new tab or moved to your phone; and the kind of device you used: phone, tablet or desktop.
- What you did inside the demo, if you said yes: where the publisher has turned it on for the room, the room asks you before you go in, with neither answer chosen for you, whether they may also see what you click in the demo, and tells you where to ask them about your data. Only if you say yes do we log, from then on: the screens of the demo you open, in order, and how long each was in front of you and in use; what you click or tap there, named by the demo’s own labels but by no words that appeared on the page after you typed unless every one of them is already in the demo’s own files, and whether a burst of clicks changed nothing on the page; how far down each screen you scroll; and that you used a field or sent a form, but never what you typed into it, how much, or which keys you pressed. We never read password, card or one-time-code fields at all, nor your clipboard, and we keep the address of a screen without its query string. With each screen we keep which device frame the room showed it in: a phone, a tablet, a laptop or a screen. If your browser sends Global Privacy Control or Do Not Track, the room does not ask and logs none of it. At a public Community address nothing inside the demo is logged, and nobody is asked. Where nothing was logged, the publisher sees only that, never why.
- What you chose to say: the comments, questions and replies you choose to leave, with where on the screen you pinned them and, unless you remove it before sending, a picture of the demo’s screen at that moment; your reactions; and your answer to “What happens next?”, which can include a reason, or the name and email address of a colleague you suggest.
The publisher and their team see these events for each viewer, together with how the viewers compare: who did most, where attention went, and who is in the room now. Nothing is decided about you automatically: it is information for the publisher.
The room does not log your location or the browser you use, and on a private link the room makes no use of your network (IP) address. On a public Community page it keeps a keyed hash of your address and of its network range, which cannot be turned back into the address, to limit how many people are in at once, and deletes it soon after you leave.
On a public Community page the same events are logged against a random id for your browser instead of a name. If you sign in to comment or react, the publisher sees your name and picture, never your email address.
The demo inside a room is the publisher’s own software, on mock data. It may load things from other websites, and a live app demo runs the publisher’s own server code, which receives the requests your browser makes to it, including your network address and browser details. We do not control what a demo does with them.
Our terms forbid publishers from building their own session replay, keystroke logging or other tracking into a demo. We cannot technically prevent a demo’s own code from doing it; what Roomi logs inside a demo comes from a script of ours that reports only to the room.
To show a publisher where on a screen viewers clicked, Roomi keeps a picture of each screen of the demo. A picture is taken only in the publisher’s own browser, while someone in their workspace previews the demo with its mock data, and never in yours, so no picture holds anything about you; the demo’s fields are drawn empty in it. Over those pictures the publisher sees where viewers clicked and how far down they scrolled, as counts that name nobody, and how many viewers went through steps of the demo the publisher chose, in order, and who stopped where. All of it is drawn from what is logged above: nothing more is logged for it.
On the plans that have replays, the publisher can also open a replay of a visit: the screens you opened inside the demo and what you clicked there, as logged above, laid out in the order and at the times they happened, over Roomi’s own pictures of the demo’s screens. A replay is not a recording of your screen. Nothing more is logged for it, no video is made, and what you typed is never in it: where you used a field, it shows only that you did.
5. Visitors to this site, and how we measure the site and the app
We measure how getroomi.com and the app are used, to understand what helps people and to improve them. It is our own measurement: our own code sends it to our own servers and keeps it in our own database. No other company receives it, it is never used for advertising, and we do not sell it. Our hosting provider, Cloudflare, handles the technical details of each request, such as your IP address, to deliver the page and protect it, as it does for every request.
What the site records
- The pages you open: each page, when, its title, and whether it was the first page of your visit.
- Where you came from: the website that sent you, by its name alone (never the page on it, or what you searched for there); a search engine or AI assistant by name, such as Google, Bing or ChatGPT; and the campaign tags in the link you followed (utm_source and the like).
- How you read: how long each page was in front of you (time with the tab in the background is not counted), how far down you scrolled, and how long each section of the page was on your screen.
- What you did: the links and buttons you clicked, by their words and where they led; what you searched for in the docs, once you stop typing; whether you saw or clicked into the film on the home page; and that you copied from a code example, and how much.
- About your visit: your country, as Cloudflare tells us from the request (never your address), whether you are on a phone, a tablet or a computer, and your browser’s family (such as Safari or Chrome), never its version or other details.
We do not store your IP address: we use it for a moment, in memory, to stop anyone flooding us with fake visits, and then it is gone. We do not record what you type anywhere but the docs search box, and nothing from any form but the free guide’s, below.
The id in your browser
So we can tell one visitor’s pages from another’s, the site keeps a random id in your browser’s local storage (section 7). It is made at random and says nothing about you. If you are in the UK or outside the EU and EEA, the site keeps it unless you turn it off, as UK law allows for measuring how a service is used in order to improve it. If you are in the EU or EEA, the site asks you first; until you say yes, the pages you open are still counted, but with no id, so nothing joins one of your pages to another. If your browser sends Global Privacy Control or Do Not Track, the site sends nothing about your visit at all.
To turn it off, or back on, use Privacy choices (getroomi.com/privacy-choices), linked at the foot of every page. Turning it off removes the id from your browser and stops anything more being sent.
Crawlers
When a search engine’s or an AI company’s crawler fetches a page, we record the name it gives itself, the page and whether it was found. That is about the crawler, not about a person.
When you sign up
If you follow a link from the site into the app, the link carries the site’s id for your browser. When you create your account, we join your visits to the site before you signed up to it: where you first came from, the page you landed on, the pages and sections you read, and how long it was from your first visit to signing up. The set-up step says so, and lets you choose not to join them; you can change that whenever you open the set-up again, or write to privacy@getroomi.com. The set-up also asks how you heard about Roomi; answering is up to you.
In the app
When you are signed in, the app records the screens you open and how long each is in view, and what you do there by its kind, never its contents: signing in or up and by which method, each step of the set-up and how long it took, each change you make (such as setting up a room, making, copying or revoking a link, or inviting someone to a team), which of the app’s instructions you copy, opening billing, starting a checkout and what happened when you came back, and the errors the app shows you. These are kept against your account, with no names, email addresses, project contents or anything you typed, so we can see where people get stuck. If your browser sends Global Privacy Control or Do Not Track, the app sends none of it, and our server keeps none that arrives with either signal.
We put your visits to the site (if you let us join them), your sign-up and what you do in the app into one timeline for your account, in the order they happened and with the time between each, so we can see where people get stuck. We read how your account was made (GitHub, Google or an emailed link) from our own sign-in records.
The free guide
When you ask for our free guide, we record the email address you give, where on the site you asked (the page, and whether it was the guide itself, a guide article or a landing page), and your answer to “Send me Roomi’s guides and news”: yes or no, the exact words you were shown, and when. That box starts unticked, and we email you the guide whether you tick it or not. If the site keeps an id for your browser (above), we join the request to your visits, so we can see where you first came from, the page you landed on, the pages and sections you read before asking, and how long it took from your first visit; if it keeps none (in the EU or EEA without a yes, or with measurement turned off), we join it to nothing.
If you leave the box unticked, we keep your address only until the guide’s email has gone, or could not be sent, and then replace it with a keyed hash: a scrambled form that cannot be turned back into your address, which lets us count one person once and honour an unsubscribe, but not write to you. If you tick it, we keep your address so we can send you guides and news, until you unsubscribe with the link in any of our emails, when we replace it with the keyed hash in the same way.
None of this is about the viewers of your rooms: what section 4 describes is separate, and is yours.
6. Why we use it, and our lawful basis
- Running your account and the service you signed up for: performance of our contract with you.
- Logging the events of a viewer’s visit, and showing them to the publisher: on the publisher’s instructions, as their processor. The lawful basis is the publisher’s to establish; for following up a pitch they sent to someone, it will usually be their legitimate interests.
- Logging what a viewer does inside a demo (section 4): the viewer’s consent, which the room asks for on the publisher’s behalf before anything is logged, and which the viewer can withdraw at any time from the top of the room, as easily as they gave it. Because the script that does it reads what happens in the viewer’s browser, the Privacy and Electronic Communications Regulations need that consent too, as the ePrivacy rules do in the EU and EEA. We ask for it and log it as the publisher’s processor.
- Emailing a viewer their link because the publisher asked us to (section 4): on the publisher’s instructions, as their processor, as for the rest of the room; the publisher chooses to send it and establishes the lawful basis. Stopping or reporting those emails, and keeping what we need to honour that: our legitimate interests in preventing our service being used to send unwanted email.
- Public Community pages, counting seats and viewer-hours, keeping the service secure, moderating the Community and handling reports: our legitimate interests in running the service, keeping its costs in check, and protecting it and the people who use it.
- Taking payment and keeping financial records: contract, and our legal obligations, for example for tax.
- Messages about your account: contract. We send no marketing to your account’s address unless you ask for it.
- Sending you the free guide you asked for, and recording the request (section 5): our legitimate interests in answering your request and knowing what brings people to us.
- Sending you guides and news: your consent, given by ticking the box when you ask for the free guide. You can withdraw it at any time with the unsubscribe link in any of our emails, or by writing to us.
- Measuring how the site and the app are used, to improve them (section 5): our legitimate interests in understanding and improving our service. Keeping the id in your browser relies, in the UK, on the exemption for storage used only to produce statistics about how a service is used in order to improve it (the Privacy and Electronic Communications Regulations, as amended by the Data (Use and Access) Act 2025), which needs clear information, which this is, and a simple way to object, which Privacy choices is. In the EU and EEA it relies on your consent, which you can withdraw there at any time.
- Keeping a record of each sign-in and how it was made: our legitimate interests in keeping accounts secure and understanding which ways of signing in people use. It is kept whether or not your browser sends Global Privacy Control, as part of keeping your account secure.
- Joining your visits to your account when you sign up, and asking how you heard of us: our legitimate interests in knowing what brings people to us. You can choose not to join them, and the question is optional.
7. Cookies and storage in your browser
We use what is needed to sign you in and keep a room working, and, on this site, what our own measurement needs (section 5). None of it is for advertising, and none of it is read by any other company.
- Signing in to the app (__Secure-better-auth.session_token): keeps you signed in. It lasts 7 days, renewed while you keep using the app, until you sign out. Short-lived cookies of a few minutes carry a sign-in with Google, GitHub or a passkey through its steps.
- In a room (__Host-pp_room): your place in the room for this visit; it lasts until you close your browser, and the room stops accepting it after 12 hours.
- In the demo (__Host-pp_demo): lets the demo inside the room open for you; until you close your browser, accepted for 2 hours.
- Releases (__Host-pp_v): keeps one visit on one version of our software while we release a new one; until you close your browser.
- Replies (pp-replies-seen, in your browser’s local storage): remembers when you last read the publisher’s replies to you in a room, so it can show you what is new.
- Measurement on getroomi.com (roomi.analytics.visitor and roomi.analytics.visit, in your browser’s local storage): a random id for your browser, and one for your current visit, which ends after 30 minutes with nothing opened. Kept only as section 5 says; the browser’s id is replaced after 13 months, and both are removed when you turn measurement off.
- Your choice (roomi.analytics.choice, in your browser’s local storage): whether you said yes or no, or turned measurement off, so we can honour it. It is the only thing kept if you said no.
What section 4 describes is reported by the room’s own page while it is open, not by a tracking cookie.
Your answer about clicks (section 4) is kept on our servers, against your place in the room, not in a cookie or anywhere else in your browser, so stopping takes effect on the very next thing the room or the demo asks of us. While you have said yes, the demo’s page loads a small script of ours, from the demo’s own address, which tells the room what you opened and clicked; it keeps nothing in your browser.
8. Who we share it with
The publisher sees what viewers did in their own rooms, and nobody else’s. Beyond that, these companies process data for us, and nobody else receives it unless the law requires it:
- Cloudflare, Inc.: hosts and runs all of it: our servers, the database, file storage, the demo containers and the network in front of them. Its Workers AI checks a Community listing’s card, cover and pages for unsafe content. What reaches it: everything the service holds, including the events logged in viewers’ visits; for the listing checks, the card’s title and line, its cover image and the text of up to 20 of the demo’s pages. When: always, for hosting; the listing checks run when you list a project, or change one that is listed. Where: its global network; a company in the United States.
- Stripe: takes payment for paid plans, keeps the invoices and works out the VAT (Stripe Tax). What reaches it: the workspace’s id and the payer’s email, and the card and billing details you give Stripe on its own pages. We never see a card number. When: only for a workspace that subscribes to a paid plan. Where: the United Kingdom, Europe and the United States.
- Twilio SendGrid: sends our emails: sign-in links and team invitations. What reaches it: the recipient’s name and email address, and the message. When: once we switch email on. Open and click tracking stay off. Where: the United States.
- GitHub, Inc.: confirms who you are when you sign in with GitHub. What reaches it: that you are signing in to us; in return your GitHub name, email address, picture and account id come to us. Your picture is then loaded from GitHub wherever it is shown, so the browser showing it asks GitHub for it. When: only if you choose to sign in with GitHub. Where: the United States.
- Google LLC: confirms who you are when you sign in with Google. What reaches it: that you are signing in to us; in return your Google name, email address, picture and account id come to us. Your picture is then loaded from Google wherever it is shown, so the browser showing it asks Google for it. When: only if you choose to sign in with Google. Where: the United States.
- Anthropic, PBC: makes Claude, which we use for our own administration of the service. What reaches it: account data, such as names, email addresses, workspaces and sign-in history, and occasionally a viewer’s name, which Anthropic may process when we do. When: when one of us uses Claude to administer the service. Where: the United States.
- OpenAI: answers, through its API, the questions a buyer might ask an assistant, so we can see whether its answers name us. What reaches it: no personal data: only our own questions, asked as a buyer would ask them, and our own name and site address. When: only once we set its API key; until then it is never asked. Where: the United States.
- Anthropic, PBC (the Claude API): answers, through its API, the questions a buyer might ask an assistant, so we can see whether its answers name us. What reaches it: no personal data: only our own questions, asked as a buyer would ask them, and our own name and site address. When: only once we set its API key; until then it is never asked. Where: the United States.
- Perplexity AI: answers, through its API, the questions a buyer might ask an assistant, so we can see whether its answers name us. What reaches it: no personal data: only our own questions, asked as a buyer would ask them, and our own name and site address. When: only once we set its API key; until then it is never asked. Where: the United States.
- Google LLC (the Gemini API): answers, through its API, the questions a buyer might ask an assistant, so we can see whether its answers name us. What reaches it: no personal data: only our own questions, asked as a buyer would ask them, and our own name and site address. When: only once we set its API key; until then it is never asked. Where: the United States.
- Google LLC (the Search Console API): tells us how our own site appears in Google Search: the searches it was shown for, and how often it was clicked. What reaches it: no personal data: only our site’s address and the credentials of our own service account. What comes back is counted across everyone who searched, never one person. When: only once we set its credentials; until then nothing is asked. Where: the United States.
- Microsoft Corporation (the Bing Webmaster API): tells us how our own site appears in Bing: the searches it was shown for, and how often it was clicked. What reaches it: no personal data: only our site’s address and our own API key. What comes back is counted across everyone who searched, never one person. When: only once we set its API key; until then nothing is asked. Where: the United States.
- Google LLC (Google Calendar): shows our co-founder’s appointment calendar on his personal pages, so you can book a call with him. What reaches it: what any page from Google receives when your browser loads it: your IP address and browser details, but not the address of the page you came from; and, if you book, the name and email you type into it, which go to Google and to him. When: only on the pages that show his calendar, once you scroll to it. Where: the United States.
We do not sell personal data, and we do not use it for advertising.
9. Where your data goes
Several of these companies are in the United States, and Cloudflare runs a global network, so your data may be processed outside the UK. Where it is, we rely on the safeguards in each company’s data processing terms: the UK Extension to the EU–US Data Privacy Framework where the company is certified under it, or the UK’s International Data Transfer Addendum.
We have not asked Cloudflare to keep our database or file storage in any particular country, so they may be stored outside the UK.
Our encrypted backups of the database are also kept on a computer in our own control.
10. How long we keep it
- Your account: until you delete it. Deleting it removes your profile and photo, your sign-in methods, passkeys and sessions, your connections from the command line tool and AI assistants, every workspace you own, and every file of every project in them.
- Projects you delete: deleting a project removes it from the service: its room closes, its links stop working, and its data, including its viewers’ events, is taken out of use.
- Permanent deletion: to have all the data associated with a project or an account permanently erased, write to privacy@getroomi.com and we will erase it, except what the law requires us to keep.
- Viewers’ events: for as long as the publisher keeps the project, then as above.
- What a viewer did inside a demo (section 4): each viewer’s screens and clicks for 12 months from the visit, then counted into daily totals per screen and per element of the build, which name nobody, and deleted. They are deleted at once when the viewer asks from the room, and within 30 days of the publisher deleting the project, totals included. A plan that shows a shorter history only hides them sooner; no plan keeps them longer.
- A viewer’s answer about clicks: each answer, the version of the words they were shown, where they gave it and when, for two years: as long as what it covers, and 12 months more, as the record of what they were asked and what they chose.
- A replay of a visit: can be opened for 30 days from the visit on Team and 90 days on Enterprise, then no longer, and the publisher can delete one sooner. A replay that has run out or been deleted does not come back, whatever the plan becomes; the screens and clicks it was drawn from are kept, and deleted, as above.
- Pictures of the demo’s screens: kept with the project, a newer picture of a screen taking the place of the older one, and deleted within 30 days of the publisher deleting the project. They hold nothing about any viewer.
- Exports: on the plans that have it, a publisher can download the counts per screen, per element, per field and per funnel step as a spreadsheet file. An export names nobody: it holds the demo’s own labels and counts, never a viewer’s name, email or visit.
- Sessions: a session stops working after 7 days without use.
- Sign-ins: our record of each sign-in (when, and which way) for 13 months, then deleted. Deleting your account deletes it straight away.
- Emails we send: the address and contents are removed from our outbox after 30 days, and the rest of the record after 90. If you ask us to stop emailing you, we keep a keyed hash of your address so we can.
- Codes and tries at a room’s door: a code’s keyed hash until it is used or its 10 minutes run out; each try at a password or a code, with its keyed hashes, as long as the publisher keeps the project, so they can see the wrong tries on each link.
- The free guide (section 5): without your yes to guides and news, your address until the guide’s email has gone (at most 30 days, while our outbox holds it), then only its keyed hash; with it, your address until you unsubscribe, then only its keyed hash. Your answer, the words you were shown, when you gave it, and where on the site you asked, are kept as the record of your consent. To have all of it erased, write to us.
- Billing records: six years, for tax.
- Our record of what we do to accounts, and of moderation: kept permanently, and cannot be edited, so we can always show what was done and why. It names the account it concerns.
- Error logs: 30 days, with email addresses and anything that looks like a key or token removed before they are stored.
- Seat-counting hashes: deleted soon after you leave, as section 4 says.
- Measurement of the site and the app (section 5): each page, section, click and app event is kept for 13 months, then counted into daily totals per page and source, which name nobody, and deleted. Crawler visits are deleted after 13 months too.
- Your visits joined to your account: a summary of how you came to us (where from, the page you landed on, what you read and how long it took), kept with your account until you choose not to join them or delete your account; deleting your account removes it and your app events, and leaves your earlier visits joined to no one.
Deleted data may remain in our backups until those are deleted.
11. Your rights
You can ask to see the personal data we hold about you, have it corrected or erased, restrict or object to how we use it, and receive a copy of it in a portable form. Write to privacy@getroomi.com. We answer within one month, and may ask you to confirm who you are first.
If you are a viewer, your request is usually the publisher’s to answer, since they control your data. Ask them, or ask us and we will pass it on and help.
If you said yes to sharing what you click in a room, you can stop at any time from the top of the room, and at the same time have what was logged of your clicks on that link deleted, from every visit. It is deleted then and there, as the publisher has instructed us; the record of what you were asked and what you answered is kept, as section 10 says.
When a viewer’s data is erased, their name may remain inside older entries of the project’s history, which can never be edited, where it is shown as “Erased viewer”, and the erased data stays in our backups until those are deleted.
If you are unhappy with how we have handled your data, you can complain to the Information Commissioner’s Office at ico.org.uk, or to the data protection authority where you live. We would like the chance to put it right first.
12. Automatic checks on Community listings
When you list a project, automatic checks decide whether it goes up straight away, as the terms, section 7, describe. They look at the listing, not at you, and a person reviews a listing whenever you appeal.
13. How we protect it
Everything travels encrypted. Files are kept in private storage and served only through our own code, checked against our records. Viewer links are kept hashed and encrypted, so the database alone opens no room. Demos are served from an address of their own, apart from the platform; a demo that runs a server runs in its own container, never next to another publisher’s and never with access to the platform’s data. Our backups are encrypted before they are stored. Our own access to accounts needs a passkey with a PIN or biometric, and every change we make is recorded.
14. Children
Roomi is not for children. You must be at least 18 to hold an account, and we do not knowingly collect data about children.
15. Changes to this policy
If we change this policy in a way that matters, we will tell account holders before the change takes effect, and change the date at the top.