Privacy
This page records documented facts for the 0.3.1 pre-release landing site and the plugin. Maintainer and controller contact fields stay marked as pending. Nothing below invents a name, e-mail or address.
Last updated: 13 November 2026 (America/Sao_Paulo).
Language: Português.
1. This landing site (current state)
These pages are a static, pre-release marketing site. As prepared in revision r5:
- The site does not use Google Analytics or any other third-party tracking or analytics service.
- The pages load no third-party scripts, fonts, cookies or trackers. The pages load no JavaScript. Styles are served from this site only.
- Every page includes
<meta name="robots" content="noindex">. The site is served by Cloudflare Workers (static assets) at a public*.workers.devaddress. Its_headersfile setsX-Robots-Tag: noindex, nofollow, and itsrobots.txtallows crawlers to fetch the pages so they can honour the noindex directives. These measures are not a password. The*.workers.devaddress is public: anyone who has the link can open the site. noindex only asks search engines not to index the pages; it does not restrict access. - There is no waitlist, form or sign-up. No page contains a
<form>element, input field or submit button, and no page sends data to any destination. The site itself does not ask visitors for personal data; technical access metadata processed by the hosting provider is described in section 2. - This site does not offer a download of the plugin package.
The site is hosted on Cloudflare Workers. Technical access metadata that Cloudflare may process when someone opens these pages is described in the next section.
2. Hosting on Cloudflare Workers
This site is hosted on Cloudflare Workers: its HTML and CSS files are uploaded as static assets of a Worker, and Cloudflare serves them from its network. When someone opens a page, Cloudflare may process technical access metadata about that request, including the visitor’s IP address, the requested URL and other traffic data, under its terms and its Data Processing Addendum (DPA). This site itself has no waitlist, form or sign-up, and it loads no analytics or third-party trackers.
What was actually read on 12 November 2026 (America/Sao_Paulo). The research used WebFetch and curl; the Grok CLI is not installed:
- Workers Static Assets (Cloudflare Developers) — page retrieved on that date. It states: “You can upload static assets (HTML, CSS, images and other files) as part of your Worker, and Cloudflare will handle caching and serving them to web browsers.” The Headers page of the same documentation says that a
_headersfile in the static assets directory “will not itself be served as a static asset, but will instead be parsed by Workers and its rules will be applied to static asset responses”. - workers.dev (Cloudflare Developers) — page retrieved on that date. It states: “When enabled, your
workers.devURL is available publicly.” - Cloudflare Customer DPA — page retrieved on that date. The published text identifies itself as Version 6.4, effective 3 April 2026. It applies where Cloudflare processes Personal Data as a Processor (or sub-processor) on behalf of the customer. Annex 1 describes, among the categories for “End Users”, personal data processed in “Customer Logs, such as IP addresses”, and defines Customer Logs as logs of end users’ interactions with the customer’s Internet properties that Cloudflare makes available to the customer. For the retention period, Annex 1 gives a criterion, not a number of days: “Until the earliest of (i) expiry/termination of the Main Agreement, or (ii) the date upon which processing is no longer necessary for the purposes of either party performing its obligations under the Main Agreement”.
- Cloudflare and LGPD compliance (Brazil LGPD FAQs) — page retrieved on the same date. Cloudflare states that it is headquartered in the United States and has global operations; that, for its application and network services, metadata about activity is processed on behalf of customers in data centers in the United States and Europe; and that this metadata “contains extremely limited personal data, most often in the form of IP addresses”, processed “for a limited period of time”.
- Workers Logs (Cloudflare Developers) — page retrieved on the same date. Where Workers Logs are used, the invocation log of a fetch request is described with the request method and the request URL. Whether Workers Logs are enabled for this Worker, and whether requests answered only from static assets produce such logs, has not been verified.
Cloudflare also states, in its own words on the LGPD FAQ page, that “Brazil personal data transferred to the US has comparable protection to that provided by the LGPD.” That is Cloudflare’s public statement. It is not a legal opinion issued here, and it is not a guarantee.
The adequacy of any international transfer of personal data under Brazil’s LGPD still requires verification. That verification has not been done in this phase. This page does not invent a retention period for visitor access logs, a location for any particular visitor or for the processing of any particular request, or any other legal guarantee beyond what the cited pages actually say. Maintainer and controller contact fields remain pending: [PENDENTE — nome do mantenedor], [PENDENTE — e-mail de contato], [PENDENTE — endereço / país do controlador].
3. The plugin, when a store owner installs it
The following summarises the documented 0.3.x privacy behaviour of Webhook Disable Monitor for WooCommerce (version 0.3.1 changes only the notification e-mail wording; storage and redaction rules were documented for 0.3.0 and were not described as changed). Full detail is in the project's privacy report and FAQ, not invented here.
- The plugin stores webhook ID, topic, counts, last response code, timestamps, episode and e-mail status, and the endpoint reduced to scheme, host and port, with the host possibly shown as
[host redacted]. - The URL path, query string, fragment, username and password are discarded before storage. The webhook name, order payloads and customer data are not stored.
- Everything the plugin stores stays in the store's own WordPress database. The plugin makes no external calls. The only outgoing message is the alert e-mail sent by the store itself through WordPress
wp_mail(). - Hosts are not detected by a “secret scanner”. A host is shown only if it is on an allow-list (registrable domain; that domain plus one of
www,api,hook,hooks,webhookorwebhooks; an allow-listed automation host such as Zapier or Make, extendable by a filter;localhost; or a private, loopback or reserved IP). Everything else, including public IPs, is shown as[host redacted]; the port is kept. - Limits already documented: a registrable domain, a safe label or an allow-listed host can stay visible, and a domain can itself be identifying. Private IPs and ports stay visible. WooCommerce's own delivery log and
wc_webhookstable, which this plugin does not control, keep the full URL and the webhook name.
4. No waitlist, form or sign-up
This site has no waitlist, no form and no sign-up. It does not ask visitors for names, e-mail addresses or any other details, and it does not link to an external form. The waitlist pages and their script were removed in revision r5 of the site; their old addresses redirect to the pre-release information page.
History, for transparency: on 12 November 2026 a form on Tally was published only for a technical test with test data and then closed; the test responses were deleted and the Tally trash was emptied. No public collection took place, and no Tally form is connected to this site.
Technical access metadata that the hosting provider may process when someone opens a page is described in section 2. The absence of a form does not mean that no personal data is processed.
5. Controller and contact (pending — not invented)
| Field | Status |
|---|---|
| Controller / maintainer name | [PENDENTE — nome do mantenedor] |
| Privacy contact e-mail | [PENDENTE — e-mail de contato] |
| Controller address / country | [PENDENTE — endereço / país do controlador] |
Existing footers still use the placeholder PENDING-MAINTAINER, kept as in the 0.3.1 pages so the appearance of those pages stays as close as possible. It has the same meaning as the explicit pending fields above. No name, e-mail, phone or address was invented.