Skip to content

We use essential cookies to run Misenta. Optional analytics measure visits. Your choice; change it anytime. Cookie policy

Legal

Retention Schedule

Last updated 18 November 2026

How long we keep each kind of data.

Asking us to delete your account

If you hold a Misenta account, you can request deletion from Settings → Your account in the app. We confirm the request by email and answer under the timeframe that applies to your request (one month for UK GDPR requests). What happens then:

  1. Your request is logged and acknowledged. Your account keeps working — a request is not an instant deletion, and you can withdraw it at any time by replying to the confirmation email.
  2. We close the account. Sign-in stops working immediately and the account stays recoverable for 30 days, in case the request was a mistake or was not made by you.
  3. We erase your personal details. After the 30 days, your name, email, password and second-factor details are permanently removed. We email you to confirm.

Removing a person's account does not automatically remove the business's food-safety evidence. Where the business controls operational records — your staff record, and food-safety entries signed under your name — those can still carry your name after your individual account is gone. Ask the business about those records. Closing the whole business account is different: export the records you must retain before closure, because its operational data is removed after the recovery period unless a legal hold applies. What Misenta holds about you as an account holder — your name, email, password and second-factor details — is erased.

Australian category-one food businesses that use records to substantiate controls must keep those records for at least three months; another requirement may call for longer. An authorised officer may accept another way to demonstrate control. New Zealand operators under a Food Control Plan or National Programme must keep required records for at least four years from creation. These are the business's retention duties, not a promise that a closed Misenta account remains accessible for those periods. See FSANZ evidence guidance and NZ Food Regulations 2015, regulations 36 and 81.

