Finxture Privacy Policy

Effective date: 2026-07-21 Revision: website analytics Owner: dmgritsan ltd, a company registered and operating in Cyprus (EU) Contact: [email protected]

Finxture is a free Chrome extension for developers: a payment sandbox that sends signed, synthetic test webhooks to a localhost or 127.0.0.1 endpoint you configure, so you can build and debug webhook handling without an inbound tunnel like ngrok. This policy also covers finxture.dev, Finxture’s website.

This page describes what Finxture does with your data. It is deliberately short, because the honest answer is short.

The short version

Finxture never sees your payment data. Your endpoint configuration, your generated test signing secret, and your scenario run history (including request and response previews) are written to Chrome’s local extension storage on your own machine and never leave it.

The one exception is optional, consent-based product telemetry — described in full below — which is limited to four coarse counters and never includes your payloads, secrets, or endpoints:

• No webhook bodies, secrets, payloads, or response content are ever sent anywhere except the localhost/127.0.0.1 address you explicitly configured.
• Telemetry sends nothing until you consent to it on first run, and is limited to exactly four usage counters (for example, “extension installed” or “scenario run completed”). It never contains payloads, secrets, endpoint URLs, response content, or your name, email, or account. It does use a locally generated, pseudonymous install identifier, described in “Usage telemetry” below, along with how to turn telemetry off at any time.
• No accounts, no sign-in, no payment processing by Finxture itself.
• No third parties receive your payload or secret data. Consented telemetry counters go only to PostHog EU Cloud, our telemetry processor (see “Usage telemetry” and “Third parties”). Cookieless website analytics goes to the same EU project and is described separately in “Website” below.

Everything below is detail in support of that claim, not a hedge on it.

What Finxture does

Finxture runs entirely inside the browser side panel. You configure a webhook target on localhost or 127.0.0.1 (with an explicit port), choose a scenario (for example, “Payment succeeds”), and Finxture delivers a sequence of deterministic, Stripe-compatible test webhook events — signed with a locally generated, test-only signing secret — directly to that address from your own browser. It keeps a durable local timeline of each run so you can inspect, replay, resume, or export it.

Finxture does not process real payments, does not talk to Stripe or any other payment provider’s servers, and does not generate or handle real cardholder data. All events are synthetic.

What we do NOT collect

To be explicit, because this is the part that matters most — regardless of telemetry, described in the next section, none of the following is ever collected:

• Webhook payloads, signing secrets, endpoint URLs or paths, or response content. They are never transmitted to us or to anyone else, under any circumstance, including inside telemetry.
• Anything typed into your local application at the other end of your webhook target — Finxture has no visibility into it.
• We do not use Chrome sync for any Finxture data — nothing is uploaded to your Google account or synced across devices.
• We do not use cookies, fingerprinting, or any cross-site tracking technique in the extension. Finxture has no content scripts and does not read the content of any web page you visit.
• We do not store your IP address as part of telemetry (see below).

Usage telemetry

Finxture collects usage telemetry only after you consent to it, and never before. This is a deliberate product decision, and we’d rather state it plainly than bury it.

• Consent, not silent collection. The first time you set up Finxture, a screen presents a telemetry toggle — pre-checked, so leaving it as-is opts you in — alongside the exact list of what is collected and, just as prominently, what never is. Telemetry sends nothing until you get past that screen. You can turn it off at any time afterward from Finxture’s settings; turning it off stops sending immediately and deletes your local install identifier (see below). Turning it back on later generates a new one.

• What’s collected: exactly four events, and nothing else. Each is timestamped:

  • installed — recorded once, when you complete first-run setup with telemetry left on.
  • endpoint_configured — recorded when you save a webhook target.
  • first_successful_scenario_run — recorded once, the first time a scenario run against your configured endpoint succeeds.
  • scenario_run_completed — recorded each time a scenario run finishes, together with which scenario it was (for example payment-succeeds) and whether the run succeeded or failed.

  Depending on how you reached Finxture, an event may also carry the coarse extension version and attribution context (for example, which marketing link or scenario page you arrived from) — never anything more specific than that. Adding any event or property beyond this exact list is a decision we record and publish before it ships, the same way this one was.

