Subprocessor List

Who this list is for

EraShift Studio LLC ("EraShift", "we") provides Pitchlume (the "Service") to businesses ("Customers"). To run the Service we use a small number of other companies. A Subprocessor is a third party that we engage and that may receive or store Customer Data (data that a Customer or its users put into the Service, including Customer Content such as drawings, CAD files, catalog material and rating tables).

All of our Subprocessors are United States companies. We use them in US regions, with one stated exception in the table (the video provider, an optional feature).

Current Subprocessors

Notes on the AI providers.

• Drawings and other customer files go only through our direct accounts with OpenAI, Anthropic and Google Cloud Vertex AI. If none of those routes is available for a request, the request fails. It does not fall back to another provider.
• We have asked each AI provider for zero data retention. Until a provider confirms it for our account, its standard terms apply, under which inputs may be kept for a limited period (up to 30 days under the terms we have seen) for abuse monitoring, and not for training.
• Which AI provider handles a given Workspace's requests depends on that Workspace's AI pathway, which EraShift sets. Not every provider in the table is in use for every Workspace.

Services that receive no Customer Data

These are not Subprocessors, and we list them so the picture is complete.

• Google LLC (Gemini API through Google AI Studio): used only with public or test data. It is not limited to US regions, so our routing rules never send it customer files or Workspace data.
• Netlify, Inc.: DNS for a domain. It receives no Customer Data.

Not our Subprocessors: services a Customer chooses to connect

Some features connect Pitchlume to a service the Customer chooses and contracts with. Those companies are the Customer's own vendors, not EraShift's Subprocessors. The Customer decides whether to connect them and is responsible for its agreement with them. These integrations are off unless a Customer turns them on.

Changes to this list

• Notice: we will post any new or replacement Subprocessor on this page, with a new version, and tell each Customer's notice contact or Workspace admins by email at least 30 days before it begins to process Customer Data.
• Objection: a Customer may object to a new Subprocessor on reasonable data-protection grounds within the 30-day notice period, as set out in the Data Processing Addendum (pitchlume.ai/legal/dpa). We will work with the Customer in good faith to address the objection. If we cannot, the Customer's remedy is the one in the DPA: it may end the affected part of the Service and receive a refund of prepaid fees for the remaining term.
• Emergencies: if we must replace a Subprocessor urgently (for example, for security or to keep the Service running), we will give notice as soon as we can and the same objection right applies.

Our requirements for Subprocessors

Before a Subprocessor receives Customer Data we check that it:

• is a United States company and processes the data in US regions, or we say plainly on this page where that is not confirmed;
• has written terms that protect the data, including confidentiality and security;
• for AI providers, is on paid commercial terms that do not allow training on our data, with zero data retention where the provider offers and confirms it;
• receives only the data it needs for its purpose.

Questions: info@pitchlume.ai.

Change log