SECURE VIRTUAL DATA ROOMS
Secure virtual data rooms.A record of who read what.
Balau AI gives your firm a permission-controlled place to put confidential material in front of people outside it, with engagement tracking that shows how that material was actually read.
A room here is more than a folder with a link on it. It is a curated set of documents, issued to people you name, bounded by the roles your firm already enforces internally, and attached to the investor, fund, deal, or matter it belongs to.
Access is granted deliberately and withdrawn the same way. What recipients do with the documents is logged as it happens, and the log outlives the raise.
WHO SENDS ONE
Who sends a data room, and why?
Most often a team raising private capital: a sponsor opening a fund to limited partners, a general partner circulating a deal to co-investors, an operator putting diligence material in front of a small, named group and needing to know it stayed with that group.
The shape of the problem repeats. Confidential material has to reach people who are not employees and never will be. The list of who receives it is short, specific, and keeps changing as the raise moves. And months later somebody asks what went out, to whom, and on what date, and the answer needs to be better than a search through sent mail.
A raise is rarely one conversation with one investor. The same names come back across vehicles and across years, so what a firm needs is not really a file transfer but a history. In Balau AI a room belongs to the investor, fund, deal, or engagement it serves, and the reading it produces sits beside the correspondence, meetings, and open commitments already held against that name.
The same pattern serves an advisory firm sending a household its review pack, or a legal team giving a client controlled sight of matter documents. Private capital is simply where the demands run highest, and where the surrounding workflow matters most.
Collections built for one audience
Group the documents a particular audience should see, and nothing beyond them, into a set you can issue as a unit.
Recipients you name
Access is issued person by person to people outside the firm, and it stays yours to withdraw.
A reading history
Opens, dates, session length, and downloads, recorded against each recipient as they happen.
Tied to the relationship
A room belongs to the investor, fund, deal, or engagement it serves, so its activity lands beside the rest of that history rather than in a separate tool.
An account of it afterwards
Grants, withdrawals, and reading history stay available for internal review long after a room goes quiet.
ENGAGEMENT, PLAINLY DESCRIBED
What does the engagement record show?
Counts and timestamps. Which named recipient opened which document, on what date, how long the session ran, and whether anything was downloaded. Which parts of a collection were visited, and which were passed over. Balau AI reports that activity as raw counts and stops there.
Read plainly, that is useful on its own. A recipient who has returned to the same document three times is worth a call before one who has opened nothing at all. Your team draws that conclusion; the product supplies the activity behind it.
Where AI helps, summarising a document set or preparing a follow-up for someone to review, personal identifiers are redacted before AI processing, and whatever comes back can be traced to the permitted sources it was built from.
Share, track, analyze. Not transact.
A data room is somewhere to put documents in front of people and see how they were read. It is not a transaction surface.
No commitments, no money
Nothing a recipient sees asks them to commit capital, subscribe, or move funds. There is no such control on the page, because that is not what this is.
Counts, not scores
Engagement stays raw activity. Balau AI does not rank recipients, grade interest, or forecast what anyone will decide.
Your judgment, not ours
Balau AI does not provide investment advice and does not execute transactions. What the activity means, and what to do about it, stays with your firm and its advisers.
ACCESS, GRANTED AND WITHDRAWN
Let people in by name. Close the door the same way.
Letting somebody outside the firm see confidential material is an act with a beginning and an end. Balau AI treats it that way, and keeps both.
Someone inside the firm invites a named person to a specific collection. The invitation reaches that collection, not everything the firm holds.
Access follows firm roles and data permissions, so nobody can hand out sight of material they were not permitted to see themselves.
Consequential actions require human approval. A person decides who is let in, and access never widens on its own.
Access can be withdrawn at any point. The route the recipient used into the material closes.
The grant, the reading it produced, and the withdrawal all survive. Ending access ends the access, not the evidence.
WHY A ROOM, NOT A LINK
Why not just send a link?
A shared link is a door with no memory. Once it leaves your hands it travels, and it tells you nothing about what happened on the other side of it. A room keeps a recipient list you control by name, a reading history recorded as the reading happens, and a line back to the relationship the documents belong to.
The practical difference shows up late, when a reviewer, a counterparty, or your own counsel asks what a particular person was given sight of, and when. With a room, the answer already exists, because it was written down while the work was being done instead of assembled afterwards from memory and inboxes.
Rooms are part of the wider platform rather than a product bolted beside it, so the same permissions, the same approval step before anything consequential happens, and the same activity history apply to a document you sent an investor and to the work your team does around it.
Data rooms are available on selected plans. How the platform protects what you place in one, and where our security and privacy programs currently stand, is set out on the security page.