Browse documentation
All documentation
Getting started
Screens & scenes
Widgets
Integrations
The assistant
Household & presence
Reception & visitors
Menus, art & broadcast
Account, plans & data
API & self-hosting
Troubleshooting

Your data

Set how long Mirra keeps assistant transcripts, presence and the activity log, take a copy of everything held about your household, and close the account for good.

Retention, export and account closure are on every plan, including Free. None of them is something you have to pay to reach.

Where to find it

All three live together at the foot of Settings, under the heading "Your data". They are grouped deliberately. How long things are kept, how to take a copy, and how to leave are the three things somebody looks for when they have decided they want less of a product in their life, and putting the last one somewhere else is a dark pattern whether or not it was meant as one.

Settings — Your dataHow long we keep thingsThree pickers. Owner onlyTake a copyDownload my dataClose this accountPassword, then the household name typed back
The three panels under "Your data", in the order they appear.
  1. Open the account menu and choose Settings

  2. Scroll to "Your data"

    It sits below branding, notifications and single sign-on, at the foot of the page.

How long we keep things

Three kinds of record expire on a schedule you choose. Everything else — photographs, scenes, screens, tasks, reminders, people, integration settings — is kept for as long as the account is open.

Each picker offers 7 days, 1 month, 3 months, 6 months, 1 year, or "Until I close my account". The defaults below are what a new household starts with.

Assistant conversations
What was asked and what was answered, turn by turn, with the time and the screen it happened on. A conversation disappears when its last remaining turn does.Default: 3 months
Who was home, and when
The record that a screen recognised a known person, or saw a face it did not know. Only written at all if you have enrolled faces on a screen.Default: 1 month
Account activity log
Sign-ins, setting changes, screens paired — with the acting account, the time, and the address the request came from.Default: 1 year

"Until I close my account" switches expiry off for that kind of record. It deletes nothing, and it is still a decision somebody made rather than the absence of one. Only an owner can change these; a menus-only sign-in never reaches this page at all.

Shortening a window

Shortening applies at once. The records that already fall outside the new window are deleted as the setting saves, and the line under the pickers reports how many went — "Saved. 1,204 old records deleted." Saying what it actually did is the difference between a setting you trust and a setting you hope is working.

Otherwise the sweep runs about once a day. A record can outlive its window by up to a day, and longer if the server has been restarting, because the timer that drives it only counts time while Mirra is up.

There is no button that deletes a single conversation. Shortening the transcript window is how you get rid of one early.

  1. Choose a shorter window

    It saves as you choose it — there is no separate save button.

  2. Read the line underneath

    It tells you how many old records were deleted there and then.

What these windows do not cover

  • AI usage records are kept whatever you set. They are the token counts, seconds transcribed and characters synthesised that your monthly allowance and your bill are worked out from, and deleting them would leave invoices nobody could reconcile. They carry no content — quantities only — and they go when the account is closed.
  • Activity-log entries that belong to no account at all, such as a failed sign-in against an address that does not exist, are governed by nobody's setting and are deleted after 365 days.
  • Face descriptors are not on this list because they are not held here. They stay in the browser database of the screen that made them and never reach Mirra, so there is no window to set.
  • Photographs, scenes, screens, tasks, reminders, people and integration settings have no expiry at all. They stay until you delete them or close the account.

Taking a copy

One file, on demand, without asking anybody and without waiting for anybody. It downloads as mirra-export followed by today's date, in JSON.

It holds the household record and its settings, the sign-in accounts, the people you have added and the fact of their enrolments, your screens and devices, your scenes and which screen shows which, your schedule rules, albums, tasks, reminders, the full text of your assistant conversations, your presence history, insights, the integrations, API keys and webhooks that exist, your menus, your own art collections, your AI usage records and your activity log.

