Data & Privacy
Open Settings → You → Data & privacy (/dashboard/settings/privacy) for self-service data exports and their request history.
Export your data
Under Data access & export, pick one of two cards: User data only (for every profile) or User + channel data (only for channels you own; the card names them). Each card lists what the export contains. For the second model, select the owned channels to include; the optional chat data depends on the channel's plan and retention period. Then choose Request export. Lumio processes the request, notifies you when it is ready, and lists it in the export log. You can request one export per model at a time, with a 24-hour interval between requests of the same model.
Each log row shows the model, when you requested it, its state and what happens next: a progress bar with a percentage while it is created, Ready with the file size and the days left until it expires, Expired once the file is deleted, or Cancelled. To stop it, choose Cancel next to it. Lumio then stops building the file and keeps nothing; the entry stays in the log as cancelled. A cancelled export does not count towards the 24-hour interval as long as Lumio had not started building it yet, so you can request a new one right away. Once building had started, the cancelled export counts like any other. A finished export can no longer be cancelled.
When the ZIP is ready, choose Download and confirm Is it really you?. The resulting download link works for five minutes and for that export only. The export is encrypted at rest and removed after seven days. The ZIP includes a README explaining its files. If you uploaded your own profile picture, the export contains the picture file itself (profile_picture.webp). It does not contain passwords, API tokens, or other members' private identifiers. Its 2FA section lists factors with kind, label, created_at, and last_used_at. A passkey factor also has provider and backup_state (whether it is synced). The export excludes authenticator secrets, passkey keys, credential IDs, signature counters, the passkey user handle, and recovery codes. For example:
{
"factors": [
{"kind": "totp", "label": "Phone app", "created_at": "2026-10-15T12:00:00Z", "last_used_at": null},
{"kind": "passkey", "label": "Laptop", "created_at": "2026-10-15T12:05:00Z", "last_used_at": null, "provider": "Passkey", "backup_state": false}
]
}
The passkey's provider is a name looked up locally from the AAGUID supplied by the device; an unknown or withheld AAGUID is shown as Passkey.
Both models also contain what you did on Lumio as a person, outside any channel:
| File | Contents |
|---|---|
ideas.json | ideas you posted on the ideas board, your comments and replies, your idea_votes and comment_votes, and the idea history entries you caused. Other people's comments under your ideas and who voted on them are not included. A comment of yours under an idea that was deleted carries idea_deleted: true and an empty idea_title. |
developer.json | Your developer profile with payout details (PayPal address and bank details in readable form; a value that can no longer be decrypted is null), verifications, developer applications, limit_requests, payouts, your self-billed credit_notes (number, dates, amounts, VAT treatment and the supplier details printed on them; the PDFs are in the developer settings under Payouts), settled_released_balances (a balance Lumio could not pay out when an earlier developer profile of yours was deleted and later credited to this profile with your claim code: amount, case, reason, release, claim and settlement dates), the developer teams you belong to with your role (no other members), and the extensions of your personal developer profile with their versions (metadata only, no bundles or sources). |
extension_reviews.json | The marketplace reviews you wrote, with the extension name, rating and text. |
lumio_activity.json | Your Stats stats_watchlist, overlay_access and widget_access shared with you, extension_testing invitations with your feedback, channel_invites addressed to you, your channel_sign_in_assignments, your roles (admin roles, user roles, permission overrides), and the copyright_reports and copyright_confirmations you submitted. Invite codes and who granted or assigned something are not included. |
Each section is an empty list (or null for the developer profile) when you have no such data. sign_in_methods.json also lists known_sign_in_devices with when each device was first and last seen (the device fingerprint itself is a hash and is not included).
The Security → Activity page and the account Audit Log offer a separate CSV/JSON export of audit rows. The account log requires audit-log:read.
AutoMod data and access requests
For Twitch messages held by AutoMod, Lumio keeps an AutoMod log with the sender, their last-known avatar, chat color and badges at hold time when available, the hold time, reason, outcome and moderator decision. The held text, flagged spans, blocked-term text, emotes and Cheers are kept with the log entry and deleted together with it once the hold is older than the account's chat retention window (Free 365 days, Pro 1,095 days), for every outcome, including denied, expired and allowed messages. An allowed message is also published as a new chat message and follows normal chat-message retention.
The log appears in the signed-in Stream History AutoMod tab for team members with both history:read and chat:automod-read, and as held-message rows in the chat history of Multichat and chat popouts for team members with chat:read and chat:automod-read (the last 24 hours without history:read). It is absent from shared reports, report exports and the self-service data export on this page. A chat participant can request access under Art. 15 GDPR at hey@lumio.vision; the support response includes any AutoMod log rows Lumio still holds for that person. A participant can also object or request erasure there. The AutoMod log belongs to the channel: Lumio deletes a person's rows in a channel on that channel's instruction, in that channel only, and an objection does not stop new rows from being logged.
Delete your profile
Open Settings → Account (/dashboard/settings/account). Three steps explain the way: Export (optional, a copy of your data first), Confirm (sign in again and hold), and Choose the period. Choose when the profile is deleted on one of three cards, each naming its date; In 30 days is preselected:
- Now - the profile is deleted right away, with no waiting period and no way back. You are signed out and the sign-in page says Your profile was deleted.
- In 7 days or In 30 days - Lumio ends your sessions and schedules the deletion for that date. The confirmation mail names it.
Then hold the red button for two seconds - it is named Delete permanently now, Delete in 7 days or Delete in 30 days - (or type your profile name when animations are Off) and pass a fresh Is it really you? check, which repeats the date. The check is needed for every choice.
If you own a channel that is not scheduled for dissolution, a yellow box names it and the button stays locked until you transfer, dissolve or schedule the channel for dissolution (see Channel settings → Danger zone). Once every channel you own is scheduled, you can delete your profile with a period that ends no earlier than the last of them: the other cards are greyed out with the reason. Now needs you to own no channel at all. When both dates arrive, Lumio first dissolves the channels and then deletes the profile.
If you are an extension developer and Lumio still owes you money, the deletion pays it out first, and the section shows what applies above the step tiles:
- A balance that can be paid out — a blue box names the amount. With a waiting period of 7 or 30 days it is paid out with your deletion request as the closing payout, also below the minimum payout amount; Now is greyed out until then. The confirmation names the amount paid out.
- A payout in progress — a yellow box names it, and the button stays locked until the payout has completed.
- Incomplete tax details — a yellow box links to the tax details in the developer verification: the closing payout needs them for its credit note, and the button stays locked until they are complete.
- No payout method or no verified developer identity — a yellow box links to the payout settings (Extensions › Payouts) or the verification, and the button stays locked until the balance can be paid out. If it cannot be paid out, write to hey@lumio.vision.
The box needs the channel you have selected to let you manage developer payouts. Without it the section shows no box, and the delete button answers with You still have a developer balance with Lumio or a payout in progress. You can delete your profile once it has been paid out. If it cannot be paid out, for example because it is below the minimum payout amount, write to us at hey@lumio.vision. The address in the message opens your mail client.
During the waiting period the deletion page shows your developer balance too. Revenue that arrives after the deletion request is paid out with Request closing payout, also below the minimum. While a payout is in progress the page says that the deletion runs once it has completed: when the waiting period ends, the deletion waits for the payout to finish. Your payout records are kept for 8 years after the year of the payout, as tax law requires, also after the profile is deleted.
During the waiting period, signing in leads to /account/deletion, which names the date. Hold Cancel deletion for two seconds to keep your profile (letting go early cancels; a plain button with animations Off), or sign out and leave it scheduled. Cancelling works until the date; once it has passed the deletion is already running and can no longer be cancelled. A reminder mail is sent seven days before the end of a 30-day period and one day before the end of a 7-day period. For the privacy policy and retention details, see Legal pages.