Privacy Policy
Last updated: April 13, 2026
This Privacy Policy describes how MakerWorld Model Webhook (the "extension") collects, uses, stores, and shares information.
Summary
- The extension runs on MakerWorld model pages.
- It lets you send model information from a MakerWorld page to a webhook URL that you configure.
- The extension does not operate its own backend or remote database.
- The extension does not sell your data and does not use analytics or advertising trackers.
- Data is stored locally in the browser and/or in Chrome Storage Sync.
- Data is only sent out of the browser when needed for extension functionality, including when you click Send to Webhook.
Information the extension collects
The extension may collect the following categories of information:
1. Settings you enter
The extension stores the settings you provide, including:
- webhook URL / API endpoint
- bearer token
- extra request headers
- request timeout value
These settings are stored using Chrome's extension storage APIs, including Chrome Storage Sync where available.
2. Information read from MakerWorld pages
When you use the extension on a MakerWorld model page, the extension reads information from the page in order to prepare the webhook payload. This may include:
- page URL
- canonical URL
- page title
- referrer
- page language
- model ID and slug
- model title and description
- author name and author profile URL
- tags
- image URLs
- Bambu Studio URL
- selected print profile information
- visible model statistics such as downloads, likes, comments, collections, and makes/prints
- Open Graph metadata
- JSON-LD / structured data embedded in the page
3. Information transmitted during requests
When you click Send to Webhook, the extension sends a POST request to the webhook endpoint you configured. That request may include:
- the configured destination URL
- request headers you configured
- bearer token if provided
- the extracted MakerWorld page and model data described above
- the current tab URL and tab title
- the extension version
4. Automatically generated technical data
Like any browser-based request, some technical information may be generated or shared as part of normal network activity, such as:
- IP address
- standard HTTP request metadata
- response status and response text returned by your webhook
The extension itself does not operate a server to collect these logs, but the services you choose to use (for example, your webhook provider) may process them under their own policies.
How the extension uses information
The extension uses information only to provide its functionality, including to:
- save and restore your extension settings
- display the extension UI
- detect supported MakerWorld model pages
- extract model information from the current page
- send that information to the webhook endpoint you configured
- show request success or error feedback in the extension UI
The extension does not use collected information for:
- advertising
- profiling
- analytics or telemetry
- sale of personal information
- unrelated marketing communications
When information is shared
Information may be shared only in the following circumstances:
1. With your configured webhook destination
When you click Send to Webhook, the extension sends the request payload to the webhook URL you configured. That recipient processes the data under its own privacy practices.
2. With Chrome / Google sync services
If Chrome sync is enabled in your browser profile, extension settings stored with Chrome Storage Sync may be synchronized by Google across your signed-in Chrome instances, subject to Google's terms and privacy practices.
3. When required by law
Information may be disclosed if required to comply with applicable law, regulation, legal process, or enforceable governmental request.
Data storage and retention
- The extension does not maintain a developer-operated remote database.
- Settings remain stored in browser extension storage until you change them, clear them, or uninstall the extension.
- Data extracted from a MakerWorld page is generally processed in the browser and sent only when you trigger the webhook action.
- The extension does not intentionally retain submitted payloads on a developer-controlled server.
- Any data received by your configured webhook destination is retained according to that service's own policies.
Your choices and controls
You can:
- view and change your settings in the extension popup or options page
- remove or replace the configured webhook URL, bearer token, and extra headers at any time
- uninstall the extension to remove its locally stored data from the browser
- manage Chrome sync behavior through your Chrome / Google account settings
Security
The extension is designed to minimize data handling by operating primarily within your browser and by not using a developer-operated backend. However:
- settings are stored in browser extension storage
- data is sent to the webhook endpoint you configure
- the security of data received by that endpoint depends on the endpoint you choose and its configuration
You should use only trusted webhook destinations. The extension requires HTTPS webhook endpoints, except for localhost or 127.0.0.1 during local development.
Children's privacy
The extension is not directed to children and is not intended for use by children.
Changes to this policy
This Privacy Policy may be updated from time to time. Updates will be reflected by changing the "Last updated" date above.