FIRECRUX — WordPress Plugin Privacy Notice

Who we are

Firecrux is a service of Greenlogic Ltd. ("Firecrux", "we"). This notice explains what the Firecrux WordPress plugin sends from your website to our service (panel.firecrux.com), why, and what you control. It applies to the website owner who installs the plugin. If you are a visitor of a website that uses the plugin, the website owner is responsible for informing you — the plugin gives them a ready-made paragraph for their privacy policy.

For the Firecrux panel itself (your account, billing, support) see our general Privacy Policy.

What the plugin sends to Firecrux

What	When	Why
Your published content — posts, pages and product listings (title, text, categories, publication and modification dates, SEO title and description if an SEO plugin sets them). Drafts and private content are never read.	Every night and when you click "Synchronize now". Only new and changed items are sent.	Content analysis, search-visibility reports, recommendations and the content Firecrux prepares for you.
Your website address and the e-mail you register with	When you create a Firecrux account from the plugin or connect it with a token.	To create and secure your account and to send verification and notification e-mails.
Cookie-consent statistics — only if you switch it on	Each time a visitor makes a choice on your cookie banner: one anonymous signal saying "accepted" or "declined".	To show what share of your traffic Google Analytics can measure at all.
Access log — only if you switch it on and Firecrux enables it for your site	The site writes a technical request log; Firecrux reads finished days once a day.	To analyse how search engines and AI crawlers visit your site (crawl budget, errors).

Everything else you see in the plugin — projects, reports, tools, messages — is data Firecrux delivers to the plugin, not data it collects.

Visitor data

The plugin is built so that Firecrux does not receive data that identifies your visitors:

The cookie-consent signal carries no cookie, no visitor identifier and no page address — only your site id and "accepted" / "declined". The visitor's IP address is not stored: Firecrux keeps only a short-lived hash of it in memory to limit abuse. Firecrux stores a daily count per site and nothing else.
In the access log, visitor IP addresses are shortened before writing (last octet removed for IPv4, last 64 bits for IPv6), query-string values are masked (search phrases and the query part of the referring address included) and logged-in users, the WordPress admin and the plugin's own requests are excluded. Search-engine bots are logged with their full address so their identity can be verified. The log is kept on your server for 14 days (at most 200 MB), then deleted.

Both switches are off when the plugin is installed. You turn them on in Firecrux → Settings → Data sharing and can turn them off at any time; the plugin stops immediately.

How long we keep it

Content: for as long as the plugin is connected. Disconnecting the plugin or deleting your account removes it from Firecrux.
Cookie-consent counts: aggregated daily totals, no personal data.
Access logs: processed into statistics; raw lines are not kept beyond processing.

Where it is processed

On Firecrux servers in the European Union, operated by Greenlogic Ltd. and its hosting providers.

Your rights and contact

Questions about this notice: use the contact form or reach our Data Protection Officer. You can disconnect the plugin (Settings → Disconnect) or delete your account (Settings → Remove my account) yourself at any time.