Legal

Privacy Policy

1. Who runs this website

This website is a personal portfolio, run by me, Thanoa (also known online as @qxthanoa), as an individual based in the United Kingdom. I'm not a registered company, and there's no separate organisation behind the site — I'm the person who decides what data it collects and what happens to it.

2. What information is collected

There are two places on this site where you can hand over information yourself: the Contact form and the Guestbook.

The Contact form

If you use it, I receive:

The Guestbook

If you post in the guestbook, the site stores:

If you like an entry, the site also stores a one-way hash of a random visitor ID generated in your browser, together with the entry it belongs to, so that each visitor can only like an entry once. Guestbook entries, names and like counts are public — anyone who visits the guestbook can see them.

I don't ask for, or knowingly collect, any other personal details about you through these forms or anywhere else on the site.

Everything else

Apart from the Contact form and the guestbook, this website is a static profile page: it doesn't have user accounts and doesn't run any analytics or tracking scripts. The site itself doesn't set cookies. Instead it uses your browser's local storage to remember a few things on your device:

Your theme, language, name and anonymous settings never leave your device. The edit codes and visitor ID are sent to the site's server only when you edit, delete or like something, so it can do what you asked. If you clear your browser's site data, those edit codes are gone, and you won't be able to edit or delete those entries yourself any more (see section 5 for what you can do instead).

One thing is outside my control: when I'm listening to music on Spotify, the page loads YouTube's embedded player in the background (see section 4), and Google may store its own cookies or similar data in your browser when that happens.

Because this site is hosted on Vercel, and loads a small number of resources (fonts, images, a live-status connection, lyrics, an embedded player) directly from other providers' servers, those providers will typically see standard technical information about your visit — most notably your IP address — in the same way any web server does when your browser requests something from it. This is covered in more detail in sections 4, 7 and 10 below. I don't receive or store this information myself.

To protect the Contact form and the guestbook from abuse, the site's server also looks at your IP address when you submit the form or post an entry, and when you open the connection check page. It asks an IP-reputation service whether the address belongs to a VPN, proxy, Tor or similar anonymising network, and it keeps short-lived counters (using a hashed version of your IP address) to limit how often something can be posted. Your IP address is never saved with your message or guestbook entry. See sections 5 and 6.

3. Why it's processed, and the legal basis

I process the information you submit through the Contact form for one reason: to read your enquiry and reply to it. I process guestbook entries so that they can be displayed in the guestbook, and likes so that they can be counted. I don't use any of it for marketing, profiling, or any automated decision-making.

For the Contact form, the legal basis I rely on is your consent — you have to actively tick a box confirming you've read the Terms of Use and acknowledge this Privacy Policy before the form will submit. For the guestbook, it's also your consent: you choose to write and publish an entry, and the notice directly under the guestbook form tells you that posting means you agree to the Terms of Use and acknowledge this policy. Where relevant, I also rely on my legitimate interest in being able to respond to messages people choose to send me and in running a guestbook people can enjoy.

The VPN and proxy check, the posting limits and the duplicate-message check all rely on my legitimate interest in keeping the Contact form and the guestbook free from spam, harassment and abuse.

4. The Discord, Roblox, music & community widgets

The homepage shows my own live Discord and Roblox status, avatar, badges and friends list, and what I'm currently listening to on Spotify. This is my own public profile information, not anything collected from visitors. It's fetched automatically — either by the site's server or directly by your browser — from Discord's, Roblox's and Lanyard's public-facing services, and simply displayed back on the page.

Visiting the site doesn't share your Discord, Roblox or Spotify account, if you have one, with me or with these services in any way. There's no login, no linking of accounts, and no way for the site to identify who you are on any platform.