• What’s never collected, even in telemetry, permanently: webhook bodies, signing secrets, payloads, endpoint URLs, hosts, ports, or paths, response bodies, or any other payload content. This is a permanent commitment, not a today-only description — even as telemetry evolves, it will never expand to include these.

• Who processes it, and where. Telemetry is sent from the extension’s background service worker directly to PostHog EU Cloud (hosted in Frankfurt, Germany), which acts as our data processor. PostHog does not receive your IP address: the project is configured to discard it on receipt. Raw events are retained for 12 months and then deleted at the PostHog project level.

• A pseudonymous install identifier, not an anonymous one. Telemetry is tagged with a random identifier generated on your device when you consent, so we can tell that the same install produced several events (for example, to compute whether a first run led to a later one) without knowing who you are. We describe this honestly as pseudonymous, not anonymous: under EU data protection guidance, an identifier capable of linking events back to one installation is personal data, even without a name attached, and we are not going to claim otherwise. The identifier is never combined with your IP address (PostHog discards it) and is deleted from your device the moment you turn telemetry off.

• Opt-out and deletion. Turn telemetry off at any time in Finxture’s settings — this stops sending immediately and deletes your local install identifier, so no further event can be linked to your prior ones. To request deletion of telemetry already recorded under a given install identifier (for example, if you noted it before turning telemetry off), contact [email protected].

Scope note: this policy covers the free, extension-only product. A future paid cloud mode — where webhook bodies necessarily transit Finxture-operated infrastructure, unlike the local-only extension described here — is a materially different data flow and will get its own reviewed policy revision published before that mode launches. Nothing here should be read as covering a product that doesn’t exist yet.

What is stored locally, and how to delete it

Finxture stores three things in Chrome’s local, per-extension storage (chrome.storage.local), which stays on your device and is never synced:

None of this is encrypted beyond whatever protection Chrome’s profile storage already provides, and none of it is accessible to other extensions or web pages. None of it is included in telemetry.

To delete it:

