Sub-processors

Studio Makker LLC — Empress

Last updated: [date of publication]

Studio Makker uses the vendors below to provide Empress. A sub-processor is a vendor Studio Makker contracts with and operates to process personal information for our customers, including one a customer switches on for its own sites (such as Google sign-in). Each is bound by written terms that restrict it to processing personal information only to provide its service to us. We remain responsible for each sub-processor's performance of its data-protection obligations.

Notice of a new sub-processor. At least 30 days before a new sub-processor processes customer personal information, we update this page and email every workspace's billing contact. You may object on reasonable data-protection grounds within those 30 days by writing to privacy@tryempress.dev. If we cannot resolve your objection, you may cancel your plan before the new sub-processor starts; the Data Processing Addendum §6 has the detail.

Infrastructure and AI

  • Cloudflare, Inc.
    • What it does for Empress: Hosting and compute (Workers, and Workers for Platforms for pooled sites), databases (D1), object storage (R2), key-value storage, Durable Objects, transactional email (Cloudflare Email Service), browser rendering, image handling, the bot check at signup (Turnstile)
    • Data it processes: Site content and media, reader accounts and sessions (with IP address and user agent), form submissions, member accounts, the console's own records, operational logs
    • Placement: Pooled: all of it on Studio Makker's account. BYO: site and reader data sit in the customer's own account; Studio Makker's account holds the workspace's fleet record, billing records and usage totals
    • Location: Cloudflare's global network; storage at rest is not pinned to a region, and pages are served from the location nearest the reader
  • Cloudflare, Inc. (Workers AI and AI Gateway)
    • What it does for Empress: Runs the AI model behind the Empress assistant; AI Gateway routes and logs model requests
    • Data it processes: Prompts, context and tool results in a chat turn; request metadata (workspace, member, turn)
    • Placement: Pooled: on Studio Makker's account. BYO: on the customer's own account
    • Location: Cloudflare's global network

The AI models. The Empress assistant runs one of two models, which a workspace owner chooses in the workspace's AI settings: GLM-4.7-Flash (@cf/zai-org/glm-4.7-flash), made by Zhipu AI, which is the default; or [second model] [Raj: name the second model when EMP-842 ships; until then publish the one-model text], made in the United States. Both are run by Cloudflare on Workers AI and reached through AI Gateway. Prompts go to Cloudflare, not to the company that made the model; neither model's maker receives customer data or is a sub-processor. Cloudflare's published terms for Workers AI state that it does not use inputs or outputs to train models, and that it keeps them only as long as it needs to answer the request. Separately, AI Gateway keeps a log of each request, including its prompt, which records what the assistant was asked; Studio Makker keeps those logs, like its server and application logs, for 30 days. Studio Makker does not train any model on customer content.

A stronger drafting model is not enabled. The product can hand some drafting to a second, stronger model; that is switched off in production. If we ever switch it on, that model and whoever runs it are listed here as a sub-processor, with the 30 days' notice above, before it processes any customer data.

Payments and invoicing

  • Stripe, Inc.
    • What it does for Empress: Payment processing, saved payment methods, bank account verification (Financial Connections), invoices (plan fees and services under Build and Services Agreements), receipts, dispute handling
    • Data it processes: Billing contact name and email, company, billing address, tax ID, card and bank details (held by Stripe, not by Studio Makker), invoice amounts, payment history
    • Placement: Both placements
    • Location: United States

Optional, at the customer's choice

  • Google LLC
    • What it does for Empress: Reader sign-in with Google on customer sites
    • Data it processes: Reader email address, name and profile image
    • Placement: Only on sites where the customer turns it on
    • Location: Google's global infrastructure, under Google's own terms

The customer's own vendors

Some processing is not ours to list:

  • The customer's Cloudflare account on BYO. Site and reader data in a BYO customer's own Cloudflare account are processed under the customer's own agreement with Cloudflare, and Cloudflare is not our sub-processor for that data; Studio Makker operates inside that account under the customer's permissions. Cloudflare remains our sub-processor for what sits on our account (the entries above).
  • Integrations the customer connects with its own credentials (for example its own Stripe account for memberships, a reservations provider, or an email platform) are the customer's vendors, not Studio Makker's sub-processors; the customer confirms its right to connect each one at connect time (Platform Terms §10.1).

Previous versions

Each change to this page is dated here, and the earlier version is kept at its own address linked from this list.

  • [date of publication]: first published.

Questions

privacy@tryempress.dev