Your Data, on Request

“Send me everything you hold about me” is a simple sentence and, for most software, a support ticket that takes a week. Somebody has to work out which systems hold the person, query each one, strip out what belongs to other people, and hope they did not miss a store nobody remembered.

In AI Rule Engine it is now a button. So is the other half of the same right: deleting your account yourself, without asking anyone.

The Your account page

Open the user menu at the top right and choose Your account. The page shows who you are signed in as and two cards, Your data and Delete your account. Both act on your own account, whichever organization you happen to be working in, and both are available on every plan.

Download everything held about you

Choose Download my data on the Your data card. The platform gathers your records, which takes a few seconds, and your browser saves them as one JSON file covering every organization you belong to:

• Your account - your name, email address, the ways you sign in, the dates of your sessions, and any accounts that were merged into yours.
• Memberships - your organizations, projects and environments, your role in each, and any pipeline stage that names you as an approver.
• What you did - audit events where you were the actor, versions you saved, releases you submitted, reviewed or published, test cases and test runs, and credits you spent or bought.
• Your records in each environment - rule set runs you started or resumed by answering a human intervention, and the settings, variables, schedules, MCP credentials, API keys and app authorizations you created or last changed, grouped by environment.
• Everything else tied to you - feedback you sent, directory records your organization’s identity provider holds about you, and your marketplace likes, favorites and flags.

That environment section is the part most exports skip. Your runs and configuration changes live where your rule sets run, not in a central account table, so the download goes and asks each host your environments run on - the shared host, and a dedicated installation if your organization has one.

A manifest of what was searched

The file ends with a manifest: every store that was searched, what it was searched by, how many records were found and included, and every store that was not searched, with the reason. It lists each host your environments run on and says whether it was searched, skipped, or could not be reached.

That is the difference between an export and an answer. A file that simply contains some records cannot tell you whether it is complete. A manifest can, and when it is not complete it says exactly where the gap is. If a kind of record reaches the per-file limit, or a host cannot be reached, the download is marked partial, the page tells you so, and the manifest names what was cut short.

What the file leaves out, on purpose

• Other people’s details. Someone who reviewed your release appears by the name you could already see for them in the app, never by their email address.
• Credentials. No password, token, API key, session value or signature. A variable is listed by name, never by its value.
• What your rule sets processed. A run’s inputs, outputs, logs and traces are your organization’s decision data rather than a record of you, so they are not in a personal export. Ask the organization that ran them.

You can download your data up to five times an hour.

Deleting your account

On the Delete your account card, choose Delete account. Nothing is removed yet. The next step shows what would be affected: the organizations you would leave and your role in each, and any projects you own, which pass to their organization’s owner. To confirm, type your email address and choose Delete account again.

Deleting removes your name and email address from every organization, project and environment you belong to and from any directory records provisioned for you, unlinks every way you sign in, and ends your sessions. When it finishes you are signed out. A deleted account cannot be restored.

What it does not do is rewrite history. The work you did stays on the record as Deleted user, for the reasons we set out in Erase the Person, Keep the Record: an erasure that turned approvals into blanks would be a hole in the audit trail, not privacy.

When deletion is refused, and what to do

Deletion is refused while you still own an organization, because an organization with no owner has nobody who can administer it. The dialog lists each organization you own with a link straight to it. Transfer ownership to another member, or delete the organization if nobody needs it any more, then come back and finish.

The refusal comes before anything is touched. You never end up half deleted.

Organization admins: export one member

An organization’s owner and admins can now export what their organization holds about one member, for example to answer a request that member made to you as their employer. Find the member in the organization’s member list and choose Export data on their row.

The file has the same layout as a personal download, scoped to your organization: the person’s membership and role here, their projects, environments and approver stages here, what they did here, and their records in your organization’s environments and nobody else’s. Account-level data, such as how they sign in or what they did in the marketplace, belongs to the person rather than to you, and they can download it themselves.

Every member export is recorded in your audit log with who ran it and which member it was about. An organization admin can never download a person’s whole account, and can never delete it. Removing someone from the organization takes away their access here and leaves their account alone.

Member exports are limited per organization, by plan:

Plan	Member exports per hour
Free	5
Pro	20
Team	50
Enterprise	100

Visit RuleEngine.ai to try it.

The AI Rule Engine Team