Security & trust at Rainmaker
This page is maintained by CyberGen AI to answer common security and privacy questions about Rainmaker. It describes controls that are live in the product today — not certifications or guarantees.
Last reviewed: June 2026
Shared responsibility
Rainmaker runs on Lovable Cloud, which provides the underlying hosting, managed Postgres, and authentication primitives. CyberGen AI owns the application code, data model, access policies, and customer-facing processes built on top. Customers are responsible for protecting their own credentials, managing who they invite into their tenant, and the accuracy of data they upload.
Platform & hosting
The application is a TanStack Start app served from Lovable Cloud's edge runtime. Application data is stored in managed Postgres with Row-Level Security enabled on every customer-facing table. Tenant and company isolation is enforced in the database withauth_tenant_ids()andauth_company_ids()helpers, so a request can only read rows the signed-in user is a member of — even if application code has a bug.
Server-side logic runs as typed RPC server functions, not as a public API surface. Secrets and API keys are read on the server only and never shipped to the browser bundle.
Access & authentication
Authentication is handled by Supabase Auth: email + password and magic link. Sessions are scoped per tenant, and role membership is stored in dedicated tenant_membersand company_memberstables — never on profile records. Role checks are evaluated server-side through SECURITY DEFINER helpers, so the browser cannot escalate privileges by editing local state.
Deal rooms & counterparty data
Marketplace listings are anonymized by default. Buyer and seller identities, company names, and contact details remain masked until both parties have signed a mutual NDA inside the platform. Deal-room messages, documents, and milestone updates are scoped to the room and are only readable by members of that room.
How we use AI
AI-generated briefings, valuation commentary, and copilot answers are produced through the Lovable AI Gateway. Prompts include only the customer data needed to answer the question, and outputs are written back into the same tenant-scoped tables — they do not leave the customer's workspace. We do not train third-party foundation models on customer data.
Subprocessors
- Lovable Cloud — hosting, managed Postgres, authentication, and edge runtime.
- Lovable AI Gateway — proxied access to large-language-model providers for in-app AI features.
We will update this list before adding new subprocessors that process customer data.
Cookies & analytics
Rainmaker uses session cookies for authentication only. We do not run third-party advertising trackers or sell customer data. Product analytics, when enabled, are limited to aggregate usage events that do not include deal content or counterparty identifiers.
Privacy requests & data deletion
Customers can request export or deletion of their tenant data by emailing the address below. Tenant administrators can also remove members and companies from inside the app, which immediately revokes access through Row-Level Security.
Security contact & vulnerability disclosure
Report suspected vulnerabilities, account abuse, or privacy concerns to security@cybergen.ai. Please include steps to reproduce and avoid accessing data that does not belong to you while testing.
Compliance
Rainmaker is not currently advertising SOC 2, ISO 27001, HIPAA, PCI, or GDPR certification. The controls described on this page reflect how the product is built today and are not a substitute for an independent audit. If your diligence process requires specific attestations, contact us and we will tell you honestly where we stand.
The next great deal is a match away.
Approved accounts onboard in 24 hours. No retainers. No banker tour. Just the connection machine pointed at your best counterparty.