Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

What cannot be exported

For public bodies planning how to answer access and portability requests - the limits of Exponential's exports (no single export of a person's data, accounts as content objects, form submissions per form, pseudonymized…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/privacy/what-cannot-be-exported.md

On this page

What cannot be exported

This page is for data protection officers, administrators and developers. Knowing the limits in advance lets you plan the access request procedure and, if requests are frequent, commission a custom export. The facts come from Privacy standards: Known gaps.

Note This page describes features and common practice; it is not legal advice. Check the law that applies to your organization with your legal counsel.

Contents

  1. The limits
  2. Why
  3. Options
  4. Related pages

The limits

LimitConsequence
No single "export all my data" functioneach place is exported separately (see "The right of access")
A user account is a content objectits fields are read on its node; there is no dedicated account export beyond the Check user accounts CSV
Form submissions are exported per formyou export each form's CSV and pick the person's rows
Audit index pseudonymized after 90 daysexp:audit export --subject-user still finds pseudonymized records; full values remain in archives
Logs are masked when shownmasked logs cannot identify a person; unmasked reading needs setup/unmasklogs and is recorded
Search phrases have no person attachedthey cannot be attributed to a requester
Suppression list stores hashesit can confirm an address is listed, not list it
Web server, Velocity and mail server logsoutside Exponential: ask the host
request-shield's lognot per person: it holds masked client networks (var/request-shield/log/shield.log)
Backupsnot searched per person; they expire with your backup rotation

Why

Exponential's content model stores many kinds of data as content objects in classes your site defines; a generic "everything about this person" export would have to know which of your classes and fields are personal. The project provides dedicated exports where it owns the data model (mail preferences, consent log, audit).

Options

  • A procedure with a checklist per place (the inventory in "Where personal data lives in Exponential").
  • A custom export by a developer, for your classes and forms: the persistent object API and template fetch functions give access to the data; put it in an extension of your own and protect it with a policy.
  • Fewer places: minimize what you collect (see "Data minimization"), and remove form submissions when cases close.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x