Privacy,
explained clearly.

This policy describes the information Quasentra processes to provide, secure, support, and improve its AI-agent authorization service.

Ask a privacy question →
01Collect for a defined purpose
02Keep credentials out of prompts
03Restrict workspace access
04Explain current limits honestly
01

Scope

This policy applies to quasentra.com, Quasentra accounts, the hosted control plane, dashboard, APIs, support interactions, and related services. It does not govern the independent privacy practices of your model provider, hosting provider, business tools, or other third parties you connect.

02

Information we process

Account

Name, email address, authentication state, account status, workspace, and plan.

Agent operations

Agent and tool metadata, policy configuration, authorization requests, decisions, approvals, incidents, and audit evidence.

Billing

Plan, transaction reference, charge status, currency, amount, and payment-provider response. Full card credentials should remain with the payment provider.

Technical

Request IDs, IP and device-related request information, timestamps, errors, rate-limit events, and security telemetry needed to operate the service.

Support

Messages, registered account details, redacted logs, screenshots, and other information you voluntarily send when asking for help.

Website

Basic server and security logs generated when a browser requests the website or API.

03

How information is used

  • provide accounts, subscriptions, authorization decisions, approvals, gateway operations and dashboard features;
  • authenticate users and agent API keys, prevent abuse, enforce quotas and protect workspace isolation;
  • investigate errors, incidents, suspected misuse and support requests;
  • process and reconcile subscriptions, payments, cancellations and eligible refunds;
  • maintain, measure and improve service reliability and security; and
  • communicate operational, security, account, billing or policy updates.

Quasentra does not need an LLM call to make deterministic authorization decisions.

04

Credentials and secrets

Agent API keys are shown once and stored as hashes. Supported gateway connector credentials are intended to remain server-side and are stored through the configured encrypted secret mechanism.

05

Service providers and disclosure

Quasentra may use hosting, database, email, security, monitoring, and payment providers to operate the service. These providers may process information only as needed for the services they supply and according to their agreements and applicable requirements.

Information may also be disclosed where reasonably necessary to comply with law, respond to lawful process, protect rights or safety, investigate misuse, or support a business restructuring. A final commercial policy should identify material provider categories and jurisdiction-specific requirements after legal review.

06

Cookies and session storage

Quasentra uses secure session and CSRF cookies required for account authentication and protection of browser actions. Operational cookies are not a substitute for agent API-key authentication. If analytics or optional marketing cookies are introduced, this policy and any required consent controls must be updated before use.

07

Retention and deletion

Information is retained while needed to provide the service, secure accounts, investigate incidents, meet operational or legal requirements, and resolve billing disputes. Different records may require different periods.

Production retention schedules, deletion timelines, backup handling, and customer deletion procedures must be finalized and published before commercial launch. Until then, customers should not treat this draft as a contractual retention commitment.

08

Security measures and limits

Current controls include hashed agent API keys, scoped permissions, tenant-aware access checks, CSRF protection for browser sessions, rate limiting, encrypted managed credentials, decision auditing, and security event monitoring.

No system can guarantee absolute security. Customers must protect their own accounts, deployment environment, agent prompts, business credentials, model-provider keys, and any tool path outside Quasentra enforcement.

09

Your choices and requests

You may contact us to ask about account information, correct inaccurate details, request account closure, or raise a privacy concern. A request may require identity verification, and some records may need to be retained where required for security, dispute resolution, billing, or law.

Specific statutory rights depend on your location and applicable law. This draft does not limit a right that cannot legally be limited.

10

Data locations and transfers

Service providers may operate infrastructure in jurisdictions different from yours. Before commercial launch, Quasentra must document its production providers, data locations, and any transfer safeguards required for the customers and regions it serves.

11

Children

Quasentra is a business and developer service and is not directed to children. Do not create an account or submit personal information if you lack legal capacity to agree to the service terms.

12

Changes to this policy

We may update this policy as the product, providers, or legal requirements change. The current version and update date will remain on this page. Material changes affecting active customers will be communicated where reasonably required.

13

Contact

Privacy questions and requests may be sent to support@quasentra.com. You may also call 0320 4579401 or write to Quasentra, Link Road, Model Town, Lahore, Punjab, Pakistan.

View contact options →