Skip to content

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

Privacy notice

Canadian edition dated 2026-11-18

How Misenta handles Canadian personal information, international processing, choices and privacy requests.

Consulter ce document en français

Team files, reactions and polls

Team collaboration also processes quoted-reply references, uploaded photo and file contents, filenames, file types, sizes and integrity checks, together with their sender and conversation references. Files use private object storage and current conversation permissions. A temporary download link expiring does not erase the stored file. Uploaded files can contain information and metadata supplied with them.

We store each user's reactions and conversation mute preferences. The app shows reaction totals and your own reaction state. Polls store the question, options, intended site/role audience, dates, your selected option and operation history. Eligible users see option totals and their own choice, not a named list of other people's votes. Votes remain linked to user accounts internally; these are not anonymous polls.

The encrypted mobile outbox preserves queued text, reply references and already-confirmed attachment references for retry. Before a picker opens, an encrypted recovery checkpoint can retain unsent text, a minimal quote and confirmed attachment metadata for the current user, business, site and conversation. Selected file bytes are not in that text outbox: files must upload and be confirmed online before their references can accompany an offline send. Private team messaging is not offered on the shared kitchen tablet.

Responsibility and contact

Misenta is operated by Serdar Kahraman, a sole trader. Postal address: Cleekim Drive, EH15 3QP Edinburgh, United Kingdom. Contact: support@misenta.app or the contact form at misenta.app/contact.

The cafe determines the purposes for its staff and operational records; Misenta processes those records on its documented instructions. Misenta is responsible for its own account, billing, support, consent, security and audit information. The person responsible for privacy requests is Serdar Kahraman, reachable at support@misenta.app; mark the request ‘Privacy’.

Applicable Canadian requirements include PIPEDA and provincial private-sector privacy laws according to the activity and jurisdiction. Our existing UK data protection obligations also apply where relevant. A UK legal basis does not replace consent or another requirement under applicable Canadian law.

Information and purposes

We use the account name, email and password hash to create and secure access. We hold staff names, shifts, time-off requests, readings, documents and other operational information on behalf of the cafe. Payments and invoices are handled with Stripe; full card numbers are not received or stored by Misenta. Support correspondence and limited security logs help us resolve problems and protect the service.

A sickness absence classification can reveal health information. Private employee files supplied by the business or employee may also contain health or other sensitive personal information. We process these records on the business's documented instructions. The business must decide what is necessary, meet applicable requirements for processing sensitive information, inform the people concerned and set appropriate retention instructions. We do not require diagnoses or detailed medical histories to record a sickness absence. Do not include unnecessary medical or other sensitive details in notes, messages or uploaded files.

Attendance, private employee records and messages

For the business, we store attendance times, actual breaks, corrections and approval history. Owner-managed pay information includes base and overtime rates, captured rate snapshots, reviewed payable minutes and payroll-preparation totals. These tools do not pay wages or determine employment entitlements.

Venue-location checks and clock-in photos are off by default. In Pro and Operations, an owner can enable them for a site. When a person chooses to clock in under that policy, a supported app or browser requests device permission and sends coordinates and accuracy, or a photo, linked to the staff member, site and attendance event. This evidence is stored, with no background location tracking, facial recognition or automated identity matching. Native location checks require a compatible app version; ordinary clock-in remains available when these requirements are off. Device permission does not establish the employer's lawful basis or replace its applicable notice and consent duties.

Private employee records can include contact and emergency-contact details, manually reviewed right-to-work documents and outcomes, payslips, contract versions, typed signatures and signing or authentication receipts supplied by the employer or employee. Owners manage private personnel records and pay rates; linked employees can read their own permitted payslips and contracts. Only owners review clock-in photos. Files can contain information or metadata supplied with them. The business chooses necessary records, purposes, applicable authority, notices to affected people and retention instructions.

Team messaging stores text, sender, conversation membership, timestamps and read state. Site channels follow current site permissions; private direct messages are available to their participants, not automatically to every owner. Pending mobile sends are encrypted on the device; delivered messages are stored by the service and are not end-to-end encrypted. Staff and operational content is not sent to advertising measurement. Business users receive information only through the relevant role, site, document or conversation controls.

Mobile app support information

Signed-in mobile apps report their installed version, build number, iOS/Android platform and a random installation identifier, linked to the user and cafe, with the report time. Our support team uses this information to diagnose version differences. It contains no advertising or hardware identifier, operational records or screen-by-screen activity, and does not depend on notification permission. We keep the latest report per installation, user and cafe until the account is erased.

Optional analytics and marketing

Necessary session and optional trusted-device cookies support sign-in. On public pages only, Google Analytics runs after Analytics consent. A separate Marketing choice controls Meta Pixel and consent-bound Conversions API measurement when configured. Neither is loaded in signed-in operational pages or internal administration. We do not sell personal information.

Consented Meta events can include browser or click identifiers, hashed account identifiers, IP address, browser user agent, time and source page. They do not include passwords or operational records. Analytics and Marketing can be withdrawn separately in Cookie preferences. This browser advertising choice does not sign you up for promotional email.

Hosting and international processing

The application and database are hosted in Germany in the European Union. Encrypted offsite database backups use Cloudflare R2. Current bucket metadata checked on 5 November 2026 reports Western Europe (WEUR) and the default jurisdiction; this is not an EU-only residency guarantee. The recipient list identifies providers for payments, email, monitoring and consented public-page measurement; some processing takes place in the United States. Canada support does not mean Canadian data residency.

Personal information processed abroad can be subject to lawful access by courts, law enforcement or national-security authorities there. Contractual safeguards cannot override those laws. Review the data processing agreement and recipient list. A business remains accountable for outsourcing; Québec businesses must assess applicable privacy-impact and written-agreement requirements before sending information outside Québec.

