Cookie policy

Cookies are small text files a site stores on the device you browse with — a computer, a phone, or the browser built into a VR headset. They let a site recognise the same device across requests, which is how it can remember that you already signed in instead of asking again on every page.

A cookie is session or persistent: a session cookie disappears when you close the browser, a persistent one stays until it expires or you delete it. Ours are persistent, with the lifetimes listed below.

This is the complete list. Every one of them is set by us, on this domain, and is strictly necessary — the site cannot do what you asked of it without them.

• age_attested — records that you confirmed you are of legal age at the doorway. Without it, the age notice covers the catalogue until you confirm. Expires after 30 days.
• onboarding_grace — remembers that you have only just arrived, so the one-time notice about watching in a browser waits for a later visit instead of landing on top of the questions above. Expires after 30 minutes.
• refresh_token — keeps you signed in between visits and lets your session renew without typing your password again. It is removed when you sign out. Expires on the date issued with it when you sign in.
• access_token — authorises the requests behind the pages you are already on: your purchases, your downloads, your workspace. It is short-lived and scoped so the browser only ever sends it to the one path that needs it. Expires within minutes and is renewed.

All four are httpOnly — no JavaScript on the page can read them, including any script that ever managed to get itself onto it — sent only on requests originating from this site, and, in production, only over HTTPS.

Your cart is not a cookie. It is stored on our servers against your account, so it follows you between devices and survives clearing your browser.

We do not use analytics cookies, advertising cookies, tag managers, pixels, session recorders, or any similar technology. No third-party analytics service receives anything about your visit, and we do not build a profile of your interests.

This is a property of how the site is built, not a promise about how we behave: there is no such code on the page for us to switch on. If that ever changes, this page changes with it, and the date above changes too.

We do keep a count of how often each page is loaded, and we want to be exact about it because it is the one thing on this page that is measurement rather than the absence of it. It happens entirely on our own server, from the request your browser already makes. No cookie and no script are involved — this is why the list above is unchanged, and why nothing here can be blocked by blocking cookies.

For each page load we record three things:

• The path of the page, without anything after the question mark in the address.
• The moment it happened.
• A short code standing in for “the same browser”, computed from your IP address and your browser’s identifying line. That code is rebuilt from scratch every midnight UTC, so the same device produces a different one tomorrow and two days of records cannot be joined together — by us or by anyone who obtained them.

Your IP address is used to compute that code and is never stored, never logged, and never sent on — it does not leave the server that received your request. There is no account, no identifier of yours, and no record of whether you were signed in. What this produces is a count: how many pages were loaded, on which day, and which pages they were.

What it cannot produce, by construction: a path through the site for any one person, a count of unique people over a week or a month, or any way to tie a visit to you. It exists so we can tell whether anyone is finding the site.

A few preferences are kept in your browser's own storage rather than in a cookie. These are never sent to us — they stay on the device and only that device can read them:

• Whether you collapsed the sidebar.
• Your recent searches, so the search box can offer them back to you. Clearing them in the search box removes them.
• Whether the current tab is showing the headset layout. This one is cleared when you close the tab.
• For creators, a marker that lets an interrupted upload resume where it stopped instead of starting over.

Clearing site data in your browser removes all of these.

No third party sets a cookie on this site through us. There are, however, two places where your browser talks to somebody else's servers, and it is worth being precise about them:

• Video and images are delivered by a content delivery network, so that a large VR file streams from somewhere near you. Your browser fetches those files from that provider directly, which means it sees what any server sees when it serves a file — your IP address, your browser, and which file was requested. The links it receives are signed and expire.
• Paymentshappen on our payment provider's own page, which opens in a separate tab. Anything stored while you are there belongs to that page, not to this one. We never see your wallet credentials, and the provider does not set cookies here.

There is no third-party font, script, or embed on our pages: the typeface is served from our own servers, so loading the site does not tell anyone else that you visited.

You can delete cookies, block them, or ask to be warned before one is set, from your browser's settings. The relevant instructions:

• Cookies in Google Chrome
• Cookies in Mozilla Firefox
• Cookies in Apple Safari
• Cookies in Microsoft Edge

Be aware of what blocking them costs here, because every cookie we set is a necessary one. If you block them for this site the age notice will cover the catalogue on every visit, you will not be able to stay signed in, and you will not be able to buy anything or reach a video you already own. Nothing you have bought is lost — you regain access as soon as you can sign in again.

We do not show a cookie banner, because there is nothing here for you to consent to. All three cookies are strictly necessary to deliver what you asked for; there is no analytics cookie, no advertising cookie and no third-party tracker to ask you about. The page counts described above set nothing on your device and cannot follow you from one day to the next — a banner would be asking permission for something we are not doing.

If we ever introduce a cookie that is not strictly necessary, we will ask you first, and the site will work whether you say yes or no.

We will update this page whenever what we store changes, and the date at the top changes with it. Because this page is an inventory rather than a statement of intent, an update means the site itself changed — not that we reinterpreted anything.

If anything here is unclear, or you think the site set something this page does not mention, write to us through the contact form. It reaches a person, and you do not need an account to use it.