Privacy
Privacy notice
The short version
- When you only read the site: the pages carry no ads, no advertising trackers and no analytics code. They set no cookies and load nothing from other companies. The company that hosts the site does receive your IP address and other technical details of every request, because no page can be delivered without them, and it keeps server logs.
- If you use the theme switch or the animation switch: your choice is saved in your own browser and sent nowhere.
- If you start the human check in the contact form: it is a security check run by Google, and it loads only after you press its button. Google then receives your IP address and details of your browser and device, and stores a cookie in your browser. The check is there to tell people from bots, not to advertise.
- If you send a message: your name, your email address and your message go to Netlify, the host, which keeps them for me, screens them for spam and sends me a copy by email.
- What I do with it: I read and answer messages. I do not sell what I receive or share it for advertising.
Who is responsible
This is the personal website of Moein Almasi. I decide how the site works, which makes me the person responsible for it (the “controller”, in the language of data protection laws such as the GDPR). That includes what the host and Google’s human check do on my behalf, as described below. For any question or request about privacy, write to me with the contact form on the home page. If you would rather not use the form, you can reach me on LinkedIn.
When you only read the site
While you only read the site, I collect nothing about you. The pages contain no advertising, no advertising trackers and no analytics code, and no tracking pixels, fingerprinting, embedded videos or social media widgets. They set no cookies. Scripts, styles and images all come from this site, and text is shown in fonts that are already on your device, so opening a page contacts no company other than the host. The site has no comments, newsletter sign-up or user accounts.
One thing cannot be avoided: a server has to receive your request before it can send you a page. The next section describes that. Everything after it happens only if you choose it: the contact form, its human check and the two display switches.
Hosting and server logs
The site is hosted by Netlify, Inc., a company based in the United States. To send a page to your browser, Netlify’s servers have to receive some technical information: your IP address, the date and time of the request, the address of the page or file requested, and details your browser sends with every request, such as its type and version.
Netlify processes this information on my behalf to deliver the site, keep it secure and diagnose faults, and it keeps server logs. How long Netlify keeps those logs is its own decision, and I do not know the period. Because Netlify runs a global network, this processing can take place in the United States and in other countries. Where the GDPR or a similar law applies, I rely on my legitimate interest in running a secure and reliable website.
Netlify can also turn its server logs into visitor statistics for the owner of a site, for example how often each page was opened and which websites sent visitors, and I may look at such figures. Netlify says that it compiles them on its servers, without cookies and without any code in the pages, and that visitors are counted anonymously. The pages themselves contain no analytics code. I do not try to identify visitors, and I do not combine this information with anything else.
Netlify describes its own handling of data in its privacy statement and on its page about the GDPR and CCPA.
The contact form
The home page has a form for sending me a message. It asks for your name, your email address and the message itself. I use them to read what you wrote and to reply, and for nothing else. Where the GDPR or a similar law applies, I rely on my legitimate interest in answering people who choose to write to me.
The form is provided by Netlify, the company that also hosts this site. When you send it, Netlify receives your message on my behalf, keeps it in my account and sends me a copy by email, so the message is also held by the email service I use. As with every request, Netlify’s servers receive your IP address and details of your browser when the form is sent. I do not know which of these Netlify stores with the message.
Netlify checks every message for spam with Akismet, a filtering service run by Automattic. I do not know exactly which details Netlify passes to that service; a filter of this kind normally sees the message and technical details such as the sender’s IP address. Netlify also asks Google to confirm that the human check was passed, as described in the next section.
The form also contains a field that people cannot see, which helps to catch automated senders. It collects nothing from you.
Messages stay in my Netlify account and in my mailbox until I delete them. I have not set a fixed period for that. You can ask me to delete yours at any time.
The human check (Google reCAPTCHA)
To keep automated senders out, the form asks you to pass a human check before it sends a message. The check is reCAPTCHA, a security service of Google. I use it for one purpose only: to tell people from bots. I do not use it for advertising or to learn anything about visitors.
Nothing from Google is loaded while you open or read this site. The check loads only when you press “Continue to the human check” in the form, and the form says what that involves before you press it. If you never press it, Google is not involved at all.
Once the check loads, your browser connects to Google. Google receives your IP address and collects information about your browser and device in order to judge whether you are a person. When you send your message, the result of the check travels with it, and Netlify asks Google to confirm it.
The check also stores data in your browser. When I last looked, in November 2026, it stored two things: a cookie named _GRECAPTCHA, kept for about six months under Google’s address recaptcha.net, and, once the box is ticked, an entry named _grecaptcha in this site’s local storage. Google describes the cookie as necessary for its risk analysis. What the check stores is decided by Google and can change.
Google provides the check to me as a service and processes this data on my behalf. Google states that it processes the data only as needed to provide and maintain the service and to keep its protection against abuse effective. Google is based in the United States and operates worldwide, so the data may be processed there and in other countries.
The check is loaded from recaptcha.net and not from google.com. Google names this address for sites that prefer not to use google.com, where cookies from its other services may be set. When I looked, the check contacted recaptcha.net and gstatic.com, both of them Google’s, and nothing else. This keeps the cookies of Google’s other services out of the check. It does not change what the check itself collects and stores.
Because the check stores data on your device and sends data to Google, it runs only after you have asked for it. The form explains this first, and nothing is loaded or stored until you press the button. I treat pressing it as your agreement. If you would rather not use Google’s check, you can reach me on LinkedIn instead. What the check has stored can be removed at any time, as described in the next section.
What is saved in your browser
The site has two optional switches: one for a light or dark theme, and one that pauses the animated background. If you use a switch to choose something different from your device’s own setting, the choice is saved in your browser’s local storage so that it is remembered on your next visit.
themeholdslightordark.motionholdsonoroff.
These two values stay on your device. They are never sent to a server, contain nothing that identifies you and are not used for anything else. Nothing is saved unless you use a switch.
If you use the human check in the contact form, Google’s check stores the cookie and the local storage entry described in the section above.
You can remove everything that is kept under this site’s address at any time by clearing this site’s data in your browser settings, or with the button below when it is shown. The cookie from the human check is kept under Google’s address recaptcha.net, so this site cannot remove it. Your browser settings can.
Links to other websites
The site links to other websites, including LinkedIn, Google Scholar, GitHub, Google Drive (where the papers and certificates are stored) and the sites of employers and universities. These are ordinary links: nothing is loaded from those services until you choose to follow one. Once you do, that site’s own privacy policy applies. This site asks your browser not to tell the other site which page you came from.
Your rights
Depending on where you live, the law may give you rights over information about you: for example, the right to know what is held, to get a copy, to have it corrected or deleted, or to object to how it is used. The GDPR in the European Union and the United Kingdom, and privacy laws in Canada, the United States, Brazil and elsewhere, provide rights of this kind.
If you have sent me a message, I hold what you sent: your name, your email address and the message. Apart from that, I hold nothing about visitors myself. The host’s server logs and the data from the human check are described above, and I do not use them to identify anyone. To ask for a copy, a correction or deletion, write to me in one of the ways named at the top of this notice, and I will answer. You may also have the right to complain to the data protection authority where you live.
I do not sell personal information, share it for advertising or use it to build profiles of people. The only automated checks are the two described above, which keep bots and spam out of the contact form. Because nothing is sold or shared for advertising, there is nothing of that kind to opt out of, and the site behaves the same whether or not your browser sends a “Do Not Track” or “Global Privacy Control” signal.
Children
This site is not aimed at children, and I do not knowingly collect information from them.
Changes to this notice
If the way the site works changes, this notice will be updated and the date at the top will change.
Accessibility
I want this site to work for everyone. It is designed to follow the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA: it is built to be used with a keyboard and with a screen reader, it respects your device’s settings for reduced motion, contrast and colour scheme, and the background animation can be paused. The human check in the contact form is Google’s own component, and how well it works with assistive technology is up to Google. If something does not work for you, please let me know with the contact form or on LinkedIn.