Floor plans are not in it — neither the drawing you made nor any image you imported to trace over. There is no way to download a plan today, so if you need a copy outside Mirra, take a screenshot. The plans themselves stay in your household until you delete them or close the account.

  1. Press "Download my data"

    Anyone with full access can do this. The data belongs to the household, and making people ask an owner for their own assistant transcripts would defeat the point.

  2. Keep the file somewhere sensible

    It contains the full text of everything ever said to your assistant.

Photographs are not inside the file. Each is listed with a link you can download while signed in — a household with a few thousand pictures could not be packed into one response, and it is worth saying so plainly rather than letting somebody discover it. Password hashes, the encrypted Home Assistant token and API key secrets are left out on purpose: the file records that they exist, not what they are. Curated art collections are left out too, because they are not yours and calling them "everything we hold about you" would be untrue twice over. Taking an export is itself written to the activity log.

Closing the account

Only the owner sees this panel, and only the owner can go through with it. Because it cannot be undone there are three gates, and a misclick cannot satisfy the last two.

CancelsubscriptionsPlan, and any artcollectionsYour passwordHousehold nametyped backEverythingdeletedScreens back topairingThe hardware staysusable
The three gates, and what is left afterwards.
  1. Cancel any subscriptions first

    Closing is refused while a plan subscription or an art collection subscription is still running. The refusal names the collections rather than counting them, so you are not left hunting through a billing portal for something you have forgotten.

  2. Press "Close account…"

  3. Enter your password

  4. Type the household name exactly

    The final button stays disabled until it matches.

  5. Press "Delete everything"

    You are signed out and returned to the sign-in page.

This cannot be undone. There is no grace period, no recycle bin, and no copy taken on your behalf. If you want your data, download it before you start.

What closing deletes

  • The household and every sign-in account in it.
  • The people you added, and their enrolment records.
  • Screens, scenes and schedule rules.
  • Floor plans, their levels and everything drawn on them — including any drawing you imported to trace over, which is deleted from storage rather than only unlinked.
  • Photographs and profile pictures — the files in storage, not only the database rows that pointed at them. Dish photographs on your menus, the works in your own art collections, and anything you sent to support go the same way.
  • Assistant conversations, presence history, tasks, reminders and insights.
  • Integrations and the credentials stored inside them, API keys and webhooks.
  • Your AI usage records.
  • The account's activity log.
  • Your screens are unpaired, reset to "New screen" and told to reload, so each one goes back to showing a pairing code and the physical thing stays useful to somebody.

What survives, and why

Three things outlive the account, and you should know about all three.

A single record that the closure happened is written before anything is deleted, deliberately with no household attached so that it survives the deletion and cannot later be disputed. It holds the household's name and id, the email of the account that closed it, the address the request came from, and the time. Having no household attached, it ages out under the 365-day rule for unattached entries.

Payments actually made to you as an artist are kept. The duty to keep a record of money paid out lasts longer than the right to have it erased, so the amount, the period it covered and the name it was paid to stay in the accounts — unlinked from your profile, with your bank details deleted along with everything else. Payment requests that were never acted on are not accounting records and go with the rest.

Face descriptors held on your own screens are not ours to reach. Clear the browser's site data on the device, or reflash it.

Stripe keeps its own record of payments it has taken, under its own policy. That is outside Mirra entirely.

Related

  • BillingHow to subscribe, change plan, find your invoices and cancel — and what Mirra does on an install where payments were never configured.
  • Sign-ins and rolesHow to give somebody their own password for your Mirra account, and exactly what each of the two roles — full access and menus only — can reach.
  • Plans and allowancesWhat each Mirra plan includes — screens, household members and assistant credits — how credits are metered, and what happens when you reach a limit.
  • What Mirra remembers, and how to see or delete itMirra stores only the facts somebody asked it out loud to remember, shows every one of them in the words that produced them, and can be told to stop remembering altogether.
  • People and presenceHow to add a household member, enrol their face on a screen, and understand what Mirra stores about them and where recognition actually happens.
  • Getting help and raising a ticketHow to raise a support ticket inside Mirra, what to put in it so it can be answered on the first read, where the support documents live, and how to suggest something for the roadmap.