Skip to content →
OppulenceOppulence
ProductFeaturesUse casesPricingResources
Sign inStart for free
See how it works
Sign inStart for free
ProductsFeaturesUse casesHow it worksPricingDownloadResourcesSecurity

Product

Commitment LedgerOppulence WebOppulence DesktopOppulence VoiceDownload

Features

Commitment registerAccount mission controlAttention queueGoverned actionsMeeting captureLive notes

Use cases

Founder-operatorAccount managementMeetingsResearch and verification
Sign inStart for free
Loading

Read one closed customer. Confirm the rows.

See how it worksStart for free
Oppulence

Product

ProductsCommitment LedgerWebDesktopVoicePricingDownload

Features

Commitment registerAccount mission controlAttention queueGoverned actionsMeeting captureLive notesLocal vaultAgents

Use cases

Founder-operatorAccount managementMeetingsResearch

Resources

Resource hubGuidesChangelogIntegrationsSecurityCompareAnswer hubBlogCustomers

Compare

CRMMeeting notesInboxAI assistants

Company

ContactPrivacyTermsResponsible disclosureDiscord
Oppulence

© 2026 Playbook Media · Oppulence

[security]

The data is yours. Connections are explicit. Sends wait.

This page is the adoption objection, written as the implementation actually behaves. The legal language lives on Privacy and responsible disclosure.

Approval before send
  • What the desktop can see

    A workspace folder you choose, meeting audio you start, the in-app browser pages you open, and the MCP servers you add. It does not get a silent tour of the whole disk.

  • What stays on the machine

    Markdown vault files, capture audio, on-device Whisper transcripts, local embeddings, and ~/.rowboat/ config. Delete the folder and those copies are gone.

  • What reaches Oppulence servers

    When you sign in: account identity via WorkOS, relationship observations you allow, and credit-gated model calls if you use the hosted gateway instead of your own keys.

  • What reaches a model provider

    BYOK goes to the provider you configured. Signed-in hosted LLM calls go through the credit-gated /v1/llm routes. Prompts can contain relationship context you asked the assistant to use.

  • Permissions and writes

    Connectors start as reads. Gmail, Slack, and HubSpot writes are proposed and held. Slack DMs are out of the first beta. Finance MCP write scopes are limited to development and staging.

  • Telemetry

    PostHog analytics is fail-closed until you enable it. You can turn it off. We do not invent a SOC 2 badge or a HIPAA claim on this page.

Docs to read next

  • PrivacyWhat we collect when you sign in, and what can stay on the desktop.
  • Responsible disclosureReport a vulnerability through the published channel.
  • What stays on deviceA walkthrough of the three pipes.

The short versions

It can be. Bring your own model keys and keep the vault on disk. Signing in syncs relationship state to the API so web and desktop match. Those are different setups.

The Go API holds connector credentials. The web BFF keeps session tokens in HTTP-only encrypted cookies. The browser never gets the WorkOS access token.

Native crash dumps stay on the machine. Crash metadata can go to PostHog if analytics is enabled.

Keep going

Approval before send
The write gate.
Responsible disclosure
How to report a vulnerability.