This Privacy Policy explains how the ruiguimaraes.net blog handles technical information and personal data in the context of publishing articles, videos, downloads and technical content.
Last updated: 1 August 2026.
1. Controller#
The controller for data associated with this blog is Rui Guimarães.
Blog website:
https://blog.ruiguimaraes.net/
For privacy-related questions, use the Contact page on the institutional website:
https://www.ruiguimaraes.net/en/contact/
2. Personal data collected directly#
This blog does not have a contact form, user area, comments, newsletter, registration system or checkout.
For that reason, in the current state of the project, the blog does not directly collect personal data submitted by users through its own forms.
3. Technical access data#
As with any website, access to the blog may generate technical data processed by the hosting infrastructure and by the servers that deliver the pages, such as:
- IP address;
- request date and time;
- accessed URL;
- HTTP response code;
- basic browser, operating system and device information;
- referrer, when sent by the browser.
This data is used to deliver the site, maintain security, diagnose errors and prevent abuse.
4. Internal search#
The blog has search enabled. Search is provided as a static-site feature and is not configured, in this project, with external analytics or advertising services.
Search terms entered by the user may be processed in the browser to display local results from the site index. The blog does not use those terms for advertising profiles.
5. Analytics, advertising and tracking#
In the current blog configuration there is no active Google Analytics, Fathom, Umami, Firebase Analytics, advertising, marketing pixels or equivalent tooling.
If any of these tools are added in the future, this policy should be updated before they are used.
6. Cookies and local storage#
The blog does not use first-party cookies for advertising or analytics.
The Blowfish theme may store functional preferences in the browser through localStorage, including appearance, accessibility options and, when applicable, language preferences. These preferences are used only to improve the user’s local experience in the same browser.
Users can delete this data at any time through their browser settings.
7. Embedded content and external services#
Some pages may include external content, such as YouTube videos. The theme uses the youtube-nocookie.com domain for embeds when videos are loaded through the Blowfish YouTube shortcode.
When interacting with embedded content or opening external links, users are subject to the privacy policies of those services.
The blog may link to external services, including LinkedIn, Forgejo, Mastodon, YouTube and technical sources referenced in articles.
8. Purposes of processing#
Technical data processed in the context of the blog is used to:
- deliver pages and content;
- maintain service security and stability;
- diagnose technical errors;
- prevent abuse, excessive scraping, spam or malicious access;
- improve the organisation and operation of the site.
Data is not used for sale, behavioural advertising, unsolicited marketing campaigns or commercial profiling.
9. Retention#
Technical access data may be retained by the hosting infrastructure for as long as necessary for security, operation and diagnostics.
Because the blog does not have its own form or user area, there is no contact database collected directly by the blog.
10. Data subject rights#
Under applicable law, data subjects may request access, rectification, erasure, restriction, objection or portability, when applicable.
To exercise these rights, use the Contact page on the institutional website:
https://www.ruiguimaraes.net/en/contact/
Data subjects also have the right to lodge a complaint with the Portuguese Data Protection Authority.
11. External links#
This policy applies only to the ruiguimaraes.net blog. Websites, social platforms, video services, code repositories and other external pages have their own policies.
12. Changes to this policy#
This policy may be updated to reflect technical, legal or operational changes.
The date of the latest update remains visible at the top of the page.