Skip to content

Export and erase personal data

Updated View as Markdown

MazeGraph connects to WordPress’s personal data exporter and eraser. Use those tools to handle a verified request for a person’s data across the site. A signed-in user can also export or erase their own MazeGraph records from Settings. Both routes affect MazeGraph data stored on this WordPress site; they do not send a deletion request to an AI provider.

Choose the right way to handle a request

If you need to… Use… Scope
Process a person’s request through the site’s privacy workflow Tools → Export Personal Data or Tools → Erase Personal Data in WordPress The person’s data reported by WordPress and participating plugins, including MazeGraph’s contribution.
Export or erase your own MazeGraph records while signed in MazeGraph → Settings → Personal → Your data; site managers also see it under Limits and privacy Only your MazeGraph data on this site.

WordPress’s Tools → Export screen creates a site content export. It is different from Tools → Export Personal Data, which assembles a person’s privacy export. See the WordPress Export Personal Data guide and Erase Personal Data guide for WordPress’s current request screens.

Process a request in WordPress

The WordPress tools use email confirmation so the requester can verify the address. Confirm that the request and the person’s identity match your site’s privacy process before sending or erasing data.

Export someone’s MazeGraph data

  1. In the WordPress dashboard, open Tools → Export Personal Data.
  2. Enter the requester’s username or email address, then select Send Request.
  3. Ask the requester to follow the confirmation link WordPress emails them. The request changes to confirmed after they complete this step.
  4. When WordPress marks the request ready, select Email Data. WordPress sends the requester a link to download the site’s personal data export ZIP. Follow the screen’s status and email instructions to complete the request.

MazeGraph adds the person’s retained sessions and conversation messages, personal instructions, saved personal notes, data-notice acceptance, onboarding preferences, Activity metadata, and daily Usage summaries. Activity entries are operational details; they do not contain chat text, tool arguments or results, or provider keys. The export is limited to data MazeGraph holds for that WordPress account. Site-wide instructions and settings, site notes, other people’s records, and provider-side records are not part of that person’s MazeGraph export.

Erase someone’s MazeGraph data

  1. Open Tools → Erase Personal Data in the WordPress dashboard.
  2. Enter the requester’s username or email address, then select Send Request.
  3. Ask the requester to confirm the email WordPress sends. Once the request is confirmed, review it and select Erase Personal Data to run the erasure.
  4. Check that WordPress reports the request as completed. Removing the completed request from the list only removes the request record; it does not run another erasure.

MazeGraph removes that person’s sessions and transcripts, session-related changes and jobs, personal Activity and Usage records, personal instructions, notes, and preferences. The operation does not erase other people’s records, site settings, WordPress connector credentials, the person’s WordPress account, or data already held by an AI provider. WordPress’s erasure screen does not delete the account or erase copies in backups; handle those separately under your site’s policies.

Let a user manage their own MazeGraph data

A person who can use MazeGraph can open its Settings screen and find Your data on the Personal tab. Site managers can also find this panel near the bottom of Limits and privacy.

  • Export my data downloads a JSON file containing that signed-in person’s MazeGraph records on this site.
  • Erase my data asks for confirmation, then permanently removes those records. It cannot be undone. The confirmation explains that other people’s data, site settings, and provider keys are not affected.

This is a self-service option for the current account. Use the WordPress privacy workflow when an administrator needs to process a request for another person or combine MazeGraph’s export with data from WordPress and other participating plugins.

Understand retention and other cleanup controls

Automatic retention and personal-data erasure solve different problems. Retention removes eligible records as they age; an export or erasure request addresses the records associated with a specific person.

In MazeGraph → Settings → Limits and privacy, administrators can set Keep sessions for to remove inactive sessions after a chosen number of days. A value of 0 keeps sessions until they are deleted manually or by a privacy erasure. Keep activity logs for controls operational logs and allows 7–365 days; the default is 7 days. Daily Usage summaries are retained for up to 400 days. See Understand Usage totals for the report’s scope and date behavior.

The Clear plugin logs control removes the site’s operational event log. It does not remove sessions, recorded changes, or background jobs, so it is not a substitute for erasing one person’s MazeGraph data.

The setting Delete all data when the plugin is deleted controls site-wide cleanup when MazeGraph is deleted from WordPress. It is off by default. When enabled, deleting the plugin removes MazeGraph’s stored data and settings; WordPress AI Connector keys are kept. Deactivating MazeGraph is not the same as deleting it. This setting is separate from a person’s export or erasure request.

For context on the data sent during a model request, read What a provider request may contain. For Activity and Usage records, see the Activity and Usage overview and Understand Usage totals.

Troubleshoot an incomplete request

What you see Likely reason What to do How to prevent confusion
The request stays pending. The requester has not confirmed the email link, or the message did not reach them. Ask them to check their inbox and spam folder; resend the request email from WordPress if needed. Confirm the address before creating the request and explain that email confirmation is required.
The export is missing old Activity or Usage rows. Automatic retention has already removed older records. Check the Activity retention setting and the Usage period covered by the report; only records still held can be exported. Set appropriate retention periods and answer requests promptly.
An erasure completed but the WordPress account remains. WordPress privacy erasure removes plugin-contributed personal data, not the user account itself. Decide separately whether the account should be deleted from Users. MazeGraph also clears that account’s records when WordPress deletes the user. Treat account deletion and personal-data erasure as separate decisions.
Data appears again after restoring a backup. The restore brought back a database snapshot that predates the erasure. Reapply the erasure to the restored site where appropriate. Record outstanding requests and account for backups in your site’s retention process.

What happened: MazeGraph records may remain after a privacy request if the wrong WordPress tool is used, the requester has not confirmed, or a backup is restored. Why: WordPress separates content exports, personal-data requests, account deletion, and backup management. Resolution: Use the personal-data workflow above, complete its confirmation and processing steps, and handle account or backup actions separately. Learning: Record which account, tool, and scope were processed so the result can be checked without confusing a request record with the data itself.

Was this page helpful?

Your feedback helps us improve these docs.

Documentation

Type to search…

↑↓ navigate↵ selectEsc close