What we do with your data, and what we don't

Scope sits between AI workflows and credentialed professional work. The data that flows through us includes case captions, claimant identifiers, deposition notices, and pricing data - the kind of data your firm's GC and your carrier's privacy office will both ask hard questions about. This page states what is in place today. Security questions are answered on request.

Where we are today

SOC 2 Type I

In preparation. Point-in-time controls audit.

Security controls are in place today (detailed below).

HIPAA

Claims vertical (preview).

Scope's serving and court-run work is not designed to carry health records. Records retrieval is a general category on Scope; talk to us before sending health records through it. Encryption and access-logging controls apply across the claims and legal verticals.

Privacy (GDPR / state laws)

Active. DPA available.

Data Processing Agreement available on request. Aligned with CCPA, CPRA, and equivalent state privacy laws. Scope's database and file storage are hosted in the United States.

HITRUST CSF is evaluated as buyer demand requires; it is not currently in progress. Payment processing runs on Stripe Connect (PCI DSS Level 1); additional financial-services certifications will be pursued as the product surface requires them.

Coverage in place

Scope carries cyber liability, technology errors and omissions, and general liability coverage.

Cyber liability
First- and third-party cyber.
Tech E&O
Technology errors and omissions, including media liability.
General liability
Standard commercial general liability for business operations.

Certificates of Insurance with full limits are available to any prospective buyer or professional on request via info@scope.bid.

What gets encrypted, where, by whom

Encryption in transit

All public traffic is TLS 1.2+ (TLS 1.3 preferred), terminated at the edge. Connections to subprocessors use TLS via their official SDKs.

Encryption at rest

AES-256 on the database (Supabase managed PostgreSQL, platform default). Sensitive columns, such as stored OAuth refresh tokens, are additionally encrypted at the application layer with AES-256-GCM.

File storage

Uploads and transcripts are stored in Supabase Storage (AES-256 at rest, platform default) and served through short-lived signed URLs. Files are not encrypted with separate per-tenant keys: the server filters each firm's files to that firm, and Row Level Security policies protect direct storage access.

Authentication

Supabase Auth with JWT-based session tokens. Bearer API tokens for MCP access (OAuth 2.0 access tokens and personal access tokens) are stored as SHA-256 hashes, never plaintext, are revocable, and are bound to a single tenant. Single sign-on via SAML 2.0 and OIDC is available. Multi-factor sign-in comes from your identity provider for users who sign in through SSO; Scope has no multi-factor sign-in of its own.

Row-level security

Each firm's data is filtered to that firm by the server: firm-side roster, spend, and matter data are scoped per organization. Row Level Security policies on the tables protect direct database access. (Shared catalog tables, such as service categories, are public-read by design.)

Audit logging

Matter, award, roster, billing, and admin actions, and LEDES and audit-log exports, are written to an audit log with actor, timestamp, IP address, user agent, resource, and before/after state. The server writes the log and the application never edits it. Per-matter audit records are exportable as CSV and PDF on request.

Data residency

Scope's database and file storage are hosted in the United States.

Files

Scope stores the files a professional delivers and the documents your firm sends with a work order, so the people on the matter can open them. AI tools connected to Scope can open those files, except on a medical records matter, where they receive information about the files and never the files.

How Scope handles medical records retrieval

