YOUR DATA, PLAINLY.

Pixtex (pixtex.dev) renders n8n workflows as images. It is operated by Muhammad Muneeb. Questions or requests about your data: support@pixtex.dev.

Workflow JSON is the most sensitive thing you give us, so the whole product is built around not keeping it:

• Exports and API renders — processed in memory to produce your image, then discarded. Workflow JSON never appears in a URL, query string, or server log.
• Share links — store the rendered image (plus the workflow JSON only if you opt in, after a scan strips pinned execution data). Everything is deleted automatically after 24 hours.
• Hosted images — store only the final PNG, not your workflow JSON. They persist until you delete them or revoke your key.
• n8n instance connections — your instance URL and API key travel in request bodies only, are used solely to list and fetch your workflows, and are never stored on our servers or written to logs. Your browser may remember the instance URL locally on your own device.

• It reads the n8n workflow open in your tab only when you click Export or Open in Pixtex, using your existing n8n session — the same request the n8n editor itself makes, from inside that page. It runs on n8n Cloud, and on a self-hosted n8n only after you switch it on for that site.
• Before anything leaves the page it removes pinned execution data, credential ids, and owner and sharing details.
• The workflow travels to api.pixtex.dev in the request body to be rendered — processed in memory and never stored or logged, exactly like an export from this site.
• Open in Pixtex passes the workflow to pixtex.dev inside your browser, once, within a minute, and never through a URL.
• An optional Pixtex key is kept in the extension on your device and sent only to api.pixtex.dev.
• The extension collects no analytics and does no tracking. Its source is public: github.com/VicegerentPrince/pixtex-extension.

• Your email address — in three cases, and only if you give it to us. (1) If you create an API key: used to verify the key, enforce per-email limits, and contact you about the service. (2) If you ask to be kept posted after an export: kept solely to email you once, the next time something ships (if you asked for early access before Pixtex Pro launched, that one email is the Pro announcement). (3) If you buy Pixtex Pro: we receive the address Polar billed, and keep it with your subscription's id and your key's public id so we can deliver your key, re-issue it if you lose it, and end it if the subscription ends. Whatever the case, it is never sold, never shared for marketing, and never added to a recurring newsletter.
• Payments — handled entirely by Polar (polar.sh), our merchant of record. We never see or store your card details.
• API keys as hashes — we store only a SHA-256 hash of your key. We cannot see or recover the key itself. The one exception: right after you buy Pro, your new key is held for at most 15 minutes so the checkout page can hand it to you, then deleted the moment it is collected.
• Usage counters — monthly render counts per key, to enforce quotas; and daily totals of renders by format and by which Pixtex surface asked (this site, the n8n node, the CLI, the extension). Numbers only — nothing about who you are or what you rendered.

We run a self-hosted, cookie-less Umami instance for aggregate page statistics (visits, referrers, which features get used). It sets no cookies, does no cross-site tracking, and involves no ad networks. We never sell or share data with data brokers.

We send transactional email — e.g. the API-key confirmation link, or your Pro key after a purchase — and, if you asked to be kept posted, exactly one announcement. Nothing else. They are delivered through Resend (resend.com), which processes your email address for that purpose only.

• Share links and their data self-delete after 24 hours.
• Revoking an API key (DELETE /v1/keys/me or npx pixtex) immediately deletes its hosted images.
• Keep-me-posted and early-access addresses are deleted after that one announcement, or sooner on request.
• To remove your email entirely, revoke your keys or write to support@pixtex.dev — we'll confirm deletion.

If this policy changes materially, we'll note it on this page with a new effective date. Continued use after a change means you accept the updated policy.