Compliance

For a workspace that posts under rules: a bank, a broker, an insurer, an estate agent or a mortgage broker, a pharmacy, a manufacturer, a council. Reelwire covers it in five steps, each closing a door the one before leaves open:

1. The content carries what the rules ask for. The templates for regulated markets take the required lines as fields of their own and will not render without them, and the ready-made feeds word their notices in code.
2. A person checks each post before it goes out, on the channels where you ask for it.
3. What went out is proven afterwards, in a sealed record an auditor checks without Reelwire.
4. Everything can be stopped at once, and kept quiet for periods you set ahead.
5. Only the right people get in, each with what their job needs and nothing more.

This page goes through them in that order, says where each one is set and on which plan, and links to the manual page that explains it in full.

Where everything is

What	Where	Plan
Compliance lines in the templates	The template's fields, in Clip studio, the Post composer and what your system sends to a custom feed	Every plan
The brand's lines on every clip and beside every post	Brands, Settings, under Localizable properties: Texts on the clip, Outro video and Post text	Every plan
How a feed is made, its languages and its disclaimer	Ready-made feeds: Type and Language in All details, and the language chosen when the feed is added to a channel	Evergreen on every plan, Live data from Individual, Official data on Enterprise
Approval before a post goes out	Channels, Settings, Approval; decided on Posts, in the Approval column	Small business and Enterprise
Never the author, and two approvers	Compliance, Approval rules	Enterprise
The sealed record, its export and checking a video	Compliance, Compliance record and Entries	Enterprise
Who did what	Compliance, Audit log	Enterprise
People from outside who only read	Compliance, Auditors	Enterprise
Who may do what	Team: Operations, Approvals, Administration	Small business and Enterprise
Every channel held at once	Stop everything, under Publication	Every plan
Silences set ahead	Stop everything, Planned silences	Enterprise
A code from a phone at sign in	Profile, Two-factor sign-in	Every plan
The data processing agreement, where the data is kept, accessibility	The website's footer, under Legal	Everybody

1. Content that carries what the rules ask for

The templates' compliance lines

The template packages made for regulated markets take what their rules ask for as fields of their own: a risk warning, a legal line, a disclosure, a licence line, a representative example, the mandatory text beside a medicine, who issued a notice. Three things hold for every one of them:

• On screen from the first frame to the last. A clip is often seen from its middle, or as a still on a platform's grid, so the line is in every frame, in a place of its own that nothing is drawn under.
• Never cut. A long line is set smaller and then on more lines. It is never shortened, and never runs off the frame.
• Your words. Reelwire never writes what your regulator asks for: the template draws what it is sent, in the language it is sent in. Each field's description says what it usually holds, such as the CFD warning or "Always read the label."

Where the rules always ask for a line, its field is required, and content without it is refused with the field named, before anything is rendered: by Validate input and Render video in Clip studio and by saving a post in the Post composer. Data your system sends to a custom feed without it makes no post on a channel whose template needs it, and the answer to the call says so. A clip without the line is never made, so it cannot go out. Where a line depends on what a post says, such as a medicine named in one tip and not in the next, the field is optional and its description says when to send it.