No professional on Scope has a published price for medical records retrieval today. Records retrieval is a general category on Scope; talk to us before sending health records through it. When Scope runs medical records retrieval, these rules are built into the product:

  • Held for review: Every file a professional delivers on a medical records matter is held until a person at Scope checks it against the request. A file that does not belong to the request is not released.
  • Notices: Emails, texts, push notifications and calendar entries about a medical records matter carry the matter number and a link to sign in, not the records or the details of the request.
  • Where the files go: Your firm downloads the records from the matter page. They go into your firm's case-management system only if a firm admin turns that on. AI tools connected to Scope receive information about the files, never the files.
  • Retention: Scope deletes the record files a professional delivers on a medical records matter at least 90 days after the work is accepted, by your firm or automatically at the end of the review period; at least 90 days after the work moves to another professional or is cancelled, for the files the first professional sent; at least 90 days after a withdrawal of the authorization is recorded on a finished request; and at least 30 days after Scope restricts a file that does not belong to the request (for example, another person's records), whether or not the work was accepted. None of these applies once a dispute has been filed on the matter, including a payment chargeback, a refund or a hold on the payment, even one since resolved. If the work is re-awarded or changes hands more than once, Scope may keep files longer rather than delete them early. Files that meet none of these stay in Scope with no end date. That includes, unless a rule above applies, files on work that stays open without being accepted or moved to another professional. Documents your firm uploads are not deleted by this schedule. For each deleted file Scope keeps its name, checksum and dates.

Who else touches your data

This is the complete list of third parties that can touch customer data, not a selection of the largest. We commit to 30 days' notice before adding any new subprocessor with access to customer data.

Vercel

Application hosting, edge runtime

Data: Operational data, no customer data persisted

Supabase

PostgreSQL database, authentication, file storage

Data: All customer data: matters, bids, reviews, professional profiles, COIs

Resend

Transactional email delivery

Data: Email addresses, email content (notification subjects/bodies)

Stripe (Connect)

Payment rail. The firm's invoice is issued on Scope's Stripe account, two lines: the professional's price and Scope's fee. When the firm pays, Stripe transfers the professional's price to their connected account in full, automatically. Onboarded professionals only.

Data: Payment instruments, billing addresses, fee calculations, reconciliation metadata

Anthropic

AI model called by Scope's own servers. The uses are listed below.

Data: Listed below.

Twilio

SMS notifications to professionals (dispatch offers, timing nudges)

Data: Professional mobile numbers, message bodies containing matter references

Zoom

Deposition room provisioning for remote proceedings

Data: Participant names and email addresses, meeting metadata; recordings only where the firm enables them

Sentry

Application error telemetry

Data: Error payloads and request context. These can carry identifiers, so this is disclosed as touching customer data rather than as infrastructure-only.

Upstash

Rate limiting and short-lived operational counters

Data: IP addresses and request counts; no matter content

Cloudflare (Turnstile)

Bot verification on public forms

Data: Challenge tokens and IP addresses at form submission

GitHub (Microsoft)

Source code repository, MCP server distribution

Data: No customer data; only public + private source code

Google (Google Maps Platform, Geocoding API)

Converts a service address into map coordinates so Scope can measure where a service attempt was logged. Not in use yet.

Data: The service address only

Google, Reddit and LinkedIn (advertising conversion measurement)

Optional. After a public inquiry or new self-service signup, and only if you select Allow measurement, Scope tells the advertising platform that referred you that the action occurred.

Data: The conversion event, advertising click identifiers, and browser information such as IP address and user agent; Google may also receive a random event identifier. No names, email addresses, phone numbers, form contents or case information.

Google and Microsoft

Calendar sync, only when a user connects a calendar. Single sign-on, only when a firm signs in with Google Workspace or Azure AD.

Data: Calendar: the connected account's email address and, where the calendar lets Scope add events, the scheduled job (title, matter number, description, time and location). New Google calendar connections do not let Scope add events; the job goes out as an emailed invite. Single sign-on: the email, name and groups the firm's sign-in provider sends Scope.

What Scope sends to Anthropic

  • Request text a user pastes into Scope's intake tool, to draft a job.
  • The papers sent with a California process-serving work order (up to eight files), where Scope has turned on its proof-of-service draft, to read the case number, court, parties and document titles. Those case details are saved with the draft.
  • A professional's text reply to a legacy bid request, when it is not in the standard format.
  • Requests sent to the demo chat on scope.bid and to the Scope GPT, with the tool results returned to them. Both use Scope's public demo key, so legal requests return demo results.
  • When your firm has turned it on and a member of your firm selects court papers in your case system: Scope checks them on its own side, does not send anything that looks medical, and sends the rest to pull out the facts needed to order outside work, each fact shown with its source page.

Scope does not send the documents or delivered files on a medical records matter to an AI provider.

An AI assistant your firm connects to Scope is your firm's own tool, not a Scope subprocessor. Scope receives the tool calls it sends and returns the results. Scope does not send your conversation with that assistant anywhere. The Scope GPT is the exception: Scope sends each request it receives to Anthropic, as listed above.

Different verticals, different sensitivities

  • Legal services

    Data we touch

    Case captions, witness names, deposition scope, records subject identifiers, sometimes SSN / DOB on subpoenaed records, work-product-privileged matter detail.

    Posture

    Attorney-client and work-product privilege respected. Each firm's data is filtered to that firm by the server. SOC 2 Type I in preparation, plus cyber and tech E&O coverage.

    Extras

    Scope stores the files delivered on a matter and the documents sent with its work order. Governance is queryable: scope_vendor_health and scope_credential_alerts surface COI / W-9 / insurance expiry across your roster; scope_roster_audit returns the event chain per matter for compliance review.

  • Insurance claims (preview)

    Data we touch

    Claimant PHI (medical records, IME reports), PII (SSN, DOB), surveillance subject identifiers, claim file numbers.

    Posture

    Encryption at rest and in transit. Claims vertical is in preview.

    Extras

    Segregated data namespaces and per-matter audit records available to a carrier's privacy office on request. Governance is queryable: scope_vendor_health and scope_credential_alerts include BAA status per professional; scope_roster_audit returns the event chain per claim file.

See something? Send something

We take security reports seriously and aim to acknowledge within 48 hours.

Security questions, on request

SOC 2 Type I is in preparation. Security questionnaires are answered on request.

A matter's lifecycle writes rows as it happens

scope_activity is the event log. Clients cannot edit or delete its rows. Available on request for audit. PII redacted in the sample below.

audit-log query: matter SC-2143

[
  { "ts": "2026-05-17T08:06:41Z", "event": "scope_created",
    "actor": "buyer", "summary": "eDiscovery scope created and opened to professionals" },
  { "ts": "2026-05-17T08:07:14Z", "event": "dispatched",
    "actor": "system", "summary": "Routed to 5 professionals in category, jurisdiction PA" },
  { "ts": "2026-05-17T08:08:02Z", "event": "quote_received",
    "actor": "vendor", "summary": "Quote returned: professional name redacted, $3,450.00" },
  { "ts": "2026-05-17T08:14:55Z", "event": "quote_awarded",
    "actor": "buyer", "summary": "Awarded to professional; engagement locked" },
  { "ts": "2026-05-17T08:15:12Z", "event": "vendor_accepted",
    "actor": "vendor", "summary": "Professional confirmed engagement" },
  { "ts": "2026-05-17T08:16:03Z", "event": "calendar_set",
    "actor": "system", "summary": "Calendar event booked May 28 2026" },
  { "ts": "2026-05-28T15:42:11Z", "event": "work_completed",
    "actor": "vendor", "summary": "Matter marked complete; deliverables uploaded" },
  { "ts": "2026-05-28T15:42:30Z", "event": "invoice_issued",
    "actor": "system", "summary": "Invoice issued to firm: professional's price plus Scope fee, two lines" },
  { "ts": "2026-05-29T11:08:44Z", "event": "invoice_paid",
    "actor": "system", "summary": "Firm paid; professional's price transferred to their account in full" }
]