Service providers and subprocessors.

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

Last updated November 10, 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, the things you hide, your words, and Deep scan results are not sent to these providers. See ourPrivacy Policy for the data flows and your choices.

Core service providers

Cloudflare

  • Purpose: Hosting the website and the licensing API (Workers), our database (D1) for purchases, licenses, activations, redemptions, install attribution, feedback, and short-lived purchase links, DNS, content delivery, network security, and hosting our self-hosted Umami analytics application, and sending transactional email (purchases and license recovery) through Cloudflare Email Service.
  • Data: Website and API request data, IP address, user agent, security signals, contact and order details, license and browser IDs, activation dates, attribution data and hashes, redemption records, purchase status, feedback text, analytics events, and for email: your email address, license key, plan details, and delivery metadata.
  • Processing location: Cloudflare's global network; the database is stored in a Cloudflare data center region.

Opskeet

  • Purpose: Website chat, help articles, and customer support.
  • Data: Chat messages, files and ratings you send; name and email if you share them; approximate location derived from IP address (IP addresses are not kept); time zone, language, browser, device, referrer, recent pages viewed on our site, and support events such as a completed purchase. The widget keeps a token in your browser storage so your chats are there when you come back.
  • Processing location: Cloudflare global network.

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.

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.

Mozilla Add-ons

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

Microsoft Edge Add-ons

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

Hugging Face

  • Purpose: Hosting the model and tokenizer files downloaded for Deep scan, which runs on your computer.
  • 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 blog posts, loaded in YouTube’s privacy-enhanced mode.
  • 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 atsupport@safescreenshare.com.