Sub-processors

Purpose: Reviewer model inference (Claude Sonnet 4.6 + Haiku 4.5)

Data accessed: Submitted draft text, after PII auto-redaction. Reviewer calls run with Zero Data Retention enabled — drafts are not retained or used for training.

Purpose: Embedding generation for the rule corpus

Data accessed: No customer-submitted content. Embeddings are computed only over our own SEC rule corpus, not over your drafts.

Purpose: Authentication and session management

Data accessed: Email address, name, hashed credentials, IP and user-agent for session security.

Purpose: Subscription billing and customer portal

Data accessed: Email address, billing name, payment method (held by Stripe — we never see card numbers), subscription status.

Purpose: Transactional email (sending) and inbound email forwarding

Data accessed: Recipient email address, message body of transactional emails (e.g. quota-warning notices, trial-ending notices, team invitations).

Purpose: Application hosting and edge network

Data accessed: All HTTP request metadata (IP, path, user-agent, timestamps). Encrypted database traffic transits Vercel’s network but Vercel does not have access to plaintext database contents.

Purpose: Managed Postgres database (with pgvector for corpus retrieval)

Data accessed: All persisted application data: account records, firm records, submitted drafts, review results, audit-event chain.

Purpose: Error monitoring and performance tracing

Data accessed: Stack traces, request metadata, user id (Clerk id, never email body or draft text). PII is filtered out of error payloads before transmission.

Purpose: Product analytics (page-views, feature usage)

Data accessed: Anonymous distinct id, event names, page paths. We do not send draft text, review results, or other content to PostHog.

Purpose: Web analytics (Google Analytics 4) and ad conversion measurement (Google Ads, including Enhanced Conversions for Web). Loaded only after the visitor grants analytics or marketing consent under Google Consent Mode v2.

Data accessed: Anonymous client identifier, page paths, event names, and aggregate device/region metadata. For Enhanced Conversions: hashed (SHA-256) email submitted via the public waitlist form, only when marketing consent has been granted. No plaintext PII, draft text, or review results are shared.