Zorqelio / Data handling and retention

What the service processes

Zorqelio processes account email addresses, workspace configuration, salted password hashes, token hashes, schemas, policies and operational usage records to provide authenticated workflow checks. Transactional email is sent through Resend; subscription processing uses PayPal; hosting and storage use Cloudflare. x402 payments use public-chain transactions and payment-facilitator infrastructure.

Payloads and evidence

Validation and quality operations inspect submitted payloads in memory. Raw validation payloads, guarded callback results and destination credentials are not stored by those operations. Schemas and quality rules are persisted as workspace configuration. Do not place passwords or unnecessary personal data into schemas, rule names or workflow identifiers.

Sanitized quality and guarded-handoff evidence is retained for seven days. Guarded input digests are removed after one day. These specific periods do not describe every account, billing, monitoring or provider record. Configuration is preserved when access pauses; evaluation expiry does not automatically erase an account.

Assistant account connections

When you approve an assistant connection, requested workspace names, policy definitions, evaluation results and handoff evidence are shared with that assistant. Workspace API tokens, passwords and billing credentials are not shared. Labels and rule text can contain customer data; review them before connecting. Connections are read-only, last at most 30 days and can be revoked in Connected apps. Access tokens expire after 15 minutes and refresh tokens rotate. Credentials are stored as hashes. Expired grants and temporary authorization records are removed by bounded scheduled cleanup. Registered client names and callback URLs are retained to keep configured clients valid. Your assistant provider has its own retention policies.

Third-party systems

Your destination integration determines what it stores. The inventory reference destination retains item data and operation receipts in your own database. Provider retention, public blockchain records and customer destinations are outside the validation payload-retention boundary.

This page describes the current technical data flow. For account-data requests or questions, contact the operator through the support contact shown on the pricing page. Do not send credentials or raw sensitive payloads with a support request.