Minds / Service providers

Know the path your data takes.

A practical directory of service roles, deployment dependencies, and customer-connected providers to review with Minds.

This directory explains service architecture. The exact contracting entities, processing regions, active vendors, and change-notification terms for a customer must be confirmed in the applicable provider schedule or DPA. It is not a representation that every listed integration is enabled for every account.

01

Website and workspace delivery

Vercel hosts the public Minds website and the Minds workspace web application. Requests to those surfaces involve network and request information needed to serve pages and operate the hosting platform. Hosted application functions may process request content needed to provide the feature being used.

The website also uses Unicorn Studio for selected visual experiences. Loading those experiences can contact its delivery infrastructure and disclose normal request information, such as the visitor’s network address and browser headers. The animation service is not the storage location for customer memory.

02

Dedicated instance infrastructure

Free and Pro are designed around dedicated Akasha instances using Firecracker microVMs. The current provisioning integration targets Google Cloud infrastructure. Provisioning records and runtime configuration determine the environment used by a particular instance; a plan name alone is not a data residency commitment.

Confirm the hosting provider’s legal entity, instance region, storage, backup, and support-access arrangements for your deployment before placing a workload with location or subprocessor restrictions. Customer-managed infrastructure and separately agreed enterprise deployments can have different operators.

03

Networking and identity

Cloudflare is integrated for customer domain and DNS management. DNS configuration and any configured proxying are distinct roles: the record’s configuration determines whether application requests pass through a proxy.

Minds uses L1fe identity and service infrastructure for account authentication, authorization, and platform operations. These systems process account identifiers and relevant session or organizational information. The applicable agreement should identify the operating entity and any underlying providers; an internal service name is not a legal entity.

04

Billing and payments

Minds’ billing integration routes through the L1fe billing services. Payment checkout, subscriptions, invoices, and metering may involve an external payment provider. Confirm the provider presented during checkout and the applicable billing arrangement.

Legacy API names and source comments mention Stripe, but those names alone do not establish the executing payment processor for a current transaction. We therefore do not publish a fixed processor or jurisdiction based solely on them. Payment providers can also process information for their own legal and fraud-prevention purposes.

05

Product analytics and diagnostics

The workspace contains a PostHog integration for page activity and identification of signed-in users. When enabled, events may be associated with a user ID, email, name, and profile information. This is not equivalent to anonymous analytics or a blanket promise that no personal information is sent.

Other diagnostics or communication libraries in the software are configuration-dependent. A library’s presence does not establish that a vendor is active for your deployment. Request the active service list and relevant settings when reviewing analytics, error reporting, or support communications.

06

Models, tools, and harnesses you connect

An external model, tool, or agent harness can receive prompts, context, retrieved passages, and tool results needed to fulfill a request. The destination depends on the provider and routing your organization enables.

Document these providers alongside Minds when mapping your data flow. A service your organization contracts directly may be your provider rather than Minds’ subprocessor. Review its terms, retention settings, data locations, and training policy separately. Do not assume that a dedicated Akasha instance keeps external model requests inside the instance.

07

Get the applicable schedule

Email legal@minds.sh with your organization, deployment, and any existing Order reference to request the provider schedule and processing locations that apply to your service. Ask for the applicable notice and objection procedure for provider changes as part of that agreement.

This website does not currently offer an automated provider-change subscription. Do not rely on an unconfigured subscription or assume a fixed advance notice period unless it is included in your agreement.

Let’s make it clear.

For privacy requests, contact privacy@minds.sh. For agreements and processing questions, contact legal@minds.sh. Include your organization and the document you are asking about. Never email passwords, API keys, or sensitive customer content.