We route requests. We do not train on customer prompts.

WeaveAPI is built as an API gateway. We collect the minimum operational data needed to authenticate requests, meter usage, prevent abuse, and keep the service reliable.

Data we process

Account records, API keys, usage counters, billing events, request metadata, error logs, and support messages may be processed to operate the service.

Prompt handling

Prompt and response content is routed to upstream model providers so they can complete the request. We do not sell prompt content or use it to train WeaveAPI models.

Retention

Operational logs are kept only as long as needed for metering, debugging, compliance, security review, and abuse prevention. We can shorten or delete records when required by law or account closure.

Upstream providers

Requests are forwarded to selected model providers. Their processing may be governed by their own terms. We avoid exposing upstream API keys to end users.

Security

Access to operator systems is restricted, production secrets stay on the server side, and database backups are retained for service recovery.

Contact

For privacy requests, account deletion, or data questions, contact the WeaveAPI operator through the support channel listed in the console.