Overview
NextPilot is a multi-tenant SaaS platform. Each customer workspace (organization) is logically isolated. Team permissions, developer keys, and channel connections are scoped to the active organization.
Data storage & isolation
CRM data — contacts, leads, conversations, messages, automations, flows, sequences, broadcasts, reports, and settings — is stored in a managed cloud database with access policies tied to organization membership.
Marketing sign-ups and contact forms are stored separately from workspace CRM data. Live data answer features, when enabled, use connections configured by workspace administrators with privacy controls.
Authentication & access control
User authentication uses secure password storage and session tokens. Dashboard routes require a valid session.
Role-based access lets workspace owners define permissions for agents and custom roles. Sensitive actions (billing, channel connect, developer keys) are limited to authorized roles.
- Organization switcher enforces context — every request is scoped to the active workspace.
- Elevated database access is used only on the server for background jobs and channel events, never exposed to browsers.
Messaging credentials
WhatsApp and other channel access tokens are stored server-side separately from public channel metadata. Tokens are not returned to the browser in full.
Inbound channel events are verified with signed requests before they are accepted.
You can disconnect channels from Settings, which revokes stored tokens for that workspace.
Encryption & network security
All traffic to nextpilot.chat and the CRM dashboard is served over HTTPS (TLS). Internal services communicate over secured infrastructure on our cloud hosting provider.
AI processing
When AI auto-reply is enabled, message content needed to generate a response is sent to the model provider you select. Disable AI per conversation or workspace-wide when human-only handling is required.
Live data answers can be restricted to verified senders and category-gated content to reduce unauthorized data exposure.
Developer access
Developer keys are scoped and revocable from Settings. You should rotate keys if compromised.
Outbound integrations you configure receive only the payloads defined by your automations and connections.
Operations & incident response
We monitor application health and messaging channel connectivity. Credentials for WhatsApp and related services can be rotated from the dashboard where supported.
Report security concerns to hello@nextpilot.chat. We investigate credible reports promptly and will notify affected customers of confirmed breaches as required by law.
Your responsibilities
Security is shared. We recommend:
- Use strong passwords and limit admin roles to trusted team members.
- Rotate developer keys and channel tokens when staff leave or integrations change.
- Review AI and automation content before scaling to production audiences.
- Comply with WhatsApp Business policies to avoid account restrictions that affect your customers.