The homepage also has a Community section that shows the public Discord server I run or promote: its name, icon, how many people are online, and the display names and avatars of some of the online members, with a button to join. Your browser fetches this directly from Discord (discord.com for the server's public widget data and server icon details, and cdn.discordapp.com for the server icon and member avatars), and it refreshes roughly once a minute while the page is open. The member names and avatars come from Discord's own public server widget, which server members can appear in according to Discord's and the server's settings; I don't collect, copy or store them, and they are shown to you only for as long as the page is open. The names appear in a small pop-up when you hover over, focus on or tap an avatar. As with any request your browser makes to Discord, Discord will see your IP address and standard browser information, under Discord's own privacy policy. Nothing about you is sent to Discord beyond that, and I don't receive anything about you from it. If you click the join button, you leave this site and are subject to Discord's terms and privacy policy, and the server's rules, from that point on.

When I'm listening to a track on Spotify, the page also does the following:

The track in the "About" section when I'm not listening to anything is a file hosted on this site itself, so playing it doesn't involve any other provider.

5. The guestbook

The guestbook lets anyone leave a public message, with a name or anonymously, and like other people's entries. No account is needed. Here's exactly how it works with your information:

6. The VPN and proxy check

The Contact form and posting a new guestbook entry aren't available from VPNs, proxies, Tor or similar anonymising networks. This is purely to keep them free from spam and abuse. Here's how it works:

7. Third-party services used by this site

I don't share the contents of your contact form submission with anyone beyond what's described below. Guestbook entries are stored in a database (see below) and shown publicly on the guestbook. The specific external services this site actually talks to are:

None of these services are used for advertising, and I don't run any analytics or tracking tools on this site.

8. How your information is stored

Contact form. When you submit the form, your message is sent, from the site's server, straight to a private Discord channel that only I can see. It isn't copied into any separate database, and no email is sent automatically anywhere in this process — the email address you provide is simply included in the message content so I can reply to you manually if I choose to.

Guestbook. Guestbook entries, likes and the posting counters are stored in a MongoDB Atlas database (see section 7). That includes entry text, optional names, timestamps and like totals, plus the one-way hashes described in section 5. The site's server is the only thing that reads from and writes to it, and the database login is kept as a server-side environment variable, never in the website's public code.

9. How long information is kept

Contact form submissions are kept for a maximum of 30 days from the date you send them. Once I've read and, where appropriate, replied to your message, I delete the forwarded message from Discord myself, and in any event no later than 30 days after you sent it. I don't archive, export, or keep copies of contact form submissions beyond this window.

Guestbook entries have no automatic expiry. They stay until they're deleted — by you, from the browser you posted from, or by me — and I may remove entries, or clear the guestbook, at any time. When an entry is deleted, it and the likes attached to it are removed from the database straight away. If MongoDB Atlas keeps backups under my plan, deleted entries can remain in those backups until they're replaced on Atlas's normal schedule; they aren't restored or used for anything else.

Posting counters (the hashed-IP counters and recent-message notes) delete themselves automatically within about two hours. VPN check results are held in temporary server memory for at most 30 minutes and are never saved to a database. Data in your browser's local storage stays on your device until you clear it.

10. International transfers

The service providers listed in section 7 — including Vercel, Discord, GitHub, Google and MongoDB — are based outside the UK, and your information (or, in the case of directly-loaded resources, your IP address) may be processed on servers located outside the UK and European Economic Area, including in the United States. The same can apply to smaller services such as proxycheck.io and lrclib.net. Where this happens, these providers are responsible for putting appropriate legal safeguards in place, such as the UK's International Data Transfer Addendum or the EU Standard Contractual Clauses. You can find more detail in each provider's own privacy policy.

11. Security

The site is served over HTTPS. The Discord webhook address the contact form relies on, and the database login the guestbook relies on, are stored as server-side environment variables and are never included in the website's public code, so they aren't visible to visitors. Contact form submissions and guestbook posts are validated on the server as well as in the browser, so they can't be bypassed simply by skipping the page's JavaScript, and guestbook text is always displayed as plain text, never as code.

Guestbook edit codes are long random values, and only a one-way hash of each is stored. Your visitor ID and IP address are only ever stored in hashed form. The posting limits and the VPN check are there to protect the site from abuse.

No method of transmission or storage is completely secure, so while I take reasonable steps to protect your information, I can't guarantee absolute security.

12. Your rights

If you're in the UK or EU, data protection law gives you a number of rights over your personal information. In relation to anything you've sent me through the Contact form or the guestbook, you can ask me to:

For guestbook entries posted from your current browser, you can edit or delete them yourself at any time, without asking me. Because anonymous entries and hashed values aren't linked to who you are, I may only be able to act on a request if you tell me what the entry said and roughly when you posted it, and I can't identify you from a hash alone.

To exercise any of these, see the contact details in section 15. I'll respond as quickly as I reasonably can.

13. Complaints

If you're unhappy with how I've handled your personal information, I'd appreciate the chance to sort it out directly first — but you also have the right to complain to the UK's data protection regulator, the Information Commissioner's Office (ICO):

14. Changes to this policy

I may update this policy from time to time, for example if the website starts doing something new with your information. Any changes will be posted on this page with an updated "last updated" date at the top.

15. Contact

The quickest way to reach me about anything in this policy, including any of the rights listed in section 12, is on Discord: @qxthanoa. I don't publish a separate email address for this website, so Discord is the best way to get in touch.

↑ Back to top