Privacy Policy
The short version
- We collect what the Service needs to run: your account, your workspaces, and how you sign in.
- Passwords are stored only as one-way hashes, and each workspace is isolated from every other by the database itself.
- We never sell your information. Card payments are handled by our payment processor, not by us.
- We set one cookie, to keep you signed in. No advertising, analytics or third-party cookies.
- You can ask to see, correct, export or delete your information: email us.
1. Who we are
QuxPulse is operated by DevQux, of [Registered address], which is responsible for the personal information described here. Contact us about privacy at [Legal and privacy contact email].
This policy covers the information we decide how to use. Your Content (what you and your members put into a workspace) is processed on the workspace owner's instructions, under our Terms.
2. What we collect, and why
| What | Details | Why |
|---|---|---|
| Account | Your email address, and your password stored only as a salted, peppered one-way hash (argon2id), never readable, even by us. If you sign in through a single sign-on provider, the identity it confirms for you. | To give you an account and sign you in. |
| Sign-in and security | For each signed-in session: when it started and was last used, and the IP address and browser description it came from. A log of security events (sign-ins, failed attempts, password changes and similar) with the same details. | To keep your account secure, let you see and end your sessions, and investigate abuse. |
| Workspaces | The workspaces you create or join, your role in each, and invitations you send or receive. | To run the Service and decide who may see what. |
| Workspace activity | A record of changes made in a workspace (roster, access, invitations, integrations, settings, single sign-on, exports and desktop sign-ins): who made each, when, what it changed and whether it worked, with the first half of the IP address for desktop sign-ins. Readable by that workspace's owners and admins. | To let a workspace see and audit who changed what, and to investigate problems. |
| Your Content | What you and your members put into a workspace: the roster, stand-ups, requests, requirement changes and reports, the delivery data synced from the tools you connect (such as Linear and GitHub), and what the desktop companion sends (mail that matches your rules, meeting transcripts and notes, pull request review decisions). | To provide the Service to that workspace. |
| Connected tools | The credentials you give us to read your tools on the workspace's behalf, sealed (encrypted) before they are stored and never shown again. The desktop companion's sign-in token is kept in your Mac's keychain. | To sync delivery data you asked us to sync. |
| Billing | The workspace's plan, subscription status, usage measured against the plan, and invoices. Card details are collected and held by our payment processor; we do not receive your full card number. | To charge for paid plans and enforce plan limits. |
| The assistant and summaries | When you use the assistant, your messages and the workspace data it reads to answer are sent to our AI model provider to generate the reply; meeting text the desktop sends is summarised the same way. We keep how much each reply used, not the conversation. | To answer you, summarise meetings, and measure use against your plan. |
We do not ask for, and ask you not to send, sensitive information such as government ID numbers or health information.
4. How we use information
- to run the Service: accounts, workspaces, the assistant and billing;
- to keep the Service and your account secure, and to prevent fraud and abuse;
- to send service emails, such as confirming your address, resetting your password and security notices;
- to charge for paid plans and keep accurate financial records;
- to understand and improve the Service; and
- to comply with the law and enforce our Terms.
6. How long we keep it
- Account information: while your account is open, then deleted when you ask us to delete it, except what the law or our records require us to keep.
- Sessions: until they expire or you end them. Security events: as long as needed to protect accounts.
- Your Content: while the workspace exists; a workspace's owner can ask us to delete it.
- Billing records: as long as tax and accounting law requires.
7. Your choices and rights
You can see and end your active sessions in your account settings. You can also ask us, at [Legal and privacy contact email], to:
- give you a copy of the personal information we hold about you;
- correct it;
- delete your account and personal information (we may keep what the law or our records require); or
- object to or restrict a use of it.
We will verify the request comes from you and respond within the time the law requires. Depending on where you live, you may have further rights, including to complain to a data protection authority. We will not treat you differently for exercising them.
8. How we protect it
Passwords are stored only as one-way hashes; connections are encrypted in transit; and each workspace's data is isolated from every other workspace's by the database itself, not just by our code. No system is perfectly secure, and we will tell you as the law requires if a breach affects your information.
9. Where it is stored
Our systems are hosted in [Hosting region]. If you use the Service from elsewhere, your information is transferred there, with the safeguards the law requires.
10. Children
The Service is not directed to children. You must be at least 18 to have an account. If you believe a child has given us personal information, contact us and we will delete it.
11. Changes to this policy
We will update this policy when what we collect or how we use it changes, and change the version and date at the top. For a material change we will give notice by email or in the Service before it takes effect.
12. Contact
Privacy questions and requests: [Legal and privacy contact email]. Post: DevQux, [Registered address].