Security and governance

Share and collaborate fast. Control with precision.

Because internal operating files and externally shared files move in the same place, control has to be built in from the start.

Governance built-in

Control is the default flow, not an option.

JarvIR is designed for environments where internal operational materials and external shared materials coexist. Permissions, logs, and link tracking are built into the core workflow to manage sensitive company information.

Role-Based Access Control
Data isolated by company and project
Activity Log and Change History
Shared Link and Download Tracking
Password and server-side session checks on share links
Approval flow for data room access requests
SSO (OIDC · SAML) · SCIM automatic provisioning
Tamper-detecting audit chain · External timestamps (RFC 3161)
Per-audience access tiers · section-level visibility enforced by the server
Automated retention-policy enforcement · connection secret encryption
Trust facts

Written down before you ask.

Where we have nothing, we say so. A product that sells verification cannot afford to overstate its own security.

Certifications and external testing

  • SOC 2 Type II — None
    Not held. We answer questionnaires with the controls below and the evidence in our code.
  • ISO/IEC 27001 — None
    Not held.
  • 외부 침투 테스트 — None
    No third-party test has been carried out. Automated checks in our repository — missing auth, security headers, leaked secrets, dependency vulnerabilities — run on every deploy.

Retention periods

  • Activity logs, share access logs, investor activity — Set by each company. 0 means indefinite; any other value is clamped to between 30 and 3,650 days (Settings → Data governance).
  • Usage and bandwidth events — Automatically deleted after 400 days (database TTL).
  • Share sessions, data room permits, email verification codes — Deleted automatically at their expiry time.
  • API tokens — Automatically deleted 90 days after expiry (kept until then for investigation).
  • Account and company data — Removable via an account deletion request (/account-deletion). Exports are available under Data governance.

Data residency

A region counts as verified only while the operator's attestation matches the fingerprint of the live deployment configuration. If it stops matching or expires, we fall back to "unverified" — we never state a region by assumption.

This is an operator attestation, not an independent audit certification.

Data processing agreement (DPA)

We will send you one on request. Choose "Privacy" in the contact form's category.

Subprocessors

Third parties that customer data can reach. Every entry must have real evidence of use in the code, or our tests fail.

PaddlePayments and billing as Merchant of Record · Billing details and subscription status
AnthropicAI generation and analysis · Documents and text included in the request
OpenAIAI generation and analysis · Documents and text included in the request
Google (Gemini)AI generation and analysis · Documents and text included in the request
Google (로그인·Play 결제)Social sign-in, Android in-app purchases · Email address and purchase receipts
AppleSocial sign-in, iOS in-app purchases · Email address (or private relay) and purchase receipts
FirebaseMobile app configuration · Device identifiers
메일 발송 공급자(SMTP)Sending invitations, notifications, and contact emails · Recipient email addresses and message bodies
S3 호환 오브젝트 스토리지Storage of uploaded files · Uploaded documents and images
Google Analytics 4 · Tag ManagerPublic-site usage analytics (consent-based) · Usage events, where consent was given
Enterprise review

You'll have the evidence to answer security review questionnaires.

There are no answers here that end with "an admin deletes it by hand." We've documented how code guarantees all three: identity, records, and controls.

Identity and access

Sign in with your company IdP, and when someone leaves, access is cut off automatically.

  • OIDC · SAML 2.0 SSO — we never skip signature, issuer, or audience validation
  • SCIM 2.0 provisioning — the path that matters most isn't creation, it's deactivation
  • admin · member roles and menu-level permissions are enforced by the server, not the screen
  • Share links are double-verified with a password and a server session

Records you can use as evidence

The value of an audit log lies not in "there is a record" but in "the record hasn't been tampered with."

  • Per-company hash chain — deleting or altering any link breaks verification for everything after it
  • HMAC checkpoints signed with a key kept outside the DB
  • Anchoring to an external timestamp authority (RFC 3161) — not even the operator can alter it after the fact
  • Audit log verification and export

Control and retention

Since internal materials and externally shared materials move in one place, control is built into the default flow.

  • Per-audience access tiers — investors, the board, and employees each see different metrics
  • The section-level visibility of share links is enforced by the server, not the UI
  • A scheduler actually enforces retention policies — you can set it and forget it
  • Data room access-request approval and download tracking, plus AES-GCM encryption of connection secrets

SSO · SCIM is available on Enterprise, while per-audience access tiers and audit log export are available on Scale and above. Everything else is included by default in all plans.

JarvIR AI SaaS

Turn your company's operational data into a compelling story for investors.

Get started for free

Sign up with your Google account, create a company, and get started right away.