Pinus Maximus Extension Privacy Policy
Last updated: June 22, 2026
Packaged extension version: Pinus Maximus v1.0.2
Scope: Pinus Maximus browser extension
Notice issuer: Keresztes Zsolt, Cluj-Napoca / Kolozsvár, Romania
Contact: Contact page or contact [at] pinusmaximus [dot] com
1. Summary
The Pinus Maximus extension is designed so that extension data generally stays in the user’s browser.
The extension does not require a Pinus Maximus account. The Pinus Maximus extension does not send analytics, technical telemetry, performance statistics, tracking data or profiling data to the developer. It does not include built-in analytics, ad tracking or user profiling, and it does not sell personal data.
Most extension data is stored locally in the browser extension database and settings. This may include saved links, folders, screens, custom names, search providers, icons, background images, appearance settings, hotkeys, import/export data and local diagnostic logs.
Network requests may happen when the user opens a saved link, uses a search provider, opens a support or tutorial link, or enables and uses an optional third-party favicon service.
Third-party services are not part of the Pinus Maximus extension. They may have their own privacy rules and their own technical operation.
2. Notice issuer and scope
This extension privacy notice is issued by:
Keresztes Zsolt
Cluj-Napoca / Kolozsvár, Romania
contact [at] pinusmaximus [dot] com
This notice applies to the installed Pinus Maximus browser extension.
Pinus Maximus is designed as a local-first browser extension. Data saved by the extension — such as user-created pins, settings, icons, background images, provider settings and local logs — is stored in the user’s browser and is not sent to the developer.
The developer does not access these locally stored data and does not use them for analytics, telemetry, performance measurement, tracking or profiling.
This notice does not apply to the pinusmaximus.com website, which has a separate website Privacy Policy. It also does not apply to external websites, browser extension stores, search providers, AI services, favicon services, image platforms, donation platforms or other third-party services that the user opens, configures or uses.
3. No account and no Pinus Maximus sync
The Pinus Maximus extension works without a user account and without built-in Pinus Maximus sync.
The pinboard database, settings, saved links, background images and custom icons are stored locally in the user’s browser. The extension does not send them to the developer.
If the browser or operating system uses its own sync, backup or profile-management features, those features operate under the rules of the browser or platform and are not part of the Pinus Maximus extension.
4. Local data stored by the extension
The extension may store the following data locally in the browser profile, mainly in the extension’s IndexedDB database and extension settings:
| Data category | Examples | Purpose |
|---|---|---|
| Pinboard data | Screens, groups, folders, saved links, item names, link URLs, order and layout | Provide the pinboard and new tab features |
| Search provider data | Provider names, descriptions, base URLs, categories, icons and enabled/default state | Enable search with selected providers |
| Appearance data | Theme choices, colours, layout, background image settings, custom icons and uploaded images | Personalise the extension |
| Background image records | Image file, title, origin, link, photographer and attribution choice | Show selected backgrounds and credit sources |
| Favicon service settings | User-added favicon service names, template URLs, file type choices and enabled state | Fetch favicons only when configured and allowed |
| Permission state | Browser-reported host permission state and extension settings related to favicon access | Show and manage optional site access |
| Local logs | App lifecycle logs, data maintenance/import/export logs and outgoing favicon service call logs | Diagnostics, transparency and troubleshooting |
| Import/export files | Backups or selected export files created or imported by the user | Move or restore the user’s own extension data |
The exact data depends on what the user adds, configures, imports, exports or enables.
5. Local storage, logs and deletion
Local extension data usually remains in the browser profile until the user edits or deletes it, resets the extension, imports replacement data, removes the extension, clears the browser profile, or uses browser tools that delete extension storage.
The Pinus Maximus extension may keep local logs for transparency and troubleshooting. These logs are stored in the user’s browser, are not sent to the developer, and are not used for analytics, telemetry, tracking or profiling.
The default retention period for local logs is 7 days. Logging can be disabled, logs can be cleared, and retention settings can be changed. “Never auto-delete” style retention applies only if explicitly selected and is not the default behavior.
Backups and exports are files created or saved from the extension. After export, their storage, protection and deletion take place outside the extension. Secure storage of exported files is the user’s responsibility.
6. Browser permissions
The extension may request the following permissions:
| Permission | Why it is used |
|---|---|
Optional host permissions for http://*/* and https://*/* | To let the browser request access to a specific service origin when the user enables or uses a favicon service that needs it. Access is optional and can be reviewed or removed. |
The extension is configured as not allowed in incognito/private browsing mode.
The extension replaces the browser's new tab page with a local extension page. This lets Pinus Maximus show the user's saved pins, screens and search controls when a new tab opens. The new tab override does not give Pinus Maximus access to the browser history, and Pinus Maximus does not use it to collect or send a list of pages the user has visited.
The extension does not declare tabs or tabGroups permissions. User-started link and Open all flows open pages; where the browser supports it, Open all tabs may be placed into a new tab group without declaring a separate tabGroups permission.
7. Firefox data collection consent
In Firefox builds that support Firefox's built-in data collection and data transmission consent system, Pinus Maximus declares data_collection_permissions.required: ["none"]. This means the extension has no required data collection or transmission category.
The Firefox manifest may also declare data_collection_permissions.optional: ["searchTerms", "browsingActivity"] for optional, user-enabled features:
| Optional Firefox category | When it may apply in Pinus Maximus |
|---|---|
searchTerms | Only when the user uses a selected search provider and the search text is included in the provider URL or request. |
browsingActivity | Only when the user explicitly enables and uses a third-party favicon provider and the saved website hostname or domain is sent to that provider for favicon lookup. |
These optional categories are not used for developer analytics, telemetry, tracking or profiling. If the user does not grant or later revokes the relevant optional consent, the affected optional feature may remain disabled while the local pinboard features continue to work.
8. Optional favicon services
Automatic favicon fetching and third-party favicon services are optional convenience features.
Third-party favicon services are not part of the Pinus Maximus extension. The user may add or enable them. Providers may have their own privacy notice, logging practices and technical operation.
Third-party favicon services are disabled by default. By default, no data is sent to third-party favicon providers.
If the user explicitly enables and uses a favicon provider, the hostname or domain needed for favicon lookup may be transmitted to the selected provider. In Firefox, this may correspond to the optional browsingActivity consent category. The provider’s privacy notice should be reviewed before using the service.
Only the hostname needed for favicon lookup is inserted into the provider request, with subdomains preserved. The full saved URL, path, query string, fragment, credentials, pin title, screen name, settings and uploaded icon metadata are not transmitted.
Local, private, .local, .localhost, single-label intranet and private IP hostnames are blocked before host permission checks or fetching. The selected favicon provider may still receive normal technical request data such as IP address, user agent and request metadata.
The extension validates returned favicon files and accepts only supported image formats. SVG favicon responses are blocked for security reasons. Accepted favicon data may be stored locally as part of the extension data.
Outgoing favicon service call logs, if retained, are stored locally. They are user-facing diagnostic data and are not sent to the developer.
When a third-party favicon provider is added, enabled, or when the provider origin / template URL changes, the extension may ask for a separate confirmation.
If the user does not want a third-party favicon provider to receive a hostname or domain, third-party favicon services can be left disabled and local or manual icons can be used instead.
9. Opening links and using search providers
When the user opens a saved link, the destination website receives the normal request from the browser.
When the user uses a configured or selected search provider, AI provider or chat provider, the Pinus Maximus extension helps construct or open the provider URL. The search text may be included in the URL or request sent to the provider to perform the selected search. In Firefox, this may correspond to the optional searchTerms consent category.
The Pinus Maximus extension does not collect the search text for the developer. The extension only helps construct or open the search URL for the selected provider.
The resulting search URL may appear in browser history. Browser history behavior belongs to the browser and is outside the control of the Pinus Maximus extension.
Search providers are optional and are not part of the Pinus Maximus extension. Third-party search providers may have their own privacy notice, logging practices and technical operation. The provider’s privacy notice should be reviewed before using the service.
When enabling, setting as default or using a custom, imported or non-recommended search provider, the extension may ask for a separate confirmation. If the provider origin or search URL changes significantly, a new confirmation may be required.
10. Support, donations, tutorials and external resources
The extension may link to the project website, tutorials, support pages, Buy Me a Coffee, social profiles, image platforms, favicon providers, search providers or other external resources.
Opening those links is optional. The external service’s own terms, privacy notice, cookies, logs, account rules, fees and technical limits apply.
The project website, contact email, donation platforms and other external services are separate environments from the extension’s local storage. Separate rules and separate privacy notices may apply to them.
11. Browser stores
If the Pinus Maximus extension is installed from Chrome Web Store, Mozilla Add-ons or another extension platform, that platform may process store-related data under its own rules, such as account, download, installation, update, review, rating, store analytics, crash report or policy compliance data.
Browser stores may provide aggregate statistics such as installs, users, downloads, uninstall counts, browser/platform/country-level aggregate information or similar store-level metrics. These statistics are provided by the browser store or platform. They are not analytics built into the Pinus Maximus extension, and the Pinus Maximus extension does not control the store’s own data practices.
The Pinus Maximus extension does not send the local pinboard database to browser stores. Browser stores may still process store-related data under their own rules, such as installation, update, review, rating or aggregate usage statistics.
12. Local extension data and external contexts
The extension mainly stores data locally in the browser so that the features configured by the user can work. These local extension data remain in the user’s browser and are not sent to the developer.
Separate data processing may occur when the user contacts the developer, visits the project website, uses a browser store, opens a donation platform, or uses a third-party service such as a search provider, AI service, favicon service or image platform.
Those external services or platforms are governed by their own privacy terms and technical operation.
13. Data sharing
The Pinus Maximus extension does not sell personal data.
The local extension database remains in the user’s browser. The Pinus Maximus extension does not send this database to the developer.
A third party may receive data when the user uses an external service that receives data from the browser or from a URL opened by the extension. Examples include an opened website, search provider, AI service, favicon service, image platform, donation platform, browser store or communication provider.
When using a favicon service, the selected provider may receive the hostname or domain needed for favicon lookup. When using a search provider, the selected provider may receive the search text in the URL or request needed to perform the search.
These third-party services are not part of the Pinus Maximus extension and may operate under their own privacy rules.
14. International transfers
The Pinus Maximus extension is local-first. The local extension database remains in the user’s browser and is not sent to the developer.
When external services are used, the relevant provider may use servers outside the user’s country or outside the EU/EEA. Such external services may include browser stores, search providers, AI services, favicon services, image platforms, donation platforms, the project website or an email service used for contact.
Those providers’ own privacy terms, transfer mechanisms and legal terms apply.
15. Local control and privacy questions
Most extension data is located only in the user’s browser. It can usually be accessed, changed, exported, deleted or reset in the extension, the browser profile or the browser extension settings.
Because local extension data is not sent to the developer, the developer cannot access it and cannot delete it remotely.
Questions about extension privacy or contact data actually held by the developer can be sent through the Contact page or contact [at] pinusmaximus [dot] com.
Data created on external platforms or in third-party services is subject to that platform’s or provider’s own privacy processes.
16. Security
The extension uses browser extension isolation, local browser storage, content security policy settings and optional permission prompts to reduce risk. Returned favicon files are validated before local storage.
No software can be guaranteed to be completely secure, error-free or always available. It is recommended to keep backups of important extension data.
17. Changes and version availability
This extension Privacy Policy may be updated from time to time.
For an installed extension version, the Privacy Policy packaged with or linked from that version applies until a newer extension version or a newer in-extension document is installed or presented.
Browser extension stores may review or distribute updates with delay. Until the user receives or installs an updated extension version, the document available in the installed version may remain the applicable in-extension copy.