Privacy Policy

Zitrino operates the GuideLite platform. For data you upload and for conversations your agents handle, you are the controller and we are the processor. For your own account and billing data, we are the controller.

Questions, requests and complaints can be sent to enquiry@zitrino.com.

Account data: name, work email, organisation, role and authentication metadata. Billing data: plan, invoices and payment references held by our payment processor.

Platform data: the knowledge sources, prompts and configurations you create, and the conversations your agents handle, including traces of retrieval, model calls, tool calls and guardrail decisions.

Technical data: log entries, IP address, device and browser information, and product usage events.

To provide and secure the service, to bill you, to support you, and to investigate abuse or incidents. Traces and audit records exist so that you and your reviewers can reconstruct what an agent did.

We do not sell personal data, and we do not use your conversation content to train external models.

Model providers process prompt and response content when your agent calls them, under the model policy you configure. Infrastructure, error-monitoring and payment providers process the categories necessary for their function.

A current sub-processor list is available on request, and we will give notice before adding a new one that processes customer content.

Conversations, traces and audit records are retained for the period configured on your organisation. Audit records are append-only within their retention window and cannot be edited.

On request or on account closure we delete customer content in line with the retention schedule, except where we are legally required to keep it.

Depending on where you live, you may have rights of access, correction, deletion, restriction, objection and portability. We provide data subject request tooling and will support your requests as processor.

Requests are answered within the statutory period, and we will tell you if an exemption applies rather than ignore it.

Access is role-based and scoped by organisation, project and environment, and fails closed. Sensitive fields are masked and redacted in transcripts, logs and exports. Secrets are held in a broker and never returned in raw form.

We hold no third-party security attestation today. Our control-by-control position is published on the compliance page rather than summarised as a badge.

Data may be processed in a country other than your own by us or a sub-processor. Where that happens we rely on an appropriate transfer mechanism. Regional data residency is not currently offered.

We will post material changes to this policy on this page and, where the change affects how customer content is processed, notify account administrators directly.