What passes through our server

On the free trial, Veda Pro and Veda Max, the text you ask Veda to rewrite (and the bit of conversation it needs for context) is sent to our server, which passes it to the AI provider and sends the answer back. It is used only to make that one call. We never store it and never log it. Your voice is turned into text on your device (on a Mac with Apple’s speech model; on Windows with the Whisper speech model, downloaded in Settings), so the recording never leaves it. Without the speech model, voice simply doesn’t work until you download it — nothing is sent instead.

The AI behind the trial, Veda Pro and Veda Max is OpenAI. OpenAI doesn’t train its models on what Veda sends, and Veda doesn’t ask it to save anything. Like every business that uses OpenAI’s API, OpenAI may keep a request for up to 30 days only to check for abuse, then deletes it. Nothing is stored on our side.

What we store

A hashed device ID — a one-way fingerprint made on your device, so a trial can be given once per machine. We never see the raw identifier.
Your plan (trial, Veda Pro or Veda Max), and whether it’s active.
For paid plans: the email address you paid with and your Paddle customer and subscription IDs, as given to us by Paddle, our payment provider. We match that email to the Google account you sign in with, so the plan reaches your computers.
Daily counts of requests and AI tokens used — numbers only, no content.
If usage sharing is on: anonymous usage events from the app (below).
Reports you choose to send us (below).
The name and email address Google gives us when you sign in to the app, tied to each computer you sign in on (below).
Feedback you choose to send from the app: the topic, what you wrote, your Veda version and Mac or Windows, the diagnostics line if you leave it on, and your email if you ask us to reply.
If you ask the site to email you the download links (on a phone): a one-way fingerprint of your address, so the same address isn’t sent them over and over, and which link brought you to the site. Your address itself goes only to Resend, our email provider, to send two emails — the links, and one reminder the next weekday morning, which you can skip from the first email. Nothing after that.

Usage data from the app

Share anonymous usage data (Settings → Privacy) is on unless you turn it off. It helps us find bugs and see which features work. When it’s on, the app sends us short events: which Veda feature you used (a rewrite, a reply, voice, the edit bar…), the name of the app you used it in (like Slack or Google Chrome) and the kind of field (chat, email, document, tracker), how long it took, word counts, how much of the result you changed, and any error. It also tells us which of our messages you saw, opened or closed, the answer you pick on the one check-in, and the topic of any feedback you send (never what you wrote). Each event also carries your Veda version, operating system version, trigger key, plan and language setting. When you change a setting, we’re told which one and its new value — except for text you wrote and anything secret (your notes, presets, style, API keys), which is reported only as “changed”. Because you sign in with Google, these events are tied to your device and so to the email you signed in with; signed out, they carry no name or email.

Usage events never include your text, your voice, the conversation on screen, what the AI wrote, window titles or your keys. Turn the switch off and the app sends nothing more and deletes anything waiting to be sent. We keep usage events for up to 13 months.

Reports you send

If a result is wrong, Report last result in the menu-bar or tray panel shows you exactly what would be sent — the text before and after, and a note if you add one — and sends it only when you click Send. You can untick Include my text to send just the app, the feature and your note. Reports work even with usage sharing off, because you send them yourself. We use them only to fix Veda.

Feedback and messages from us

Give feedback in the app sends the topic you pick, what you type, and your Veda version and Mac or Windows, plus settings and states (never your text, names or keys) if you leave diagnostics on. Every minute the app also checks for short messages from us, like a new feature or “please update”. That check carries only your app version and Mac or Windows, nothing about you: the app decides on your device which messages apply.

Cookies on this website

The app sets no cookies. This website uses Google Analytics to see how people find Veda — only if you click Accept on the cookie notice, and never if your browser sends Do Not Track. We count clicks on download and buy buttons, and the length of docs searches (not what you searched for). No advertising cookies are used.

What stays on your device

Your voice profile — what Veda learns about how you write — and the writing samples it learns from are kept on your device and are never uploaded. So are your About you answers and notes, your presets, your activity log and any API keys you add.

So is Veda’s memory: the conversations it remembers, the people in them, your facts, your Ask Veda chats and briefs. They’re kept in an encrypted file on your device and never sent to our server. When you ask a question, only the matching messages go to the AI with it. A calendar you connect is read from your device; its sign-in stays there too. The meeting countdown and the meeting card are made on your device. Your free times go to the AI only when a reply you asked for is about finding a time, and people’s emails and time zones from invites stay in the encrypted memory file.

With memory always on (the default), Veda also reads the chat or email window in front of you every few seconds while you’re at the keyboard, on your device, so Brief and Ask Veda can tell you what’s waiting on you. It never reads password fields, private windows, a locked screen or apps you exclude, and you can switch it to “when Veda is used” or pause it from the menu bar. Nothing read this way leaves your device unless you ask a question that needs it.

Meeting notes

When you press Take notes, Veda listens on your device to your microphone and to the call’s sound (no bot joins the call) until you press Stop. Every minute, that audio is turned into text on your device and then thrown away; it is never saved on your device or on our server. The transcript, your jottings and the notes written from them are kept in Veda’s encrypted memory on your device, deleted with memory or one by one, and not sent to us. You’re responsible for telling the people on the call that you’re taking notes.

