Security
Your data, your Dropbox, your team
epiensos handles the documents that decide whether a company is funded. The design starts from that.
Tenant isolation
The team is the tenant. Every table carries a team id and every query is scoped by it in the API layer, not only in the interface. API keys belong to one team. There is no cross team read path.
Authentication with Clerk
People sign in with Clerk on web and iOS, with the verified email domain deciding immediate activation or the waitlist. Agents use per team API keys with scopes, shown once at creation and revocable at any time.
Secrets in provider stores
Source credentials, integration tokens, and AI provider keys are stored in the hosting provider's secret store, never in the database and never in the repository. Integration events with PolyAccounts are signed.
No training on your data
Your opportunities, applications, facts, and files are never used to train models. AI providers are called with data retention disabled where the provider supports it, and the provider router lets you choose which providers your team uses.
Data stays in your Dropbox
Dropbox is the system of record for application and deliverable files. The platform keeps working copies in blob storage for the duration of a job and mirrors the result to your Dropbox under Grants, Funder, Opportunity. Disconnect Dropbox and the mirror stops, your files stay yours.
Confirmation before consequence
Nothing is submitted to a funder, and no deliverable is sent, without an explicit confirmation from a person on your team. Portal automation runs only after that confirmation and records a receipt.
Roles and assignment
Owner, admin, grant writer, finance, clinical, regulatory, reviewer, and viewer. Tasks carry a required role. Sensitive actions such as submission and API key creation are limited to owners and admins.
Audit trail
Every approval, decline, section edit, submission, and outcome is recorded with who did it and when. Activity is visible on the dashboard and in the application history.
Infrastructure
Where things run
- Web app and marketing site on Netlify. API, MCP server, webhooks, and scheduled jobs on Netlify Functions.
- PostgreSQL on Neon with versioned migrations. Vector search for company fact retrieval lives in the same database, scoped by team.
- Working files in Netlify Blobs, system of record in your Dropbox.
- Email out through SendGrid. Email in through a Gmail API watch on a mailbox you configure.
- Payments through Stripe. Card details never touch our systems.
- Analytics and error reporting through PostHog, gated by configuration and never including document content.
Responsible disclosure
Found something?
Email security@epiensos.com. We acknowledge reports within two business days and keep you informed until the issue is resolved.
Invitation only
Request an invitation
Sign up is invitation only while we work with early teams. People from approved organizations get immediate access after signing in at app.epiensos.com. Everyone else joins the waitlist and a platform admin releases accounts in order.