Where a legal hold applies (a claim, an investigation, a regulator's request), erasure waits until it lifts. Your request stays open with us in the meantime and we act on it once the hold ends — you do not need to ask again. Backups age out on the schedule below.

If you are a staff member rather than the account holder, your employer is the controller of your records: ask them, and we will act on their instruction.

Connected content, secrets and retained history

Google API review content uses an encrypted temporary cache for up to 29 days per retrieval. Expired content is unavailable and purged; this cache is excluded from durable CSV exports and backups. Your authored reply drafts, consent/read markers and opaque operation/hash references are separate records retained under the normal account schedule. The shorter Google cache limit is an exception to general account-lifetime and backup periods.

Disconnecting Google stops Misenta access for every location on that connection and clears its cached content. A restricted encrypted refresh-token queue may survive account erasure solely to relinquish the grant, with a seven-calendar-day processing deadline; confirmation or deadline processing clears the secret. A pending or manually confirmed removal is distinguished from provider acknowledgement. Other connector secrets support only the configured connection; disconnecting does not erase records already sent to the external service. The business can also remove access in the provider’s settings.

Reviewed POS snapshots, invoice/time handoff evidence, supplier dispatch receipts and your authored review history follow the existing business-record retention and access controls. A Remote payslip explicitly released by the owner is retained as an encrypted PDF snapshot under those business-record rules; it is not part of the temporary Google review cache. Disconnecting Remote clears Misenta’s connection credentials and prevents further provider calls; previously released private payslip records remain under the normal retention and current employee-access controls. Connector secrets and provider payslips are excluded from the mobile offline cache. The business remains responsible for records retained with the connected provider.

AI proposal details, credentials and decision receipts

Structured action proposals and their review details expire within 5 minutes and become unavailable for approval. Scheduled cleanup removes those expired details in bounded batches; expiry is not a promise of immediate physical deletion. Policy-operation receipts and limited access audit are retained for 90 days. Proposal and action-decision metadata, including outcome receipts, is retained until 90 days after the associated connection’s recorded expiry or revocation, then removed in bounded cleanup batches. A task or draft shift created after approval becomes an ordinary business record with its own retention and audit history; it is not erased when the proposal details expire.

Authorisation requests and codes expire after 5 minutes, access credentials after 10 minutes, and rotating refresh authority after at most 30 days, or earlier when sign-in policies or access change. Connection metadata is kept for 90 days after its recorded expiry or revocation. Scheduled cleanup removes ended credential proofs in bounded batches; spent refresh proofs may remain to detect replay. Connector audit logs do not store full model prompts or result narratives; temporary structured proposal details are separate. User or business erasure also removes associated connector metadata. External AI conversations follow the chosen provider’s retention and cannot be recalled by Misenta.

Google Business Profile API content and authorisation policies

Employment and recruitment records

Owners record the purpose and retention-review date for right-to-work records, family-leave notices, flexible-working requests and saved SSP estimates. Staff can submit their own notices and requests before that employer review; a pending review has no invented retention period. A review date prompts manual deletion review and does not automatically erase records or earlier versions. Each recruitment application has an expiry derived from the employer's published retention period. The separately enabled, bounded recruitment cleanup removes expired applicant content unless a hold applies. An active hold requires explicit release; its review date never releases it automatically. Holds also prevent whole-business or location erasure from removing protected applications. Closing a vacancy stops new intake but does not erase applications. Hiring does not remove the original application automatically. Existing guarded account erasure, minimal audit receipts and rolling backup periods still apply.

After a hire, Misenta keeps a protected email match on the staff record so an invitation can connect the right account. It is cleared when the account is linked or the staff record is deactivated.

Door staff register retention

There is no single UK GDPR retention period for every venue. The owner must choose a justified period for the purpose of the record and check the venue’s own licence conditions. Misenta suggests 12 calendar months; this is an app default, not a legal minimum or a licence compliance certificate. Some licences require a bound or countersigned register, which this digital register does not replace. See the ICO storage limitation guidance.

Each record shows its scheduled deletion date and any active retention hold. A hold preserves the record beyond that date until an owner explicitly releases it. Owners should review holds when due and retain only what is needed. These controls do not automatically change an existing venue’s settings or create a sign-out time for an open entry. Account erasure and backup handling remain subject to the separate rules in this schedule. An active door staff hold also postpones whole-business trial erasure until explicitly released. Unrelated register entries that reach their own retention date can still be deleted automatically if they are not protected by a hold.

Schedule

DataKept forNotes
Optional AI-connection credentials, proposals and access metadataProposal details expire within 5 minutes; limited access and policy receipts 90 days; connection and action metadata 90 days after recorded connection expiry or revocationAuthorisation requests and codes expire after 5 minutes. Access credentials expire after 10 minutes; rotating refresh authority lasts at most 30 days and may end earlier under work sign-in policies or access changes. Structured proposal and review details expire within 5 minutes, after which approval is blocked; scheduled cleanup removes them in bounded batches. Expiry does not mean immediate physical deletion. Policy-operation receipts and limited access audit are kept for 90 days. Proposal and action-decision metadata, including outcome receipts, is removed in bounded batches once the associated connection has been expired or revoked for 90 days. Created tasks and draft shifts remain ordinary business records under their own retention and audit rules. The separate scheduled cleanup also removes expired requests/codes and credential proofs for ended grants in bounded batches. Spent refresh proofs remain while needed to detect replay. Consent and access audit contain limited actor, client, scope, location and count metadata, not full model prompts or result narratives; temporary structured proposal details are separate. Revocation stops future connector access immediately even before physical cleanup. Disabling business writes immediately blocks later approvals. User/business erasure also removes the associated connector metadata; external AI conversations follow the chosen provider’s retention and cannot be recalled by Misenta.
Mobile app version reportsLatest report per installation, user and business, until account erasureNew reports replace the version/build and last-reported time. These support records are removed when the user or business is erased.
Your live operational & staff dataFor the life of a paid accountDoor staff register and recruitment records follow their specific policies below. Private family-leave and SSP review dates prompt manual retention review. Earlier deletion of other records goes through a data-subject request — usually via the business as controller — and may be subject to audit or legal retention.
Door staff register records and retention holdsOwner-reviewed venue period; app default 12 calendar months, with a recorded expiry for each entryAn owner must review the venue’s licence conditions and document the period before new sign-ins. Closed records run from sign-out; open records run from sign-in. First adoption gives existing records at least 30 days before automatic deletion. Shorter policies apply prospectively and do not bring existing deadlines forward. An owner can place an investigation or other justified hold, record its reason and review date, and explicitly release it. A review date does not release a hold. After release, an expired record can become eligible for automatic deletion. Owner retention controls remain available while billing is read-only.
Attendance evidence & payroll-preparation historyAccount lifetime, subject to controller instructions and lawful retentionIncludes stored owner-enabled clock-in coordinates, accuracy and photos, breaks, corrections, approval history and captured base/overtime rates. Upload-link expiry does not erase a completed attendance record or its evidence.
Private employee records & contract evidenceAccount lifetime, with controller-led retention reviewIncludes contact details, right-to-work files and manual reviews, payslips, immutable profile/contract versions and signing receipts. A recorded retention date is for manual review; it does not automatically erase the record or earlier versions. Follow a deletion request through the business, subject to lawful retention.
Team collaboration, attachments & read stateAccount lifetime, subject to controller instructions and lawful retentionMessage and attachment contents, quotes, reactions, poll votes and operation history follow the business-account retention and guarded deletion process. Removing membership ends access but does not automatically erase shared history. Expiring upload/download links do not erase completed files. Queued mobile text and picker recovery checkpoints remain until their documented completion or cleanup; exported copies outside Misenta remain under the recipient's control.
An unpaid trial account30 days after the trial ends, subject to erasure safeguards and active holdsAn active door staff or recruitment retention hold postpones whole-business trial erasure until explicitly released. The existing eligibility, notice and legal-hold safeguards still apply. For those 30 days the account is read-only: subscribe to keep it, or export your records. We email the owner when the trial ends, 7 days before and 1 day before erasure. Erasure removes the locations, checklists, records, photos, documents and team logins; only minimal consent evidence and a receipt with counts remain.
A closed account, before erasure30 days after closureRecoverable in case a deletion request was a mistake or was not made by the account holder; then the personal details are erased.
Record that a deletion request was made6 yearsThe request, its deadline and how it ended — kept as proof we answered, without your name or email attached once the account is erased.
Food-safety records & their audit trailWhile the account is active; exportable on closureWe provide export so you keep your own copy.
Account & billing records6 years after account closure where legally requiredMisenta as controller; tax/accounting obligation.
Support correspondence24 monthsKept to resolve issues and maintain service history.
Request / security logs90 days, then purgedRequest and security logs are separate from the staff and operational records above. Avoid including unnecessary medical or other sensitive details.
Backups30-day rolling windowDeletions in the live database age out as backups expire.
Mobile on-device cache & outboxOutbox: queued until synced. Cached reads may persist locally until pruned or the device is wiped.Stored on the device, namespaced per user and business. Signing out and clearing the device removes local data.

Service operator

Misenta — Serdar Kahraman, sole trader

Cleekim DriveEH15 3QP EdinburghUnited Kingdom

Contact: support@misenta.app