You sign in to Veda with Google when you set it up. Veda asks Google only for your name, email address and profile photo — nothing from your mail, files or calendar. Our server checks Google’s answer and keeps your name and email with each computer you sign in on, so your plan and trial follow you to up to 3 computers, and so we know who uses Veda and can write to you about your trial or a problem we can fix. The photo stays on your device. We never sell this, never share it with advertisers, and won’t send you marketing you haven’t agreed to. Sign out (click your name at the foot of the sidebar) deletes your name and email for that computer from our server at once; Veda then waits on its sign-in page until someone signs in again.

Google Calendar

If you connect Google Calendar, Veda asks Google only to see your calendars and events (read-only). It reads them on your device to show your meetings, the meeting card, your brief, answers to your questions and free times in replies you ask for. It never creates, changes or deletes anything in your calendar. The sign-in is kept on your device and never reaches our server. Your calendar stays on your device too, except for the meeting details a result you asked for needs (say, the titles and times for “what’s on tomorrow?”): those go with that one request, through our server, to the AI that writes it — and are never stored or logged on the way.

OpenAI, the AI provider that writes Veda’s results — only the meeting details a result you asked for needs, only to write that result. OpenAI doesn’t train on it and may keep a request for up to 30 days only to check for abuse, then deletes it.
Railway, which hosts our server, carries that request to OpenAI over HTTPS. Our server doesn’t store or log it.
No one else. We don’t sell Google user data, share it with advertisers or data brokers, or transfer or disclose it for any other purpose. Because our server keeps none of your calendar, we have none to hand over, even if asked.

How your calendar data is protected

The Google sign-in is kept on your device: in the macOS Keychain on a Mac, and encrypted with Windows Data Protection for your user account on Windows. It never reaches our server.
Veda reads your events straight from Google over an encrypted (HTTPS) connection and holds them only in the app’s memory while it runs. It doesn’t save a copy of your calendar.
What Veda keeps from your meetings — notes you take, your brief, and the names, email addresses and time zones of people in your invites — is stored only on your device, in Veda’s memory, encrypted with AES-256. The key is held in the macOS Keychain or by Windows Data Protection.
The meeting details a result needs travel to the AI over HTTPS. Our server passes them on without storing or logging them; OpenAI may keep a request for up to 30 days only to check for abuse, then deletes it, and doesn’t train on it.
No one at Veda can see your calendar data.

How long it’s kept, and how to delete it

Your events aren’t stored: they’re gone from Veda when it quits.
Meeting notes and other memory from your meetings are kept for your memory period — 90 days unless you choose 30 or 365 in Memory — then deleted automatically. People’s names, email addresses and time zones stay until you remove them.
You can delete any of it at any time: delete a meeting note, remove a person in Memory, or use Memory → Forget everything. Connectors → Disconnect deletes the sign-in and revokes Veda’s access at Google. Uninstalling Veda and deleting its folder removes everything.
Our server holds no Google user data, so there’s nothing to delete there. For help, write to [email protected].

Veda’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is never sold, never used for advertising, never used to train AI models, and never read by people at Veda. Disconnecting in Veda (Connectors) deletes the sign-in from your device and revokes Veda’s access at Google; you can also remove it at myaccount.google.com/permissions.

Apple Mail (Mac)

If you connect Apple Mail, Veda reads recent email in the Mail app on your Mac — your inbox and sent mail, from people only, never newsletters or no-reply mail — while Mail is open. It reads through Mail itself, after macOS asks your permission, and never sends, moves, flags or deletes anything. What it reads goes into Veda’s memory on your Mac, encrypted like everything else there, and is kept for your memory period. Like the rest of memory, only the part a reply, brief or answer you asked for needs goes to the AI with that one request; our server doesn’t store or log it. Disconnect in Connectors stops the reading; delete anything already remembered from the Memory page.

Your AI apps (MCP)

Off unless you turn it on. In Connectors you can let Claude or Cursor on the same computer read your Veda memory and meeting notes, read-only, through MCP (Model Context Protocol). They can search memory, open a conversation, see what’s waiting on you, look up a person and read meeting notes; they can’t change or delete anything. Veda only answers the apps you turned on, and nothing while memory is paused.

What those apps read leaves Veda: Claude or Cursor sends it to their own AI service, under their own privacy terms, not ours. Veda’s server isn’t involved. With usage data on, Veda tells us only which tool was used and by which app — never the question or the answer. Turn an app off in Connectors to stop it at once.

Payments

Payments are handled by Paddle, the merchant of record for Veda. They process your card details, taxes and receipts; we never see your card. Paddle tells our server when a purchase, renewal, cancellation or refund happens, so we can start, change or end your plan. See also our terms and refund policy.

Questions or deletion

Removing Veda from a device (Settings → Plan & usage) signs that device out. Turning off Share anonymous usage data stops usage events at once. To have your account data, usage events, reports and feedback deleted, email us at [email protected].