Export a frontend user's data

Studio roles: "Owner", "Administrator" and "Frontend user manager".

When a person asks which data your organisation holds about their account (a data access request under the GDPR), export it from their page. You get one JSON file for yourself; you decide what to send the person.

1. Open "Frontend users" and choose the person.
2. Choose "Export data" at the top of the page.
3. Your browser saves the file.

The page's "History" then shows "Exported", with who exported it.

What the file contains

Each part of the file starts with a description in your language:

• Profile: the account the person signs in with: email, their own first and last name, the language of their mails, when and through which frontend it was created, and whether it is blocked.
• Organisation membership: status, member code, register and the names the register gave, the facts stored from the last check (member status in the register, groups, membership start, claims), the last check, the last valid check and the deactivation. Empty without a membership.
• Frontend activations: the frontends the person signed in to, and when first and last.
• Sign-in history: every attempt of the person to sign in, sign up, enter a code, reset the password or request support, newest first, kept for 24 months. The IP address only while it is stored, which is one day.
• Administrative actions: what Studio users of your organisation did with the account (blocked, unblocked, exported), newest first, without who acted.

What it does not contain

• The member data your registers hold, such as date of birth, phone or postal address. Look in the register for those.
• The reasons of membership checks.
• Attempts with the person's email address that were never linked to their account, such as an email typed before signing up: anyone can type an address, so these may be someone else's.
• The Studio users who acted.

Keep the file safe: it holds personal data.