Skip to content

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

Legal

Privacy Policy

Last updated 18 November 2026

This policy explains how Misenta handles personal information. Its UK sections describe UK GDPR and the Data Protection Act 2018. The Australia and New Zealand information below explains how to contact us and which local privacy rules may apply to you.

Misenta (formerly ProCafe) is referred to in this policy as “Misenta”, “we” and “us”.

Who is responsible for your data

When you use Misenta to run your business, you (the business) decide how to use your staff and operational records — staff names, shifts, time-off requests, food-safety readings, handover notes and similar. In UK GDPR terms, you are the controller of those records and Misenta is your processor: we process that data on your instructions, as set out in our Data Processing Agreement.

Misenta is the controller of its own data: your account details, billing, support correspondence, any marketing you opt in to, and our security and audit logs. This policy covers that role too.

What we collect and why

  • Account identity — name and email of the owner/manager, and a one-way hash of your password (we never store the password itself). Basis: performance of our contract with you.
  • Staff & operational data you enter — held on your behalf as your processor. This includes the names, company, optional licence details, sign-in/out times and notes you enter in a door staff register, plus retention-policy reasons, record-hold reasons and review dates. Recording a licence number does not verify that licence. We do not decide why your operational data is collected; you do.
  • Billing — payments are handled by Stripe, our payment processor. Card details are entered directly with Stripe; Misenta never receives or stores full card numbers. Basis: contract and our legal obligations.
  • Support & security logs — to run, secure and support the service. Signed-in mobile apps report their installed version, build number, iOS/Android platform and a randomly generated installation identifier, associated with the user and business, together with the time of the report. This helps our support team diagnose version differences. It does not include advertising or hardware identifiers, food-safety records or screen-by-screen activity, and does not depend on notification permission. Basis: our legitimate interests in operating a safe service.

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.

Attendance, private employee records and team messages

For your business, we store attendance times, actual breaks, corrections and approval history. Owner-managed pay information includes hourly 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 location. When you choose to clock in under that policy, a supported app or browser asks for the relevant device permission and submits the location coordinates and accuracy, or the photo, with your staff, location and attendance references. These are stored attendance evidence, not temporary permission checks. There is 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 for using this information.

Private employee records can include contact and emergency-contact details, manually reviewed right-to-work documents and review outcomes, payslips, contract versions, typed signatures and authentication or signing receipts supplied by the employer or employee. Owners manage private personnel records and pay rates; linked employees can access their own permitted payslips and contracts. Clock-in photo review is restricted to owners. Uploaded documents and images can contain information or metadata supplied with the file. The business must choose necessary records, explain its purposes to staff and other people whose details it supplies, and set an appropriate lawful basis and retention instructions.

Team messaging stores message text, sender and conversation membership, timestamps and read state. Site-channel access follows current site permissions; private direct messages are available to their participants, not automatically to every owner. Pending mobile sends are encrypted on the device, but delivered messages are stored by the service and are not end-to-end encrypted. Staff and operational content is not sent to advertising measurement.

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.

Special-category data

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 the 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.

Cookies & analytics

In the signed-in app we use strictly-necessary cookies only: a session cookie to keep you signed in and, if you choose “remember this device”, a token cookie so that browser can skip the two-factor step. These are not used for tracking.

On our public pages (marketing, help, legal, security and contact) we use Google Analytics to understand visits and traffic at a high level. It sets analytics cookies and shares usage data with Google as a sub-processor. Analytics is not loaded in the signed-in app or the internal admin area, so your operational and account pages are not tracked.

Analytics runs only with your consent: we ask on your first visit and load nothing analytics-related until you accept. You can change your choice at any time via the “Cookie settings” link in the footer of any public page. See our Cookie Policy for the full list of cookies.

If you separately consent to Marketing, we use Meta Pixel and consent-bound Meta Conversions API events to measure Meta advertising. A verified trial or paid subscription event can include Meta browser/click identifiers, hashed account identifiers, IP address, browser user-agent, time and source page. We do not send operational records or passwords. Basis: your consent, which you can withdraw independently of Analytics at any time. See the Cookie Policy for the precise boundary and retention.

Where your data lives

The service and its database are hosted in the EU. Encrypted offsite database backups use Cloudflare R2. Bucket metadata checked on 5 November 2026 reports Western Europe (WEUR) and the default jurisdiction; this is not an EU-only residency guarantee. Some sub-processors (for example email delivery or payments) may process limited personal data in other countries. The providers and locations are listed in the Sub-processor List. Where UK transfer law applies, we use an applicable UK adequacy decision or transfer agreement/addendum. Australian and New Zealand businesses should also review their own cross-border handling obligations for staff data entered into Misenta.

How long we keep it

