Skip to main content

Legal

ScreenOps Subprocessors

Effective September 9, 2026 | Version screenops-subprocessors-2026-08-v2 | ScreenOps Product

ScreenOps may use the providers below to operate the service. A provider is involved only when the applicable feature, customer configuration, or delivery path requires it; not every provider processes data for every ScreenOps customer. See the Mosari Platform Subprocessor List for the platform-wide disclosure.

Counsel review pending. This page is an operating draft prepared for the ScreenOps launch; treat it as internal-quality until legal sign-off.

Current subprocessors

ProviderServicePurposeData categories
Cloudflare, Inc.WorkersApplication compute and edge hostingRequest metadata, application traffic
Cloudflare, Inc.D1Primary application databaseAccount, company, CRM, field-service, and audit records
Cloudflare, Inc.R2Object and media storageUploads, photos, generated assets, exports
Cloudflare, Inc.KVConfiguration and lightweight stateNon-secret configuration keys and cache-like values
Cloudflare, Inc.QueuesBackground and sync jobsJob payloads (record identifiers, sync metadata)
ResendTransactional emailAuthentication, invitations, and notificationsEmail addresses, message content
Stripe, Inc.Payments and billingSubscription billing and payment processing where enabledBilling identifiers, payment metadata
Intuit Inc.QuickBooks OnlineAccounting synchronization when a company connects itInvoices, customers, sealed connection tokens
Twilio Inc.Messaging (conditional)SMS configuration and delivery when the feature is enabled and approvedRecipient phone numbers, message content
Google LLCMapsAddress lookup and mapping features when enabledLocation queries, API usage metadata

Changes to this list

When we add, remove, or materially change a subprocessor we update this page and record the change internally with a date. Customers with contractual notice rights are notified per their agreement.

Questions

For data processing questions, see our Privacy Policy or contact us using the address published at /.well-known/security.txt.

Questions? Visit Help & resources or account recovery.