Built to be trusted with your network.
Oka only works if you trust it with your relationships and your inbox. Every promise below maps to something in our code — not aspiration. When we can't yet claim something, we say so.
Nothing goes out to an investor until you approve that exact message.
Your raise, your data, your team — kept fully separate from every other workspace.
Gmail is connected per person. Your team sees investor conversations only if you allow it.
Advisors, angels and teammates see exactly what they shared — and can withdraw anytime.
You stay in control.
Oka's AI finds and ranks investors, maps who can introduce you, drafts outreach, and keeps your pipeline moving. But it does the work in the open: nothing goes out to an investor without you.
A draft is a draft until you send it. Where your workspace has Oka's agent switched on, Oka can also send an email or LinkedIn message from your own account — but only one message at a time, only after you have approved that exact message, and only from an account you have allowed sending from once (withdraw it in Settings anytime). It never sends on a schedule, in bulk, or from a teammate's account. Changes the AI makes to your pipeline are shown to you, and for 24 hours you can undo them in one click — unless the same entry has been changed again since, in which case Oka tells you rather than overwrite it.
We read only what you allow
When you connect Gmail, we read the To, From, Cc, and Date headers of your messages to map who you've been in touch with and surface direct connections to funds. That is all we read, unless you allow more.
Message content is read only while “Read investor replies” is switched on. It is off until you turn it on — we ask you once right after you connect, and you can change it anytime in Settings → Connected accounts. While it is on, Oka reads investor replies to your outreach and keeps where you stand. Where your workspace has Oka's agent switched on, it also keeps the text of your email conversations with investors on your deals, so the assistant can answer from them. The text of other mail is never kept, and attachments are never stored. Switch it off and the stored conversation text is deleted. LinkedIn chats have their own switch, “Read LinkedIn chats with investors” — off until you turn it on, and while it is off Oka keeps nothing from your LinkedIn chats.
The same switch decides whether Oka Notes, our notetaker, can be used for your investor calls where your workspace has Oka's agent on. It never joins on its own — only a call you turn it on for, after you have told the participants. It keeps a transcript, never audio or video. Switching it off takes Oka Notes off your upcoming calls, unless a teammate (editor) who has it on is invited too; transcripts of calls already held stay with your workspace until it is deleted, you ask us to delete them, or the workspace has been closed for 12 months.
The permission your Google account grants is technically broader than this. The limits above are enforced in our code, not by Google — which is why we spell them out here and in our privacy policy.
Workspace isolation, enforced on every query
Your funds, matches, direct connections, notes, and relationship graph are scoped to your workspace and never shared across customers. Every read from our database is scoped to your workspace in the application — the customer identifier is attached to the query before it runs, so a query can only return rows that belong to you.
We treat a missing scope as a failure, not a leak: our data access is written so that an unscoped query fails closed rather than returning another customer's data. No request in oka can cross from one workspace into another.
Access within your workspace is permission-based. Team members see only what their role allows, and the workspace owner controls who is in and what they can do.
Your connections and data in transit
Gmail, Google Calendar, and LinkedIn connect through our EU partner Unipile (France), which holds the authorization. Oka never sees your Google or LinkedIn password. Older direct Google connections, where they still exist, keep their tokens encrypted at rest with AES-256-GCM, decrypted only in memory and never exposed to the client.
Connections are per person. A teammate connecting their inbox never lets anyone else send from it or read it — the team sees only the investor conversations described above, and only while that teammate has “Read investor replies” on.
All data is encrypted in transit using TLS, and encrypted at rest by our infrastructure providers.
Your grants, your controls
From Settings → Connected accounts you can disconnect Gmail or LinkedIn in one click — we delete the connection at Unipile and the conversations synced from it. From Settings → Your data you can export everything we hold about you, or delete your account outright. Account deletion runs with a 7-day grace window, so it stays reversible until then. If your workspace is closed, the workspace owner exports or deletes from the page they see after they sign in.
Nothing here is buried in a support queue. Disconnect, export, and delete are one-click actions you run yourself, whenever you want.
Connectors stay in control of their network
When someone shares their network to open direct connections for a founder, they can see exactly what's shared — and nothing more than the connections that create a direct connection. There is no hidden export of their contacts.
A connector can withdraw their network at any time. Once they do, their connections stop surfacing as direct connections and are removed from what oka holds. Sharing is always theirs to take back.
We don't sell your data
We use what you connect only to provide oka's features — mapping your network to relevant funds, surfacing direct connections, and, where you allow it, keeping track of your conversations with investors. We do not sell your data and we do not use it for advertising.
If you're an investor in our dataset and not an oka user, you can request removal at any time. Submit your email on our remove-my-data page and, once verified, we delete your profile and add a suppression tombstone so it can't be re-ingested.
What we don't yet claim
We'd rather under-promise. We do not currently hold a SOC 2 report, guarantee EU-only data residency, or publish an external penetration test. When those land, we'll say so here — not before.
Our sub-processors
We rely on a small set of trusted providers to run oka. Each one processes data only to deliver the service, under a data-processing agreement: an EU-hosted database and authentication provider, cloud hosting, account connections, AI processing, call transcription, web search, payment processing, transactional email, analytics, and error monitoring.
Our database and authentication run in the EU.
The full list, with what each provider does and where, is in section 5 of our privacy policy.
Reporting a vulnerability
If you believe you've found a security issue, we want to hear from you. Please email security@getoka.ai with details and we'll respond promptly. We appreciate responsible disclosure and will not pursue action against good-faith research.