Skip to content

Virtual Data Room · DC GEEKS

Share what isconfidential.Keep theevidence.

Covenant is the data room for M&A, financing, audits and boards. Every organization is isolated, every page is delivered with the viewer's own watermark and every action lands in a chained log you can verify.

Illustrated interface with synthetic data.

01The problem

The most sensitive documents in a deal often travel through the least controlled channels.

  1. i

    Attachments nobody can recall

    A file sent by email keeps circulating after the deal closes. You cannot tell who opened it or how many copies exist.

    attachment.pdf → forwarded

  2. ii

    Links anyone can forward

    A public link cannot tell the invited buyer apart from whoever received it forwarded.

    public link · never expires

  3. iii

    Permissions in a spreadsheet

    When access is decided outside the system, nobody can later explain why someone saw a document.

    permissions_v7_final.xlsx

Covenant turns each of those decisions into a rule enforced on the server and recorded.

02How it works

From an empty folder to closing, in five moves.

  1. Step 1 of 5

    Prepare

    Create the deal, define the index and upload documents. Each version is checked by its real content, hashed with SHA-256 and processed in the background.

    PDF, images and text are rendered for the viewer. Office files are stored and flagged as preview unavailable.

    Project Condor

    2 Financial
    • 1.1 Articles of incorporation.pdf

      Uploading
      sha256 ······
    • 2.3 Financial statements 2025.pdf

      Uploading
      sha256 ······
    • 4.2 Customer portfolio.csv

      Uploading
      sha256 ······
    • 6.1 Network diagram.docx

      Uploading
      sha256 ······
  2. Step 2 of 5

    Invite

    Organize participants by side: sell side, each buyer, advisors. When the deal requires it, nobody sees a page before accepting the NDA.

    Invitations expire and every access can have an end date.

    Project Condor

    • VSLMJR

      Sell-side team

      NDA accepted
    • CAPG

      Buyer A · Meridian Group

      NDA accepted
    • CBRT

      Buyer B · Pacific Ventures

      NDA required
    • EX

      Advisors

      Invited

    Buyer A and Buyer B cannot see each other

  3. Step 3 of 5

    Control

    Set levels per folder and group: view, download, download original or manage. When someone asks why they have access, the system shows the full reasoning.

    The nearest explicit permission wins over the inherited one.

    Level

    IndexBuyer ABuyer BAdvisors
    1CorporateViewinheritedViewinheritedDownloadexplicit
    2FinancialViewexplicitNo accessexplicitDownloadinherited
    3LegalViewinheritedViewinheritedManageexplicit
    4CommercialNo accessexplicitNo accessexplicitViewexplicit

    Why can they see this document?

    1. Active participant, NDA accepted
    2. Buyer A group on 2 Financial: View (explicit)
    3. Version ready for the viewer

    Decision: can view, cannot download

  4. Step 4 of 5

    Answer

    Questions follow a stateful flow with approval before publishing. A buyer never sees another buyer's questions.

    Each answer is published only to the groups you choose.

    Does the port operator contract include a change-of-control clause?

    Q-014
    1. Draft
    2. Submitted
    3. Assigned
    4. Answered
    5. Published

    Buyer A · Meridian Group

    Sees their question and the answer published to their group.

    Published

    Buyer B · Pacific Ventures

    Does not see other buyers' questions.

    0

  5. Step 5 of 5

    Close

    Review real activity by document and by group, export the audit log and verify that the chain has not been altered.

    Verification recomputes every hash from the first event.

    Activity by group

    Export CSV
    • Buyer A
    • Buyer B
    • Advisors
    #1201ab12f#12024733a#1203d8f98#1204dabd3#120519b2a#120684163#1207d878f#120806835

    Chain verified

03Security

Security explained by its mechanisms, not by its badges.

We would rather tell you exactly how it works. These are the architecture decisions that protect every document in Covenant.

  1. 01BrowserHttpOnly cookie
  2. 02Web applicationsingle public origin
  3. 03APIprivate network
  4. 04Session → organizationderived on the server
  5. 05PostgreSQLforced RLS
