Social media records for public records requests.
When a request names your social media, the record should already be waiting. Search your connected accounts by date, channel and keyword, review posts with their comments and replies, and export the responsive set. What gets released stays your decision.
30-day free trial · no credit card · unlimited accounts and users
From request received to records produced.
The clock starts the moment the request lands. Three steps, one archive: no screenshot hunts, no asking the platform, no discovering too late that a post was deleted.
Search the archive the way the request is worded.
Requests arrive as dates, topics and account names. Search your connected accounts the same way: set the date range, pick the channels and authors, then narrow by keyword until the candidate set matches the scope of the request.
- Date-range filters that match the request window
- Channel and author filters across your connected accounts
- Keyword search across posts, comments and replies

Review posts with their comments and replies.
A post on its own is half the story. Brolly keeps supported posts together with their comments and replies, and keeps captured edits and deletions from connected accounts, so reviewers see the conversation the requester is asking about, including versions that no longer appear on the platform.
- Conversation context kept with every captured record
- Edited and deleted content included where captured, with timestamps
- Review before release: exemption and redaction decisions stay with you

Export a package built for scrutiny.
Export the responsive set with its available metadata, digital checksums and audit history, in formats designed to support evidentiary review. Brolly does not decide exemptions, redactions or release; it hands your reviewers a set they can stand behind.
- PDF, CSV, HTML and JSON export formats
- Digital checksums on exports; metadata and audit history on records
- Cross-team handoff: records finds, communications confirms, legal clears

Why the production holds up.
Requesters and reviewers ask questions a screenshot cannot answer. The archive can.
The conversation stays whole
Posts are kept with their comments and replies, so a produced record shows the exchange the requester asked about, not an isolated message stripped of what people said back.
Edits and deletions included
Supported edits and deletions from connected accounts are captured with timestamps, so content that changed after publishing can still be reviewed and, where responsive, produced.
Metadata and checksums
Records keep their available metadata and audit history, and exports carry digital checksums, so a reviewer can verify that the package they received matches the export that was made.
Review and release are yours
Brolly narrows the responsive set and gives reviewers context. Exemptions, redactions and the decision to release remain your responsibility, made under your state’s law with counsel.
The rest of the records picture.
Responding to requests is one obligation. Here is how it connects to the others.
The social media archive
How capture works: supported posts, comments, edits and deletions from connected accounts, preserved in near-real time with search and export built in.
Explore the archiveSocial media recordkeeping
Requests are the moment of truth; retention is the everyday obligation. How agencies keep social media records under their schedules, long before anyone asks.
See recordkeepingState-by-state requirements
Statutes, response expectations and oversight bodies vary by state. Our government hub covers all 50, with a dedicated guide for each.
Find your state’s requirementsProducing for requests is one part of official channel governance: coverage, record, access and activity evidence across the channels your organization owns.
Asked by records officers with a deadline.
Do deleted posts and comments count as public records?
How fast can we produce responsive records?
Who decides what is exempt or gets redacted?
What does an export include?
Is this the same thing as FOIA?
Be ready before the request arrives.
Connect your accounts in minutes, and the next request starts with a search instead of a scramble.