Effective 14 November 2026
This privacy policy governs this site. This site functions as a personal portfolio and blog operated from Florida, United States. This site is committed to protecting visitor data privacy by adhering to a strict data-minimization approach and respecting international data protection principles, including the European Union’s General Data Protection Regulation (GDPR).
§1 Data Controller and Contact Information
Because this site is a personal blog and portfolio, the data controller is the individual site owner operating out of Florida, USA. For any privacy inquiries, questions about data processing, or requests to exercise data rights, visitors may contact the site owner directly using the primary email address listed on the contact page of this site.
§2 Information Collected Automatically (Server Logs & Backend Analytics)
This site is self-hosted on a server managed via Virtualmin. This site does not utilize third-party client-side trackers, advertising tracking cookies, or external analytics platforms such as Google Analytics. Instead, this site uses a standard installation of AWStats to analyze server logs.
When a visitor browses this site, the visitor’s web browser automatically transmits certain technical information to the server log files. This technical data includes:
- The visitor’s Internet Protocol (IP) address.
- The date and time of the visit.
- The specific pages, files, and URLs requested.
- The HTTP response status code (such as a successful page load or an error).
- The size of the data transferred.
- Referrer URLs (the website or search term that directed the visitor to this site).
- User-Agent strings (the visitor’s web browser type, operating system, and version).
This data is processed locally on the Virtualmin server. It is used strictly to ensure server security, maintain website stability, diagnose system errors, and view general aggregate visitor statistics. This site does not merge log data with any personally identifiable information.
§3 Data Collected via User Interaction
At this time, this site acts strictly as a read-only platform.
- No Comments: Public comments are completely disabled across this site. Consequently, this site does not collect names, email addresses, website URLs, or IP data linked to user commentary.
- No Accounts: There is no public registration system or user login portal available, meaning no account credentials or profile data are collected.
§4 Mature Content and Access Controls
This site may host mature content intended strictly for adult audiences. To restrict access to such materials, this site may implement age-verification mechanisms or content gatekeeping tools.
- Minimal Verification: Any gatekeeping mechanism used on this site is designed to verify eligibility without collecting or storing personally identifiable information, government identification, or permanent user profiles.
- Functional Storage: If an access gate utilizes a browser cookie or local storage token to remember that a visitor has passed an age check during a browsing session, that token is strictly functional and is not used for tracking or profiling.
§5 Third-Party Embedded Content and External Integrations
To enrich the content on this site, external media may be embedded or linked.
- YouTube Video Embeds: This site may embed videos hosted on YouTube. When a visitor views a page containing an embedded YouTube video, Google or YouTube may set cookies and receive information about the visitor’s interaction with that video, subject to Google’s privacy rules.
- Social Media Connections: This site may include links or integrations to external decentralized networks, such as Bluesky. Interacting with these external links will direct the visitor to platforms operated under separate privacy frameworks.
This privacy policy does not apply to third-party services. Visitors are encouraged to review the privacy policies of external platforms such as Google and Bluesky to understand how those entities handle user data.
§6 Legal Basis for Data Processing (GDPR)
For visitors residing within the European Economic Area (EEA), the legal basis for collecting and processing the technical server data described in §2 is Legitimate Interest under GDPR Article 6(1)(f). This interest includes securing the self-hosted infrastructure, preventing malicious network attacks, and understanding generalized traffic patterns to keep this site functioning properly. If functional storage is used for content gatekeeping as described in §4, the legal basis is the technical necessity to provide the requested restricted content.
§7 Data Retention
Raw server access logs managed by Virtualmin are automatically rotated and purged on a regular system schedule. Aggregated, non-identifiable statistics generated by AWStats are stored locally on the server to track historical growth and traffic changes over time.
§8 International Privacy Rights
Regardless of geographic location, this site aims to provide universal privacy protections. Depending on a visitor’s jurisdiction (such as the EU under the GDPR or various US state privacy laws), visitors may hold the following rights:
- The Right to Access: The right to request confirmation as to whether personal data is being processed and obtain a copy of the data.
- The Right to Rectification: The right to request the correction of inaccurate or incomplete data.
- The Right to Erasure (“Right to be Forgotten”): The right to request the deletion of personal data, subject to technical server constraints.
- The Right to Object or Restrict Processing: The right to object to the processing of data based on legitimate interests.
To exercise any of these rights, visitors should reach out via the contact email listed on this site. Because this site does not store names or account records, any request relating to server logs must include the visitor’s specific IP address and the precise timeframe of the visit so the site owner can locate the relevant technical logs.
§9 Amendments to This Policy
The site owner reserves the right to update this privacy policy at any time to reflect changes in site features, content restrictions, or hosting configurations. Any modifications will be posted directly to this page with an updated effective date.