The path of every request: the browser never talks to the API or to storage directly, and the organization is decided on the server before the database is touched.
  1. 1

    Isolation per organization

    The active organization is derived from your session on the server, never from what the browser sends. Every query runs under forced PostgreSQL Row-Level Security policies: a row from another organization does not exist for your transaction.

    FORCE ROW LEVEL SECURITY

  2. 2

    Hash-chained audit

    Each event stores the hash of the previous one. Changing a row breaks the chain and the verifier detects it when recomputing. The database only allows inserting events.

    sha256(prev_hash ‖ event)

  3. 3

    Dynamic watermarks

    The viewer serves pages rendered on the server with the viewer's name, email, organization, IP and time burned into the image. It is not a layer you can remove from the browser.

    Cache-Control: no-store

  4. 4

    Encrypted, write-only secrets

    Connector credentials are encrypted with AES-256-GCM. The interface confirms they exist and when they changed; it never shows them again.

    AES-256-GCM

  5. 5

    No public file addresses

    No document has a direct address in storage. Every page and every download goes through deal, group and folder authorization.

    authorized per request

Try it: a real chain computed in your browser

These four synthetic events are chained with SHA-256 right here. Alter one and watch what happens to the ones after it.

Computing…

  1. #1

    deal.participant.added

    Buyer A

    prev
    …
    hash
    …
  2. #2

    deal.permissions.updated

    2 Financial: VIEW

    prev
    …
    hash
    …
  3. #3

    document.page.viewed

    2.3 p.3

    prev
    …
    hash
    …
  4. #4

    qa.answer.published

    Q-014

    prev
    …
    hash
    …

Covenant does not claim compliance certifications. If your evaluation needs formal evidence, let's talk about what you need to review.

04Configuration Center

Providers configured from the interface, not from files.

The Configuration Center manages storage, mail and antivirus with revisions, validation, connection tests and activation. No environment variables to edit, nothing to rebuild.

Activating new storage never moves your documents. New versions go to the active provider and each version remembers where it lives.

Configuration Center

  • Local storage

    Active · built in

    Server disk, available from minute one.

  • S3-compatible

    Validated

    For services that implement the S3 API.

  • SMTP mail

    Active

    Invitations, notices and welcome messages for new organizations.

  • Antivirus (clamd)

    Not configured

    Without antivirus, every file is flagged as not scanned. Never as clean.

S3-compatible

Revision 3

Connector lifecycle

  1. Draft
  2. 2Validated
  3. 3Connection tested
  4. 4Active

Secret key

Configured · write-onlyReplace

Validated

05White label

Your brand in the room. Ours, discreet.

Each organization sets its name, logo, primary color, sign-in message and support email. The color is checked for contrast before it is saved.

Pick a sample organization

Live preview

ACAndes Capital Partners

Sign in to the data room

Access for invited participants only.

Email

admin@demo.covenant.test

Password

••••••••••
Sign in

powered by Covenant

Contrast with white text:6.59:1· Meets AA

06Analytics

Activity you can read, without embellishment.

Metrics are computed from real viewing events: time per document, pages viewed and activity by group. When there was no activity, the dashboard says so.

Reading minutes per day, last 21 daysBuyer ABuyer B
21 days agotoday

Most read documents

  1. 2.3 Audited financial statements128 min
  2. 3.1 Key customer contracts94 min
  3. 4.2 Customer portfolio61 min
  4. 6.1 Systems architecture37 min

Illustrative preview with synthetic data.

07Use cases

Built for conversations where a document carries weight.

deal.type = M_AND_A

Due diligence with several buyers in parallel, each isolated from the rest, with moderated questions and answers approved before publishing.

  • One group per buyer
  • Q&A with approval
  • Activity by group

08Frequently asked questions

Direct questions, direct answers.

  • No. We do not claim certifications we do not hold. The security page describes the platform's concrete controls so you can evaluate them.

  • By default, on the server's local storage. An administrator can activate S3-compatible storage from the Configuration Center; existing documents stay where they are.

  • PDF, PNG and JPEG images, and plain text, CSV or Markdown are shown in the protected viewer. Office files are accepted and stored, but flagged as preview unavailable and downloadable per permission. The limit is 200 MB per file.

  • No. Buy-side groups do not see questions, participants or activity of other buy-side groups.

  • Only if the group's permission on that folder includes it and the version is processed. PDF downloads are watermarked, unless the permission is download original.

  • Files are still processed, but flagged as not scanned. Covenant never presents a file as clean if it was not scanned.

  • You send the request and the DC GEEKS team reviews it. If approved, your organization is created for 14 days and, if you ask, a sample deal with synthetic documents.

  • Yes. Each organization configures name, logo, primary color, sign-in message and support email. The color is checked for contrast to keep things legible.

Put Covenant to the test with a sample deal.

Request a trial organization. Every request is reviewed by a person on the team.