Package	The line, on every frame	Required
Finance (Brokers and trading)	Risk warning, in a framed strip with a warning mark.	Optional in every variant, because whether a post needs one is your regulator's call: send it with every post that does.
Finance (Banks)	Legal text, such as what a rate means and how deposits are protected, under a hairline.	Optional in every variant. Representative example requires the representative APR and two to eight lines of the example.
Finance (Insurance)	Disclosure: who the insurer or agent is, the licence and where it applies, that cover is subject to the policy's terms, conditions and exclusions.	Required in Premium example, Cover comparison and What is covered, the variants that show a price or a cover; optional elsewhere.
Finance (Real estate)	Brokerage, your licensed name, in the header and never less than half the size of the contact line; Disclosure, the licence and the statements, above the footer line.	Brokerage in every variant; Disclosure optional.
Tech and industry (Software and SaaS)	Footnote, such as trademarks, "Prices exclude VAT" or the conditions of a figure.	Footnote optional. Required where a claim needs its basis: how a figure was measured in Case study, Feature launch and Uptime report, with the period in Uptime report; the date in Release notes and API change; the identifier in Security advisory; the time zone in Webinar.
Tech and industry (Hardware and electronics)	Footnote, such as how the figures were tested, that results vary, that a screen is simulated.	Footnote optional. Required: the test condition beside every measured figure in Battery life, Product launch, Spec sheet and Compare models; the date in Firmware update; the terms in Warranty.
Tech and industry (Manufacturing and industry)	Footnote, such as the legal entity, the standard or how a figure was measured.	Footnote optional. Required: the period of a safety or quality figure in Safety days, Quality rate and Machine uptime; each certificate's number and expiry in Certificates.
Public bodies (City councils)	Issued by, the department or office, with an optional Reference.	Issued by in every variant; the reference in Public notice; the source and period of every figure in City in numbers. Warning requires the level and the hazard, drawn in the colours people know from the weather services (yellow, orange, red and violet), never the brand's.
Real estate (Estate agents and realtors)	Licence, the agency's licence or registration line, in the imprint; Disclosure under it.	Licence in every variant; Disclosure optional. Every listing's price or rent and its energy class ("Exempt" where none is needed); in Energy certificate, the certificate's kind, its figure and the energy source, as German adverts ask; the period and source of every chart.
Real estate (Mortgage brokers)	Legal, who you are, who regulates you with your number, and the risk warning; the Representative example with it, at the foot.	Legal in every variant. The representative example in every variant that shows a rate (Rate table, Fixed or variable, Payment examples, Representative example, Rates over the year, Loan to value explained), and every rate with its APR; the period and source in Rates over the year.
Pharmacies (Community pharmacies)	Mandatory text, on a plain card beside a leaflet mark, larger than the brand's footer line.	In Offer of the week; to be sent in any other post that names a medicine. The source and period in Pollen forecast and UV index.
Pharmacies (Pharmacy groups and cooperatives)	Mandatory text, on a plain strip.	In Offers, Recall notice and Supply notice; to be sent wherever a medicine is named. A health figure's source in Cold and flu, Recall notice and Supply notice, and its period in Cold and flu.

Prices, rates and figures are drawn exactly as sent, with the decimals they were sent with, never recalculated or rounded by the template. Every field of every variant, with what it holds and how long it may be, is in the variant's version page in the Catalogue, under its schema.

A new post starts from the template's example, its example warning or disclosure included, so you change what is there rather than start from nothing. Replace it with your own words before the post is saved: the example is a placeholder, not your regulator's text.

The brand's own lines

Two things a brand adds to everything it wears, both in its Settings under Localizable properties, in every language the brand speaks (Brands):

• Texts on the clip: two lines at the top and two along the bottom, drawn by every template. The bottom lines suit what every clip of the brand must carry, such as the company's registered name.
• Post text: a description, hashtags and a link that go beside every post, never on the clip, 300 characters in all. A webhook receives the description as the post's disclaimer.

An end card can carry a notice too: the Outro template has a Legal line, such as a risk warning or terms, set small but readable at the foot. Made from the brand's Outro video row with Create one with Reelwire and switched on, it closes the brand's clips (Background, stinger, intro and outro).

Ready-made feeds: how they are made, their languages and their disclaimers

Every ready-made feed says how its content is made, under Type in its All details (Ready-made feeds): Evergreen (written once with AI, reviewed by a person), Live data (new data on every run, its wording possibly polished and translated by AI) or Official data, no AI (straight from the authority or licensed provider, wording and languages fixed in code, no AI at any step). For a regulated account, Official data is the safe choice, and it is part of Enterprise.

Languages matter the same way. A feed with its languages named comes in those alone, every one written by the feed's own code; a Multi-lingual feed is translated by AI into the language you choose, which suits most uses but may change the wording of something a regulator cares about. Where a post must be compliant word for word, choose a feed with its languages named.

Some feeds carry a disclaimer, written by Reelwire's code rather than by AI, on the clip after the source line and at the end of every description that has room for it: "Not financial advice." on the finance feeds, "Not medical advice." on the health feeds, and the others listed under Disclaimers.

For a feed's post, the compliance record keeps what Reelwire's AI steps did to it, step by step, beside everything else that went out.