Retention is set out in the Retention Schedule. In general, operational data is retained for the account lifetime, subject to the specific periods in that schedule and lawful controller instructions. Door staff register entries follow an owner-reviewed venue policy, with a suggested app default of 12 calendar months. Owners must check their licence conditions and record a reason; this is not a universal legal minimum. Existing records receive at least 30 days on first adoption, and shorter policies do not bring recorded deadlines forward. An owner can apply a reasoned retention hold with a review date. The date does not release the hold; an expired record can become eligible for automatic deletion once an owner releases it. An active door staff hold also postpones whole-business trial erasure; an active recruitment hold also protects its applications from business or location erasure. Unrelated register entries can still expire under their own retention rules. Other account-erasure safeguards remain in place. Backups age out on a rolling window, and logs are kept only as long as needed. Google review API content uses the shorter cache limit described above.

Who we share it with

Within your business, records are shown to the users permitted by the relevant role, site, document or conversation controls described above. We also use the sub-processors that help us run the service — see the Sub-processor List. We do not sell personal data. We do not share advertising data with Meta unless the visitor has granted the separate Marketing choice.

Your rights

Under UK law, you can ask to access, correct, delete, restrict, object to or port your data. Because much of the data in Misenta belongs to a business (the controller), a staff member’s request usually goes to their employer; Misenta helps as processor. Contact support@misenta.app. You can also complain to the Information Commissioner’s Office (ICO) about UK matters. We respond to UK GDPR requests within one month where that law requires it.

Where you are based

Misenta is offered from the United Kingdom to businesses in several countries. The blocks below add, for each country we serve, the local law and authority that also apply to you, the tax position, and who operates the service. They add to the sections above and do not remove anything from them.

Ireland

This policy is written for UK data-protection law. The following states which local law and supervisory authority also apply to you and how to reach them.

For a business or person in Ireland, the EU General Data Protection Regulation (Regulation (EU) 2016/679) and the Data Protection Act 2018 apply to personal data we process about you as controller. The supervisory authority is the Data Protection Commission (dataprotection.ie). You can lodge a complaint with it, and you keep the rights set out under “Your rights” above. The service operator is based in the United Kingdom; the European Commission’s adequacy decision for the United Kingdom under Article 45 GDPR covers transfers from the EU to the UK.

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.

France

Cette politique est rédigée pour le droit britannique de la protection des données. Pour une entreprise ou une personne située en France, le règlement général sur la protection des données (règlement (UE) 2016/679, RGPD) et la loi n° 78-17 du 6 janvier 1978 relative à l’informatique, aux fichiers et aux libertés s’appliquent aux données personnelles que nous traitons en qualité de responsable du traitement. L’autorité de contrôle est la Commission nationale de l’informatique et des libertés (CNIL, cnil.fr), auprès de laquelle vous pouvez introduire une réclamation. Vous conservez les droits décrits à la rubrique « Your rights » ci-dessus (accès, rectification, effacement, limitation, opposition, portabilité, retrait du consentement).

L’exploitant du service est établi au Royaume-Uni ; la décision d’adéquation de la Commission européenne pour le Royaume-Uni au titre de l’article 45 du RGPD couvre les transferts depuis l’Union européenne vers le Royaume-Uni. Le service et sa base de données sont hébergés dans l’Union européenne.

Misenta est exploité par Serdar Kahraman, entrepreneur individuel. Adresse postale : Cleekim Drive, EH15 3QP Edinburgh, Royaume-Uni. Contact : support@misenta.app ou le formulaire de contact sur misenta.app/contact.

France (English version)

This policy is written for UK data-protection law. The following states which local law and supervisory authority also apply to you and how to reach them.

For a business or person in France, the EU General Data Protection Regulation (Regulation (EU) 2016/679) and the French Data Protection Act (loi Informatique et Libertés) apply to personal data we process about you as controller. The supervisory authority is the CNIL (cnil.fr), with which you can lodge a complaint; you keep the rights set out under “Your rights” above. The service operator is based in the United Kingdom; the European Commission’s adequacy decision for the United Kingdom under Article 45 GDPR covers transfers from the EU to the UK. The service and its database are hosted in the EU.

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.

Deutschland

Diese Richtlinie ist für das britische Datenschutzrecht verfasst. Für ein Unternehmen oder eine Person in Deutschland gelten für personenbezogene Daten, die wir als Verantwortlicher verarbeiten, die Datenschutz-Grundverordnung (Verordnung (EU) 2016/679, DSGVO) und das Bundesdatenschutzgesetz (BDSG). Zuständige Aufsichtsbehörde ist die Landesdatenschutzbehörde Ihres gewöhnlichen Aufenthaltsorts, Ihres Arbeitsplatzes oder des Orts des mutmaßlichen Verstoßes (Art. 77 DSGVO); eine deutschsprachige Fassung dieser Erklärung mit Rechtsgrundlagen nach Art. 6 DSGVO finden Sie unter https://misenta.app/de/legal/datenschutz.

