This Self-hosted Privacy Notice explains what personal data YottaBot Inc. ("YottaBot," "we," "us," or "our") receives and processes when an enterprise runs the self-hosted YottaBot software ("Self-hosted Software") in its own Kubernetes cluster, cloud account, VPC, data center, or other approved environment. It should be read with the YottaBot Enterprise Self-hosted Terms and the customer's written agreement.
Account administration, sales, billing, support, and website visits are covered by the YottaBot SaaS Privacy Policy.
1. What Stays in the Customer's Environment
The standard Self-hosted Software does not send Customer Content, prompts, files, outputs, connector payloads, user directory data, or logs to YottaBot servers merely because it is installed. It may communicate with YottaBot solely to verify license status, entitlement, version compatibility, renewal status, or revocation status, unless the customer separately enables remote support, hosted features, optional telemetry, model-provider routing, or sends support materials to YottaBot.
For the standard self-hosted deployment, YottaBot does not collect user data, Customer Content, prompts, files, logs, workflow payloads, tool payloads, connector data, model inputs, model outputs, secrets, or credentials from the customer's runtime environment.
2. Our Role
For self-hosted runtime Customer Content that remains in the customer's environment, YottaBot is not a controller or processor merely because the customer uses the Self-hosted Software. The customer is responsible for that data, including its notices to its own users.
For license verification and any materials the customer chooses to send to YottaBot, YottaBot generally acts as a business or controller.
3. License Verification Data
For self-hosted deployments, we may collect limited metadata needed to verify license status and entitlements, such as license ID, customer or account identifier, product version, deployment or instance identifier, entitlement status, verification timestamp, source IP address, and request metadata. License verification is not designed to transmit Customer Content, user account lists, prompts, files, logs, tool payloads, outputs, secrets, or credentials.
We use this data to verify licenses, entitlements, version compatibility, renewal status, and license compliance, and to secure the license service.
4. Data the Customer Chooses to Share
A customer may also choose to share support materials, enable optional telemetry, grant remote access, or connect the self-hosted deployment to third-party model providers or hosted features. Those customer choices may cause additional data to be processed outside the customer's environment.
If a self-hosted customer sends support bundles, logs, screenshots, account information, billing information, security reports, or other materials to YottaBot, we process that information under this notice, the SaaS Privacy Policy, and the applicable written agreement.
Customers should not send passwords, private keys, API keys, access tokens, production secrets, payment-card data, protected health information, or other highly sensitive information through email, Slack, screenshots, support tickets, or recordings unless the parties agree to a secure handling method.
5. Model Providers
Self-hosted customers may configure provider routes according to their deployment and written agreement. When they do, prompts, context, tool payloads, metadata, and outputs go from the customer's environment to the providers the customer chooses, under those providers' terms.
6. Staff Access
For self-hosted customers, YottaBot personnel do not have access to the customer's cluster or Customer Content unless the customer provides access, sends materials to YottaBot, or enables a support path that permits access.
7. Retention
Self-hosted customers control retention inside their own environments except for materials they choose to send to YottaBot and license verification metadata processed by YottaBot. We keep license verification metadata and support materials for as long as needed to verify licenses, provide support, maintain security, comply with law, and enforce agreements.
8. Rights and Requests
People whose data is in a self-hosted deployment should contact the customer that runs it. For license verification data or materials sent to YottaBot, contact support@yotta.bot. We may need to verify identity and authority before responding.
9. Changes and Contact
We may update this notice from time to time. The Last Updated date shows the latest version. Questions: support@yotta.bot.