2. A person checks before it goes out

Approval is set per channel: open the channel's Settings under Channels and set Approval to "Every post, by hand". From then on nothing on that channel is handed over, by email, webhook or platform connector, until somebody holding the Approvals permission approves it on Posts, in the row's Approval column. They are emailed when posts start waiting, at most once an hour.

• A change waits too. An update to a post that already went out is held for approval like the post was. A request to delete one is never held: taking something down publishes nothing.
• Approvals grants no editing. A compliance reviewer with Approvals alone approves and rejects, and cannot change a channel, a brand or a source.
• Only Approvals switches it off. Anybody who edits channels can ask for approval; switching it off needs Approvals, so whoever makes the posts cannot remove the review on them.

On Enterprise two more rules apply, on the Compliance screen's Approval rules card: nobody approves their own post or change, and a channel can ask for two approvers, two different people holding Approvals, before a post goes out.

All of it is in Approvals.

3. Proof afterwards: the compliance record

Approval says somebody checked. The compliance record proves it, years later, to somebody who was not there. From the moment a workspace is on Enterprise, with nothing to switch on:

• Every hand-over is an entry per channel: the video's fingerprint and three frames of it, the text in every length, the template, its variant, version and build, where the content came from and who wrote it, what AI did, who approved it, and the ways it went out. Every decision, delivery outcome, report and change to an approval rule is an entry too.
• Sealed three times: each entry is linked to the one before, signed by Reelwire, and covered once a day by an outside time-stamping authority, so nobody, Reelwire included, can change one unseen.
• Exported for an auditor: Download export for an auditor gives a report to read and the records with a script that checks every seal on any computer, without asking Reelwire.
• Check a video: which post a file is, by its fingerprint. Keep the files Reelwire hands over to you: a copy downloaded from a platform never matches, because platforms re-encode what they publish.
• The audit log: everything people and API keys did, from settings and permissions to approvals, exports, stopping everything and switching two-factor sign-in on or off.

Every entry is kept ten years. A workspace that leaves Enterprise keeps its record 90 days more, for a last export.

4. Stopping everything

Stop everything, under Publication, holds every channel of the workspace at once, on every plan: no new post is made, nothing already handed over leaves, and scheduled posts wait until you resume. A request to delete still goes out, because taking something down is often what a crisis needs most. It can be pressed by whoever holds Operations or Approvals, so a compliance reviewer can stop what they may not edit, and every screen says so while it holds.

On Enterprise, planned silences do the same for periods set ahead, such as a quiet period before a company's results or a council's pre-election period. Stopping, resuming and every planned silence are lines in the audit log, with who. See Stop everything.

5. Who gets in

• Permissions, not roles. On Team, each colleague holds Operations, Approvals, Administration or any mix, and none reaches round another: somebody who operates cannot switch approval off, and an administrator cannot give an API key the right to approve unless they hold Approvals themselves. An AI assistant's connection approves nothing unless the person connecting it switches that on.
• Auditors read the record, its export, the audit log and the rest of the workspace, and change nothing. They take no seat, a workspace has at most five, and they are locked out the moment it leaves Enterprise (Auditors).
• Two-factor sign-in asks a code from an authenticator app after the password, on every plan. It is each person's own choice on their Profile: ask everybody who holds Approvals or Administration to switch it on. Every switch is emailed to the person and kept in the audit log.

The paperwork

Three documents on the website, in the footer under Legal, are what a compliance or procurement team usually asks for first:

• the Data Processing Agreement, under the GDPR's Article 28, part of the terms, so there is nothing to sign;
• Hosting, where your data is kept;
• Accessibility, how the product meets WCAG and where it falls short.

What people get wrong

"The template refused my post." It is missing a line its rules require, and the message names the field. Add your own words there and render again.

"Reelwire should know our risk warning." It does not write one: the words are yours, and they change with your regulator, your product and your country. Put them in the post, or in the data your system sends, every time; a post list's post can be reused with them already in it.

"Approval is on, so we are covered." Approval stops a post until somebody looks. Proving later who looked, and what exactly went out, is the compliance record, which is Enterprise's.

"The time stamp on our newest posts is missing." Entries are sealed and signed within seconds, and the next daily time stamp covers them.