Privacy Policy

Last updated: November 3, 2026

1. What Vesta is

Vesta is a Multi-Criteria Decision Analysis (MCDA) tool. It helps you structure and compare alternatives across multiple criteria using AHP and structured pairwise comparisons. Your projects are stored in your account so you can access them from any device.

2. Data we collect

Account information: your name, email address, and profile picture, provided by your Google account when you sign in via Google OAuth.
Project data: the criteria, alternatives, weights, comparisons, and any other content you create inside Vesta.
Collaborator addresses: the email address of each person you invite to a project, so that the invitation can reach them and they can join.
Change history: each change made to a project, with who made it and when, so that everyone on the project can see how the decision was reached.
Results reached: the date a project's ranking was first viewed after an edit. It is kept per project, never per person, and tells us whether projects get as far as a result.
Terms acceptance: which version of the Terms of Service you accepted, and when.
Project notifications: records of project activity that needs your attention, when the notification was created, and whether you have read it or the work has been completed. These records are linked to your account so that your inbox and read state agree across devices. We also retain your email preferences, delivery and suppression status, and the next eligible reminder time. These let us respect opt-outs, avoid duplicates and limit project emails to one per rolling seven days. We also remember when you dismiss the project email notice so it stays dismissed across your devices. Dismissing that notice does not change your email preferences or record consent to receive emails.
Usage analytics: product usage events (e.g. which features you use, how often you interact with the app) collected via PostHog. Your IP address is discarded before storage, and no names or email addresses are included. Events are associated with your account identifier (a random string, not your name or address, but still data that relates to you) so that repeat visits from one person are not counted as many. Analytics are necessary for us to understand how the product is used and to improve it.
Server usage measurements: MCP tool names, success or failure, handler duration, the client family reported by your MCP client, and the date, account identifier and project identifier for saved model changes. We use these to understand MCP adoption and compare model editing through MCP and the web app. These observations are stored with Cloudflare and cleared after 100 days by scheduled cleanup. They contain no tool arguments, project content, names, email addresses, IP addresses or credentials. Authorized administrators see aggregate usage figures. Deleting your account removes its observations.

3. How we use your data

To authenticate you and associate projects with your account.
To store and retrieve your projects across sessions and devices.
To show project notifications appropriate to your current access and keep their read state in sync.
To send project activity emails according to your preferences, combining eligible updates into at most one email per rolling seven days.
To understand how the product is used and guide product improvements (analytics only).

We do not sell your data or use it for advertising.

For optional project activity emails, we rely on our legitimate interest in helping you follow work that needs your attention and decisions in projects you participate in. These messages contain no advertising. You can object at any time by turning off the relevant switches in Profile → Project emails, or stop all project emails using the unsubscribe link in each message. Those choices do not stop account or security messages needed to provide the service. Accepting the Terms or dismissing a notice is not consent to marketing emails.

If solo reminders are enabled, the separate “Reminders for my own projects” preference controls them. They concern an unfinished step in a project where you are the only member, after seven full days without meaningful progress. They share the same seven-day account email limit.

4. Google user data

When you sign in with Google, Vesta receives your name, email address and profile picture. It requests nothing else from your Google account: no access to Gmail, Drive, Calendar or contacts.

Your name and picture are shown to you and to people on projects you share.
Your email address identifies your account and matches you to the projects you were invited to.
This data is not sold, not used for advertising, and not shared with anyone except the service providers listed below, which store or process it on our behalf.

Vesta's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

5. AI-assisted features

Built-in AI features, including saved drafts from the previous AI builder, pairwise comparison guidance, duel insights and audit insights, require your own OpenAI API key, and call OpenAI directly from your browser. Your API key is not sent to Vesta. Usage is billed to your own OpenAI account.

Creating a project through a connected AI assistant does not require an API key in Vesta. That workflow sends the project model to Vesta through MCP; it does not save the assistant's chat as a builder transcript. Your assistant's own data-handling settings also apply.

When you finish a saved draft from the previous AI builder, Vesta stores the conversation with that project so its owner can compare the original discussion against the final weights. Only the current project owner can retrieve this saved conversation; it is excluded from public views, collaborator views and project exports. New projects default to private. If you make a project public, its model, description and results are readable by anyone with the link. The builder shows the opening message that will become the project description before you create it. Other saved AI insights are part of the project and follow its access settings.

Relevant text is also sent through a Vesta-operated check to OpenAI's Moderation API to prevent abuse. For the AI Model Builder, this checks your messages when you create the project, rather than on each conversation turn. Other AI features check the relevant project text before generation. This check runs on Vesta's own account. Vesta does not retain the moderation request separately from your saved project. If the check is unavailable, your request proceeds.

Your API key can be kept in memory for the current browser session only, or stored encrypted on your device (automatically forgotten after 30 days of inactivity); you control which, and can delete it at any time from your account settings. We recommend using a key dedicated to Vesta with a spend limit set in your provider's console, since a leaked key is a billing risk, not a data one.

6. Data storage and third-party processors

Your projects, the collaborator list, change history, notification records and server usage measurements are stored with Cloudflare, Inc. Sign-in is handled by Firebase Authentication, operated by Google LLC, which holds your account record. Browser usage analytics are processed by PostHog, Inc. Resend (Plus Five Five, Inc.) delivers two emails: a welcome sent to your own address when you create your account, and the invitation sent when you add a collaborator to a project, which carries the address you invited and the project's name. Resend uses them for nothing else. When project email delivery is enabled, Mailjet (Sinch Email) receives your verified email address and a digest containing project names, the kind of attention needed, and links to the relevant steps. We process delivery, bounce, spam and unsubscribe events to prevent further unwanted mail. Open and click tracking are disabled for these project emails. The following policies describe how our providers handle personal data:

The moderation check described above is the fifth: it sends the specific text being checked to OpenAI, and nothing else about you.

7. Data retention and deletion

Your projects and account data are retained for as long as your account exists. You may delete individual projects at any time from within the app. To permanently delete your account and all associated data, including all projects and their content, go to your profile page and use the Delete account option. This action is irreversible. It deletes your account record and your sign-in record at once. Within minutes it also deletes every project you own along with its collaborator list, and removes you and your email address from every project someone else shared with you. It also removes any API key saved in the browser you use to delete it. A key saved on another device stays there, encrypted, until you remove it or it expires after 30 days of inactivity.

Reading a notification keeps it in your history. Notification history is removed when you lose access to the relevant project notifications, the project is deleted, or you delete your account. Account deletion also removes your email preferences and pending project emails, and queues removal of provider contacts. Minimal delivery receipts and a revocation marker remain in the email service to prevent duplicate delivery or restoration by old requests. Provider delivery logs follow the provider’s configured retention; deleting a contact does not erase a message already received in an inbox.

We retain a minimal account identifier and revocation time to prevent old sessions from restoring a deleted account.

Change history is also kept in an archive as a record of who changed what. It names people by an internal account ID and by a one-way code derived from their email address, never by the address itself.

Backups held by our infrastructure providers may keep a copy for a short period afterwards, under their own retention schedules.

8. Your rights

Depending on your jurisdiction you may have rights to access, correct, or delete your personal data. You can exercise your right to deletion directly in the app via the profile page. For anything else, write to us.

9. Contact

Questions about this policy or your data: support@vesta-mcda.com