Subprocessor List
Last updated July 2026 · v.01
Required Policy Attachment to the Master Services Agreement.
1. Purpose
This Public Subprocessor List identifies the third-party service providers Clasp uses to operate the Service. These subprocessors support hosting, authentication, messaging, billing, OCR, and metadata-only AI functionality. This list is provided for transparency and does not create contractual rights or obligations.
Contractual terms governing subprocessors are defined in Appendix H of the Clasp Master Services Agreement (MSA).
2. How Clasp Uses Subprocessors
Clasp uses subprocessors to:
host and secure the platform;
authenticate Users;
process notifications and email delivery;
process payments;
perform OCR for search indexing;
generate metadata and embeddings;
maintain system performance and reliability.
Clasp does not transmit document text or Customer Data to external large language models. Clasp does not use subprocessors for marketing, analytics, or advertising.
3. Current Subprocessors
3.1 Google Cloud Platform (GCP)
Function: Hosting, storage, encryption at rest, encryption in transit, load balancing, networking.
Location: United States
Data Processed: Customer Data, Account Data, Usage Data, OCR outputs, embeddings, metadata.
3.2 Supabase
Function: Authentication flow for “Sign in with Google” and OTP generation.
Location: United States
Data Processed: Account Data, authentication metadata.
Notes: Supabase does not access document content.
3.3 Unstructured.io
Function: OCR and document parsing for search indexing.
Location: United States
Data Processed: Document text for OCR extraction only.
Notes: OCR output is used solely for indexing and search.
3.4 Twilio (only for SMS)
Function: Programmable SMS messaging for system notifications.
Location: United States
Data Processed: Phone number metadata, notification content.
Notes: Twilio does not access document content.
3.5 Postmark
Function: Transactional email delivery and reliability routing.
Location: United States
Data Processed: Email metadata, notification content.
Notes: Clasp does not guarantee delivery times or deliverability rates.
3.6 Stripe
Function: Payment processing and subscription billing.
Location: United States
Data Processed: Billing information, payment metadata.
Notes: Clasp does not store payment card data (PCI).
3.7 AI Assisted Components
N/A Clasp does not use external AI vendors for embeddings or inference. All metadata and embeddings are generated internally.
Location: N/A
Data Processed: N/A
4. Subprocessor Changes
Clasp may add or remove subprocessors as needed to operate the Service. Changes to this public list do not amend the MSA. Contractual notice requirements, if applicable, are defined in Appendix H.
5. Questions
For questions about subprocessors, contact Clasp Legal Technologies, Inc.
Email: hello@clasplegal.com
Mail: Clasp Legal Technologies, Inc., 300 Creek View Rd, Suite 209, Newark, DE 19711, United States