Privacy policy
Last updated: 9 November 2026
Who we are
Cadence Venture Management Systems LLC, a limited liability company formed in Delaware, United States, is responsible for the personal data described here. We have no establishment in the European Union or the United Kingdom. You can contact us about privacy at privacy@cadencevms.com.
This website and the early-access list
When you request early access on this website we collect your email address and the time of your request. After you sign up you can also choose to tell us more. Every one of these answers is optional:
- your role and the size of your leadership team
- how you manage leadership priorities and accountabilities today
- a few words on why you want early access
- whether you would like an in-person demo, and the city and country for it
- whether you would like to receive occasional product updates
This website does not set cookies. Our hosting provider may process technical data, such as IP addresses, to deliver the site and protect it from abuse. See our cookie policy.
| What we do | Why | Lawful basis | How long we keep it |
|---|---|---|---|
| Keep your email on the early-access list, send you a confirmation and tell you when access opens | To manage your request for early access | Steps you ask us to take before you sign up | Until you ask us to remove you |
| Keep your optional answers | To understand who Cadence VMS is for and to arrange demos you ask for | Your consent, which you give by choosing to answer | Until you ask us to remove them |
| Send you occasional product updates | Only if you tick the box asking for them | Your consent | Until you unsubscribe or withdraw consent |
Emails we send
- A confirmation email when you request early access.
- An email when access opens.
- Product updates, only if you asked for them.
Every email has an unsubscribe link. Once you unsubscribe, we do not email you again from this list. You can also withdraw your consent to product updates at any time by contacting us.
Who we share it with
We use service providers to run the early-access list. They process your data on our behalf.
- Railway, to host this website and store the list.
- Google, through Google Sheets, where we keep a copy of the list.
- Resend, to send our emails.
The Cadence VMS application
The rest of this policy describes the Cadence VMS application, which is currently invite-only.
What we collect, why, and for how long
| Data | Purpose | Lawful basis | Retention |
|---|---|---|---|
| Your name, your username, and the email you use for each organization | To sign you in, to identify you to your organization, and to send invitations, password resets and alert emails | Contract | Until you delete your account. If an organization closes, its data is removed 90 days later |
| Records that name you, such as objectives, initiatives, projects, matters, tasks, targets, reports and meeting attendance | To run the organization's operating rhythm | Contract | While the organization's account is active. If you delete your account, they show "Former member" instead of your name |
| Sign-in records and links | To keep you signed in, and to make invitation, reset and confirmation links work once | Contract | Sign-in records for 30 days. Links for 30 days after they are used or expire |
| A log of the alert emails we sent you | To avoid sending the same alert twice | Legitimate interests | 400 days |
| Post-meeting survey answers | Measuring whether Cadence VMS is helping meetings and saving attendees time | Legitimate interests | While the organization's account is active. They stay in aggregate figures with nothing linking them to you, including after you delete your account |
| Meeting agendas, talking points, notes and the record kept when a meeting ends | To plan, run and follow up the meeting | Contract | While the organization's account is active. Only the people invited to the meeting and its owner see them |
| Items in your own list (matters and tasks only you can see) | To let you keep track of your own work | Contract | Until you delete them, or your account. They are deleted with your account |
| Events and thinking time you add to your own calendar on Up next: the title, date, start and end time, room or video link, and notes | To let you plan your day around your Cadence VMS meetings | Contract | Until you delete them, or your account. Only you can see them. They are in your data download and deleted with your account |
| Agenda templates you make | To let your organization reuse them. Your name is shown to your organization as the template's maker | Contract | Until the template is removed |
| Agenda templates you share with the community, and the name you choose to show with them | To let other Cadence VMS users copy them | Your consent, which you give by choosing to share and to be named | Until the template is withdrawn. If you delete your account, it stays public without your name or organization |
| API keys: each key's name, its first characters and a fingerprint (never the key itself), the admin who created it, its units and its expiry date | To let an organization connect other systems, and to show its admins which keys exist | Contract | While the organization's account is active, so its figures can still show which key sent them. A revoked or expired key stops working straight away |
| A record of each call made with a key: when, which key, the result and how many figures it carried | To show organization admins how their keys are used, and to keep the service secure | Legitimate interests | 90 days on the API page. The activity record keeps each call for 400 days |
| A record of what is done in each organization: for each change, sign-in, export, call made with an API key and use by Cadence's operations, who did it (or which key), when, through what (the application, an API key or Cadence's operations), the kind of thing and its number, the names of the fields changed but never what was typed, whether it was allowed or refused, and the network it came from (the first three parts of the address, never the full address). For reading, how many things of each kind each person read each day | To keep the service and the organization's data secure, and to look into misuse | Legitimate interests | 400 days. If you delete your account, it shows "Former member" instead of your name |
| Figures sent with a key | To report the organization's figures, as with figures people enter | Contract | While the organization's account is active. Figures held in a history sync that is not reviewed are deleted after 7 days |
| Business records from the organization's accounting, CRM and other systems, uploaded as a report (such as a QuickBooks General Ledger) or sent with a key: for each record its date, account or stage, type, the other account it moved to or from, its amount, and a code in place of the customer's or supplier's name | To calculate the organization's figures, and to work out figures for metrics the organization adds later, back to the date its history starts | Contract | While the organization's account is active, and included in the organization's export. If the organization is deleted, they are removed 90 days later |
| Records from the organization's GitHub repositories: for each pull request merged into the branch the organization counts, its number, repository, branch, the dates it was opened, first committed and merged, whether someone other than its author reviewed or merged it, its kind (revert, hotfix or fix), any Linear issue keys in it and the identifier of its merge commit, with its author replaced by a code; for each deploy, its repository, environment or workflow, result and dates, and for each production deploy the identifiers of the commits it contains, to work out how long changes take to reach production | To count the organization's software delivery figures, such as production deploys and change failure rate, and to work out figures for metrics it adds later | Contract | While the organization's account is active, and included in the organization's export. If the organization is deleted, they are deleted at once |
| Records from the organization's Linear workspace, for the teams its admins choose to read: for each issue, its key and number, team, status and each change of status, labels, estimate, cycle, priority, project, project milestone, parent issue, due date, the dates it was created, triaged, started, completed or canceled, its SLA dates, and the issues marked as blocking it with when each link was made, with the people who created and were assigned it replaced by codes; each change of its status, team, priority, estimate, labels, cycle, project or due date, with who made the change replaced by a code; each team's statuses, labels, cycles and number of members; for each project of those teams, its name, link, status, dates and whether each is a day, month, quarter, half or year, teams and initiatives, the names and planned dates of its milestones, with its lead replaced by a code, and each change of its status or target date, dated by Linear; the health (on track, at risk or off track) and date of each update posted on those projects and their initiatives, never the update's text; the names and target dates of the workspace's initiatives; where the organization uses Linear's releases, the name, link and completion date of each release its issues are in; and, where the workspace uses customer requests, which issue or project each request is linked to and when, with the customer replaced by a code | To count the organization's cycle, flow, handoff, quality, acceptance, incident and project figures, to move work between its teams as its admins set up, and to work out figures for metrics it adds later | Contract | While the organization's account is active, and included in the organization's export. If the organization is deleted, they are deleted at once |
| Records from the organization's Railway projects, for the projects its admins share and the environments and services they count as production: for each deploy, its project, environment, service, status, the reason Railway gives for it (a deploy, a redeploy or a rollback), the identifier of its commit, and the times it started, went live and finished or crashed, with whoever triggered it replaced by a code; and each shared project's environment and service names | To count the organization's production deploys, failed deploys, rollbacks and crashes, to confirm which GitHub deploys went live, and to work out figures for metrics it adds later | Contract | While the organization's account is active, and included in the organization's export. If the organization is deleted, they are deleted at once |
| Meeting audio, video, and transcript | Live extraction of discussed items during the meeting, generating the end-of-meeting recap, and letting people verify what was said | Contract | While the organization's account is active |
Who in your organization sees what
A meeting, and everything in it, is visible only to the people invited to it and to its owner. Organization admins do not see meetings they are not invited to. Events and thinking time you add to your own calendar on Up next are visible only to you: nobody else in your organization sees them, organization admins included. The Executive team has its own page, like any business unit: it opens for the people on the Executive team and for people who can see the whole organization. Being on the Executive team does not change what else they can see or change. Matters and tasks live in a list: one meeting, a meeting series, a business unit's list, or your own list. Only the people in that list see them, plus the people Responsible and Accountable for each item. When an objective, initiative or project goes At Risk or Off Track, Cadence VMS raises a matter about it in its unit's list; the people Responsible and Accountable for that item also see that matter. Notes added to a matter show who wrote them and when. When a business unit sits under another, the parent unit's people also see the sub-unit's lists, and the parent's admins act as the sub-unit's admins. Someone in a list can move or copy an item to another list they belong to, which shares it with that list's people. Health readings can count a unit's shared list, but without its titles or the names in it.
Community templates
If you share an agenda template with the community, only the template is shared: its name, description, parts, minutes and prompts. Nothing from your meetings is shared. An admin of your organization approves it first, and then a Cadence reviewer checks it before it is public. It shows your name, your organization's name, both or neither, as you choose. It is anonymous unless you choose otherwise. Our terms set out the licence that applies.
How your email is used across organizations
You have one username and one password for every organization you belong to. Each organization knows you by the email it invited you with, or one you confirmed for it, and sees only that email and its own data. An organization does not see your other emails, or anything about your other organizations. Your username may be visible to other people.
API keys
An organization's admins can create keys that let other systems, such as Make, Zapier or the organization's own software, send business records and figures to Cadence VMS. A key can only send records and figures and read the list of inputs and reporting cycles. It cannot read figures, people, meetings, matters or tasks. The services an organization connects are chosen by the organization, and what they receive from its other systems is between the organization and that service.
Business records
Cadence VMS calculates an organization's figures from the records behind them, such as ledger lines, deals and issues, rather than from totals worked out elsewhere. It keeps those records so it can also work out figures for metrics the organization adds later.
It keeps only what the calculations need: the date, the account or stage, the type, the other account involved, and the amount. Descriptions and notes are not kept. Customer and supplier names are replaced with a code that is the same each time for the same name, so Cadence VMS can tell, for example, how much revenue came from the ten largest customers without keeping who they are. For an uploaded report, the names are replaced in your browser before anything is sent. For records sent with a key, they are replaced as the records arrive, before anything is stored. Account names, such as "Checking" or "Advertising", are kept so the organization's admins can match them.
The records stay while the organization's account is active, and the organization's admins can download them from Exports. If the organization is deleted, they can no longer be seen or used, and they are removed with the rest of its data 90 days later. Deleted data can remain in our backups until they expire.
Some of these records may relate to individuals, for example a customer who is a person. The organization decides what its systems send and is responsible for having a lawful basis to share it with us.
GitHub
An organization's Technology or organization admins may connect GitHub by installing the Cadence VMS app on the organization's GitHub account and choosing which repositories it can see. GitHub decides who may install it. The app only reads; it never changes anything on GitHub. GitHub's install screen says the app gets read access to code: that is GitHub's name for the Contents permission, which Cadence VMS needs to list each repository's branches, releases and the commits each production deploy contains. Commit lists arrive with each commit's message and author: Cadence VMS keeps only the commit's identifier and drops the rest at once. It never opens files, diffs or code, and never keeps commit messages, descriptions or comments.
Cadence VMS reads pull request titles and branch names when they arrive, only to tell whether a pull request is a revert, a hotfix or a fix, and to find Linear issue keys. It keeps what it found and drops the text. People are kept as codes, never by name or username, and Cadence VMS never scores or ranks people.
GitHub also sends the app a message when a pull request, review, push, deploy, deploy status, workflow run, release or repository changes in the repositories it can see. Cadence VMS checks that each message comes from GitHub and uses it only to read again; it drops the message's content as it arrives.
To read, Cadence VMS uses short-lived tokens that GitHub issues to the app. They are not stored. When someone connects GitHub, Cadence VMS asks them to authorize the app once, to check that the installation is one their GitHub account can see, and then cancels that authorization straight away. An admin can disconnect at any time on the GitHub page in Integrations; the records already kept stay until the organization is deleted. Removing the app from GitHub is done on GitHub. GitHub's own handling of repository data is covered by GitHub's privacy statement.
Linear
An organization's Technology or organization admins may connect Linear. A Linear workspace admin approves the Cadence VMS app on Linear and chooses which teams it can access. The admins then choose, team by team, which teams Cadence VMS reads and the business unit each one matches to. Teams left on "Don't read" are never read.
Cadence VMS reads once a day, and when an admin chooses Read now. Linear also sends Cadence VMS a short message whenever an issue, label, cycle, project, project or initiative update, customer request, user or team permission changes in the workspace. Cadence VMS checks that each message comes from Linear and was sent in the last minute, then reads again only what changed. These messages include the issue's title and description: Cadence VMS uses only the identifiers and times in them and drops the rest as they arrive. Every 15 minutes it also checks for changes, in case a message did not arrive. Where the setup has been applied, a nightly pass runs at 23:30 in each team's time zone.
Cadence VMS never asks Linear for issue titles, descriptions or comments, or for the text of project and initiative updates, and never keeps them, with one exception: when a tester sets a QA or UAT round to failed, needs debugging or needs refining, Cadence VMS reads the tester's write-up in that round once and copies it into the card it creates for the fix, without keeping it. It keeps the names of projects and of their milestones, to show them on the Linear page, and the names and target dates of the workspace's initiatives, to suggest which Cadence VMS initiative each one is. To check the setup, it also reads whether initiatives and customer requests are turned on in the workspace and how often Linear reminds project leads to post an update. To recommend a setup, it also reads the workspace's plan and how many issues and projects it has. People and customers are kept as codes, never by name or email, and Cadence VMS never scores or ranks people.
Linear's approval screen says the app can read and write, see initiatives and customers, and change initiatives. Linear only offers writing as one permission that covers everything. Cadence VMS uses it only for what an organization's admins turn on and confirm in Cadence VMS:
- in the Linear setup, creating the teams the setup suggests that they confirm, adding the labels, statuses and issue templates they review and apply, turning on Triage, renaming the teams, statuses and labels they choose, setting the cycles, time zone and estimates of teams they choose, and moving those teams' cycles to match, setting how pull requests move those teams' issues and how their boards show cards; turning on the workspace's initiatives, customer requests and SLAs, where they choose to; setting how often Linear reminds project leads to post an update; adding the standard milestones, without dates, to projects that lack them; and linking the Linear projects and initiatives they match to the plan, putting those projects in the initiative they choose;
- when an admin re-applies the setup on the Linear page, making again only the changes they tick, and merging a status or label into the one that means the same, only when they tick it and, if any issue uses it, type MERGE to confirm: the issues in a merged status are moved to the other status and the merged status is archived; the issues with a merged label are given the other label first, and the merged label is deleted only if every one of them got it;
- handing work between teams: when a Feature reaches a stage, Cadence VMS creates the next team's card under it (for example "Design: PRD-142", "Build: PRD-142", a QA or UAT round, a fix card after a failed round, or a release card), with a title and description Cadence VMS writes, its Type and board labels, and where it applies a cycle and the person who asked for the change;
- moving cards: placing a Feature at the stage its open work is at, and putting it back if it is moved by hand; moving a card to Done when its QA round passes; completing a release card once its code is live in production; and cancelling the open cards under a Feature someone cancels;
- in the nightly pass, moving an issue that has an estimate from Backlog to Ready, moving an issue to the right team's Triage by its Type, and, where the organization uses Cadence VMS's due dates instead of Linear's SLAs, setting the due date of defects and incidents from their priority. A due date someone has moved by hand is kept. When the executive the organization chose reverses a lowered Urgent priority, Cadence VMS sets it back to Urgent;
- adding comments that Cadence VMS writes, such as that a card waits for the cards blocking it, that a QA round is on hold, or which release a Feature went out in;
- where the organization uses Linear's releases, adding build cards to the next planned release and turning on release notes for the pipeline its admins choose;
- planning: when someone creates a project in Cadence VMS for a unit that uses Linear, creating it in Linear with its lead team, dates and milestones; changing a project's name, dates and milestones when they are changed in Cadence VMS; putting a project in the initiative chosen for it in Cadence VMS, and taking it out of another one Cadence VMS keeps in step; and, once one of an initiative's projects is in Linear, creating or matching that initiative in Linear and keeping its name, target date, status and description in step, and posting its health as an initiative update that Cadence VMS writes;
- in the nightly pass, and when it creates a card, putting cards under a Feature into the milestone for their stage, such as Designs complete for design cards. A card someone has put in another milestone is left where it is.
Admins can turn the handoffs, and each nightly change, off on the Linear page. Cadence VMS never deletes or merges anything in Linear, except a project milestone someone removes in Cadence VMS, a project's place in an initiative when its initiative is changed in Cadence VMS, and a status or label an admin merges as described above, and never changes the title, description, comments, estimate, labels or customers of issues people create, except the status and label of issues in a merge an admin confirms. Every change is listed on the Linear page with why it was made, and shows in Linear as made by Cadence VMS. Cadence VMS creates only the teams an admin confirms in the setup; where Linear doesn't let it, the admin creates the team in Linear and gives Cadence VMS access to it. If Cadence VMS loses access to a team it reads, it tells the organization's Technology admins.
Cadence VMS keeps who made each change to an issue, as a code, to check that work handed from Product to Technology was approved, to tell the right person when something they did needs a follow-up, and to notice when an Urgent priority set by Customer Support is lowered. Each person may link their own Linear account from their profile in Cadence VMS: Linear asks them to sign in and approve, Cadence VMS reads only which Linear user they are, keeps it as a code, and gives up the access straight away. Only the person can link or unlink their account.
The figures Cadence VMS works out from these records can be overridden by the people who may enter the unit's figures. An override keeps both figures, with the name of the person who made it and the note they wrote, and shows wherever the figure does.
Cadence VMS keeps the access Linear gives it encrypted, and renews it every day. An admin can disconnect at any time on the Linear page in Integrations: Cadence VMS gives up its access straight away, and the records already kept stay until the organization is deleted. A Linear admin can also remove the app in Linear's settings, and Linear then tells Cadence VMS. Linear's own handling of workspace data is covered by Linear's privacy policy.
Railway
An organization's Technology or organization admins may connect Railway. They sign in with Login with Railway and choose which of their Railway projects to share. Cadence VMS asks Railway only for viewer access to those projects, with the person's name and email to show who connected it. Railway's viewers have read-only access: they cannot see environment variables or make deploys, so Cadence VMS cannot change anything in Railway. The admins then tick, project by project, the production environment and the services that count. Nothing is counted until they do.
Cadence VMS reads once a day, and when an admin chooses Read now. Every 15 minutes it also checks the latest deploys of the production services, so a crash is not missed before Railway relabels it. It never asks for environment variables, logs or build output. Railway sends each deploy's commit message and commit author along with the deploy; Cadence VMS drops them as they arrive and never keeps them. Whoever triggered a deploy is kept as a code, never by name or email, and Cadence VMS never scores or ranks people.
Where an admin adds Cadence VMS's address to a Railway project's webhooks, Railway also sends a message when a deploy's status changes. Cadence VMS uses it only to read that project's deploys again, and drops the message's content, including any commit message, as it arrives.
Cadence VMS keeps the access Railway gives it encrypted, and renews it every hour. An admin can disconnect at any time on the Railway page in Integrations: Cadence VMS forgets its access straight away, and the records already kept stay until the organization is deleted. Railway does not offer a way for an app to give up its access, so to remove the app from Railway too, the person who connected it opens Account Settings, then Apps, in Railway, chooses Cadence and then Revoke Access. The same page lets them add or remove the projects they share. Railway's own handling of project data is covered by Railway's privacy policy.
Our legitimate interests
We rely on legitimate interests for four things. One is the post-meeting survey: measuring whether Cadence VMS is helping meetings and saving time, which is how we measure the effectiveness of our own product rather than running your account. Answering the survey is always optional. Another is the log of alert emails, which exists only to avoid sending you the same email twice. The third is the record of calls made with API keys, which lets organization admins see how their keys are used and helps us keep the service secure. The fourth is the activity record, which helps us keep the service and each organization's data secure and look into misuse. It is not shown in the application; we use it only to look into a security problem, and Download my data gives you your own lines.
Alert emails
We send you a daily digest of the items that need your attention, and an immediate email for a P1 matter or a past-due item of yours. You can change the time and days of the digest, or turn either kind off, under Account in the application. Every alert email also has a link that turns them off.
Who we share it with
We use providers to run the application. They process your data on our behalf.
- Railway, to host the application and store its data.
- Resend, to send invitation, password reset and alert emails.
- Other Cadence VMS users, who see community templates you choose to share, with the name you choose to show.
- Cadence reviewers, who are our own staff, see templates waiting to be published.
- Perplexity, which provides the AI engineering assistant and workspace in which we test changes on copies of the data.
- Anthropic, when someone uses the metric assistant. It receives the question that was asked, the organization's name and description, and the names of its metrics.
The AI meeting assistant is not available yet. When it is, meeting audio, video, and transcript will be shared with third-party providers that capture and transcribe meetings and generate suggestions and recaps. We require these providers not to train their own models on this data.
Copies to test changes
Before we release a change that alters how data is stored, we test it on a copy of the application's data, so that nothing is lost or shown to the wrong person. The copy includes every organization's records and the accounts database. Only we can make one, each copy is recorded, and we delete it once the test is done, usually within a few days. The testing runs in a secure workspace provided by Perplexity, whose AI engineering assistant we use to build and test Cadence VMS. Perplexity processes the copy on our behalf.
Where your data goes
Because we are a company based in the United States, we may access and process your data in the United States, and our providers may process it in other countries. When personal data leaves the UK or the EEA, we rely on the safeguards our providers offer under their data processing terms: the European Commission's standard contractual clauses, with the UK addendum where needed, or the EU-US Data Privacy Framework.
Automated decisions
Once the AI meeting assistant is available, it will listen during your meetings and suggest new Matters, Tasks, Projects, or Initiatives based on what was discussed. It never creates these directly: a suggestion only becomes real once a person with permission to create that type of item approves it. If the assistant gets something wrong, the suggestion is simply not approved, so it never takes effect. The assistant will also generate a written recap of each meeting.
Cookies and analytics
The application sets one essential cookie, which keeps you signed in for up to 30 days. It has no advertising or tracking cookies, and it does not use analytics today. If we add anything optional, we will ask you first, before it runs, with the choices Allow all, Only necessary and Custom, and you can change your mind under Account. The details are in our cookie policy.
Whether you have to give us your data
Your username and email are required to sign in and use Cadence VMS. Meeting audio and video will only be captured if the AI meeting assistant is active for that meeting. It will be on by default, and the person running the meeting can turn it off. Answering the post-meeting survey is always optional.
Your rights
You can ask for access to your data, to correct it, to erase it, to restrict or object to how we use it, and to receive it in a portable format. Where we rely on your consent, you can withdraw it at any time.
Signed-in users can do most of this themselves under Account, then Privacy:
- Download my data gives you a summary and a file of what we hold about you in your organizations.
- Correct my details changes your name and username. Your name updates on everything that names you.
- Delete my account erases your name, username and emails, and deletes the items in your own list and the events on your own calendar. Templates you shared with the community stay public without your name or organization. What you did stays in each organization's history, shown as "Former member", and your survey answers stay in aggregate figures with nothing linking them to you. If you are the only owner of an organization, you first hand it over to someone else or delete it. Deleted data can remain in our backups until they expire.
For anything else, or if you cannot sign in, write to privacy@cadencevms.com. We answer within one month. You can complain to the data protection authority in the country where you live or work, or where you believe a problem occurred.
Children
Cadence VMS is not aimed at or expected to be used by anyone under 16.
Changes to this policy
When we change this policy we update the date at the top of this page. If a change matters to how we use your data in the application, we also tell application users by email.