vega

Terms of Service

The agreement between you and Vega: what the service does, what you are responsible for, and what we do not promise.

version 2.1effective 2026-08-19

1This agreement

These terms govern your use of Vega — the website at tryvega.tech, the connectors you install into Claude, ChatGPT, Claude Code or a code editor, the MCP server they talk to, and any public profile you publish. By creating an account or connecting a tool you accept them. If you do not accept them, do not connect Vega.

The Privacy Policy and the subprocessor list are part of this agreement.

2What Vega is

Vega captures your real AI work sessions, turns them into a private, structured record of what you have worked on, and derives a work identity from it — a map of your contexts, work moments, growth signals and coaching. If you choose to, you can publish an approved subset of that as a public profile.

Vega does four separate things with what it captures, and they are separate on purpose: it stores your work, it reads your work to answer your questions about it, it may train on content from free personal seats where the holder gave explicit permission, and it may aggregate structure across customers into a benchmark where the holder opted in. Sections 3 to 5 of the Privacy Policy set out the rules for each, and accepting these terms is not agreement to either of the last two.

Vega is not a backup service, not a transcript archive, and not a system of record. Do not rely on it as the only copy of anything.

3Pilot status, and what we do not promise

Vega is early software running a small pilot. We are stating the following plainly because a customer who discovers it later is right to be angry.

  • There is no uptime commitment and no service level agreement.
  • Capture is not guaranteed to be complete. Sessions can be missed, deferred or dropped — by a classifier outage, by a connector that is not running, by a filter judging a session personal, or by a limit on how long an unmatched capture waits before it expires. Vega does not currently show you what it lost.
  • Features can change or be removed without notice while we are at this stage.
  • Data loss is possible. Our backup and restore process has not been proven by a restore drill.
  • Some parts of the product are drawn but not built. Where a control is disabled, it does nothing. Where the security page and this document disagree with a screen in the product, this document and the security page are correct.

4Your account

  • You must be at least 18 and able to enter into a contract.
  • One person, one identity. Do not share an account or let someone else use your connector token.
  • Keep your access tokens secret. Vega stores them only as hashes and cannot recover one for you; if a token leaks, revoke it and issue a new one.
  • Keep your email address current — it is how you sign in and how we reach you.
  • You are responsible for what happens under your account.

5What you are authorising when you connect

Connecting a tool authorises Vega to receive and store material from your sessions in that tool, to send it to our providers for classification, summarising and search, and to derive a work record from it. Three properties of that arrangement deserve to be read twice.

  • Capture is automatic and silent. Vega's tools instruct the assistant to capture without asking you and without announcing it, so that the assistant does not interrupt your work. You will not see a capture happen. Only publishing to a public profile requires your approval; collection does not.
  • On a company account, your teammates see your work moments by default. There is no queue in which you approve each moment before your team sees it. They do not see your prompts or the model's replies.
  • Asking Vega a question sends your own content out again. Vega's answers are produced by a model provider, so when you ask Vega about your work it sends excerpts of your own stored prompts and replies to that provider at that moment. The answer returns to you alone. Section 13 of the Privacy Policy sets out exactly what is sent and to whom.

You can pause capture, set a lower retention level per category, exclude an individual moment from your team, mark a moment as sensitive so that nothing is stored, or disconnect a tool entirely. Pausing stops new capture; it is not retroactive, and captures already received before the pause may still be processed.

6What you put into Vega

You keep ownership of your content. Vega claims no ownership of your prompts, your sessions or anything derived from them for you.

You grant Vega the licence it needs to run the service for you: to store your content, to process it, to send it to the providers named on the subprocessor list, to derive your work record from it, and — only where you have published a profile — to display the facts you approved. That licence is limited to operating the service and ends when you delete the content or your account, except for copies already sent to a provider and copies in backups until those expire.

Using your content to train Vega's engine is a separate act with its own rules. Content from a paid seat never enters it, with or without permission. Content from a company account never enters it, with or without permission. Content from a free personal seat enters only where you gave explicit, separate permission for that specific thing, and you can take it back with one click on the screen you gave it. Your raw prompts and replies never enter it under any setting. See sections 4, 5 and 14 of the Privacy Policy.

Reading your own work back to you is not training, and neither is recomputing it. When Vega answers your questions, re-runs your work under a better set of work types, or corrects a scorer and recalculates your own results, it is operating the service for you: your data, your output, nothing changed for anyone else. That is included on every plan and needs no separate permission.

