Provider use is trigger-based. Core infrastructure handles the service, optional providers receive data only when the applicable feature is used, and client analytics require an affirmative choice. The details below distinguish those flows.
1. Scope and our role
ClaimVela is operated by Abdel Rahman Trawi, who provides the service under the ClaimVela brand (“ClaimVela,” “we,” “us,” or “our”). ClaimVela provides intake, collaboration, workflow, and AI-assisted review tools to personal injury law firms. For prospective-client and matter information submitted by or for a customer firm, the firm decides why and how that information is used. ClaimVela processes it to provide the service under the firm's instructions.
The customer firm is responsible for its own privacy notices, legal basis, professional duties, conflict procedures, retention rules, and responses to people whose information it controls. ClaimVela separately determines how it uses account, billing, security, and service-administration information described here.
2. Information we process
- Account and firm information: names, business contact details, authentication identifiers, organization membership, permissions, and account settings.
- Intake and case information: contact information; incident descriptions; injury, treatment, medical-record, insurance, employment, wage-loss, damage, court, identity, signature, and representation information; communications; notes; and uploaded evidence or documents.
- Usage and security information: device and browser information, IP-derived region, timestamps, authentication and audit events, feature use, error details, and records needed to protect and operate the service.
- Billing information: Paddle customer, subscription, product, price, plan, payment-status identifiers, trial and renewal dates, and transaction or invoice information retrieved for billing history. Paddle acts as merchant of record and processes checkout, tax, billing address, and complete payment-card details. ClaimVela does not receive or store complete card numbers.
- Connected-service information: provider and calendar identifiers, granted OAuth scopes, encrypted refresh credentials, synchronization status, and internal event mappings when a user connects Google Calendar.
- Support information: messages, attachments, and troubleshooting details you provide when requesting help.
3. How we use information
We use information to:
- provide, secure, support, and improve ClaimVela;
- authenticate users and enforce firm and role boundaries;
- run intake, client-portal, document, workflow, and reporting features;
- generate AI-assisted summaries, issue spotting, and follow-up suggestions when requested;
- process subscriptions and maintain billing access;
- detect abuse, diagnose failures, and maintain audit records; and
- comply with law and enforce our agreements.
ClaimVela does not sell personal information or use intake content for targeted advertising.
4. AI-assisted features
When an authorized firm user or prospective client uses an AI-assisted workflow, ClaimVela sends OpenAI the content needed for that task. Depending on the feature, this can include intake or conversation text, structured client and matter facts, staff document instructions, existing summaries, or the complete bytes of a selected PDF, JPEG, or PNG evidence file. For evidence review, the selected file is transmitted directly as an input file or image; processing is not limited to text extracted inside ClaimVela.
ClaimVela does not represent that every OpenAI request uses a zero-retention setting. AI output can be incomplete or wrong and must be reviewed by an authorized professional. ClaimVela uses AI to organize known information and surface gaps—not to make representation decisions, provide legal advice, determine liability, or value a claim.
5. Service providers and disclosures
We disclose information only as needed to operate the service, follow customer instructions, protect rights and safety, complete a business transaction, or comply with law. The descriptions below identify the information each current or available provider can receive; they do not mean every provider receives every category of ClaimVela data.
- SupabaseUse classification: Core
- When used: Every account and workspace
- Why used: Authentication, session handling, database, and private object storage
- Information involved: Account and organization records, roles and settings, intake and case records, communications, audit and billing-status records, and files stored in ClaimVela.
- VercelUse classification: Core
- When used: Every service request for hosting; client telemetry only after “Allow analytics” on a selected route
- Why used: Application hosting, server APIs, content delivery, and opt-in Web Analytics and Speed Insights
- Information involved: Requests and content handled by the hosted application pass through Vercel infrastructure. With analytics consent, its client telemetry components collect route-level usage and real-user performance information only on selected measured routes.
- ResendUse classification: Core
- When used: When ClaimVela sends or receives email
- Why used: Authentication, operational, support, portal, billing, reviewer, lead-response, and firm-authored CRM email
- Information involved: Sender and recipient addresses, subject lines, complete email bodies, secure links, organization names, routed inbound replies, and delivery, bounce, complaint, or suppression metadata. Client or case information can be present when a user includes it in an email or reply.
- OpenAIUse classification: Conditional
- When used: When an AI-assisted workflow is requested
- Why used: User-requested intake, conversation, summary, and evidence-analysis assistance
- Information involved: The text, structured information, instructions, existing summaries, and selected complete PDF, JPEG, or PNG evidence file needed for the requested feature.
- PaddleUse classification: Conditional
- When used: When a buyer views localized pricing or uses billing
- Why used: Merchant of record for checkout, tax, subscriptions, transactions, invoices, and the buyer portal
- Information involved: Buyer email, internal organization and checkout metadata, selected product and price, subscription and transaction details, billing address, tax identifiers, and payment information entered with Paddle. ClaimVela retains provider identifiers and billing state, not complete card numbers.
- Google measurementUse classification: Conditional
- When used: Only after “Allow analytics” on a selected measured route
- Why used: Google Tag Manager, Google Analytics, and Google Ads conversion measurement
- Information involved: Page paths and titles, referrers, device and browser information, IP-derived location, selected interactions, campaign and click identifiers, and conversion-stage data. Verified trial and paid-subscription conversions can include an internal organization identifier as the transaction identifier used to prevent duplicate conversion reporting.
- Google CalendarUse classification: Conditional
- When used: When an individual user connects calendar synchronization
- Why used: Private consultation-event synchronization
- Information involved: The granted OAuth scope and encrypted refresh credential, consultation time and duration, internal intake, consultation, organization, and event identifiers, and a link to the signed-in ClaimVela record. Generated events do not include the client’s name, contact details, or matter facts.
- TwilioUse classification: Conditional
- When used: Only if production SMS is configured and the applicable feature is enabled
- Why used: Optional outbound and inbound SMS delivery; Twilio is not currently configured for ClaimVela production
- Information involved: If enabled, sender and recipient phone numbers, complete message or portal-link text, provider message identifiers and delivery status, inbound replies, and opt-out commands.
- Apple iCloud DriveUse classification: Recovery
- When used: When an encrypted recovery archive is created and copied off-device
- Why used: Configured destination for an additional encrypted production recovery copy
- Information involved: The encrypted archive can contain database, authentication, storage metadata, and stored-file bytes. Checksum sidecars and separate recovery-validation reports can contain plaintext operational metadata such as archive filename and hash, production commit, validation time and results, artifact hashes, and aggregate user, bucket, and object counts—not decrypted customer records or file contents.
For a concise control and procurement overview, see the Security provider map.
7. Retention and deletion
Customer firms control the primary lifecycle of their intake and case data, subject to their agreement, legal obligations, and available account controls. We retain account, billing, audit, backup, and security information only as reasonably needed for the service, legitimate business records, dispute prevention, and legal compliance. ClaimVela does not currently publish fixed production-data or backup-retention periods. The encrypted-recovery process does not automatically delete older recovery points, so a deleted record can remain inside an encrypted archive until that recovery point is manually retired.
8. Security
We use technical and organizational safeguards intended to protect information, including encrypted network transport, tenant-aware access controls, row-level database policies, private file storage, audit history, and restricted server credentials. No online service can guarantee absolute security. See our Security page for more detail.
9. International processing
ClaimVela and its service providers may process information in countries other than the one where it was collected. Customer firms are responsible for determining whether their use requires additional contractual safeguards or notices for international transfers.
10. Your choices and privacy requests
If you submitted information to a law firm through ClaimVela, contact that firm directly because it controls your intake record. Account users may use the support channel shown in their ClaimVela account, order confirmation, or written agreement to request account access, correction, or deletion. We may need to verify identity and preserve information where law or a customer's professional duty requires it.
11. Health information and children
ClaimVela is not represented as a HIPAA-compliant service and does not enter into a business associate agreement unless the parties separately sign one. Do not use ClaimVela for protected health information that requires a business associate agreement unless one is in effect.
ClaimVela accounts are intended for legal professionals and authorized staff, not children. A law firm may collect information about a minor only when it has authority and a lawful professional purpose to do so.
12. Changes and contact
We may update this policy as our service or legal obligations change. Material updates will be posted here and identified by a revised date. For privacy or account questions, contact ClaimVela at admin@claimvela.com or through the support channel in your account. Billing and payment inquiries may also be handled through Paddle's buyer support.