easyRechtssicher Rechtstexte

By easyrechtssicher

0+ active installationsVersion 2.1.0

Display maintained German website legal texts using page assignments, a block or shortcodes, with optional local storage.

Description

easyRechtssicher connects a WordPress website to legal texts configured for that website in the easyRechtssicher service. Supported document types include a privacy policy, imprint, withdrawal information, email signature and social media privacy information, subject to the registration and service plan.

Choose the target page in Settings > easyRechtssicher, insert the Gutenberg block, or use a shortcode such as [easyrecht type=”dse”]. Existing Elementor content and page layouts are retained. Elementor is optional; the normal integration also works without a page builder or an AI assistant.

The service supports German business projects. English output requires an available English document version. Availability in other countries does not imply support for every jurisdiction. The plugin does not generate replacement legal wording with a language model and does not guarantee legal compliance.

Optional local delivery

An administrator can enable local document storage. This requires the website’s own registration key (ers_live_ or ers_test_), matching registration ID and registered website domain. Do not put an agency-wide key in a customer website. Older legacy keys remain usable with the existing widget where supported, but cannot authenticate the local Agent API path.

The plugin checks the key-to-registration and domain relationship before downloading documents. Successfully downloaded HTML is filtered through WordPress’s allowed post HTML and stored in the local database. Frontend display in this mode needs no external widget request. German documents are fetched by default; English is a separate option and never silently receives German text instead.

WordPress checks for updates through its hourly WP-Cron schedule and administrators can request a refresh. The timing depends on site traffic and the site’s Cron configuration. Existing page/CDN caches may delay visible updates and must be refreshed through their own controls.

When an update fails, the last successfully checked matching document remains visible with a warning. A warning also appears after more than two hours without successful verification. A missing English document does not label a freshly checked German document as unverified. If no matching local copy exists, a clear availability notice appears. Changing the key, registration or website domain does not reuse a previous customer’s cached text.

An access error is not proof that a contract has ended. Service terms govern permitted static use and update entitlement. The explicit stop-and-delete control removes local copies and disables this refresh schedule; ordinary plugin deactivation removes its schedule and retains stored data.

Agency tools

Administrators can opt in to three WordPress Abilities on supported WordPress versions (6.9+): easyrecht/inspect-page, easyrecht/prepare-binding and easyrecht/apply-binding. All are disabled by default and require administrator permission. A compatible MCP adapter can expose them to an agency’s agent.

Inspection reports hints from stored page content and Elementor data. It is not a complete site, consent or network scanner. An installed plugin is not proof that a service is used. Unknown operator details, hosting arrangements and business practices must be clarified. Applying a prepared binding requires explicit confirmation and changes the page assignment; it does not publish pages or write an ERS customer profile.

The separate existing agency REST API requires its own authorised account. Profile replacement and factual confirmation must be handled by the authorised agency/customer. Unsupported AGB or unknown legacy document requests never silently return a privacy policy.

External service and privacy

The GPL-licensed plugin code is separate from the paid easyRechtssicher service. A valid registration and the appropriate service rights are required for document access. This plugin does not place orders or make purchases.

In the default widget mode a visitor’s browser connects to https://easyrechtssicher.de for the selected registration ID, document type and language. As with normal HTTP connections, that service receives the visitor’s IP address, user agent and potentially origin/referrer information. A JavaScript-free iframe fallback is provided. A same-origin enqueued loader loads the service’s widget script for each individual instance.

In local mode WordPress sends authenticated server-side GET requests to https://easyrechtssicher.de/api/v1/registration/resolve and /api/v1/agent/documents. The registration key is transmitted as a Bearer header over HTTPS, with the website domain for matching. No key is placed in public HTML. Local documents are not sent to another service for AI processing.

The private distribution also checks easyRechtssicher’s authenticated plugin-update endpoint. The separate WordPress.org distribution uses the standard directory update channel instead. Existing installations are not silently switched between channels.

Service terms: https://easyrechtssicher.de/agb
Service privacy policy: https://easyrechtssicher.de/datenschutz
API information: https://easyrechtssicher.de/agent-api

Installation

  1. Install and activate the plugin.
  2. Open Settings > easyRechtssicher and enter the key from your existing customer portal account. The registration ID is resolved automatically; verify that the domain matches.
  3. Select the target legal-text pages, insert the block, or add [easyrecht type=”dse”] and [easyrecht type=”impressum”].
  4. To enable local delivery, use a registration key, select local storage, save, and request the first refresh. Check the per-document status.
  5. Leave the agency abilities disabled unless your authorised administrator explicitly needs the agent integration.

The plugin works on self-hosted WordPress. A listing on WordPress.org is a distribution channel, not a hosting requirement. WordPress.com installations require a plan allowing plugins; this release has not been independently tested on WordPress.com. A directory listing does not guarantee a recommendation by an AI assistant.

FAQ

Where is my key?

Use your existing account at https://easyrechtssicher.de/portal/api-keys. A read-capable registration key does not grant agency profile-writing permission.

Does this work with Elementor or the Classic Editor?

Yes. Use page assignments or shortcodes. The Gutenberg block is available in the block editor. An official Elementor MCP/Angie integration is a separate compatibility question and is not implied by ordinary Elementor rendering.

Which shortcodes are supported?

Use [easyrecht_link type=”dse”], [easyrecht_link type=”imp”] or [easyrecht_link type=”wbl”]. Add lang=”en” for English. The include names are [easyrecht_dse_include], [easyrecht_imp_include] and [easyrecht_wbl_include].

Which old shortcodes are supported?

Legacy shortcode aliases are available only in the private package, provided another plugin has not already registered those names. Unsupported types produce an explicit notice.

Are texts available during an outage?

With local delivery enabled and at least one successful matching download, the last checked text is retained with a warning. Default widget delivery depends on the service being reachable.

Changelog

2.1.0

  • Optional local documents, conditional refresh, availability warnings and explicit deletion controls.
  • Administrator-only, opt-in agency inspection and confirmed page-binding abilities.
  • Unsupported document types are not substituted with a privacy policy.
  • Widget resources are enqueued and separate instances retain their own targets.
  • Separate private and directory builds, with no automatic customer channel migration.

2.0.12

  • Detect translated page languages for the block and shortcodes. Explicit German/English selection takes precedence.

2.0.11

  • Add links to edit the connected registration’s documents in the customer portal.

2.0.8

  • Add automatic document-to-page assignments while retaining blocks and shortcodes.

2.0.0

  • Gutenberg block, widget embedding and legacy shortcode support.