Privacy

What we see, and what we don’t.

The short version: processed, never stored. Your memory, people, notes and screen context are kept only on your device, encrypted. When you write, rewrite or ask, the text needed is sent to the AI, the answer comes back, and nothing is kept on our side. Veda never stores your text or voice unless you send us a report. If usage sharing is on, we see which features you use, in which apps, and any errors. For a walk-through of what’s read and when, see the privacy guide.

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, with zero data retention: OpenAI doesn’t keep what Veda sends — not for training, and not in logs. The request is processed and the answer comes back; nothing is stored on either 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: your licence key, the email address you paid with and your Paddle customer and subscription IDs, as given to us by Paddle, our payment provider.
  • 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).

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. 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”.

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.

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.

When you ask about the window in front of you, Veda reads its text on your device, through the system’s accessibility features and, for apps that draw their own text, the system’s own text recognition on a picture of that one window. The picture is never saved or uploaded; only the text goes with your question.

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.

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 to the AI provider that writes it — through our server on the trial, Veda Pro and Veda Max, straight from your device with your own key — and are never stored or logged on the way.

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 (Connections) deletes the sign-in from your device and revokes Veda’s access at Google; you can also remove it at myaccount.google.com/permissions.

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 issue and update your licence key. 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 and reports deleted, email us at support@getveda.app.