Security
Your fund's data is your fund's data.
Orivade handles information that matters. Here is exactly how we handle it, what we access, what we don't, and how you stay in control.
What Orivade accesses
When you connect Gmail or Outlook, Orivade accesses your email via OAuth 2.0 — the same standard used by every major calendar, productivity, and accounting application. We never see your password. Authorization can be revoked at any time from your Google or Microsoft account settings.
Orivade reads metadata (sender, subject, date) and message bodies from investor-related threads only. We do not read personal, internal operational, or unrelated email.
What Orivade does with it
Orivade processes your authorized investor communications to build and maintain your fund's institutional record. Your data is never sold, pooled, aggregated with other customers, or used to train generalized AI models. Each fund's data is scoped to its own workspace.
No Orivade employee reads your fund's data except with your consent, where necessary for security, or where the law requires it. Deleting your workspace removes its records.
AI and subprocessors
Some features rely on third-party services. When Orivade drafts a reply, answers a Fund Memory question, or summarizes a thread, the relevant message content is sent to Anthropic (Claude); semantic search sends message text to Voyage AI for embeddings. Billing runs through Stripe, transactional email through Resend, error monitoring through Sentry, and web analytics through privacy-preserving Plausible.
Each provider processes your data only to deliver its part of the service. Under their API terms, Anthropic and Voyage do not use your content to train their models.
Drafting and your judgment
Drafted communications are generated by Orivade and reviewed and sent by you. Orivade does not communicate on behalf of your fund autonomously. Every draft is a starting point — final judgment stays with the person who knows the relationship.
Orivade never initiates outbound emails. It does not have write access to your inbox unless you explicitly authorize a specific send action.
Data portability
Your fund's institutional record can be exported in full at any time, in standard formats. If you stop using Orivade, your data comes with you. We do not hold data hostage, require advance notice, or charge for export.
Export includes investor records, document index, conversation summaries, and all structured data Orivade has built from your inbox.
Encryption
All data is encrypted in transit (TLS) and at rest. OAuth access and refresh tokens are additionally encrypted at the application layer with AES-256-GCM before they are stored.
Infrastructure
Orivade runs on Vercel for application hosting and scheduled jobs, with your records stored in Neon, a managed Postgres service, in US regions. We use separate environments for production, staging, and development, and production credentials are never accessible from development environments.
Access controls
Internal access to production systems follows least-privilege principles. All access is logged, reviewed quarterly, and tied to named accounts. No shared credentials exist in production.
Compliance roadmap
We are pursuing SOC 2 Type II certification. We conduct annual penetration testing with an independent third party. Security findings are triaged and remediated on defined SLA timelines based on severity.
Security questions or concerns
If you have a security question, concern, or want to report a vulnerability, contact us directly. We respond to security inquiries within one business day.
[email protected] →