Authenticated application access
Protected application areas require an authenticated session. Server-side boundaries guard dashboard and administrative routes before protected content is returned.
Security & Data Protection
PlanAI uses authenticated access, server-enforced authorization, tenant-aware data boundaries, and deployment-specific controls to protect customer work.
Available safeguards vary by product, contract, configuration, and connected service. Security requirements are confirmed for each customer before production use.
Current control approach
The controls below describe implemented product patterns. They are not certifications and do not replace a customer-specific security assessment.
Role-based authorization
Administrative and enterprise functions use server-enforced role and permission checks. Hiding a navigation item is not treated as an authorization control.
Tenant-aware data access
Organization and company membership are used to scope protected operations. Product security tests include changed-identifier and cross-tenant denial cases.
Server-side credential handling
Integration secrets and provider tokens are handled by server-side routes. Supported deployments use environment-specific secrets and scoped provider credentials.
Audit and operational records
Enterprise workflows include audit records for selected authorization and administrative events. Exact event coverage and retention are confirmed for each deployment.
Fail-closed security checks
Security-sensitive routes are designed to reject missing or invalid sessions, tenant context, roles, tokens, signatures, or connector configuration.
Protection through the request path
Product applications separate the public website from authenticated workspaces. Protected requests are evaluated on the server using session, membership, role, and tenant context before application data or privileged operations are made available.
Transport protection
Production web traffic is served over HTTPS. Protocol and edge configuration are verified in the target deployment rather than represented as a universal fixed version.
Trusted identity context
Protected services derive identity and tenant context from verified server-side sessions and memberships instead of trusting caller-supplied identity headers.
Scoped external access
External integrations are enabled individually. Provider permissions, credential ownership, test evidence, and support boundaries are reviewed for the contracted scope.
HTTPS application request
Encrypted transport to the deployed application edge
Session and authorization checks
Identity, membership, role, and route policy evaluated server-side
Tenant-scoped operation
Application and data access constrained to the authorized context
Current compliance position
PlanAI does not currently make a public claim that its products are SOC 2 certified, ISO 27001 certified, HIPAA compliant, PCI DSS Level 1 certified, or FedRAMP authorized. Use of certified infrastructure or service providers does not, by itself, certify PlanAI.
Regulatory and contractual requirements depend on the product, data, customer use case, deployment, and enabled integrations. Any required control, data-processing term, or assurance must be reviewed and agreed in writing before regulated or specially protected data is introduced.
Do not submit protected health information, payment-card data, government-controlled data, or other regulated information unless a signed agreement and approved deployment explicitly cover that data.
Deployment-specific review
Security scope is documented for the selected product and customer environment instead of inferred from a generic badge.
Identity and provisioning
Enterprise identity options can include SAML or OIDC sign-in and SCIM provisioning. The supported lifecycle is confirmed and tested with the customer's identity provider before launch.
Data lifecycle
Data categories, storage, retention, deletion, backup, recovery, and customer exit requirements are defined for the contracted deployment and validated before production onboarding.
Integration acceptance
A connector is part of the supported scope only after its permissions, tenant boundaries, failure behavior, monitoring, and target-environment acceptance have been documented.
Customer security review
A practical review connects product controls to the exact use case, data, identities, and integrations under consideration.
- 1
Define the use case
Identify the product, users, data categories, integrations, hosting expectations, and applicable customer policies.
- 2
Review the configuration
Confirm identity, role mappings, tenant boundaries, provider scopes, retention expectations, and support ownership.
- 3
Validate before production
Test the agreed authentication, authorization, integration, recovery, and negative-security cases in a non-production environment.
- 4
Record the approved scope
Document supported capabilities, customer responsibilities, limitations, evidence, incident contacts, and contractual requirements.
Discuss security requirements
Share the intended product, data categories, identity provider, integrations, and procurement requirements to begin a scoped review.