Der Betreiber des Dienstes ist im Vereinigten Königreich ansässig; der Angemessenheitsbeschluss der Europäischen Kommission für das Vereinigte Königreich nach Art. 45 DSGVO deckt Übermittlungen aus der EU in das Vereinigte Königreich ab. Der Dienst und seine Datenbank werden in der Europäischen Union gehostet.

Misenta wird betrieben von Serdar Kahraman, Einzelunternehmer. Postanschrift: Cleekim Drive, EH15 3QP Edinburgh, Vereinigtes Königreich. Kontakt: support@misenta.app oder das Kontaktformular unter misenta.app/contact.

Germany (English version)

This policy is written for UK data-protection law. The following states which local law and supervisory authority also apply to you and how to reach them.

For a business or person in Germany, the EU General Data Protection Regulation (Regulation (EU) 2016/679) and the Federal Data Protection Act (BDSG) apply to personal data we process about you as controller. The competent supervisory authority is the data-protection authority of the German state (Land) where you live or work or where the alleged infringement took place (Article 77 GDPR). A German-language version of this policy with Article 6 legal bases is at https://misenta.app/de/legal/datenschutz. The service operator is based in the United Kingdom; the European Commission’s adequacy decision for the United Kingdom under Article 45 GDPR covers transfers from the EU to the UK. The service and its database are hosted in the EU.

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.

Australia

This policy is written for UK data-protection law. The following states which local law and supervisory authority also apply to you and how to reach them.

Where the Privacy Act 1988 (Cth) and the Australian Privacy Principles apply to personal information we hold about you for our own account, billing or support purposes, you can ask us to access or correct it and can raise a concern with the Office of the Australian Information Commissioner (oaic.gov.au). The “Australia and New Zealand” section above explains how requests are handled. The service is hosted in the EU and the operator is based in the United Kingdom, so your information is held overseas.

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.

New Zealand

This policy is written for UK data-protection law. The following states which local law and supervisory authority also apply to you and how to reach them.

Where the Privacy Act 2020 applies to personal information we hold about you for our own account, billing or support purposes, you can ask us to access or correct it and can raise a concern with the Office of the Privacy Commissioner (privacy.org.nz). The “Australia and New Zealand” section above explains how requests are handled and the timeframes that apply. The service is hosted in the EU and the operator is based in the United Kingdom, so your information is held overseas.

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.

United States

This policy is written for UK data-protection law. The following states which local law and supervisory authority also apply to you and how to reach them.

US state privacy laws may apply to personal information we hold about you for our own account, billing or support purposes, depending on where you live. We do not sell personal information and do not share it for cross-context behavioral advertising, other than the consent-gated Meta advertising measurement described under “Cookies & analytics”, which you can decline or withdraw at any time. If you are a California resident, the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA) may give you the right to know what personal information we collect and how we use it, to delete it, to correct it, to opt out of any sale or sharing, to limit the use of sensitive personal information, and not to be discriminated against for exercising those rights. To exercise a right, email support@misenta.app with “Privacy” in the subject; we verify requests before acting on them and you may use an authorized agent. Staff and operational records entered by a cafe are the cafe’s records; send those requests to the cafe first.

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.

Australia and New Zealand

Australian and New Zealand customers use the same EU-hosted service described above. If you are in Australia, you can ask us to access or correct the personal information Misenta holds about you for its own account, billing or support purposes. You can raise an Australian privacy concern with us and, where the Australian Privacy Act applies, with the Office of the Australian Information Commissioner. The Australian Privacy Principles include rules about notice, access, correction and overseas disclosure. They do not impose the UK GDPR's one-month response or ICO reporting rule on Australian requests.

If you are in New Zealand, you can likewise ask us about account, billing or support information we hold about you and raise a concern with the Office of the Privacy Commissioner. Where the New Zealand Privacy Act applies, a decision on an access or correction request is generally due within 20 working days, subject to permitted extensions. Since 1 May 2026, Information Privacy Principle 3A may require a business that collects someone's information from another source to make that person aware of the collection. A business entering staff details should review its own notice duties. New Zealand's Principle 12 also governs relevant overseas disclosures; whether using a service provider is a disclosure depends on how the provider uses the information.

For staff and operational records entered by a business, contact that business first for access or correction. We assist the business with requests involving information it controls. For information we handle for our own purposes, contact support@misenta.app directly.

Security & breaches

Our security measures and how to report a problem are on the Security page. If a personal-data breach is likely to put people at risk, we notify affected customers without undue delay. We assess any reporting to the ICO, the Australian regulator or the New Zealand Privacy Commissioner under the applicable local law; the UK 72-hour rule is not a universal deadline for every market.

Contact

Questions about this policy or your data: contact Misenta.

Service operator

Misenta — Serdar Kahraman, sole trader

Cleekim DriveEH15 3QP EdinburghUnited Kingdom

Contact: support@misenta.app