A post is a record
R.C. 149.43 defines a record by what it documents, not where it lives. If a post describes a decision, a service, a closure or an operation, it is doing the same work as a memo and carries the same obligation.
Your office’s Facebook posts, replies and comment threads document public business, which means they fall under the same retention rules as your email. Most offices find that out during a records request. Here are the rules, in one place, written plainly.
Six things Ohio offices consistently discover late, usually during a records request.
R.C. 149.43 defines a record by what it documents, not where it lives. If a post describes a decision, a service, a closure or an operation, it is doing the same work as a memo and carries the same obligation.
Comment threads, replies from your account, edits and reactions are part of the record. A capture that saves the original post and drops the conversation around it leaves out the part people usually ask for.
A screenshot holds one moment with no metadata, no thread and no edit history, and it only exists if someone remembered. That is a habit, not a system, and it will not survive scrutiny.
Removing a post does not remove the retention obligation, and it can create a second problem on top of the first. An archive preserves what was posted even after it comes down.
Removing comments or blocking constituents on an official account raises First Amendment questions. The Supreme Court set out when an official’s account activity counts as state action in Lindke v. Freed (2024). A written policy applied consistently is the protection.
Most offices do not need a new policy. The records retention schedule your commission already approved almost certainly reaches this content. The gap is capture, not paperwork.
Whatever tool or vendor you use, these are the requirements a records officer ends up needing.
Automatically, through the platform’s own connection, as things are posted. Anything that runs on a schedule or depends on a person remembering will have gaps, and the gaps are what get asked about.
The post, the replies, the comments, the images, the timestamps and the edit history. A record stripped of its thread answers a different question than the one being asked.
By date, account and keyword. An archive nobody can search is a box in a basement, and a ten-day records deadline does not leave room to scroll.
Your records officer has to hand something to a requester or an attorney with the metadata intact. Ask any vendor to show you an export before you sign, not after.
I’m Crissy Devine. I build and maintain websites for Ohio county offices, townships, villages, courts, transit authorities and family & children first councils. This question kept reaching me from clients, and the answers were scattered across statutes, retention schedules and case law with no plain-English version anywhere.
Web Chick does not sell social media archiving. I am not trying to sell you anything on this page — I just got tired of watching records officers find out about this the hard way.
Crissy, Web Chick
Based in Fairfield County, working with agencies across Central and Southeast Ohio and remotely with public entities statewide.
Generally yes. Under the Ohio Public Records Act (R.C. 149.43), a record is information kept by a public office that documents its organization, functions, policies, decisions, procedures, operations or other activities. The format does not matter. A post, a photo caption, a reply and a comment thread on an official account can all meet that definition, which means they fall under your approved records retention schedule the same as an email or a memo.
There is no single statewide number. Retention is set by your own records retention schedule, approved by your records commission under R.C. 149.38 through 149.412. The practical step is to classify social media content against the schedule you already have, then make sure the capture method actually holds it for that long. Most offices find their existing schedule already covers the content and the gap is capture, not policy.
Be careful. Deleting content that qualifies as a record can conflict with your retention schedule, and removing or blocking constituents on an official account can raise First Amendment questions. The U.S. Supreme Court addressed when a public official’s social media activity counts as state action in Lindke v. Freed (2024). The safe pattern is a written policy, consistent enforcement, and an archive that preserves what was posted even if it later comes down.
Not in any practical sense. A screenshot captures one moment, loses the metadata, the thread and the edit history, and depends on someone remembering to take it. If a records request or a lawsuit arrives, you need the full record with timestamps and context, not a folder of images. Continuous automated capture is the difference between having an archive and having a habit.
Personal accounts are generally outside your archive, but the line moves when an employee or elected official uses a personal account to conduct public business. That is precisely the situation Lindke v. Freed dealt with. The workable answer is a policy that tells staff which account to use for official business, so the record lands where you can retain it.
Most use a dedicated social media archiving service that connects to the account through the platform API and captures posts, replies and edits continuously. Web Chick does not sell or resell archiving. This page exists because the offices we build websites for kept asking what the rules were, and the answers were hard to find in one place.
This page explains how records rules generally apply to social media. It isn’t legal advice — your records commission and legal counsel set your schedule.
If it saved your office an afternoon, that was the point. What Web Chick does build is accessible, ADA Title II compliant websites for Ohio public entities — if that is on your list, the door is open.