Who can see the data. Who can approve the work.
The product’s access controls and operating limits, stated plainly.
Accounts and workspace membership
Passwords use scrypt hashing. Sessions use hashed tokens and HttpOnly, SameSite cookies, with Secure cookies in production. Membership roles are checked on the server. Owners invite operators or viewers through single-use links; invitation email is not sent by the product. Email ownership is not verified. Keep your recovery code securely.
Private sources and derived records
Files are stored outside the public web root. Uploads begin private to their uploader and workspace owners. Company and source visibility are reviewed separately. Retrieval, agent context, observations, dependent tasks and packets recheck access. Revoking a source stops retrieval and access to its dependent records; it does not erase previously downloaded copies.
AI processing
An authorized person explicitly confirms an OpenRouter run. Bounded source text is sent to the selected model through OpenRouter, requesting providers with data collection disabled and zero-data-retention eligibility. Routing controls are not independent certification. Do not submit material whose permissions or agreements forbid this processing. Agents have no external execution tools, and their output remains proposed until a person saves it for review.
Investor statements and recurring missions
Investor links share an owner-reviewed fixed LP-specific snapshot, expire, and can be revoked. They require the private capability link and are excluded from indexing; possession grants access to the selected statement until revoked or expired. Recurring missions retain their approved goal and selected records, recheck current owner authorization, and prepare drafts for manual application.
Provider secrets
Optional read-connector tokens are encrypted on the server. The OpenRouter management key is not deployed. A dedicated runtime key has a $10 total usage cap, with additional per-workspace and global run limits. These release limits can cause the agent service to pause; no automatic top-up occurs.
Storage and operations
The release uses a single server with a persistent SQLite volume and private files. This is a bounded initial deployment, not a highly available cluster. Database backups use SQLite’s consistent online VACUUM INTO snapshots; Fly volume snapshots are an additional provider recovery layer. Restore checks and release verification are documented with the source.
What is not claimed
No SOC 2 certification, independent financial audit, investment-performance improvement, legal compliance certification, or verified customer outcome is claimed. Team-reviewed metrics and resolutions record acceptance by your team. Financial records are team-reviewed operating inputs, not independently audited administration. Bank transfers, filings, and external notices require separate integrations.