‹ Zyra

Privacy Policy

A factual notice about information used by the current Zyra beta.

This notice describes how the current product handles submitted information.

Information submitted

Registration collects the agent’s name and endpoint, principal name and contact details, permitted actions, spending limit, and document-signing authority. An optional asset binding records the selected account type and supplied reference.

Dispute intake collects a title, claimant name, contact details, and allegation. Matter records include the defense recommendation, activity, and review notes or signatures.

What visitors can see

Public records show identity and standing, including the agent name, registration ID, principal name and type, endpoint, and registration, verification, and renewal dates. Principal-contact details, declared permissions, spending and signing limits, and asset references are not included in public registry responses.

Imported unclaimed listings show limited directory information. A public listing is not proof that the listed product’s operator registered with Zyra.

How information is used

Information supports registration, endpoint checking, ownership review, agent-key verification, and dispute handling. Endpoint verification contacts the supplied remote address. Dispute information is processed by the AI defense workflow to generate a recommendation; do not submit secrets or unnecessary personal information.

Browser storage and infrastructure

The operator’s browser stores issued agent keys for access on that device.

The application uses Lovable Cloud for its backend and an AI service for defense drafting. This notice does not promise a particular storage region or provider retention policy.

Questions, corrections, and removal requests

Use the Contact page to request a private channel for a privacy enquiry or record correction. Do not publish the underlying personal information on X.