Print-friendly bundle for PDF export and procurement sharing.
This page aggregates an executive summary of privacy, terms, security, subprocessors and changelog to simplify browser-based PDF export.
Privacy summary
- 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.
- 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.
Terms summary
MFE Debugger provides instrumentation, ingestion, incident correlation, billing and an administrative console for operating micro-frontend architectures.
Customers must not use the service for unlawful activity, unauthorized data submission, abusive load testing, attempts to bypass commercial limits or improper credential use.
Customers are responsible for configuring environments, credentials, domains, billing and SDK payloads in line with their legal obligations, contracts and internal policies.
Service operations depend on infrastructure, subprocessors and external connectivity. Support follows the operating queue and may include dedicated workflows for enterprise customers.
Accounts may be suspended for non-payment, abuse, security risk, material breach of these terms or any use that threatens the service for other customers.
For enterprise agreements, order forms, DPAs, technical exhibits and specific addenda may complement or supersede these initial public terms.
Security summary
- Authentication with per-device sessions, session rotation and audit trail.
- SSO, MFA, managed domains and SCIM controls according to plan maturity.
- API keys scoped by organization or project, with revocation and usage history.
- Persistent ingestion queue and a dedicated worker for session and incident materialization.
- Operational playbooks for backup, restore, deployment and incident response.
- Security reports are triaged through the primary operational channel and routed to technical investigation.
- When material impact is confirmed, the case enters the incident workflow with audit trail, containment, remediation and communication.
- Enterprise customers may require specific response flows and notification timelines by contract.
Subprocessors summary
Document changelog
Public status, support entry points and export/deletion operations with grace period were connected to the operating flow.
Neon and Sentry were added as operational subprocessors for managed database and observability.
Public privacy, terms and security pages were added together with a global trust footer.
The initial public subprocessors list, disclosure page and security.txt route are now available.
The base DPA, vendor questionnaire, privacy ops and response templates were structured for due diligence.