Questions before beta access.

Redcliffe is a compliance intelligence platform for regulated content. It helps teams review, draft, and update marketing material against source-linked obligations, with issue flags, suggested fixes, and an audit trail.

Redcliffe is operated by REDCLIFFE CONTENT PARTNERS LTD, a company registered in England and Wales under number 15880789. Registered office: 21 Dwyer House, 2 Townmead Road, London, England, SW6 2NZ.

The current beta covers the UK Financial Promotions Model and the UK Gambling, Betting and Gaming Promotions Model. UK financial promotions includes COBS 4 investment-promotion coverage, UK cryptoasset-promotion, UK finfluencer/social-media promotion, retail banking and insurance promotion overlays, and promotion-facing SDR sustainability-label coverage. US financial promotions are in build; US gambling, betting and gaming promotions remain planned.

A Redcliffe compliance model combines a jurisdiction, a regulated content category, source-linked obligations, and a governed release record. For example: the UK Financial Promotions Model, the planned US Financial Promotions Model, or a gambling, betting and gaming promotions model. Environmental and sustainability claim rules are added inside those models where they affect the regulated content.

Yes. Governed model source sets are monitored for regulatory source changes. Changes are flagged for review and can feed the next governed model release; they do not silently rewrite the active model or a customer's approval record.

Not at this stage. UK cryptoasset promotions are included in the UK Financial Promotions Model beta because the relevant rules sit inside the UK financial-promotions regime. We may split it commercially later if customer use supports that.

It is shown as the UK Finfluencer and Social-Media Promotion Model because teams search for that problem directly. It is included in the UK Financial Promotions Model beta because the review still sits inside the UK financial-promotions regime.

Yes, where the claim is part of a UK financial promotion. Financial-product sustainability claims, anti-greenwashing, and promotion-facing SDR label, naming, marketing, and consumer-facing disclosure checks are included in the UK Financial Promotions Model beta. Broader environmental claims are handled as sector-specific overlays inside the relevant model, not as a standalone generic model for now.

Redcliffe is built for compliance teams, legal teams, law firms, agencies, and marketing leads who need repeatable review records for regulated content rather than loose suggestions.

General-purpose tools can help produce polished drafts, but regulated content also needs source-linked obligations, risk flags, fixes, approval history, and release governance. The Why Redcliffe page explains the distinction.

The product is designed around practical content inputs: text, documents, URLs, and static images or screenshots. Static creative review is beta evidence support: it helps Review assess visible text, layout, prominence, imagery, CTAs, and proof signals, but video is not included and publication approval stays with the customer.

No. Redcliffe is designed to improve the quality, speed, and record of content review. Publication decisions and required approval workflows stay with the customer, their approvers, and their professional advisers.

Findings and drafts are tied back to source-linked obligations. The product is designed to preserve context, cited sources, reviewer actions, and approval history so a team can understand how a decision was reached.

Beta requests and customer workspaces are handled through Redcliffe's access-controlled systems. Customer content is processed to provide the service and is not used to train public foundation models.

Compose has an explicit web-search option for briefs that need current market facts. When search is off, Redcliffe works from the selected compliance model, project context, and user-provided facts.

We review the request, check fit for the current beta or future coverage, and follow up with next steps. Approved beta access normally starts as a 30-day evaluation period. We can extend access for active testing partners where useful.

Yes. The pricing page shows the current beta packaging, with Essentials, Pro, Team, and Enterprise options. Paid subscriptions are being wired through Paddle; during beta, access is still managed through a 30-day evaluation period so we can validate usage, model access, and team workflow.