Skip to content
BenchEWS
All pages · Site directory →
WHAT DO YOU WANT TO DO? · BENCHEWS = RESEARCH PROGRAMME · STUDIO = REFERENCE SOFTWARE
Research journey · origins → CRTI → BenchEWS→Scrutinise · Science & evidence→Apply · Engineering & Studio→Contextualise · Practice & business→
Understand
In five secondsResearch journeySocietal viability corridorLemming metaphor · analogyMetaphors & mental modelsWhat BenchEWS isBeyond Early Warning · Distinctive approachResearch Map (PDF, external) ↗
More ways to understand
Programme paper (Zenodo, external) ↗Reading pathways
Research
Origins & historySocietal viability corridor1789–2050 · Scientific outlookCRTI & AIP resultBenchEWS structureWhat BenchEWS isResearch Map (PDF, external) ↗
More research entry points
Programme paper (Zenodo, external) ↗MathematicsSpectral Compression · AIPCore conceptsResearch domains
Measuring Self-Correction
BenchEWS – Measuring Self-Correction
Book edition
Publication Edition v1.0
Evidence
Validation frameworkEvidence & maturityPublicationsScientific Observatory
Evidence context
BenchmarksFalsifiabilityLimitations
Software
BenchEWS StudioViability Corridor · Interactive simulationStudio Web · Web Laboratory ↗Studio 2.0Studio 3.0 / ECHO · plannedRoadmap
Documentation & simulation
DocumentationSimulation
Context
IntentionAuthorPress
Background & legal
Philosophical foundationsTheoretical horizonMedia kitLicense & open scienceLegal noticePrivacy
🔒 Private analytics
DE

Privacy · Data-minimizing statistics

As little data as possible.

This website uses no advertising trackers, analytics cookies, device identifiers or visitor profiles.

01 / Controller

Contact

Bernd von Mallinckrodt
Dorfstraße 7
46569 Hünxe
Germany

Email: BenchEWS@vonmallinckrodt.de

02 / Website delivery

Technically necessary connection data

When a page is requested, the hosting infrastructure processes connection data needed to deliver the content and keep the service secure. These data include the IP address, time of the request, requested address and technical status information. This web application does not transfer IP addresses into its own statistics database.

03 / Page-view and engagement statistics

Aggregated signals instead of visitor profiles

Only aggregated counts are stored per calendar day and page: page views, broad origin category, language version, voluntarily supplied UTM campaign terms, scroll-depth thresholds, time thresholds, link categories, internal page transitions and a broad loading-time category. Full referrer addresses, IP addresses, user accounts, device identifiers and individual browsing histories are not transferred into the statistics database.

  • No cookies
  • No local storage or session storage
  • No fingerprinting
  • No unique visitor identifier
  • No personal visitor profiles
  • No disclosure of statistics for advertising

04 / Purpose and legal basis

Improving content without observing individuals

The aggregated statistics are used solely to identify which research pages are read and which content should be improved. Where personal data are processed for technical reasons, the legal basis is the legitimate interest in secure delivery and data-minimizing reach measurement under Article 6(1)(f) GDPR.

05 / External links

Zenodo, ORCID and other sources

Simply reading this website does not automatically load external publication pages. The external provider's privacy terms apply only when you open an external link.

06 / Rights

Access, rectification, erasure and objection

Within the applicable legal framework, data subjects have rights including access, rectification, erasure, restriction of processing and objection. They may also lodge a complaint with a competent data protection supervisory authority. Requests can be sent to the email address above.

07 / Hosting and Studio Web

Server-side processing and retention

The website and public Studio Web are hosted on IONOS infrastructure. In Public Web, submitted numerical series and CSV contents are processed on the service infrastructure; computation does not take place exclusively on your device. The documented analysis boundary parses CSV contents in memory. An appropriately available offline edition is intended for local processing.

Studio usage telemetry is separate from research data. The documented implementation stores only aggregate daily counters and allowlisted categories, not raw observations, filenames, result values, IP addresses or visitor identifiers. Usage counts are not a count of unique people (USAGE_COUNTS_NOT_USERS).

The configurable default for persistent Studio telemetry aggregates is 180 days. The production setting, effective periodic deletion and retention periods for infrastructure, error and security logs have not yet been fully verified. This default is therefore not a confirmed production deletion period and does not apply generally to server logs or analysis artifacts. Please contact the controller above with questions about specific data processing.

Information duties: BfDI on Article 13 GDPR · Legal basis: General Data Protection Regulation · Updated: 23 October 2026.

BenchEWS

BenchEWS · Privacy · Computational implementation: BenchEWS Studio / MalliSoftware

© 2026 Bernd von Mallinckrodt · BenchEWS Research Programme · Website content: CC BY 4.0 unless notedMalliSoftware: non-commercial software-engineering label for open reference toolswww.vonmallinckrodt.comAbout the authorAcknowledgementsPressLegal noticePrivacyLicense & copyright