Light bulb in the Kreativbar logoKreativbar – spirits of marketing
Solution finder

Websites & privacy / eRecht24

Maintaining website notices with eRecht24

A booking form is added to the site. The service changes, while the published privacy notice still dates back to the previous relaunch.

Selecting privacy settings on a tablet
Example workflow Update website notices
Starting point
New booking form recorded in project
Result
Updated privacy notice ready for review

Why we recommend eRecht24

eRecht24 provides project-specific legal texts and a website integration. Kreativbar uses this integration in its own web project for German and English notices.

How it helps your team

Maintain the services used in your project and publish the updated notices on the site. At the next redesign, check that the information matches the features actually in use.

Follow a booking feature beyond the visible page

A website introduces registration for free training. Visitors see a name, an email address and a date. Behind the form there may be a database, a confirmation email service and a calendar entry. Before changing the eRecht24 project, trace what actually happens with the people responsible. Make an inventory of services and their roles. A provider name alone seldom explains which information is processed in which situation.

Then work backwards. Open the published privacy notice in every offered language and compare its description with the current form. A successful synchronisation shows that a text was transferred. People still need to assess whether its underlying facts are accurate. Record unresolved questions precisely enough for a qualified reviewer to investigate. Where responsibilities between a business and a supplier are unclear, actual data flows and contracts provide a more useful starting point than wording copied from another website.

Build a service inventory for editors

List the features visitors actually use. Start at the homepage and follow common journeys such as an enquiry, newsletter subscription or event booking. For each feature, record its internal owner, the service involved and where the configuration is documented. Separate active services from past experiments. An old provider account does not necessarily mean that service still runs on your site. Conversely, an embed may initiate a connection as soon as someone opens an article.

Use the inventory to maintain the eRecht24 project deliberately. When editors introduce a form, they can see who supplies technical details and who reviews the substance. Connect the check to your normal publishing workflow. A prompt when a relevant feature changes is more practical than reconstructing a year of changes afterwards. Store evidence and agreements in the appropriate internal location so unresolved questions can be assessed against the correct material.

Deliver notices in your design at the right address

Integration requires the content and its location to match. Visitors often arrive through the privacy link next to a form checkbox. Test that exact route, including the expected language, site navigation and return journey. A link to a previous domain may look correct while showing an obsolete version. Test direct visits from saved addresses too. A working link in the administration interface cannot replace checking the public route.

Keep a short publishing note for those responsible. Record which project detail changed, which pages were affected and who checked the result. This makes later issues easier to isolate. Define who arranges individual review when difficult substantive questions arise. The integration’s value is dependable publication of reviewed material and less manual copying. Accurate input remains a separate responsibility.

What belongs in a handover note for the website editor?

An agency implements a new contact form. The project owner understands its purpose, the technical team knows the data flow and the editor maintains the wording. Ask each party to answer a specific question for handover. Which fields are optional? Which system receives the enquiry? On which language pages does the form appear? Add the answers to the inventory before the responsible person reviews the inputs in the eRecht24 project. Keep technical details nobody can verify visible as outstanding work.

After approval, test the published site. Open the link beside the form on a phone, switch to the second language and return to the form. Record the version actually displayed and its date. A successful backend synchronisation helps an English-speaking visitor very little if only the German page changed. Name someone who will check publication in both languages and report the outcome to the editor.

Three tests for your pilot

Inventory a form from two perspectives

Complete a test booking and describe every visible field. Independently ask the technical team to list the systems involved. Compare the two results. An email provider or calendar function may appear only on the technical list. Resolve the missing information with the owners before updating the provider project.

Trace a change in two languages

Change a verifiable detail in a test project, such as a contact method. Check both published language versions, including links from forms and the footer. Record time and outcome. This enables separate investigation of translation errors, stale cached versions and incorrect destination paths.

Rehearse a failed update

