This policy explains what personal data Quorum collects, why, who helps us process it, and how you can have it deleted.
1. Who we are
Quorum is operated by Remo Yukoff, an individual (“we”, “us”), who is responsible for the personal data described here. You can reach us at support@usequorum.dev.
2. What we collect
Account
When you sign in with Google or GitHub we receive your email address, your name and your profile picture. Your verified email address identifies your account.
Jira connection
The URL of your Jira Cloud site, the email of the Jira account and its API token. The token is stored encrypted and is never shown back to you or sent anywhere except your own Jira site.
Test management connections
If you connect Xray, Zephyr, TestRail or Qase, the credentials that tool needs and the details that tell Quorum where to use them: for Xray, the client ID and secret of an API key and its region; for Zephyr, an API access token, its region and the Jira site it belongs to; for TestRail, the address of your TestRail site, the email of the TestRail account, its API key and the account’s name; for Qase, an API token. The credentials are stored encrypted, are never shown back to you, and are sent only to the tool they belong to.
Your work in Quorum Designer
The Jira tickets you open (summary, description, acceptance criteria, related tickets), and the sessions you create from them: test cases, questions, answers, chat messages, the test cases Quorum reads back from where they were sent, and the record of what was sent to Jira or your test management tool. For each Jira project, where its test cases go (for example the project, suite, section or folder in your test management tool).
Your work in Quorum Reporter
For each workspace: its name, its members (name, email address and role) and the invitations sent from it, including the email addresses invited and who invited them. Its test management data: projects, folders, test cases and every version of them, links between cases and Jira stories, plans, milestones, runs, results with their notes and step results, bug report drafts and the Jira bugs created from them. For each change, which member made it and when.
Billing
The status of your subscriptions (product, plan, billing period, renewal, trial and cancellation dates), their identifiers at Polar, and which products’ free trials you have used. For seats bought for a workspace: the number of seats, who holds each one (email address and account) and who held it last. Your card details and billing address are collected and kept by Polar, which sells the subscription to you as merchant of record; we never see your full card number.
Usage
For each month, how many generations, chat replies and bug drafts you ran and what they cost in AI processing, to apply the fair-use allowance.
Requests and technical data
The messages you send us (for example through “Talk to us”), and the technical logs our hosting provider keeps when you use the site, such as IP address, browser and request times.
3. How we use it
We use your data only to:
- provide Quorum: sign you in, read your Jira tickets, generate test cases and send them to the destination you chose, keep your workspaces’ test management data, draft bug reports and create the bugs you accept;
- send the invitations to a workspace that its owners ask us to send;
- run your subscription, take payments and apply the AI allowance;
- answer your requests and tell you about changes to your subscription or terms;
- keep the service secure, prevent abuse and fix problems.
We do not sell your data, we do not use it for advertising, and Quorum has no advertising or analytics trackers. We do not use your Jira or test management content to train AI models.
Where the law asks for a legal basis, we rely on the contract with you (to provide the service and billing), our legitimate interest in keeping Quorum secure and working, and legal obligations (for example, keeping invoices).
4. Who can see your data in Quorum
- Your Designer sessions and your connections to Jira and test management tools are visible only to you.
- A Reporter workspace’s test management data is visible to every member of that workspace, together with the members’ names, email addresses and roles, and who changed what. When you accept an invitation, the workspace’s members can see your name and email address.
- When a company buys seats for its workspace, its owners see who has been assigned a seat.
5. AI processing
When you generate test cases or chat with the agent, the content of the ticket you are working on, its related tickets, the test cases Quorum already created for it and your session are sent to an AI model provider through OpenRouter, only to produce your results. When you ask for a bug report draft, the failed test case, its step results, your note, the run’s environment and the linked story are sent the same way. These providers process the data under their own terms and privacy policies. Do not put information into Jira tickets or test results you work on in Quorum that you are not allowed to share with them.
6. Who processes your data
We rely on these service providers (subprocessors) to run Quorum:
- Vercel: Hosting of the application (United States).
- Neon: Database hosting (United States, AWS us-east-1).
- Polar: Reseller (merchant of record) of Quorum subscriptions: checkout, payments, invoices and taxes. For seats bought for a workspace, Polar also receives the email address and account identifier of each person given a seat.
- OpenRouter and the AI model provider it routes to: Generation of test cases, questions and chat replies from the ticket content you work on, and of bug report drafts from failed test results.
- Resend: Sending emails, such as invitations to a workspace and replies to your requests.
- Google and GitHub: Signing in, when you choose that provider.
Your Jira data stays in your Jira site (Atlassian) as well. When a project sends test cases to a test management tool (Xray, Zephyr, TestRail or Qase), the approved test cases, with the story’s key and link, are written to your account in that tool, which handles them under its own terms. Quorum only reads from these tools and writes what you approve. Our providers may process data in the United States and other countries. We will update this list when it changes.
7. Cookies and local storage
Quorum sets one essential cookie to keep you signed in (it expires after 7 days). Your browser also remembers a few preferences, such as the light or dark theme and the layout of the work screen. Polar and its payment processor set their own cookies on the checkout and billing pages to process payments and prevent fraud.
8. How long we keep it
- Account, Jira and test management connections, and sessions: while your account exists.
- Reporter data: while its workspace exists. It belongs to the workspace, so it stays there when a member leaves or stops paying.
- Disconnecting Jira or a test management tool deletes its stored token or key right away. You can also revoke it in that tool (for Jira, in your Atlassian account) at any time. Test cases already sent stay in the tool they were sent to; delete them there if you no longer want them.
- Usage records: while your account exists, to show and apply the allowance.
- Billing records and invoices: as long as tax and accounting laws require, even after your account is deleted. Polar keeps them under its own policy.
- Hosting logs: for a short period, as set by our hosting provider.
To delete your account and its data, write to support@usequorum.dev from the email address you sign in with. We delete it within 30 days, except what we must keep by law. Before we delete anything, we tell you what will happen to the workspaces you own or belong to, and we can export your Reporter data for you first. Deleting your account does not cancel a running subscription by itself: cancel it first from the billing page, or ask us to.
9. Security
Data travels over HTTPS. Jira API tokens and test management credentials are encrypted at rest. Every account sees only its own Designer data and the workspaces it is a member of, and sign-in relies on Google or GitHub. No system is perfectly secure; if we learn of a breach that affects your data, we will tell you without undue delay.
10. Your rights
You can ask us for a copy of your data, to correct it, to delete it, or to stop or limit a use of it, and you can object to how we use it. Write to support@usequorum.dev; we answer within 30 days. Depending on where you live, you may also complain to your data protection authority.
11. Children
Quorum is a tool for professionals and is not meant for anyone under 18. We do not knowingly collect data from children.
12. Changes to this policy
We will update this policy when Quorum or its providers change. The date at the top shows the latest version. If a change materially affects how we use your data, we will tell you by email or in the app before it applies. See also the Terms of Service.