PT-BR/EN
Privacy

Data handling built around product operations, support and incident response.

This page summarizes how MFE Debugger handles account, billing and technical diagnostic data. It is intended to serve as a public baseline and should be complemented by the DPA, contractual terms, subprocessors and customer-specific configurations.

Effective date: 2026-04-13Last reviewed by: Security, Privacy and OperationsPrivacy contact: support@mfe-debugger.local

Processing principles

  • We collect account, billing and technical usage data required to authenticate users, operate the service and investigate incidents.
  • Diagnostic data may include session metadata, runtime events, release information, application manifests and artifacts submitted by the SDK.
  • Customers remain responsible for the content they choose to send to the service and should avoid submitting unnecessary or prohibited data under their own internal policies.
  • We do not sell personal data and limit sharing to subprocessors and providers required for service delivery, communications and billing.

Rights and operations

  • Request access, correction, export or deletion of data linked to an account or tenant.
  • Review retention, billing and data operation settings through the administrative console.
  • Open privacy, security or vendor review requests through the support and security channels listed on the public trust pages.

Data categories

Account and identity data
  • name
  • business email
  • membership
  • authentication method
  • session and device information
Operational product data
  • organization
  • project
  • environment
  • billing
  • seat usage
  • API keys and audit trail
Technical diagnostic data
  • runtime events
  • session titles
  • SDK metadata
  • release information
  • materialized incidents

Operational commitments

  • Maintain an audit trail for administrative actions and tenant-sensitive events.
  • Apply plan-based retention and support tenant-level export and deletion operations.
  • Respond to formal privacy requests within the operational workflow agreed with each customer.
  • Update subprocessors and public trust materials when the operating architecture changes in a material way.

Initial subprocessors

Neonmanaged PostgreSQL database, operational storage and pooled production connections
Sentryerror monitoring, traces, technical alerts and runtime failure investigation
Stripebilling, checkout, customer portal and subscription webhooks
Customer or operator SMTP providertransactional email such as verification, recovery and alerts
Application hosting and PostgreSQLproduct execution, operational persistence and queues

Contact and requests

For privacy reviews, deletion, export, retention, legal review or due diligence, contact support@mfe-debugger.local. See also Security and Terms.