Discuss how the team would notice a failed transfer. Check which version remains visible and who verifies it. Tell the responsible person where to find the last reviewed version. A technical success message and substantive approval should each be identifiable in the handover record.

Preparing your team to use the tool

Plan publication and later corrections together

Follow the finished version to the place where it is actually used. A preview in the workspace may be correct while a public page, emailed attachment or portal link still points to an earlier version. Agree on acceptance at the end of the full route. Open the result with access equivalent to the intended recipient’s. Check the language, legibility, references and decisive information. Record the date and a short note explaining what was checked.

Include a correction in the exercise. Who can replace an incorrect version if its author is away? Which copies remain with recipients and how will they learn of a material change? One realistic error is enough for an initial rehearsal. Measure time from the report to corrected publication. If changing one sentence requires updating several manual copies, reconsider the publishing route. After the next update, try a direct visit from an old bookmark as well. Returning users rarely reach content exclusively through a homepage.

Follow a new service from purchasing to publication

Rehearse the introduction of a fictional booking service. Marketing knows its intended purpose, purchasing knows the contract and the technical team knows how the calendar will appear on the website. None of those people automatically holds all the details. First decide which information needs to come together for a qualified review. A product name alone does not tell you whether a visitor opens an external link or whether content from a service loads while they are still on your own page.

For the exercise, trace the visitor’s journey on paper. They arrive on the contact page, pick a time and receive a confirmation. At what point do they enter information? Which organisation is visible there? Who inside the business can see or change a booking? For each answer, record whether you observed it in the planned implementation or heard it in a sales demonstration. An unanswered question can remain on the sheet. An assumption should not silently become the basis of published wording.

Use that overview when reviewing the project holding your legal texts. The person maintaining its details needs an intelligible reason for a change. They should know which website it affects, which languages belong to it and who can help with substantive doubts. Whether supplied wording describes the actual use depends on those facts and the review of your circumstances. Discuss uncertainties with the appropriate adviser before treating a version as settled.

Compare the two languages after a change

On a multilingual site it is not enough to see a revised version in an administration screen. Open the published text once from the German contact form and once from the English page. Check that the link stays in the expected language, the relevant passage is present and the surrounding page still makes clear which business provides the information. There is no need to submit a real enquiry for this check. Follow the journey up to the point where the visitor reads the information.

Introduce a delay into the exercise. The German version has been edited while the English version is still under review. Who notices the difference, how is the status recorded internally and when will someone check the public output again? The time an editor saves a change can differ from the time a website picks up an update. A spot check should therefore record the address and language actually viewed as well as the editorial version expected there.

Finally reverse the scenario. The booking service is being replaced or removed. What must someone inspect before closing the task? Consider the booking page, wording beside the form, linked information and the second language. A workable handover identifies the person confirming the technical change and the person arranging review of the wording. Maintaining the information then becomes part of a concrete website change instead of an issue rediscovered only when a visitor reports a contradiction.

Find the published pages after a relaunch

Ask one colleague to follow an old bookmark to the legal notice, another to use the English navigation and a third to open the privacy information beside the contact form. Have each person record the page and language they reached. If an older copy remains visible somewhere, the list helps the website maintainer identify the template that still points to it. Repeat those same journeys after the next update. Include a phone in the exercise so the mobile menu is covered as well. Keep the URLs with the release notes. That gives the next editor a short set of reproducible checks for the pages visitors actually use, including links shared by colleagues before the relaunch.

Review the published wording alongside actual website behaviour

A notice can correctly name an embedded video service. Whether that service loads at the intended moment on a particular WordPress page is a separate question. Give editorial and technical colleagues the same sample page to review. Editorial checks the provider and description while the technical team observes loading before and after a choice. Bring differences together in one list with an owner and a follow-up test.

Read the Borlabs guide

Explore eRecht24

Advertising · We may earn a commission if you purchase eRecht24 through this partner link.

Review features and plans at eRecht24