You are responsible for what you capture. You confirm that you have the right to put the content into Vega, and that doing so does not breach an obligation you owe to someone else — an employer, a client, a patient, a candidate, a counterparty, or a confidentiality or professional-secrecy duty. Vega cannot check this and does not try to.

7Company accounts

A company account is created by a person, joined by invitation or a verified email domain, and administered by that company's owner and managers.

  • Your personal Vega and a company seat are separate accounts and stay separate. Neither links to the other.
  • A company sees its members' work moments. It does not see prompts, replies, growth scores, coaching or captures.
  • Cross-person figures require at least three contributors; below that the surface shows nothing.
  • A company can set whether prompt text is visible in team memory, and members are always shown which setting is in force. Every change is written to a log any member can open, and that log is protected against edits and deletes at the database level.
  • A company administrator cannot turn capture off for a member, cannot change a member's privacy settings, and cannot see them. Every privacy control belongs to the individual.
  • If you leave, your company's work stays with the company and your personal Vega stays with you.

8Acceptable use

Do not use Vega to:

  • capture another person's sessions without their knowledge, or use someone else's connector token;
  • capture content you are not permitted to disclose to a third party;
  • attempt to reach data belonging to another account, or to defeat the account, company or three-person boundaries;
  • probe, scan or load-test the service without written permission — reporting a vulnerability in good faith under the terms on the security page is welcome and is not a breach;
  • scrape, resell or redistribute the service or another person's public profile;
  • publish a profile containing claims you know to be false, or another person's personal data;
  • break the law, or infringe someone's rights.

9Public profiles

A public profile is opt-in and every fact on it is one you approved. It is a public web page: anyone with the link can read it, and search engines and AI systems may index or cache it. Unpublishing removes it from Vega, not from someone else's cache.

You are responsible for what your profile says. Vega derives the facts from your real sessions but does not verify your claims about yourself, and we do not present a profile as a verified credential.

10The tools you connect

Claude, ChatGPT, Cursor and any other assistant you use are other companies' products, governed by their own terms and privacy policies. Vega reads from your sessions in them; it is not a party to your relationship with them, does not control them, and is not responsible for them. If one changes how it works, Vega's capture may change or stop.

11Price, and the trade

Free pays with data. Paid pays with money. Never both, never neither.

On a free seat, the deal is that your content — with your explicit, separate, revocable permission — may help improve the engine everyone uses. On a paid seat, your money is the payment: nothing of your content improves anything outside your own account, and there is no setting, no discount and no request that changes it. There is no plan on which you pay and Vega also learns from your work.

Vega is free during the pilot. There is no card at any point in sign-up and no payment integration exists, so today every seat is on the free side and the paid half of that sentence has never been exercised. If we introduce paid plans we will say so in advance and you will be able to decline and export or delete your data.

12Benchmarks

If Vega ever compares your work with other customers' work, three rules bind us: you must have opted in, only structure travels — never the words in your work, never a name — and no figure is produced from fewer than three people's contributions.

Vega computes no cross-customer benchmark today and has no control that would record your opt-in. Both will exist before the first one is computed.

13Suspension, termination and what happens to your data

You can stop at any time: pause capture, disconnect a tool, delete a moment, delete your personal Vega, or delete your identity. Deletion is irreversible.

We may suspend or close an account that breaches section 8, that we are legally required to close, or that puts the service or another person at risk. Where we can, we will tell you first and give you a chance to fix it.

If you delete your identity while you own a company account, you must transfer or delete that company first — the service will refuse otherwise, so that a company is never left without an owner. Company seats you hold are released rather than destroyed, so one person leaving cannot delete a company's work.

Deletion has limits, and they are set out in section 19 of the Privacy Policy. Read them before relying on deletion.

14No warranty

Vega is provided as it is. We do not warrant that it will be available, that capture will be complete or accurate, that a score or a coaching suggestion is correct, or that it fits any particular purpose. Everything Vega derives is a measurement of a sample of your work, not a judgement of you.

15Liability

16Changes to these terms

These terms carry a version number and an effective date, shown at the top. A change to what you agree to raises the major version and we will ask you to accept it again before you carry on using Vega. Corrections that change nothing you agreed to raise the minor version. Every published version is kept.

17Governing law and disputes

18The rest

  • If a provision is unenforceable, the rest stays in force.
  • Not enforcing a term once does not waive it.
  • You may not transfer this agreement. We may transfer it to a successor of the business, and will tell you if we do.
  • These terms, the Privacy Policy and the subprocessor list are the whole agreement between us about Vega.

Questions about these terms: help@tryvega.tech.