privacy

Tqoia Privacy Policy

How the Tqoia public website and workspace request flow handle personal data.

Get your Tqoia

1. Purpose

This policy explains personal-data handling for the Tqoia public website and public workspace request flow. Customer workspace processing may also be governed by customer agreements, data processing terms, workspace settings, and instructions from the organisation controlling that workspace.

2. Data collected on the public site

When you browse the public site, technical request data may be processed to deliver pages, protect the service, diagnose faults, and understand aggregate site operation. When you request Tqoia access, we collect the form information you provide, such as name, work email, organisation name, requested workspace slug, and the credentials or acceptance fields required by that flow.

3. Workspace data

Tqoia workspaces may contain business and personal data connected to CRM, entities, corporate records, invoices, accounting entries, bank transactions, payroll records, documents, KYC and AML cases, projects, notifications, discussions, travel records, and audit trails. The relevant customer is normally responsible for deciding what workspace data is entered and who may access it.

4. Why data is used

Personal data is used where needed to:

  • respond to workspace requests and onboarding questions;
  • create, secure, authenticate, and administer accounts and workspaces;
  • operate business workflows requested by authorised users;
  • support audit trails, security review, fraud prevention, and service reliability;
  • meet legal, regulatory, contractual, and compliance obligations where applicable.

5. Automation, imports, and integrations

A customer may configure imports, OCR, notifications, agents, AI-assisted processing, external integrations, storage, email, or messaging delivery. Those operations should be configured with least-privilege access and reviewed against the customer's own privacy and compliance obligations.

6. Sharing

Data may be shared with authorised workspace users, administrators, service providers needed to run the service, and parties required by law or security response. We do not treat workspace records as public merely because they are processed through Tqoia.

7. Retention and security

We use administrative and technical controls intended to protect data in transit, at rest where configured, and through access-control boundaries. Retention depends on the data category, customer instructions, operational backup requirements, legal obligations, and security needs.

8. Your choices

If your data is controlled by a Tqoia customer, contact that organisation first for access, correction, deletion, objection, or restriction requests. Public-site or onboarding requests can be addressed through the contact channel used for your Tqoia enquiry.

9. Updates

This policy may be updated as Tqoia features, hosting, integrations, and legal requirements change. The current public version is published on this page.