Deal Flow security and data handling inside Mautic

Records stay local; outbound and offline behavior is bounded

Core deal records are stored in the instance’s Mautic database, and attachments are stored under var/dealflow/uploads. License validation sends a key and hostname over HTTPS; update checks add the plugin version. Administrator-configured webhooks can send deal and contact payloads. Successful validation results are cached for 24 hours and have a validation-only fallback during API outages; initial activation still requires the API, local active-status and integrity gates still apply, and an outage does not delete data. These are the verified boundaries for Deal Flow 0.9.4.

Verification basis (2026-08-23): the served DealFlowBundle-latest.zip archive, the webhook documentation, and the installation documentation.

Where the verified data paths store records

What activation, validation, and update checks send

• Activation and validation: the license key and instance hostname.
• Update checks: the license key, hostname, and current plugin version.
• Transport and request handling: these requests use HTTPS. Normal request infrastructure can process standard IP metadata.

Administrator-configured webhooks are an explicit exception

An administrator can configure outbound webhooks that send deal and contact payloads to a chosen destination. That behavior is not vendor telemetry: it is an integration path the instance administrator enables and controls. The webhook documentation covers the available integration surface.

Inbound webhook requests use HMAC signing. That control applies to the inbound webhook path and should not be generalized into a claim about every possible external integration.

What happens when the license API cannot be reached

A successful validation result is cached for 24 hours. During a later validation request, an API failure uses the last-known validation state; when no prior validation state exists, the validation result can be temporarily API-unreachable-valid. This fallback applies to validation results only. It does not activate a new license, and it does not bypass the plugin’s local active-status or integrity gate.

Initial activation requires the API and fails when the API is unreachable. An unlimited duration of offline operation is not verified. A temporary API outage does not delete deals, contacts, attachments, or other stored plugin data.

Local safeguards visible in the shipped archive

• Deal UI and REST operations use Mautic permission checks.
• Browser-based attachment upload and delete actions use CSRF protection; attachment REST operations use API authentication.
• Stored attachment names are hashed on the server. Direct file uploads enforce a MIME-type allowlist and a size limit.
• The inbound webhook route is public by design and authenticated separately with HMAC signatures.

These are scoped implementation observations from the shipped 0.9.4 archive, not a claim that any software or deployment is risk-free.

Frequently asked questions

What does a normal Deal Flow license request send?

Activation and validation send the license key and hostname to the Deal Flow license API. Update checks also send the current plugin version. The request uses HTTPS, and ordinary request infrastructure can process standard IP metadata.

Does Deal Flow send telemetry from Mautic?

No vendor telemetry or analytics path was found in the shipped 0.9.4 archive. Administrator-configured outbound webhooks are a separate path and can send deal and contact payloads to destinations the administrator chooses.

What happens if the Deal Flow license API is offline?

Successful validation results are cached for 24 hours. During later validation, an API failure uses the last-known state or a temporary API-unreachable-valid result when none exists. This validation fallback does not activate a license or bypass local active-status and integrity gates. Initial activation requires the API, unlimited offline operation is not verified, and a temporary outage does not delete stored deal data.

Where does Deal Flow store customer data?

Core deal records are stored in the Mautic database. Attachments are stored under var/dealflow/uploads with hashed server-side filenames. License records are held by the Deal Flow license service in Firestore.