Legal and trust
Cookies and browser storage
This website sets no cookies and runs no analytics, advertising or tracking, so there is no cookie banner. In your browser’s local storage it keeps how smoothly your device draws the site’s motion, from your first visit, so a slower device gets lighter motion straight away – and your choices, each only after you made it or ran a check.
Measured in your browser when this page’s script runs.
Need this page another way – plain text, large print or read aloud? Download it as plain text or write to support@xovris.ai for the format you need.
What the site keeps in your browser
In short Every item the site keeps in your browser - what it keeps, why, and for how long.
How long Until you clear this site’s data in your browser (Local storage)
xovris.lastCheck- What it keeps
- The last website address you checked
- Why
- So the next page can offer it again
- In your browser now
- Read when the page loads
xovris.stack- What it keeps
- The stack you chose in the install guide
- Why
- So the docs show the commands for your stack
- In your browser now
- Read when the page loads
xovris.pm- What it keeps
- The package manager you chose
- Why
- So every command is written for it
- In your browser now
- Read when the page loads
xovris.currency- What it keeps
- The currency you chose for prices
- Why
- So the pricing page shows prices in your currency next time
- In your browser now
- Read when the page loads
xovris-motion- What it keeps
- Your motion setting
- Why
- So pages move as you chose
- In your browser now
- Read when the page loads
starlight-theme- What it keeps
- Your theme: light, dark or automatic
- Why
- So the site keeps the look you chose
- In your browser now
- Read when the page loads
xovris-contrast- What it keeps
- Whether you asked for more contrast
- Why
- So the site keeps the contrast you chose
- In your browser now
- Read when the page loads
starlight-synced-tabs__pm- What it keeps
- Which tab you chose in the docs: your package manager or your AI tool
- Why
- So every docs page opens on the same tab
- In your browser now
- Read when the page loads
xovris.helper.visitor- What it keeps
- A random number for this browser, used by Xovris’s helper
- Why
- So each browser has its own daily allowance of helper messages; it says nothing about who you are
- In your browser now
- Read when the page loads
xovris.mascot.spot- What it keeps
- Where you last put Xovris on the page, as a share of the window
- Why
- So Xovris waits where you left it on the next page; pressing Home on it forgets the spot
- In your browser now
- Read when the page loads
xovris.glyph.memory- What it keeps
- The address you asked Xovris to remember, with that check’s result and its date
- Why
- Kept only after you choose “Remember it”, so Xovris can offer to check it again; “Forget it” removes it
- In your browser now
- Read when the page loads
xovris.helper.kept- What it keeps
- Your conversation with Xovris’s helper, kept for your next visit
- Why
- Kept only after you choose “Keep it”, for 30 days from your last message; “Forget it” removes it
- In your browser now
- Read when the page loads
xovris.helper.state.v1- What it keeps
- The same summary, beside a conversation you chose to keep
- Why
- Kept only after you choose “Keep it”, with the conversation it sums up; “Forget it” removes both
- In your browser now
- Read when the page loads
xovris.sound- What it keeps
- That you turned Xovris’s sounds on
- Why
- So the sounds stay on from page to page; turning them off removes it
- In your browser now
- Read when the page loads
xovris.notifyBack- What it keeps
- The services you asked to be told about when they are back, until that happens or seven days pass
- Why
- So the page shows that you will be told, and lets you stop it
- In your browser now
- Read when the page loads
xovris.delegation- What it keeps
- Which way you chose to connect your app: Xovris does it, the wizard does it from your terminal, or you do it by hand
- Why
- So the connect section opens on the way you chose last time
- In your browser now
- Read when the page loads
xovris-render-tier- What it keeps
- How smoothly this device drew the site’s motion the last time it was measured
- Why
- So a slower device gets lighter motion straight away instead of stuttering while it is measured again. It is kept only once you choose motion yourself; until then each page measures again and nothing is stored
- In your browser now
- Read when the page loads
xovris.for- What it keeps
- Whose examples you chose to see first: a kind of home or organisation, or the job you do
- Why
- So every page puts your examples first; choosing “Everyone” removes it
- In your browser now
- Read when the page loads
xovris.depth- What it keeps
- That you asked the site to explain things in detail
- Why
- So every page opens its technical detail for you; choosing “Simply” removes it
- In your browser now
- Read when the page loads
xovris.legal.read- What it keeps
- A short fingerprint of each section of the legal pages, the guides and the trust centre as this browser last read them, and the date – never your words or your address.
- Why
- Only if you ask a legal page, a guide or the trust centre to mark what changes: so it can mark any section that has changed since you last read it.
- In your browser now
- Read when the page loads
xovris.fonts- What it keeps
- That this browser has already fetched the site’s two typefaces
- Why
- So the next page draws its words in them from the first moment, instead of a stand-in face that is swapped a moment later
- In your browser now
- Read when the page loads
xovris.uptime- What it keeps
- The answers of your last few checks of an address from several countries, and when each ran
- Why
- So checking the same address again within ten minutes shows the answer you already have, and one browser never runs more than six of these checks an hour
- In your browser now
- Read when the page loads
xovris.builds.v1- What it keeps
- The pages you built on /build, each with your request
- Why
- So your builds are here when you come back - never sent anywhere; Forget removes them
- In your browser now
- Read when the page loads
xovris.build.kept.v1- What it keeps
- The build you are working on and its history
- Why
- So every moment of it stays one you can go back to on this device - never sent anywhere
- In your browser now
- Read when the page loads
xovris.build.approved.v1- What it keeps
- Which moment of a change you approved, and when
- Why
- So the moment you chose to publish stays the one that goes live
- In your browser now
- Read when the page loads
xovris.build.limit.v2- What it keeps
- The limit you set on what building may spend
- Why
- So a build never spends past the limit you chose
- In your browser now
- Read when the page loads
xovris.build.door.v1- What it keeps
- When your last build ask on /build was answered, and how
- Why
- So your next ask opens straight on the next step that fits it – kept 30 minutes
- In your browser now
- Read when the page loads
xovris.build.budgets- What it keeps
- The ceilings you set for your builds – page weight, JavaScript and monthly running cost
- Why
- So every build is checked against your own limits each time you open /build – kept until you change or clear them
- In your browser now
- Read when the page loads
xovris.build.minAge- What it keeps
- The youngest a package may be, in days, before a page you build may load it
- Why
- So a package published only days ago waits until it is as old as you chose – kept until you change it
- In your browser now
- Read when the page loads
xovris.build.notify.v1- What it keeps
- Whether to tell you when a build is ready
- Why
- So a long build can let you know when it is done
- In your browser now
- Read when the page loads
xovris.build.pane.v1- What it keeps
- Whether the preview of your build is open beside the conversation
- Why
- So /build opens the way you left it
- In your browser now
- Read when the page loads
xovris.build.preview.v1- What it keeps
- The page you are building, as it is now
- Why
- So the preview in its own tab shows the moment you are looking at
- In your browser now
- Read when the page loads
xovris.build.rules.v1- What it keeps
- The rules you gave for your builds
- Why
- So every build follows the rules you set, on every message
- In your browser now
- Read when the page loads
xovris.build.voice.v1- What it keeps
- Whether the builder reads its answers aloud
- Why
- So the device’s own voice speaks only when you turned it on
- In your browser now
- Read when the page loads
xovris.doc.look- What it keeps
- The colours and credit line you chose for files you make
- Why
- So every file you download looks the way you chose
- In your browser now
- Read when the page loads
xovris.doc.plain- What it keeps
- Whether the files you make carry a plain version, and the reading age you chose for it
- Why
- So every file you download comes with its plain version the way you chose
- In your browser now
- Read when the page loads
xovris.build.launch.v1- What it keeps
- What you chose for putting a build live – where it is hosted and its address
- Why
- So going live picks up where you left it on this device - never sent anywhere until you go live
- In your browser now
- Read when the page loads
xovris.build.hosts.v1- What it keeps
- The hosts you had Xovris read for putting a build live, each with the day it was read
- Why
- So their terms and prices are there again on this device without reading them twice - never sent anywhere
- In your browser now
- Read when the page loads
xovris.build.hosts.pending.v1- What it keeps
- Hosts whose reading had not finished when you left
- Why
- So Xovris reads them again by itself the next time the page opens, instead of asking you
- In your browser now
- Read when the page loads
xovris.build.queue.v1- What it keeps
- Messages you wrote for your build to send after the change in hand
- Why
- So they wait their turn across a reload and go out one at a time - never sent before their turn
- In your browser now
- Read when the page loads
xovris.models.recent- What it keeps
- The last four AI choices you picked in a chat box, on this device
- Why
- So the ones you use stand first the next time you open the box - nothing about what you asked
- In your browser now
- Read when the page loads
How long For as long as this browser keeps this site’s data, as a small database (IndexedDB)
xovris-build-signing- What it keeps
- A key this browser made to sign the hand-over packs of your builds - its private half never leaves this browser
- Why
- So every pack you download carries the same public key, and a buyer can check each one is yours and unchanged
- In your browser now
- Read when the page loads
How long Until you close the tab (Session storage)
xovris.status- What it keeps
- Your own run of the status page’s checks: how many were fine and when
- Why
- So the status in the header shows your run on every page for the rest of this visit; it goes when you close the tab
- In your browser now
- Read when the page loads
sl-sidebar-state- What it keeps
- Which groups of the docs sidebar are open
- Why
- So the sidebar stays as you left it while you move between pages
- In your browser now
- Read when the page loads
xovris.helper.chatxovris.helper.chat.buildxovris.living.carry- What it keeps
- Your conversation with Xovris’s helper in this tab
- Why
- So the conversation carries on when the helper takes you to another page
- In your browser now
xovris.helper.chatRead when the page loadsxovris.helper.chat.buildRead when the page loadsxovris.living.carryRead when the page loads
xovris.helper.history- What it keeps
- The earlier conversations you started with Xovris’s helper in this tab
- Why
- So a new conversation keeps the last one a press away, until you close the tab
- In your browser now
- Read when the page loads
xovris.mascot- What it keeps
- Whether you minimised Xovris, the site’s helper
- Why
- So it stays minimised on your next visit until you bring it back
- In your browser now
- Read when the page loads
xovris.helper.turn- What it keeps
- How many times the helper has opened in this tab
- Why
- So its suggestions take turns across every area instead of repeating the same few
- In your browser now
- Read when the page loads
xovris.glyph.askedxovris.helper.keep.no- What it keeps
- That you said no to Xovris remembering your checks, for this tab onlyThat you chose not to keep the conversation
- Why
- So Xovris does not ask again while this tab is open
- In your browser now
xovris.glyph.askedRead when the page loadsxovris.helper.keep.noRead when the page loads
xovris.helper.state.v1- What it keeps
- Xovris’s short summary of a long conversation with its helper, in this tab
- Why
- So a long conversation carries on without every message being read again; it goes when you close the tab
- In your browser now
- Read when the page loads
xovris.programme- What it keeps
- The integration counts xovris.ai last measured (how many integrations passed an install test and how many are ready) and when it read them
- Why
- So moving between pages in this tab asks for the counts once in ten minutes instead of on every page; it goes when the tab closes
- In your browser now
- Read when the page loads
xovris.planView- What it keeps
- How you last viewed a plan in a chat
- Why
- So a plan opens the way you left it in this tab
- In your browser now
- Read when the page loads
xovris.wall.kept- What it keeps
- What you typed before signing in, for up to 30 minutes in this tab
- Why
- So your first message is back in the box once you are in - taken once, then removed
- In your browser now
- Read when the page loads
xovris.ask.handed- What it keeps
- What you typed in a box on one page, for up to 10 minutes in this tab
- Why
- So the conversation on the next page asks it for you without your words ever going in a web address - taken once, then removed
- In your browser now
- Read when the page loads
The build fails if any page sets a cookie, and the list above is checked against every place the site’s code writes to your browser.
Measured on this build
In short Each release is read just after it goes live; any cookie or item this page does not list is named here.
Reading this build’s measurement…
Each release’s pages are read this way just after it goes live, and this page shows only that release’s own reading; any cookie or item this page does not list is named here.
Why no consent is asked
In short Each item is strictly necessary, so no consent is asked; clearing this site’s data removes them all.
Each item is strictly necessary to give you something you asked for, so under the Privacy and Electronic Communications Regulations it needs no consent. Clearing this site’s data in your browser removes them all.
The free check
In short A free check contacts public DNS resolvers and domain registries from your browser, without cookies.
When you run a free check, your browser contacts public DNS resolvers and domain registries directly, without sending or accepting cookies. The privacy notice explains what they see. Privacy
No recorded example is needed here: this page is the document itself, and the check at its head ran in your browser as you opened it.