Naar de inhoud

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

Legal

Data Processing Agreement

Last updated 5 November 2026

This DPA forms part of the agreement between the cafe (the controller) and ProCafe (the processor) for the staff and operational data ProCafe processes on the controller’s behalf.

Subject-matter & duration

ProCafe processes the controller’s data for as long as the controller has an account, to provide the ProCafe service.

Nature & purpose

Storing and presenting rotas, attendance, time-off requests, food-safety and operational records, private employee documents, payroll-preparation information and team messages, so the controller can run their cafe. The controller determines which optional attendance policies to enable and the necessary purposes, lawful basis, notices and retention instructions for its staff and other people whose information it supplies.

Types of data & people

Staff names, optional logins, shifts, time-off and operational records; attendance times, breaks, corrections and approvals; captured base and overtime pay rates and reviewed payable minutes; private contact and emergency-contact details, right-to-work documents and manual review outcomes, payslips, contract versions and signing or authentication receipts; and team message text, participants, timestamps and read state. These concern the controller's staff and contacts whose details they provide. Owner-enabled foreground venue checks add stored coordinates and accuracy; owner-enabled clock-in photos add image evidence. Neither is background tracking or facial recognition. Files can contain information or metadata supplied with them. Sickness absence classifications can reveal health information; private employee files may also contain health or other sensitive personal information. These records are processed on the controller's documented instructions, subject to the requirements described in the Privacy Policy.

Team collaboration includes message and quote content, photo/file contents and metadata, conversation membership, read state, reactions, mute preferences, poll questions/options, user-linked votes and operation history. Current conversation or poll-audience permissions control access; the app exposes aggregate poll counts and each person's own choice rather than other voters' identities.

Optional connections chosen by your business

An owner separately authorises provider connections or supplies an authorised API key. ProCafe 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 ProCafe 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 ProCafe 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 ProCafe-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 ProCafe 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 ProCafe 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 ProCafe’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

Processor obligations

  • Process only on the controller’s documented instructions (this DPA and the product’s use).
  • Keep the data confidential and ensure staff with access are under confidentiality.
  • Apply appropriate technical and organisational security measures — see the Security page.
  • Assist the controller with data-subject requests and with security/breach duties.
  • Notify the controller of a personal-data breach without undue delay.
  • Delete or return the data at the end of the service, subject to any legal retention.
  • Make available the information needed to show compliance with these obligations.

Sub-processors

The controller authorises the sub-processors on the Sub-processor List — including Stripe, our payment processor (card details are handled by Stripe; ProCafe does not store card numbers). We give advance notice before adding or changing a sub-processor, and where this DPA provides it, the controller may object and, failing resolution, terminate.

International transfers

Where a sub-processor is outside the UK/EEA, an appropriate transfer safeguard is used (for example a UK adequacy decision or the UK International Data Transfer Agreement / Standard Contractual Clauses). We prefer UK/EEA-based sub-processors where practical.

Audit

On reasonable request and notice, ProCafe provides information to demonstrate compliance.

Service operator

ProCafe — Serdar Kahraman, sole trader

Cleekim DriveEH15 3QP EdinburghUnited Kingdom

Contact: support@procafe.app