Social Media Policy Generator
Generate a company social media policy covering brand voice, confidentiality, disclosure, approvals and crisis escalation.
What is Social Policy?
A social media policy generator. It tells staff what is expected when they post for the company or about it, including the approval process for anything sensitive and the escalation route for a developing crisis — while making clear that it does not stop anyone speaking about their own working conditions, which is what makes the policy defensible.
How it works
The guidelines you select become the behaviour rules — brand voice, confidentiality, respectful engagement, disclosure of affiliation, copyright, crisis escalation. The approval, monitoring and personal-account sections are added only when switched on, and the monitoring section states the response-time commitments and, explicitly, that individual employees are not being surveilled.
- Fill in the details the document needs. Business name, jurisdiction, dates, the clauses that apply to you. Nothing is uploaded and no account is created — the form is the only input, and the document is assembled in the page.
- Watch the blanks, not just the text. Any field you leave empty appears in the document as [[a highlighted marker]], and the panel above the output lists exactly which blanks are left. A half-finished policy should never look finished.
- Copy or download, then have it reviewed. Copy the document to the clipboard or download it as a .md file named for what it is. Every page states the same thing: this is a template, and it needs a qualified lawyer's eye before you publish or sign it.
Examples
A privacy policy for a side project
A solo developer shipping a newsletter signup needs a policy that says what is collected, why, and how to ask for deletion. Selecting the categories actually collected — rather than copying a competitor's list — takes two minutes and produces a document that is true.
Terms of service with a real liability cap
The liability clause is written from a number you supply instead of being left as "our total liability is limited to [amount]". A cap that is never filled in is a clause no one can rely on.
A DMCA notice a provider will actually action
A takedown that is missing the URL of the original work, or the statement under penalty of perjury, is one the service provider is entitled to ignore. Every required element appears in the generated letter, in the order the statute describes.
A DPA for a new vendor
Processors, security measures, breach notification window, transfers and audit rights as one document, with the subprocessor and SCC clauses switched on because this vendor uses both.
Common mistakes
Publishing a template without reading it
A policy that promises something you do not do — deleting data on request within 30 days, or never sharing data with third parties — is worse than no policy, because it is a documented misstatement. Read every clause against what actually happens and cut the ones that do not apply.
Assuming one document covers every jurisdiction
A privacy policy written for the UK does not automatically satisfy California, Brazil or Canada, and an employment clause that is standard in one country can be unenforceable in another. Name the jurisdiction you are actually writing for, and check the rules that follow from it.
Bundling consent and calling it consent
A single "I agree" covering marketing, analytics, photographs and treatment is not valid consent under most regimes, because consent has to be specific and separately given. Use one form per purpose, and never pre-tick the optional boxes.
Leaving the blanks in after generating
The marker can be more subtle to spot in a document than on the page — search the pasted text for the bracket characters before publishing, or use the missing-field list to confirm it is empty.
Frequently asked questions
Can a policy restrict what employees post on personal accounts?
Only within limits. Protected speech about working conditions cannot be restricted in many jurisdictions, and blanket monitoring of personal accounts is a privacy problem. A policy that covers harassment, discrimination, disclosure of confidential information and genuine reputational damage is on firmer ground than one that prohibits criticism.
Who should approve a sensitive post?
Someone senior enough to say no, named in the policy rather than described as "management". A named approver, a full business day for review, and a rule not to publish when no one is available to respond covers most of the ways a social post goes wrong.
Should the policy mention deletion of critical comments?
It should say you do not delete legitimate criticism, because that is the rule staff will be asked to break under pressure. Content that is unlawful, spam, or contains someone else's personal information can be hidden or reported, and saying that plainly keeps the moderation decisions consistent.