Back to Privacy Policy

Sub-processors

Last updated: 9 May 2026 · We notify customers 30 days before adding any sub-processor that processes case data.

EZClaim engages a small number of sub-processors to provide hosting, email, and optional AI features. The table below lists every sub-processor that may handle workspace data, the purpose of the engagement, the categories of data accessed, the region(s) where processing occurs, and the contractual status.

Sub-processorPurposeData accessedRegionStatus
Posh VPS (Hostinger / 5.223.79.50)Application + database hosting (Postgres, Redis, MinIO when active)All case data at rest (encrypted column-level for NRIC, contacts, addresses)Asia-Pacific (Bangladesh)Self-hosted infrastructure provider; data-residency migration to MY-resident hosting (AWS ap-southeast-5 KL or local provider) tracked as Sprint 9
Cloud AI provider (US)Section 10 conclusion drafter, damage-from-photo description, cross-section coherence check, BM↔EN translationSection narratives + photo bytes (1600px web variant)United StatesOpt-in per workspace via Settings; no calls happen without explicit configuration
CloudflareDNS + CDN/edge cache + TLS terminationRequest metadata (IP, URL, user-agent); does not see decrypted application dataGlobal anycastCloudflare data-processing agreement covers SaaS sub-processing
Resend (planned, Phase 7+)Transactional email delivery (invitations, notifications)Recipient email + body (no case content)United States / European UnionNot yet integrated — currently log-stub only; will be disclosed before activation
Better-Auth (self-hosted library)Authentication framework — sessions, MFA, organisation/membershipNone — runs in-process against the application databaseN/A — library onlyOpen-source dependency; no data leaves the platform
Helsinki-NLP OPUS-MT (in-process)Bahasa Malaysia ↔ English translation for police-report narrativesPolice narrative text (held in-process)N/A — runs locally on the platform serverMIT-licensed model; no external API calls
Tesseract.js (in-process, WASM)OCR fallback for scanned PDFs and uploaded imagesPDF and image bytes (held in-process)N/A — runs locally on the platform serverApache-licensed; no external API calls
Per-firm SMTP relay (tenant-controlled)Email delivery via the firm's own provider (Gmail, Zoho, AWS SES, Resend SMTP, etc.)Tenant-controlled — EZClaim only forwards messages the firm has chosen to sendTenant-controlledN/A — credentials owned by the firm and encrypted at rest in IntegrationConfig

Notification of changes

Adding a new sub-processor that processes case data triggers a 30-day advance notice to every firm’s MANAGEMENT contact via in-app notification + email. Firms have the right to object — objections lift the notice period requirement to 60 days while alternatives are evaluated.

Questions

Direct enquiries about sub-processors, data residency, or DPA flow-down terms to dev@aifactory.fyi.

This page is informational. The legally binding sub-processor terms live in your firm’s Data Processing Agreement.