Privacy
This page says, in plain words, what this website collects about the people who use it, what it does with that, and who else handles it. It covers tonvincollection.com only. The other sites in the collection are separate sites with their own practices. It was last reviewed on .
What we collect
You can read the public pages without an account and without giving us anything. Like every website, serving you a page means your network address and the page you asked for pass through Cloudflare, the network in front of this site, and through our server.
Beyond that ordinary handling, we collect information in these situations only:
- when you send a message through the contact form;
- when anyone asks for a sign-in link, and when you sign in to the Client portal, if we have added you to it;
- when Google Analytics counts a visit to a public page;
- when an error report is sent because something went wrong, if error reporting is enabled.
Analytics
The public pages use Google Analytics to count visits and see which pages are read. It does not load with the page. It loads after your first click, key press, scroll or touch, or after six seconds if you do nothing, whichever comes first. A visit that ends before either happens is not counted.
Once it has loaded, Google Analytics sends Google the address of the page you are on, along with the technical details its tag collects, and it sets its own cookies in your browser.
It is switched off on the sign-in pages and in the Client portal. If you move onto them from another page, it is turned off for as long as you stay, because those addresses can hold a one-time sign-in link and your email address.
Our security policy also allows a page-view counter script from Cloudflare to load. Cloudflare adds that script from its side if the setting is on; the site’s own code does not add it.
The contact form
When you send the contact form, your name, email address and message are saved in the collection’s database and emailed to our team through Resend, an email delivery service. Your address is set as the reply-to, so we can answer you directly.
If saving fails, the email is still sent where it can be; if the email fails, the saved copy is still there. If either step fails, our server log records the failure and the saved message’s reference number, not your name, email address or message.
The form has a hidden field that only automated programs fill in. A submission that fills it is dropped without being saved or sent.
To limit abuse, the form accepts only a few messages a minute from one network address, taken from the header Cloudflare adds to your request or, failing that, from the forwarding header. A request that arrives with neither header is not counted or limited. The count is held only in the running server’s memory and stops counting after a minute. It is not written to the database.
Saved messages stay in the database until we delete them: the site has no automatic expiry. If you want yours deleted, tell us through the contact page and give the email address you used.
Signing in to the Client portal
The Client portal is for people we have added to it. There is no public sign-up, and the sign-in form does not create an account for an address we have not added.
For people we have added, we store your email address, a role (either member or administrator) and the time of your latest sign-in: each time you open a link, the sign-in system updates a verified time on your record. When you ask for a sign-in link, we email it to you through Resend. The link works once and lasts twenty-four hours.
The sign-in system saves a one-time link record when a link is requested: the address that was typed in, a scrambled form of the link’s secret and its expiry time. It does this for any address typed into the form, whether or not we have added it; only an address on our list is emailed. The record is deleted when the link is used. A link that is never used, or that has expired, is not removed automatically, so its record stays in the database.
Opening the link starts a session, kept in a cookie in your browser for up to ninety days. We check that you are on our list when the link is opened, and on every request to the Client portal after that, so removing someone takes effect on their next request.
To stop the sign-in form being used to flood someone’s inbox, we count link requests in the server’s memory, per email address and per network address, and refuse more than a few in a short time. Requests that arrive without a usable Cloudflare address share one count. These counts are not written to the database.
The sign-in pages are marked so that Cloudflare does not store them and search engines do not list them. They are also outside the analytics described above.
Games saved on your device
The DERELICT game saves your progress and settings in your own browser, in local storage on your device. The entries are named tvc.derelict.save, tvc.derelict.settings and backup copies of the save that start with tvc.derelict.save.bak. The game also writes and removes a short test entry to check that storage works.
These entries are read and written by the game in your browser. The game does not send them to us. Clearing this site’s data in your browser removes them. If your browser blocks storage, the game still runs and tells you that progress will not be saved.
Error reports
When error reporting is enabled, an error on the site sends a report to our self-hosted error tracker. A report has the page path, a status, the name and message of the error, the error reference code the site generates, and at most the top five lines of the error’s stack: function names, file names and line numbers. Reports about errors in your browser reach the tracker through this site’s own server, not from your browser directly.
Reports are built from those fields alone. They never include cookies, request headers, what you typed into a form, the query part of an address, or an email address; email addresses and token-like strings that turn up in a path or message are replaced before the report is sent. When error reporting is not enabled, nothing is sent.
Who processes data
These are the services that handle information on our behalf or that your browser contacts through this site:
- Cloudflare is the network in front of the site. It carries every request, including a contact message, and it serves files such as images and video previews from its storage.
- Google runs Google Analytics, described under Analytics.
- Resend delivers email: it receives the contact message we forward to our team, and the sign-in links we send to people we have added.
- Our self-hosted error tracker receives the error reports described above, when error reporting is enabled.
- The music and video pages play files from audio hosts of other sites in the collection and from Cloudflare storage. The audio and video files are fetched only when you press play. The preview images that stand in for a video, on the videos page and in the showcase, are fetched from Cloudflare storage when the page that shows them loads.
Your choices and how to reach us
You can use the whole site without the analytics: the script is optional, and your browser’s tracking protection, a content blocker or Google’s own opt-out tool will stop it. Clearing this site’s data in your browser removes game saves and sign-in cookies.
To ask what we hold about you, or to have a contact message deleted, use the contact page. For a security problem, use the security page, not the contact form.
We update this page when the site changes. The date at the top is when we last reviewed it. It describes what the site does; it makes no claim of any certification.