Skip to main content
Transparency

Service providers and subprocessors.

The companies that help us host, sell, support, secure, and measure Safe Screen Share.

Last updated August 24, 2026

This page lists the main third parties that may handle data in connection with Safe Screen Share. "Subprocessor" is included for familiar procurement terminology. Depending on the activity and applicable law, a company may instead be our processor, service provider, or an independent controller.

Screen content, blur rules, selected text, and local AI results are not sent to these providers. See our Privacy Policy for the data flows and your choices.

Core service providers

Cloudflare

  • Purpose: DNS, content delivery, network security, and hosting our self-hosted Umami analytics application.
  • Data: Website and API request data, IP address, user agent, security signals, and analytics events.
  • Processing location: Global network; the analytics workload is configured in Western Europe.

Vercel

  • Purpose: Website hosting, serverless routes, logs, and Vercel Web Analytics.
  • Data: Website requests, IP address, user agent, server logs, aggregate analytics, checkout metadata, and short-lived attribution data.
  • Processing location: Global infrastructure, including the United States.

Railway

  • Purpose: Licensing API hosting and PostgreSQL hosting for self-hosted Umami.
  • Data: API request data, license and purchase service traffic, operational logs, and website or extension analytics stored by Umami.
  • Processing location: Project-selected regions; the Umami database is hosted in the European Union.

MongoDB Atlas

  • Purpose: Managed database for purchases, licenses, activations, redemptions, install attribution, and short-lived purchase links.
  • Data: Contact and order details, license and browser IDs, activation dates, attribution data and hashes, redemption records, and purchase status.
  • Processing location: The cloud region configured for our Atlas deployment.

Resend

  • Purpose: Transactional email delivery for purchases and license recovery.
  • Data: Email address, license key, plan details, and delivery metadata.
  • Processing location: United States and provider infrastructure.

Crisp

  • Purpose: Website chat and customer support.
  • Data: IP address, device and session metadata, contact details, chat messages, and attachments you provide.
  • Processing location: Core customer data in the European Union.

Better Stack

  • Purpose: Public system status page and status badge.
  • Data: Request data such as IP address, user agent, and status-page interactions.
  • Processing location: European Union, United States, and provider infrastructure.

Evendeals

  • Purpose: Regional pricing eligibility, discount display, and offer measurement.
  • Data: Page URL, IP-derived country, user agent, discount eligibility and interaction data, and local or session storage for offer state.
  • Processing location: Global edge and hosting infrastructure.

Independent services and sales channels

The following companies generally decide for themselves how to process data for payment, marketplace, distribution, model-download, or embedded media services. Their own terms and privacy notices apply.

Creem

  • Purpose: Merchant of record for direct checkout, tax, invoices, fraud checks, refunds, and chargebacks.
  • Data: Contact, billing, payment, transaction, tax, device, and fraud-prevention data. We receive fulfillment details, not full card numbers.
  • Processing location: European Union, United States, and payment-provider infrastructure.

AppSumo

  • Purpose: Marketplace sales, redemptions, customer service, and marketplace refunds.
  • Data: Account, contact, order, payment, redemption, and support information.
  • Processing location: United States and provider infrastructure.

SaaSZilla

  • Purpose: Legacy marketplace sales, redemptions, customer service, and marketplace refunds.
  • Data: Contact, order, payment, redemption-code, and support information.
  • Processing location: Singapore and provider infrastructure.

Google Chrome Web Store

  • Purpose: Extension distribution, installation, updates, and store operations.
  • Data: Google account, device, network, store, installation, and usage data handled by Google under its policies.
  • Processing location: Global Google infrastructure.

Hugging Face

  • Purpose: Hosting the model and tokenizer files downloaded for local AI Redact.
  • Data: File request, IP address, user agent, and delivery logs. Page content and AI results are not sent.
  • Processing location: United States, European Union, and provider infrastructure.

YouTube

  • Purpose: Embedded videos on selected website pages.
  • Data: IP address, device, cookie, account, and viewing data as determined by Google when an embed loads or is used.
  • Processing location: Global Google infrastructure.

Changes

We may replace or add providers as the Services change. We will update this page before or around the time a new provider begins handling data. For material changes, we will provide additional notice when required. You can ask about a provider or request change notifications at [email protected].