This overview describes controls implemented in ClaimVela today. It is not a certification or a contractual service-level commitment. Where a feature is optional or a standard commitment is not offered, we say so.
Security principles
Tenant isolation
Authenticated organization membership and database row-level policies restrict records to the correct firm.
Private-by-default files
Evidence and matter documents use private storage paths and authorized, time-bound delivery.
Least-privilege access
Privileged server credentials remain server-side, while user requests operate through scoped authorization checks.
Human-controlled outcomes
AI can organize facts and surface gaps, but attorneys control conflicts, case qualification, outreach, and representation.
Procurement facts at a glance
These concise answers are intended to make an initial vendor review easier. They describe the current product rather than a roadmap. Use the PI intake software pricing and evaluation guide to place this evidence beside implementation, total-cost, and exit questions for every shortlisted vendor.
Identity and MFA
Email confirmation is required, passwords must contain at least 12 characters, refresh-token rotation is enabled, and authenticator-app TOTP MFA is available. ClaimVela does not currently enforce MFA across an entire firm.
Access and tenant isolation
Firm membership, four application roles, server-side authorization checks, and database row-level policies constrain access by organization. Privileged service credentials are used only in narrowly scoped server workflows.
Private files and portals
Customer files use private buckets and tenant-scoped paths. Authorized downloads use 60-second signed links. Client-portal links expire, can be revoked, and create short-lived sessions.
Audit history
Database-triggered, administrator-visible records cover selected team-access, public-intake, branding, export, and deletion events. This is not a record of every data read.
Data portability and deletion
Firm administrators can export structured firm records and audit data as JSON. File binaries are downloaded separately. Administrators can permanently delete eligible, non-converted intakes; other retention depends on the firm’s duties and applicable law.
Continuity
ClaimVela has tooling to create encrypted snapshots and validate isolated restores for database, authentication, and storage data. The archive is not represented as independent disaster recovery without key escrow and restore testing outside the source Mac and backup folder. No standard contractual RPO, RTO, backup-frequency promise, or uptime SLA is currently offered.
Application and data controls
- Authentication: confirmed email sign-up, protected sessions, rotating refresh tokens, 12-character minimum passwords, and optional authenticator-app TOTP MFA.
- Authorization: organization membership and owner, administrator, attorney, and staff role checks are enforced in the application and database, including for sensitive administrative actions.
- Database security: row-level security policies constrain authenticated access, while elevated service access is reserved for narrowly scoped server workflows.
- File security: private object storage, controlled tenant paths, and short-lived signed downloads reduce unintended exposure.
- Portal security: access links expire and can be revoked, short-lived sessions constrain continued access, and uploads are subject to origin, session, rate, signature, format, and size checks. Review the PI client portal workflow and safeguards.
- Transport and browser protection: HTTPS, restrictive security headers, content-security policy, clickjacking protection, and content-type protections are applied to production responses.
- Auditability: selected administrative and workflow security events are database-triggered and visible to firm administrators. This is not a record of every read.
- Secret handling: sensitive provider secrets, application encryption keys, and privileged database credentials remain server-side and outside public browser bundles. Publishable client credentials are intentionally browser-scoped.
AI and sensitive information
AI features are invoked for specific user-requested tasks and receive the relevant content needed to produce a response. ClaimVela preserves a human decision boundary: AI output is assistance, not verified fact, legal advice, medical advice, or an automated representation decision. Firms must review generated content before acting on it.
Service-provider map
“Core” providers support the ordinary operation of ClaimVela. “Conditional” providers receive data only on the relevant measured route or when a firm enables the applicable integration or feature. “Recovery” identifies the configured destination for an encrypted additional recovery copy.
- Supabase
- CoreWhen used: Every account and workspace
- Purpose: Authentication, session handling, database, and private object storage
- Vercel
- CoreWhen used: Every service request for hosting; client telemetry only after “Allow analytics” on a selected route
- Purpose: Application hosting, server APIs, content delivery, and opt-in Web Analytics and Speed Insights
- Resend
- CoreWhen used: When ClaimVela sends or receives email
- Purpose: Authentication, operational, support, portal, billing, reviewer, lead-response, and firm-authored CRM email
- OpenAI
- ConditionalWhen used: When an AI-assisted workflow is requested
- Purpose: User-requested intake, conversation, summary, and evidence-analysis assistance
- Paddle
- ConditionalWhen used: When a buyer views localized pricing or uses billing
- Purpose: Merchant of record for checkout, tax, subscriptions, transactions, invoices, and the buyer portal
- Google measurement
- ConditionalWhen used: Only after “Allow analytics” on a selected measured route
- Purpose: Google Tag Manager, Google Analytics, and Google Ads conversion measurement
- Google Calendar
- ConditionalWhen used: When an individual user connects calendar synchronization
- Purpose: Private consultation-event synchronization
- Twilio
- ConditionalWhen used: Only if production SMS is configured and the applicable feature is enabled
- Purpose: Optional outbound and inbound SMS delivery; Twilio is not currently configured for ClaimVela production
- Apple iCloud Drive
- RecoveryWhen used: When an encrypted recovery archive is created and copied off-device
- Purpose: Configured destination for an additional encrypted production recovery copy
Additional detail about the categories of data involved appears in the Privacy Policy.
Data lifecycle and continuity
- Export: firm administrators can export structured firm records and security-audit data in JSON. Private file binaries are retrieved separately through authorized downloads.
- Deletion: administrators can permanently delete eligible, non-converted intakes. Other information may be retained for the firm’s professional duties, operational records, disputes, security, or applicable law.
- Recovery: tooling can create encrypted recovery snapshots and validate isolated restores for database, authentication, and stored-file data. The additional archive is not represented as independent disaster recovery without key escrow and restore testing outside the source Mac and backup folder. These controls do not create a contractual RPO, RTO, backup frequency, or uptime guarantee.
Shared responsibility
Customer firms are responsible for:
- using unique credentials and enabling available multi-factor authentication;
- granting the minimum role needed and promptly removing former users;
- securing devices, browsers, networks, and exported data;
- verifying portal recipients before sending sensitive links;
- maintaining lawful authority and professional safeguards for uploaded content; and
- reviewing AI output and maintaining independent deadline, conflict, and legal controls.
Current assurance scope
ClaimVela does not currently claim SOC 2 certification or HIPAA compliance and does not offer standard business associate agreement coverage. A standard uptime SLA, contractual RPO/RTO, fixed universal retention period, or data-residency commitment is not included unless stated in a signed agreement.
Do not use the service for protected health information that requires a business associate agreement unless the parties separately execute one. Firms should complete their own review before onboarding regulated or contractually restricted data.
Security review or concern
For a vendor review, email admin@claimvela.com with the controls, contractual terms, data-location requirements, or documents your firm needs. ClaimVela will distinguish current capabilities from roadmap items and will not represent an unavailable certification or agreement as complete.
If you believe an account or ClaimVela data may be at risk, stop sharing the affected credentials or links and use the same address. Include a concise description, affected area, timing, and safe reproduction details without unnecessary client data.