1. Scope and controller
This policy applies to FaultPilot websites, SaaS workspaces, APIs, monitoring agents, the FaultPilot Interactive Recorder extension, public status pages, and support interactions. “FaultPilot,” “we,” and “our” refer to the operator of the FaultPilot service. Workspace customers control the application and telemetry data they submit; FaultPilot processes that data to provide the service.
2. Information we handle
- Account data: name, email address, organization, authentication records, workspace membership, preferences, and billing status.
- Monitoring data: URLs, IP addresses, domains, request configuration, availability results, response times, incidents, maintenance events, status-page content, and alert delivery records.
- Logs and test evidence: customer-submitted logs, browser-test steps, selectors, screenshots, videos, console output, execution results, and encrypted secret references.
- Technical data: IP address, browser/device information, security events, audit records, and diagnostic information needed to secure and operate FaultPilot.
- Support data: messages, attachments, and information you choose to provide when requesting assistance.
3. Interactive Recorder and Chrome extension
The extension has one purpose: converting interactions explicitly performed during a user-started recording into an editable Browser Test. It may handle the selected URL, browsing activity inside the authorized recording tab, element labels/selectors, clicks, scroll, hover, drag-and-drop, keyboard actions, form values, and limited page content needed to identify interacted elements.
FaultPilot requests runtime access only to the website origin selected by the user. Capture remains inactive until recording starts, and optional access is removed when recording stops.
Password, one-time-code, token, and similar values may be temporarily relayed in memory to the authenticated FaultPilot dashboard so they can immediately be replaced with encrypted backend secret references. Secret plaintext is not written to extension storage. Payment-card fields are excluded. Non-secret active steps use Chrome session storage and are removed when recording stops, a participating tab closes, the extension updates, or the browser session ends.
4. How we use information
- Provide monitoring, testing, alerting, incident, maintenance, logs, and status-page functionality.
- Authenticate users, enforce workspace permissions, prevent abuse, and investigate security events.
- Process subscriptions and administer service limits.
- Diagnose failures, respond to support requests, and improve service reliability.
- Meet legal obligations and enforce our terms.
We do not sell personal or recorder data, use it for targeted advertising, credit decisions, or unrelated profiling. Information received from Chrome APIs is used according to the Chrome Web Store User Data Policy, including Limited Use requirements.
5. Sharing and processors
We disclose information only to service providers required to operate FaultPilot—such as infrastructure, database, object storage, email, alert delivery, payment, and security providers—under appropriate contractual and security obligations. We may also disclose information when required by law, to protect users or the service, or as part of a business transaction subject to appropriate safeguards. Public status-page information is intentionally published by the workspace administrator.
6. Retention and deletion
Retention depends on the selected plan, workspace configuration, telemetry type, security requirements, and applicable law. Ephemeral extension data is removed as described above. Saved tests, secrets, logs, evidence, incidents, and account data remain until deleted, expired under configured retention, or the workspace is closed, subject to limited backups, fraud-prevention, financial, and legal records.
Workspace owners can delete supported resources in the dashboard. Account or privacy requests can be sent to support@faultpilot.com.
7. Security and international processing
FaultPilot uses access controls, encryption in transit, secret encryption, tenant authorization, audit and operational safeguards appropriate to the service. No system is completely secure, so customers must protect credentials, limit submitted sensitive data, and promptly report suspected compromise. Information may be processed where FaultPilot and its providers operate, with safeguards required by applicable law.
8. Your choices and rights
Depending on your location, you may have rights to access, correct, delete, restrict, object to, or export personal information and to complain to a regulator. Workspace administrators may need to handle requests involving customer-controlled data. Contact support@faultpilot.com; we may verify identity before fulfilling a request.
9. Changes and contact
We may update this policy as FaultPilot evolves. Material changes will be communicated through the service or another appropriate channel, and the date above will be updated.
Privacy and Chrome extension questions: support@faultpilot.com.