Register status
This register describes verified hosting, account evidence and optional integrations as of the effective date. It is not an exhaustive customer-specific processing schedule. A provider account or software dependency does not establish that it receives data in every deployment. The parties must identify the applicable providers, regions and contractual safeguards in the completed schedules when adopting a DPA.
Verified hosting and account evidence
DigitalOcean, LLC: hosting of the BotStacks sandbox API is verified by a successful cluster access check and the running API container image. This supports identification of the hosting provider for that environment, not a claim that all BotStacks processing occurs there or in a single country. DigitalOcean publishes a Data Processing Agreement at https://www.digitalocean.com/legal/data-processing-agreement; the applicable account agreement, resource inventory and backup configuration must still be reconciled.
Pinecone Systems, Inc.: billing records establish a Pinecone account, and source code integrates Pinecone vector storage. This does not establish which live indexes receive which customer data, their configured regions, or a universal deletion interval. Pinecone publishes its DPA at https://www.pinecone.io/legal/data-processing-addendum/. Its standard DPA restricts certain sensitive personal data; a specially negotiated arrangement must be verified before routing such data to that service.
Stripe: the BotStacks billing account and customer portal are verified. Payment processing can include independent-controller activities as well as contracted services; do not classify every payment activity as a customer-content subprocessor. Determine the contracting entity and processing role from the applicable account terms.
Optional memory and AI integrations
The current Mem0 integration uses the Mem0 software library with Pinecone storage and OpenAI embeddings. Source configuration defaults memory reads and writes to disabled. The library integration alone is not evidence that Mem0's hosted service receives customer content. Actual enabled backends, model providers, routing, account terms and regions must be confirmed per deployment.
The source disables Mem0 telemetry, uses opaque scoped identifiers, suppresses memory-text logging and disables the library's separate entity store. These implementation controls do not establish every provider's training policy or retention settings. No blanket zero-retention, no-training, residency or completed international-transfer claim is made here.
Customer-specific provider information
For a customer-specific processing schedule, contact [email protected] or [email protected]. The schedule identifies the provider's legal entity, purpose, affected data categories, processing regions, transfer safeguard and relevant configuration. Customer-selected integrations and independent payment services may have separate roles and terms.
Deployment scope
Enabled providers can vary across hosting, model inference, retrieval, email, billing, monitoring, support, backups and website services. Ask for the inventory applicable to your deployment before submitting specially regulated information. Google Fonts is also loaded by the website; that integration does not establish a complete customer-content processor inventory.
Changes and objections
Where adopted, the DPA provides at least 30 days' notice of subprocessor additions or replacements and a process for reasonable data-protection objections. Contact [email protected] or [email protected] to request the register applicable to your agreement and designate your notice contact.