Privacy Policy

1. bridgistic.app

• The site runs no analytics or advertising scripts. It stores one value in your browser, the colour theme you choose (bridgistic-theme in local storage).
• The offer status check (/api/offer-status) returns only whether the welcome offer is open and how many Lifetime licenses remain. It receives no personal data from you.
• When you start checkout, the page loads Paddle.js from cdn.paddle.com and passes the email you entered to Paddle, so that your license can be issued to it. Paddle.js is not loaded before you start checkout.
• The site and the offer status check are hosted on Cloudflare.

2. Payment (Paddle)

Paddle collects your payment details and the information its checkout asks for. According to the WPistic Privacy Policy, WPistic does not store full card numbers. It keeps only the billing metadata needed to reconcile payments, such as plan, amount and status.

3. WPistic license server (api.wpistic.com)

When Paddle reports a completed payment, the license server stores:

• the Paddle notification itself, which includes your email and transaction details;
• a WPistic organization with your email as the billing email;
• the order, the subscription or lifetime record, and your license.

Your license key is stored only as a hash with a short prefix and a masked form. The full key is sent to you once, by email.

When a site activates the key, the server records the site's domain, site and home URLs, an installation ID, the environment, and the WordPress, PHP and plugin versions. License events record the IP address and user agent of the request.

4. The Bridgistic plugin, on your own WordPress site

The plugin keeps its data in your WordPress database:

• API keys: key ID, label, scopes, limits and an encrypted secret.
• An audit log: time, key ID, action, status, IP address, a hash of the parameters and a summary. Entries are pruned after 90 days.
• Pending and decided approvals.
• Snapshots of content taken before changes, so they can be rolled back.
• Usage counters, memory notes, playbooks and schedules.
• If you activate a license, the activation token and the license status.

The only outside service the plugin contacts is the WPistic license server, and only when a license is activated, re-checked or deactivated. It then sends the key (on activation), the domain, the site and home URLs, an installation ID, the environment, and the WordPress, PHP and plugin versions.

Snapshots and backups

Snapshots are stored only in your own WordPress database. They are never sent to WPistic, to bridgistic.app or to the relay, and WPistic holds no backup of your WordPress site. The plugin does not expire snapshots on its own: they stay until you delete them or uninstall the plugin.

What uninstalling does today

Deleting the plugin in WordPress removes its eight tables (keys, audit log, snapshots, approvals, usage, memory, playbooks and schedules), deletes its option allowlist and signing settings, clears its scheduled tasks and removes its sandbox folder in your uploads directory. Deactivating the plugin only stops its scheduled tasks.

Two items stay in WordPress after an uninstall: the stored license activation, and the WPistic installation ID, which other WPistic plugins share. Uninstalling does not contact the license server, so the site keeps its activation there. Deactivate the license on the License screen first if you want to free the site for another one.

5. Dashboard (dashboard.bridgistic.app)

The dashboard runs in your browser. The site connections you add, including the key secret, are kept in your browser's session storage and cleared when you sign out or close the session. Requests are signed in your browser and sent directly to your WordPress site. The dashboard has no server that stores your keys.

6. Relay (mcp.bridgistic.app)

The relay is optional. It is for AI clients that connect over the web instead of running the Bridgistic MCP server locally. For each connected site it stores:

• the site URL, the Bridgistic key ID, the key secret (encrypted with AES-256-GCM) and the granted scopes;
• when the connection was created and last used;
• the OAuth grants for your AI client.

It forwards tool calls to your site as signed requests and does not store request or response bodies. Its logs use a fixed format that identifies a site only by a short hash. Rate-limit counters include the caller's IP address and expire within two minutes. Sign-in flow state expires after 10 minutes, and access tokens are valid for one hour. The relay runs on Cloudflare.

7. Service providers

These are the providers that handle Bridgistic data, limited to those we have verified in our code and configuration.

8. Retention

• Lifetime Deal license. The license record is kept for the life of the license and deleted if you cancel or are refunded.
• Account and billing data. According to the WPistic Privacy Policy, these are kept while your account is active and afterwards as legal, tax and accounting obligations require.
• Backups. Backups of the license server database, which include the records in section 3, are kept for about 60 days, for every plan. This is the only backup data WPistic holds for Bridgistic.
• On your site. The plugin prunes its audit log after 90 days. Snapshots stay until you delete them or uninstall the plugin.
• Relay. The relay keeps the short-lived items described in section 6.

9. Your rights

Section 7 of the WPistic Privacy Policy describes your rights over the data WPistic holds, such as access, correction and deletion, and how to exercise them. The plugin's data is in your own WordPress database and under your control.

Contact

Support and refunds, for Bridgistic and the whole WPistic ecosystem: [email protected].
General company enquiries: [email protected].