Security approach
RecoveryPilot uses layered controls appropriate to a customer-specific software and AI platform. Current application controls include authenticated access, owner and customer role separation, customer-workspace boundaries, server-side authorization for sensitive actions, audit records, restricted document storage, encrypted network transport, provider access controls, and human approval queues for consequential AI-assisted changes.
Customers must protect their own accounts and connected systems, assign least-privilege access, use MFA where available, promptly remove departed users, keep contact and escalation information current, and notify RecoveryPilot of suspected unauthorized access.
Data lifecycle
Collection and use
RecoveryPilot is configured to receive only the information needed for enabled services. Customers control which integrations, files, voice flows, and operational modules are activated.
Retention
Retention is set by data type, customer instructions, operational need, provider capability, security and audit needs, and legal or contractual requirements. A customer-specific schedule may be recorded during implementation. We avoid keeping sensitive information “just in case.”
Offboarding and deletion
Authorized customer administrators may request an export and offboarding plan. RecoveryPilot identifies the export scope and format, disables connections and access, removes active data according to the agreed schedule, and records completion. Limited information may remain temporarily in protected backups or be retained for security, legal hold, dispute, tax, or contractual purposes. Backup copies age out through their normal cycle.
Continuity and incident response
RecoveryPilot maintains operating procedures for triage, containment, evidence preservation, customer coordination, recovery, and follow-up. Service restoration prioritizes identity and access, customer configuration and data, customer-facing workflows, integrations, and reporting. Recovery procedures and provider restoration capabilities are tested and updated as the platform matures.
Customers should maintain a backup call route, current escalation contacts, and independent copies of information they require for their own legal or business-continuity obligations.
Subprocessors and service providers
The providers below are used only when the corresponding RecoveryPilot feature is enabled. Exact provider scope may vary by customer order and deployment. RecoveryPilot evaluates access and configuration before production use and seeks contractual data protections appropriate to the service.
| Provider | Purpose | Information involved | Feature status |
|---|---|---|---|
| Google Cloud / Firebase | Hosting, identity, database, storage, and server functions | Accounts, configuration, operations, audit records, and authorized uploads | Core platform |
| OpenAI | AI document, support, and operational assistance | Only content and context sent by an enabled AI workflow | Enabled platform AI |
| Anthropic | Optional AI processing or verification | Only content sent by a specifically enabled workflow | Optional; customer/deployment dependent |
| Retell AI | AI voice infrastructure | Caller metadata, audio, transcripts, and authorized tool inputs/results | Voice customers only |
| Stripe | RecoveryPilot subscription billing and payment processing | Business billing contacts and processor-held payment data | When billing is activated |
| DigitalOcean | Customer-specific integration infrastructure | Data processed by the deployed connector or service | When required by implementation |
| Google Workspace / configured email provider | Transactional, support, and business email | Names, email addresses, message content, and delivery metadata | When email is enabled |
Payment and card information
RecoveryPilot designs payment flows so card and bank credentials are entered through the configured payment processor’s secure interface rather than spoken to the AI agent or stored in ordinary application records. Customers are responsible for their processor account, permissions, refund and retry decisions, and authorized payment practices.
AI and voice controls
- Customer-approved operating rules, disclosures, hours, escalation paths, and payment parameters are configured before launch.
- AI suggestions can be reviewed and edited before being applied to portal data.
- High-impact operational changes use explicit approval controls where supported.
- AI output may be inaccurate and does not replace customer supervision or professional advice.
- Customers are responsible for call-recording, communications, collection, consumer, and employment-monitoring permissions and notices applicable to their use.
Provider changes
RecoveryPilot updates this page when a material provider is added, removed, or changes purpose. Customer notification and objection rights, if any, are governed by the applicable DPA and signed service agreement.
Report a security concern
Email support@recoverypilotai.com with “Security” in the subject. Do not include passwords, payment credentials, SSNs, private keys, or unnecessary consumer data. Include contact information, the affected customer workspace, a concise description, and the time observed.