TeaQL Service Privacy Notice

This notice explains what information may be sent to TeaQL-operated server-side services when you use hosted TeaQL capabilities such as online model exploration, model-assisted generation, demo runtimes, or managed support workflows.

It is intended to help customers understand the data flow before they connect a client, upload a model, or invoke a server-side TeaQL capability. It is not legal advice.

Scope

This notice applies when a client application, browser, command-line tool, generated SDK, or integration calls a TeaQL-operated service.

It does not apply to TeaQL code that you run entirely inside your own environment. For self-hosted deployments, your organization controls the runtime, database, logs, retention, and access policies.

Information You May Send to TeaQL Services

Depending on which capability you use, your client may send the following categories of information.

Category	Examples	Why it is processed
Account and contact information	Name, email address, organization, support contact details	Account administration, support, security notices
Project and model information	KSML files, entity names, field names, relationships, constants, workflow objects, metadata annotations	Model analysis, code generation, examples, validation, support
Generation inputs and outputs	Generation options, target language or runtime, generated package metadata, error messages	Produce generated APIs, diagnose generation failures
Runtime requests	Query filters, selected fields, paging, sorting, service-request payloads, view-object payloads	Execute hosted demos, previews, and server-side TeaQL functions
Uploaded sample data	Test records, fixtures, CSV/JSON samples, demo payloads	Demonstrations, debugging, examples, support
Technical logs	IP address, user agent, request time, endpoint, status code, latency, trace identifiers	Security, reliability, abuse prevention, troubleshooting
Diagnostic data	Stack traces, validation errors, build logs, schema compatibility messages	Debugging, quality improvement, customer support

You should not upload production secrets, credentials, private keys, payment card numbers, health records, government identifiers, or other highly sensitive personal data unless you have a written agreement with TeaQL that explicitly covers that use.

What TeaQL Does Not Need by Default

TeaQL services do not require full production databases for normal model exploration or code generation.

For most workflows, TeaQL only needs:

• model definitions,
• representative schema metadata,
• non-sensitive sample payloads,
• generation configuration,
• error reports needed to diagnose a problem.

When a database connection is required for a specific managed workflow, the connection details, access scope, and retention expectations should be agreed separately before use.

How Uploaded Information Is Used

TeaQL may use uploaded or transmitted information to:

• provide the requested hosted capability,
• generate code, schemas, metadata, examples, or documentation,
• execute demo or preview requests,
• troubleshoot support cases,
• protect the service from misuse,
• monitor reliability and performance,
• improve product quality using aggregated or de-identified diagnostics.

TeaQL does not use customer project data to sell advertising.

Server-Side Runtime Calls

Some TeaQL clients call server-side capabilities instead of doing all work locally. A runtime call may include:

• the requested entity or service object,
• filter expressions,
• selected fields,
• pagination and sorting,
• the current user or tenant context provided by your application,
• form or workflow payloads,
• correlation identifiers for tracing.

The server processes this information to return the requested result. Application teams should configure their UserContext, permissions, field selection, logging, and masking rules so only necessary data is sent.

Logs and Retention

TeaQL-operated services may retain technical logs and diagnostic records for security, reliability, billing, and support.

Retention periods can vary by service and customer agreement. Support artifacts supplied by a customer may be deleted after the case is closed unless longer retention is required by contract, security review, or legal obligation.

Customers can request deletion of uploaded project materials or support artifacts by contacting TeaQL through the agreed support channel.

Access and Sharing

Access to customer-uploaded information should be limited to personnel and systems that need it to operate the service, provide support, or maintain security.

TeaQL may use infrastructure, hosting, analytics, logging, or support providers to operate the service. Those providers should process information only for service operation and support purposes.

TeaQL may disclose information if required by law, to protect the service, or to investigate abuse or security incidents.

Website Analytics and Cookies

The TeaQL website uses Google Analytics to understand aggregate website usage and improve documentation, examples, and navigation. Analytics is loaded only after a visitor accepts analytics cookies in the website consent notice.

Google Analytics may process information such as page views, referring pages, approximate location, device type, browser, operating system, and interaction timing. Google Analytics may also set cookies or similar identifiers in the visitor's browser after consent is given.

TeaQL uses this analytics data for product and documentation improvement. TeaQL does not use website analytics data to sell advertising.

Visitors can reject analytics cookies from the consent notice. If analytics cookies are rejected, the website does not load the Google Analytics script for that browser and stores the rejection preference in local storage. Visitors can also control or delete cookies and local storage through their browser settings.

Customer Responsibilities

Before sending data to a TeaQL-operated service, customers should:

• classify the data they plan to upload,
• remove secrets and unnecessary personal data,
• use synthetic or masked examples where possible,
• avoid uploading full production datasets unless explicitly agreed,
• configure field-level selection and masking in TeaQL-based applications,
• ensure they have the rights and legal basis to transmit the data,
• document whether they are using hosted TeaQL services or self-hosted TeaQL runtimes.

Self-Hosted Deployments

When TeaQL is deployed inside your own infrastructure, TeaQL software may still process application data, but the data remains under your operational control unless you separately send it to TeaQL for support, generation, diagnostics, or managed services.

In self-hosted deployments, your organization is responsible for:

• database access controls,
• runtime logs,
• audit trails,
• backups,
• retention,
• network security,
• data subject request handling,
• compliance with laws and customer contracts.

Security Practices

TeaQL-operated services should use standard security controls appropriate to the service, such as encrypted transport, access control, operational logging, and restricted support access.

Customers with specific security, residency, encryption, or retention requirements should confirm those requirements before using hosted capabilities with sensitive data.

Contact

For privacy, security, deletion, or support questions related to uploaded TeaQL project materials, use the support or account contact provided in your TeaQL agreement.

If you are evaluating TeaQL without a separate agreement, do not upload confidential or regulated data. Use synthetic examples instead.