Retention, access and correction

The retention schedule sets the service's periods and deletion process. You may request access, correction and information about use and disclosure, and raise a privacy concern at support@misenta.app. Withdrawal of optional consent applies prospectively; necessary service or legal retention may continue. Requests about employer-controlled records usually go to the employer, with Misenta assisting on its instructions.

We respond within the applicable statutory period. PIPEDA access requests normally require a response within 30 calendar days; an extension needs a permitted reason and the required notice. You may complain to the Office of the Privacy Commissioner of Canada or the competent provincial commissioner, including Québec's Commission d’accès à l’information, or to the UK ICO where its law applies.

Security incidents

We use appropriate access and security controls and notify affected customer organisations of personal-data breaches without undue delay. We assess and perform reporting, individual notification and incident-record duties required by applicable law; Canadian thresholds and timelines are assessed separately from the UK GDPR's 72-hour reporting rule. Report a concern to support@misenta.app without including unnecessary sensitive information.

Optional connections chosen by your business

An owner separately authorises provider connections or supplies an authorised API key. Misenta stores connection permissions, location or tenant mappings and encrypted access credentials to carry out the selected workflow. These connections follow the business’s instructions and current role/site controls; they are separate from the providers used to operate Misenta itself. The external service’s own terms, privacy information and retention also apply.

Google Business Profile is separate from optional website Google Analytics. With an approved Misenta API application and owner consent, we retrieve the mapped location’s review text, reviewer display name, rating, provider dates and reply status. A saved, human-written reply is sent to Google only after explicit confirmation. In-app alerts contain Misenta-authored site/platform/time references. Changing Analytics consent does not connect or disconnect a review profile.

Xero receives the selected reviewed invoice, supplier/contact references, account/tax mappings and amounts for a confirmed DRAFT bill. Employment Hero Payroll/KeyPay regional accounts in the UK, Australia and New Zealand receive explicitly mapped employee identifiers and reviewed approved time, earning categories and wage inputs in GBP, AUD or NZD. Owners can release verified provider payslips only to their mapped employee. These handoffs do not approve or pay bills, calculate statutory payroll, file taxes or pay staff.

Remote Global Payroll uses separate company-authorised OAuth consent. We retain the company and selected legal-entity/employment identifiers, country and time-code mappings, encrypted access/refresh tokens and handoff evidence. Owner-confirmed handoffs send approved time inputs, their effective dates and stable source references in seconds or whole hours. They do not send monetary pay items, wage rates or currency conversions; Remote’s own payroll rates and rules apply. An existing Remote Global Payroll account, approved Misenta partner setup and verified external-ID support are required. Only the mapped employee can access a provider payslip after the owner explicitly releases it.

Square, Toast and Lightspeed item-sales imports retain selected product, quantity, modifier, NET/tax/refund and source-time fields; the additional readers discard customer, address, staff and payment-detail expansions. A separately confirmed supplier order email sends the approved order snapshot to the owner-reviewed supplier recipient through the configured transactional email service. Approval alone does not send an order.

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.

Optional AI-account connections and reviewed actions

Where configured, you may connect your own ChatGPT or Claude account using your individual Misenta sign-in. Core supports permitted reads. Pro and Operations also support the bounded actions below only after the owner enables them; business writes are off by default. Owners control access for managers, supervisors and staff through role defaults and individual membership overrides. Each person separately consents to the business, locations and categories. Existing read grants do not gain write access automatically. Current membership, normal app permissions, location restrictions and plan limits are checked again for each request and approval.

Read categories contain limited task and maintenance details, published shifts, recorded waste totals and published allergen declarations. Titles and published staff names may contain personal information. Authorised action proposals can contain a task title, assignment and due date, or the staff and shift details needed for a bounded copy into draft schedules. The same signed-in person must review the exact proposal and approve it in Misenta before one open task is created or a draft schedule copy is applied. These actions do not record readings, complete or sign off checks, publish schedules, process private HR or pay data, or delete records. Raw incident stories, private HR and health files, pay, SIA details, photos and operational notes remain excluded.

Your business decides whether sharing permitted records with its chosen AI service is appropriate. The provider receives authorised results under your own account and workspace terms, including its retention, training settings and international processing arrangements. Misenta does not make a model inference call or automatically connect existing customers. You can disconnect in Settings → AI connections. Disabling business writes blocks later approvals immediately; disconnecting cannot recall information already copied into an external conversation.

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

Shared manual workflows follow the employer’s recorded policy and the selected venue’s stored country. Verified UK statutory guidance and SSP estimates apply only to UK employment; display language never selects employment law. On your business's instructions, HR tools store employer-entered right-to-work checks and evidence references, follow-up dates, private family-leave notices and review history, flexible-working declarations and decisions, and reviewed Statutory Sick Pay inputs and estimates. These records can reveal health, family or pay information. Current owner permissions and location restrictions protect private administration; linked staff can access only their permitted own notices and requests. Lateness reports use associated published shifts and actual clock-ins, with a reviewed grace threshold; they do not score absence, deduct wages or make disciplinary decisions.

Recruitment stores the employer's published vacancy and applicant privacy notice, applicant contact details and statement, review stages and explicit hiring handoff. A public vacancy link exposes only its published job information and application form. Applicant records remain private to authorised owners. Your business is responsible for its applicant notice, necessary information, lawful basis and retention instructions. These tools do not perform government identity checks, decide statutory eligibility, rank applicants automatically, run payroll or pay wages. Private HR, applicants and SSP inputs and amounts are excluded from the optional AI connector. Human-written team recognition stores an optional recipient reference under the existing conversation permissions.

The public job form loads a Cloudflare Turnstile security check in your browser. Misenta sends Cloudflare the response and the IP address available to its server, which can be the address of a proxy.

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.