Privacy Policy

Draft · July 16, 2026

The short version: RevBud is local-first. Your deals, dossiers, drafts, notes, and transcripts live on your Mac and stay there. Your RevBud account exists for identity and metering only. When RevBud needs the big model, the relevant slice of context rides an encrypted call through our proxy and is never stored. We would rather hold less of your data than more of it.

1. What RevBud is, in privacy terms

RevBud is a native macOS application: an AI sales buddy that works your selling day with you. It is designed so that the substance of your work, everything a competitor or a court would call your book of business, never becomes our data. This policy explains what stays on your Mac, what our servers hold, what transits our servers without being stored, and the choices you control.

2. Local-first: what lives on your Mac and nowhere else

The following data is created and stored only on your Mac. It is never uploaded to, stored on, or readable by RevBud servers:

Deals and pipeline state, including account and contact dossiers.
Drafts the buddy writes and everything you edit.
Notes, commitments, and briefs.
Call transcripts. Call listening runs entirely on-device.
Your learned writing voice and the examples it is built from.
Chat history with your buddy.

You can export all of it at any time with one click, in documented, versioned formats. Export never locks, including after you cancel.

3. What our servers store, and what they never store

WE STORE

Identity: your name, email address, and authentication records needed to sign you in.

WE STORE

Entitlements: your plan, trial state, and billing status. Payment card details are held by our payment processor, not by us.

WE STORE

Meters: counters of metered usage (for example, work-product actions and Live voice minutes), so plans and trials work. Counters are numbers, not content.

WE STORE

Opt-in telemetry: feature pulses and crash reports, only if you turn them on. See section 6.

NEVER

Deals, dossiers, drafts, notes, transcripts, or chat content. These stay on your Mac.

NEVER

Prompt bodies and model responses. Cloud thinking is transit-only: context passes through our proxy to the model provider for the duration of the call and is not logged or persisted by us. This no-log rule is an architectural law of the product, not a preference.

NEVER

Connector tokens. Credentials for your email, calendar, CRM, and other connected tools live in your Mac's Keychain and never touch RevBud servers.

4. Cloud thinking: what transits, and when

RevBud's storage is local, and its heaviest thinking is cloud-based. When a job needs the big model, the relevant slice of context (for example, the email thread being answered and the matching deal frame) is sent over an encrypted connection through the RevBud proxy to a model provider, used to produce the result, and never stored server-side by RevBud.

We are deliberate about this claim: during cloud thinking a context slice does leave your Mac in transit, and we will never pretend otherwise. What we promise is that storage is local, transit is encrypted, and our proxy does not log or retain your content.

The plain-English inventory of every flow, what leaves your Mac and when, is published and kept in sync with the product.

5. Voice

Local voice (hold-to-talk) transcribes on-device. On the Live tier, real-time conversation streams your audio off the Mac for the duration of the session, and only while a persistent on-screen indicator is lit that says so. Live audio is not stored by RevBud.

6. Crash reporting and telemetry (opt-in)

Both are off by default and controlled by visible toggles:

Analytics are feature pulses only: which features run, meter levels, latency percentiles. Never message content, never contact data.
Crash and bug reports include a log bundle that is safe-logged and scrubbed: entity identifiers rather than names, phone numbers, or message bodies.

7. Account deletion

You can delete your RevBud account at any time. Deletion wipes our server-side state for you: identity, entitlements, meters, and any opt-in telemetry, under our published retention schedule. Your local data is yours and remains on your Mac; if you want it gone too, delete the app and its data folder, or export first.

8. GDPR and CCPA

Our posture under the GDPR, CCPA, and similar laws is that the best way to protect your data is not to hold it. The personal data we process as a business is limited to identity, entitlements, meters, and opt-in telemetry. For that data you have the rights to access, correct, delete, and export it, and we honor them via in-app controls and the contact below. We do not sell personal data, and we do not use your content to train models.

9. Changes

If this policy changes, the app will tell you in its own voice before the change takes effect, and this page will show the new date and a summary of what changed.

10. Contact

Questions, requests, or complaints: [email protected].