Pinus Maximus Website Privacy Policy
Last updated: June 18, 2026
Scope: pinusmaximus.com website
Notice issuer: Keresztes Zsolt, Cluj-Napoca / Kolozsvár, Romania
Contact: Contact page or contact [at] pinusmaximus [dot] com
1. Summary
The Pinus Maximus website provides information about the Pinus Maximus extension and related resources.
The website does not require an account or login. It does not use marketing tracking, ad profiling, marketing pixels, or advertising cookies.
The website does not use IndexedDB. It may use localStorage only to remember basic user choices and consent decisions, such as analytics consent, theme/light-dark mode, or language choice.
The website may use an external infrastructure provider, such as Cloudflare, for hosting, DNS, CDN, security, load balancing, and other infrastructure tasks.
Based on the website operator's decision and with user consent, the website may use a Cloudflare Web Analytics / Real User Monitoring (RUM) beacon script to measure basic traffic and performance metrics. This is not used for marketing tracking or ad profiling.
The installed Pinus Maximus extension is separate from the website and has its own Privacy Policy.
2. Scope
This notice applies to the pinusmaximus.com website, including legal pages, product pages, guides, support information, and extension document copies shown before installation.
It does not apply to the installed Pinus Maximus extension. It also does not apply to external websites, browser stores, donation platforms, search providers, AI services, favicon services, image platforms, or other third-party services opened from the website.
3. No account, no marketing tracking
The website can be visited without a Pinus Maximus account.
The website does not intentionally collect personal data through marketing pixels, ad trackers, ad profiling, or advertising cookies.
The website does not use IndexedDB.
The website may use localStorage to remember basic user choices and consent decisions locally. These entries are stored in the user's browser. The website may currently use the following localStorage keys:
| localStorage key | Example | Purpose |
|---|---|---|
pinusMaximus.privacyConsent | version, updatedAt, choices, savedAt | Remember privacy choices, such as essential preferences and whether optional analytics was allowed or declined |
pinusMaximus.theme | pineforest-dark | Remember the selected appearance theme or light/dark mode |
pinusMaximus.locale | hu | Remember the selected language version |
The localStorage entries are not used for marketing tracking, ad profiling, or creating a user profile. The user can usually delete or change them in the browser settings, developer tools, or through controls provided by the website.
4. Hosting, infrastructure, performance measurement and contact
The Pinus Maximus website may use an external infrastructure provider, such as Cloudflare, for hosting, DNS, CDN, security, load balancing, and other infrastructure tasks.
When the website is served and protected, such a provider may process technical server-side data, logs, security events, or aggregate statistics. This may be based on the legitimate interest in operating a secure, reliable, and abuse-resistant website.
Cloudflare may provide infrastructure-level security and performance functions, such as CDN, DNS, load balancing, bot and abuse protection, inspection of HTTP headers and other technical request characteristics, web asset discovery, robots.txt or AI crawler rule handling, and security challenges or restrictions when suspicious traffic is detected.
Cloudflare security cookies and technical scripts
Cloudflare security and functionality-supporting features do not necessarily appear during every visit. During normal traffic, Cloudflare may not place a security cookie in the browser and may not run a separate security challenge.
However, if Cloudflare detects suspicious, automated, or abusive traffic, it may use temporary security cookies or similar technical identifiers. Some Cloudflare features may also load technical JavaScript files, for example for bot protection, security checks, email address protection from bots, or serving web resources.
| Technology or feature | When may it appear? | Purpose |
|---|---|---|
Cloudflare security cookies, for example __cf_bm | In connection with bot protection, Bot Fight Mode, Bot Management, or challenge-related protection | Detect bot traffic, handle automated or suspicious traffic, and protect the website |
Cloudflare challenge cookie, for example cf_clearance | After completing Cloudflare Challenge, Managed Challenge, Under Attack Mode, or a similar security check | Remember that the visitor successfully completed a security check |
Cloudflare load balancing or traffic management cookies, for example __cflb or _cfuvid | Only if the relevant Cloudflare feature is active and needed during the visit | Support stable delivery, load balancing, rate limiting, or traffic management rules |
| Cloudflare bot protection or challenge-handling scripts | If Cloudflare runs a security check or bot protection challenge | Filter bots and suspicious traffic, verify human visitors |
| Cloudflare Email Address Obfuscation script | If email address protection is active on the page | Protect email addresses against bots |
| Technical helper scripts served through CDN | If the website uses such a technical resource | Operate interface or documentation features, non-marketing technical delivery |
| Cloudflare Web Analytics / RUM beacon | Only if enabled by the user | Optional, cookie-free, non-marketing traffic and performance measurement |
Cloudflare security cookies and technical scripts may be part of the website's essential security and functionality technologies. They help keep the website secure, stable, and reliable. They are not used for marketing tracking, ad profiling, or creating individual user profiles.
The optional Cloudflare Web Analytics / RUM is handled separately: it only works if the user enables it.
Cloudflare Web Analytics / RUM
This is an optional measurement that the website operator may use to understand traffic and performance in aggregate. It is not used for marketing tracking, ad profiling, or creating individual user profiles.
The following categories and metrics may be involved in Cloudflare Web Analytics / RUM:
| Category or metric | Meaning |
|---|---|
| URL or page path | Identifies the visited page or page section |
| Browser | Type of browser used by the visitor |
| Operating system | Type of operating system used on the visitor's device |
| Country | Country-level aggregate view of visits |
| Affected page element | Page part or element related to a performance metric |
| LCP | Largest Contentful Paint, a metric for main content loading performance |
| INP | Interaction to Next Paint, a metric for responsiveness to user interactions |
| CLS | Cumulative Layout Shift, a metric for visual stability |
These metrics help understand traffic, loading performance, Web Vitals-style experience metrics, and the reliable operation of the website.
According to Cloudflare, Cloudflare Web Analytics does not use cookies or localStorage to collect usage metrics and does not fingerprint individual visitors based on IP address, user agent, or other data.
During measurement, Cloudflare systems may still process technical and temporary personal data to the extent needed for request delivery, security, aggregation, and statistical processing.
More information about Cloudflare Web Analytics is available in the Cloudflare Web Analytics documentation (opens in a new tab). More information about Cloudflare data practices is available in the Cloudflare Privacy Policy (opens in a new tab).
Cloudflare, Inc.
101 Townsend St.
San Francisco, CA 94107
USA
The website operator generally has only limited or aggregate access to data created in Cloudflare infrastructure. For individual access, objection, or deletion requests, the current contact channels in Cloudflare's own privacy notice can be used: Cloudflare Privacy Policy (opens in a new tab).
If a user sends an email or uses a contact channel, the message content, email address, and necessary technical email data may be used to reply and handle the request.
The Pinus Maximus contact email may operate through an external email provider, for example Migadu. The email provider may process messages and technical metadata under its own terms and privacy notice.
Migadu-Mail GmbH
Rohnen 587
CH-9414 Schachen
Switzerland
For privacy questions about email and technical data processed in Migadu systems, the current contact channels in Migadu's own privacy notice can be used.
Contact messages are kept only as long as necessary, unless legal, security, accounting, dispute-handling, or another justified reason requires longer retention.
5. External links and platforms
The website may link to browser stores, donation platforms, social profiles, image platforms, guides, third-party services, or other external resources.
Opening these links is optional. The external services' own terms, privacy notices, cookies, logs, accounts, fees, and technical limits apply.
6. Browser stores and support platforms
Browser stores may process store-related data under their own rules, such as downloads, installs, updates, reviews, ratings, or aggregate statistics.
Donation or support platforms may process payment, account, and support-related data under their own rules.
These platform processes are not analytics built into the Pinus Maximus website.
7. International transfers
The website itself does not create a Pinus Maximus account or central user profile.
External infrastructure, email, analytics, and platform providers may use servers outside the user's country or outside the EU/EEA. The relevant provider's own privacy terms and transfer mechanisms apply.
8. Privacy questions
Questions about website privacy or contact data actually held by the developer can be sent through the Contact page or contact [at] pinusmaximus [dot] com.
For individual access, objection, or deletion requests related to data created in Cloudflare infrastructure or during Cloudflare Web Analytics / RUM operation, the current contact channels in Cloudflare's own privacy notice can be used: Cloudflare Privacy Policy (opens in a new tab).
Data created on external platforms or in third-party services is subject to that platform's or provider's own privacy processes.
9. Changes
This website Privacy Policy may be updated from time to time. The current version is available on the website.