Privacy Policy

In short

• We store your email address and name so that you can sign in and your colleagues can tell who did what.
• We store work data: tasks, comments, documents, and files you upload yourself.
• We do NOT receive the contents of your repository files. The agent program on your machine sends us only file names, paths, and commands. That is how it is built, not a promise about how it behaves.
• We do not sell data, do not share it with advertising networks, and do not train models on it.
• You can delete your account; the data tied to it goes with it.

Who processes the data

Quiel is operated by its owner, trading as Quiel (“we”). You can reach us at [email protected].

The platform runs on servers rented from Contabo GmbH, physically located in the European Union (France). Backups are kept in Cloudflare R2 object storage.

What data we receive, and from where

Account data. Your email address, your name, and an avatar if there is one. The source is however you signed in: GitHub, Google, or a link sent to your email. The email address serves as an identifier: it is what a colleague uses to invite you to an organization.

Sign-in data. Access tokens from your provider (GitHub, Google) and a session identifier in a cookie. Tokens are stored so that signing in keeps working. We store no passwords: Quiel has no password sign-in.

Work data. Organizations, projects, tasks and their descriptions, questions and answers, documents, comments, and files you attach to a task or a question yourself.

Agent data. When you connect your agent program to a project, we receive the machine name you gave it, the operating system, the program version, and the working directory.

Action log. The names and arguments of commands an agent is about to run, and your decisions to allow or deny them. Arguments are truncated and values that look like passwords or keys are masked. This log exists so that you stay in control of your agent, and it is visible only to members of your organization.

Integration data. If you connect Slack, Telegram, or GitHub, we store the identifiers needed to deliver a notification to you: your Slack user id, your Telegram chat id, the GitHub app installation number. If you allow browser notifications, we store the push subscription endpoint and the keys that encrypt it.

Technical records. Requests to the server along with an IP address, browser version, and timestamp, as with any web service. They are used to investigate failures and to prevent abuse.

What we do not receive

We do not receive the contents of your project files. The agent program running on your machine passes the platform file names, paths, and commands, and nothing of what is inside the files.

This is not a promise to be careful; it is a property of how the program is built. There is no code in it that reads file contents and sends them to us. Its source is distributed through npm and can be inspected.

The exception is what you attach yourself: a file you add to a task through the browser is of course stored, because otherwise it could not be opened.

Why we use this data

The data is not used for advertising, is not shared with advertising networks, and is not used as training material for machine learning models, neither ours nor anyone else's.

• So that you can sign in and stay signed in between visits.
• So that colleagues can see who created a task, who completed it, and who approved a dangerous command.
• So that a notification reaches you the way you chose: by email, in Telegram, in Slack, or as a browser notification.
• So that the platform works: hands tasks to agents, opens pull requests, shows the state of checks.
• So that we can investigate failures and abuse.

Data from your Google Account

When you sign in with Google we request only three basic scopes: openid, email, and profile. That gives us your Google identifier, your email address and whether it is verified, your name, and a link to your avatar. We neither request nor receive access to your mail, drive, calendar, or contacts.

This data is used for exactly one thing: to create or find your Quiel account and show colleagues who you are. If the address matches an existing account and Google has confirmed the address is yours, you are signed into that account. Otherwise one person would end up with two separate records.

Our use of data received through Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. We do not transfer this data to third parties except as described below, do not use it for advertising, and do not train models on it.

You can revoke access at any time at myaccount.google.com/permissions. After revoking, signing in with Google stops working, while your Quiel account and its data remain.

Who we share data with

We do not sell data and do not hand it to third parties for their own purposes. Sharing happens in two cases only.

The first is the contractors the service cannot run without: hosting (Contabo GmbH), backup object storage (Cloudflare LLC), and the mail server that sends our email. They process data on our instructions and may not use it otherwise.

The second is services you connect yourself. By connecting Slack you agree that task titles and events will be posted to the channel you chose; by connecting Telegram, that notifications will arrive in your chat; by connecting GitHub, that the platform will open pull requests on your behalf. Each connection is made explicitly by you and can be removed at any time.

We will disclose data on a lawful demand from a public authority where we are required to.

How long we keep data

Account data and work data are kept for as long as your account and the organization you belong to exist.

Backups of the database and files are kept in encrypted storage and are overwritten as newer ones accumulate; data deleted from the platform disappears from backups as they rotate.

Technical request records are kept for a limited time and are used only to investigate failures.

How to delete your data

To delete your account and the data tied to it, write to [email protected] from the address you sign in with. We will delete the record and confirm it in reply.

Some data you can remove yourself: unlink GitHub, Google, or Slack in your profile, turn off notifications, delete a task or a document.

Data belonging to an organization you do not own is deleted by its owner: we will remove your account, but tasks you created inside someone else's organization remain part of it. Otherwise deleting one person would tear apart a team's work.

Your rights

You have the right to learn what data of yours we hold, to receive a copy of it, and to ask for corrections or deletion. Write to [email protected]; we respond within a reasonable time, normally within thirty days.

If you are in the European Union, you keep the rights granted by the GDPR, including the right to complain to the supervisory authority in your country.

Cookies

We use cookies only to keep you signed in as you move between pages and to remember the interface language you picked. There are no third-party advertising or analytics cookies on the platform.

Security

Connections to the platform are protected with TLS. Integration tokens are stored encrypted in the database. Server access is restricted by keys, and backups are encrypted.

Absolute protection does not exist, and promising it would be dishonest. If we learn of a breach affecting you, we will tell you.

Changes to this document

We may change this policy, for example when a new integration appears. The version date is shown at the top of this page. We will notify you by the email address on your account about material changes.