• Use Clear history in Finxture to remove stored runs (this keeps your workspace configuration and signing secret).
• Use the signing-secret controls in Finxture to regenerate or clear the stored secret.
• Remove the Finxture extension from Chrome (chrome://extensions) to delete all Finxture local storage immediately and completely — Chrome does this automatically as part of removing an extension.

Permissions Finxture requests, and why

Finxture asks for the minimum Chrome permissions needed to work, and requests network access to your own local server only at runtime, only for the one host you choose:

Finxture does not request host_permissions for arbitrary websites, does not request downloads, nativeMessaging, unlimitedStorage, or any Chrome permission beyond the two above. It has no content scripts. Separately from the loopback permission above, and only once you consent, Finxture sends the telemetry counters described above to PostHog EU Cloud; this is ordinary extension network activity, not tied to your local endpoint or its permission grant. Finxture also declares externally_connectable for https://finxture.dev/* only, so that site (and no other) can detect whether Finxture is installed and hand over scenario and campaign context (for example, which link you followed) for the attribution use described in “Usage telemetry” above; no other website can message the extension this way.

The connectivity check Finxture offers (a HEAD request to your configured URL) reads only the HTTP status code and timing to tell you whether your local server is reachable; it does not read or store the response body.

Exports

Finxture lets you export a run as JSON, entirely on your own device:

• Export full JSON includes the complete run, including the signing secret. It is intended for your own debugging and is not suitable for sharing publicly.
• Export redacted JSON removes credentials, signature and authorization headers, cookies, API keys, cardholder-like fields, customer contact data, response previews, and target paths, so it is safer to share (for example, in a bug report).

Both exports are triggered only by your explicit action and are saved as a local file download by your browser. Finxture does not upload either export anywhere, and exports are never included in telemetry.

Third parties

Finxture does not share your webhook payloads, signing secrets, endpoint data, or run history with any third party — that data is never collected in the first place, so there is nothing to share.

For the extension, one limited data flow exists outside your local machine: telemetry, described above, which — only once you consent — goes to PostHog EU Cloud, our telemetry processor, hosted in Frankfurt, Germany. We do not share telemetry with any vendor beyond PostHog. finxture.dev uses the same processor for the limited, cookieless analytics described in “Website” below.

The only other third party in the picture is Google, which operates the Chrome Web Store. Like any extension listing, Finxture’s Chrome Web Store page may show Google-provided aggregate install and rating statistics; that data is collected and controlled by Google under Google’s own privacy policy, not by Finxture.

Website

finxture.dev uses PostHog EU Cloud for limited, cookieless website analytics. The site records a page view and a click on a Chrome Web Store install link. Those events contain only the page’s origin and path, the referring page’s origin and path (with its query and fragment removed), and any standard utm_source, utm_medium, utm_campaign, utm_content, and utm_term parameters on the Finxture URL. Other query parameters and fragments are discarded and are not sent. The site has no forms today.

Website events use a random identifier held only in the current page’s memory. It is not written to a cookie, local storage, or session storage and is replaced on every page load, so it cannot persistently identify or follow a visitor. PostHog person profiles are disabled for these events. The same PostHog project and EU hosting described under “Usage telemetry” apply; captured IP addresses are discarded by the project, and raw events are deleted after 12 months. No consent banner is shown because this analytics setup stores nothing on the visitor’s device and uses no persistent visitor identifier.

Separately, when the published extension ID is configured, the site sends the extension a narrowly scoped installation probe. If the extension acknowledges it, the site hands over the scenario_id and the same five UTM parameters from the current URL. This context stays in the extension’s local storage and is sent with extension telemetry only if that extension user separately consents as described under “Usage telemetry”. The site does not record whether the probe succeeded.

A scenario-update subscription is planned but has not shipped. Before it launches, this policy will be revised — with a new dated revision, published first — to describe exactly what is collected, how consent is obtained, and how to unsubscribe, following the same “publish before it ships” commitment described in “Future changes” below.

Data protection (GDPR)

Everything sensitive the extension creates — your endpoint configuration, signing secret, and run history — stays in local browser storage on your device and is never processed by us at all. If you consent to telemetry, the local install identifier described in “Usage telemetry” above is pseudonymous personal data, not anonymous data: it can single out one installation across events, even though it carries no name, email, or account. We process it, and PostHog EU Cloud processes it on our behalf, only for the counter-level activation and retention analysis described above, only for 12 months, and only until you turn telemetry off. The website analytics described above is separate: it does not create a persistent visitor identifier, but PostHog necessarily receives the network request before the project discards its IP address. If the website’s data handling changes — for example, when the scenario-update subscription described in “Website” above launches — this section will be updated first, in the same dated policy revision that introduces the new data flow.

This policy is issued by dmgritsan ltd, a company registered and operating in Cyprus (EU). We don’t add a full choice-of-law or venue clause here — this policy is short because there generally isn’t much to construe.

Future changes

Finxture’s roadmap includes a future, separate paid cloud mode, described in “Usage telemetry” above. That mode does not exist today and is not enabled by anything currently shipping; it will receive its own reviewed policy revision before it launches, because it introduces a materially different data flow (webhook bodies transiting Finxture-operated infrastructure) that this policy does not cover.

If Finxture’s data handling changes in any other way — including telemetry gaining new events or properties beyond the four described in “Usage telemetry” above, or the scenario-update subscription described in “Website” above launching — we will:

1. Publish the change in a dated revision of this policy before it ships.
2. Describe plainly what is collected, why, and how it can be controlled.
3. Never retroactively apply a broader policy to justify data already collected under this one.

Changes to this policy

We will update the effective date below whenever this policy changes and will keep prior versions available on request. Continued use of Finxture after an update means you accept the revised policy; if you disagree with a change, stop using Finxture and remove it (see “How to delete it” above).

Contact

Questions about this policy or Finxture’s data handling: [email protected]

Effective date: 2026-07-21