Skip to content
DQaaS
  • Ways to use
  • Capabilities
  • Docs
  • Security
  • FAQ
Sign in

Version 2026-11-02

Terms of Use

Operator: IQaaS, a trading name; a registered legal entity will be named here. Contact: [email protected]. Security reports (security issues only): [email protected]. Governing law: England and Wales. This text is not legal advice, and nothing here is a claim of compliance or certification.

1. The service

DQaaS is a data quality, profiling and catalogue service, used through a console, REST API, CLI and MCP endpoint. It is an invite-only beta for a small number of people. By signing in and accepting the current version you agree to these Terms, the Acceptable Use Policy and the Privacy Notice.

Acceptance is a click in the console. We record your account, the version and the time. No IP address is stored. Until you accept the current version, reads still work but changes through the console, your user tokens and connected MCP clients are refused. When we publish a new version you are asked again.

2. Your account

  • Sign-in is through GitHub and needs an invite. We store the GitHub profile data listed in the Privacy Notice.
  • You are responsible for activity under your account and tokens. Keep tokens private.
  • You must be at least 18 and able to form a binding contract.
  • If you act for an organisation, you confirm you may bind it.

3. Your data

  • You keep your rights in your data. You give us only the permission needed to run the service for you: load it for a job, compute and store profiles, rule results and other metadata, and delete the working copy.
  • Rows are not persisted. Metadata is, and can contain values from your data (top values, minimum and maximum, failing examples). Columns detected as sensitive have their sample values redacted, but detection is heuristic and can miss a column. See the Privacy Notice.
  • You confirm you have the right to upload or connect the data and to have it processed by us and our processors.
  • Do not upload health data, special category data or children’s data without a written agreement with us first.
  • You are responsible for connection credentials you give us. Use read-only credentials where you can.

4. Results are heuristics

Profiles, scores, sensitive-column flags, semantic types, near-duplicate matches, anomalies and lineage guesses are produced by heuristics. They are labelled inferred where that applies, and they can be wrong or miss things. Do not treat them as legal, compliance, audit or security assurance. We claim no certification and no accuracy.

5. No payments

There are no paid plans and no payments during the beta. Billing is switched off. If that changes, we will publish new terms first.

6. No SLA; resets

  • The service is provided as is. There is no uptime promise, no support commitment, and no guarantee of availability.
  • We may change, limit or end the beta. Data may be reset or deleted with 30 days notice. In an emergency we may act sooner.
  • Back up anything you need. Our backups exist for disaster recovery of the whole service, are kept 14 days, and are not a way to restore your single file or record.

7. Acceptable use and suspension

Use must follow the Acceptable Use Policy. We may withdraw invites, suspend an organisation, revoke tokens, remove members or delete an organisation. Suspension applies to a whole organisation, as the Acceptable Use Policy explains; there is no suspension of a single user.

8. Ending your account

You can delete your account (DELETE /v1/me) and your organisation (DELETE /v1/org, or DELETE /v1/orgs/{id} with the organisation name as confirmation) yourself. An organisation owner can export the organisation’s configuration and metadata first (GET /v1/orgs/{id}/export, admin or owner). When an account is closed, personal details are cleared at once, and the remaining account record is removed 30 days after closure. Encrypted backups keep deleted data for up to 14 days. Details are in the Privacy Notice.

9. Security and incidents

We use reasonable measures (encrypted volume and backups, hashed tokens, per-organisation filtering) but promise no security outcome. Tell us about issues at [email protected]. We will tell affected users of a personal data breach as the law requires.

10. Liability

Nothing in these Terms limits liability that the law does not allow to be limited, including liability for fraud, or for death or personal injury caused by negligence. The beta is free. To the extent the law permits, we are not liable for loss of data, profit or business, or for indirect loss, and our total liability to you for any claim is limited to what you have paid us, which is nothing during the beta. You are responsible for backing up your own data and for what you upload.

11. Changes

We may update these Terms. For material changes we will give notice by email or in the console, and ask you to accept the new version. Continued use after the notice means you accept it.

12. Governing law

The law of England and Wales applies, and the courts of England and Wales have jurisdiction. If you are a consumer outside England and Wales, mandatory rules of your own country that cannot be waived still apply to you.

Terms of Use | Acceptable Use | Privacy | Back to home

DQaaS · [email protected]

  • Sign in
  • Docs
  • Security
  • Terms
  • Acceptable use
  • Privacy
  • llms.txt
  • Sitemap