Skip to content

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

Retention schedule

Canadian edition dated 2026-11-18

Published retention periods, account deletion and the business's responsibility to retain required records.

Consulter ce document en français

Deletion requests

Request deletion in Settings → Your account or contact support@misenta.app. The request is recorded and acknowledged; it does not immediately delete the account and can be withdrawn by replying. We respond within the applicable legal period. After closure, sign-in stops and the account is recoverable for 30 days; account name, email, password and second-factor details are then erased and confirmation is sent.

Employer-controlled staff and signed operational records can retain names where the business has a lawful retention need. Direct those requests to the business; Misenta follows its instructions. A lawful hold for a claim, investigation or authority request can defer erasure until it ends. The request remains open during the hold.

This service schedule is not a statement of every Canadian food-record retention rule. Keep the required copy for your actual activity, including after cancellation. Covered federal retail traceability and provincial purchase or training records can have distinct periods and retrieval requirements.

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.

Retention schedule
InformationPeriodNotes
Live staff and operational dataAccount lifetimeEarlier deletion subject to the business's instructions and lawful retention.
Attendance evidence and payroll-preparation historyAccount lifetime, subject to instructions and lawful retentionIncludes owner-enabled coordinates, accuracy and photos, breaks, corrections, approvals and captured base/overtime rates. Upload-link expiry does not erase completed evidence.
Private employee records and contract evidenceAccount lifetime, with business-led retention reviewContact details, right-to-work files and reviews, payslips, immutable profile/contract versions and signing receipts. A recorded retention date is for manual review; it does not automatically erase records or earlier versions. Requests remain subject to the business's instructions and lawful retention.
Team collaboration, attachments and read stateAccount lifetime, subject to 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.
Closed account before erasure30 days after closureRecovery window before personal account details are erased.
Deletion-request evidence6 yearsRequest, deadline and outcome; detached from name and email after erasure.
Food-safety records and audit trailWhile active; exportable on closureThe business keeps its required copy.
Account and billing records6 years after closure where legally requiredApplicable tax and accounting obligations.
Support correspondence24 monthsService history and issue resolution.
Request and security logs90 days, then purgedMinimal personal information.
BackupsRolling 30-day windowLive deletions age out with the backups.
Mobile cache and outboxOutbox until sync; cache until pruned or clearedSeparated by user and business. Complete sync before clearing local data.