Opnori Privacy Policy
Effective date: 12 November 2026
Opnori is an operations workspace for restaurants, operated by its founding team ("we", "us"). A UK company to operate Opnori is being incorporated; its registered name, company number, registered address and data-protection registration will be added to this page when incorporation completes.
Opnori is currently in an internal pilot with the founders' own restaurants. This policy explains what personal data Opnori handles, why, and your rights.
If you have a question or want to use your rights, email privacy@eosaxis.com.
1. Who is responsible for your data
- If you work for a restaurant that uses Opnori: the restaurant that employs you is responsible (the "controller") for your personal data in its Opnori workspace — your name, role, rota, availability and the account it invited you to create. We process that data on the restaurant's behalf and on its instructions.
- We are responsible only for what we decide ourselves: keeping Opnori secure (such as sign-in attempt counters and sign-in records), the restaurant owner's account and our agreement with the restaurant, and our legal obligations.
2. What we collect
Applying to use Opnori (restaurant businesses)
- The details you enter on the application form (business name, trading name, registration number, business address, contact name, contact e-mail and a short description). Our review team sees an application only after you confirm your e-mail address by opening the link we send; until then it is not shown to anyone.
Setting up your business (restaurant businesses)
- When a restaurant joins Opnori, our team sets up its business configuration on its instructions — brands, work locations, stores, opening hours, menu, purchasing catalogue, scheduling rules and order connections — before the first sign-in, and later makes changes the restaurant asks for. When our team uses the set-up or change-request access-period process, access is limited to that restaurant and to at most 14 days for set-up or 72 hours for a requested change. A team member may also provide ongoing assistance through a separate assigned account, without that set-up access period. This is limited to that restaurant and the product's permitted business capabilities, and requires a current assignment that can be withdrawn or may expire. Configuration changes are recorded with the team member, a description of the change and the time. Changes made through the set-up or change-request access-period process also record a reason. Daily configuration-view activity is recorded, and assigning or withdrawing ongoing assistance is recorded with its reason. The restaurant's owner can see the company-related records made available in Opnori. To check that order connections work, our team sees how many orders each store has received and when the last one arrived, never their contents or any customer details. Our team does not enter staff personal data through these configuration tools. Separate, read-only access to the limited staff-account records described under "Limited detailed support access" below follows the additional safeguards stated there. Staff are invited by the restaurant itself, which also decides which stores each person can use. We use the name, e-mail address and phone number of the restaurant's contact person to set up and support its account.
Limited detailed support access — only when enabled
The default platform view contains permitted business summaries, not unrestricted individual records. To view individual AI usage, an authorised Opnori team member with an internal platform role of Director, Head or FDE/BD must have a current assignment to your company and use their own authenticated platform session with the required multi-factor verification. They must select your company, one of its brands, a support or billing purpose, a reason and a date range, then preview and confirm a separate access permission. A platform role alone, including Director, is not enough.
Each individual usage entry contains an internal account reference, the fixed label "Metered person", and totals for registered calls, settled and unsettled calls, recorded settled cost, outstanding budget reservations and the combined amount counted against the budget. Real and simulated use are shown separately. These are totals for the selected period, not daily breakdowns, and the view does not return a profile-name field. Registered calls are not a count of messages or a guarantee of successful replies; the amounts are platform metering records, not a supplier invoice. Token counts are not metered and are not estimated. If a staff profile is de-identified, retained billing records remain linked to the same internal account reference; this view does not reconstruct the removed name. An internal reference can still be linked to a person, so these records are not described as anonymous.
A different access permission is required to view completed company staff-data deletion receipts. Only Director or Head users currently assigned to that company may use this view; FDE/BD users cannot access its receipt list or count. They must select the company, a support or privacy-status purpose, a reason and a date range, then preview and confirm. This view is not filtered by a brand or an individual. Each receipt contains only the company identifier and name, a receipt reference, the fixed record type "staff_person_erasure", the completion time and the status "completed". It does not return identity fields for the affected staff member or the person who carried out the deletion, request contents or per-person deletion details. It does not include private assistant-memory or attachment-deletion requests, or a queue of pending requests.
For both views, a date range can cover at most 31 consecutive UK calendar days, including both the first and last day, and cannot end after the current day in Europe/London. The deletion view selects receipts by their completion date in that timezone. Each permission covers only one of these data types and one company; individual usage access also covers only the selected brand. A confirmed permission lasts no more than 30 minutes from confirmation and ends sooner if it is closed or the session or underlying authorisation ceases to be valid. It does not renew automatically; a new period of access requires another preview and confirmation.
Both views are read-only. Current authorisation is checked on each read, including before the results are returned, and access is recorded in the activity audit. Each page contains at most 50 usage entries or 50 deletion receipts. These permissions do not grant bulk export, unattended collection, access to another company or access through an AI assistant. The views do not expose conversations, prompts, replies, attachments, credentials, health, HR or payroll records. We do not use this limited access for staff scoring, ranking or employment decisions. Restaurant Owners can review the company-related support activity made available to them, without receiving the underlying restricted records through that audit view.
Signing in
- Your name and the email address you use as your sign-in name. Account emails to that address include a verification link when you apply, the account-creation link for a restaurant owner, and — only when your manager or owner issues one for you (or Opnori, for a restaurant owner, after confirming who you are) — a single-use link to set a new password. If you are currently an authorised Owner, the same account address may also receive the Owner operating emails described below, subject to your notification-contact confirmation, preference and current Owner access. We do not use it to match you with other accounts, and nobody can request a password link for themselves by typing an address. A password link is emailed only to a sign-in address that has been confirmed; otherwise it is handed to you directly. You confirm your sign-in address yourself while signed in, from Settings, by opening a single-use link we email to it (valid for 24 hours); for a restaurant owner, creating the account from an account-creation link emailed to that same address also confirms it. We record when it was confirmed. Changing your sign-in name ends the confirmation, and a confirmed address gives no other access. Confirming an address for operating emails does not confirm your sign-in address.
- Your password, stored only as a one-way hash. We never see it in plain text.
- If you choose to connect a Google or Microsoft account in Settings, we store only a stable account identifier from that provider (Google: the account's "sub"; Microsoft: the tenant identifier and object identifier). The email address the provider shows is displayed to you once so you can confirm the right account; it is not stored. We request only the basic "openid", "email" and "profile" scopes and do not access your mailbox, calendar, contacts or files. Personal Microsoft accounts (Outlook/Hotmail) can be connected.
Working in Opnori
- Your role and which store(s) you belong to.
- Your rota shifts, the availability you submit, cover requests, stock counts and deliveries you record, and when each action happened.
- Records of important actions ("receipts") so the restaurant can see who did what.
Owner operating emails — daily summaries and alerts
When available, daily summaries are shown on the Noriclaw page for Owners, Managers and Staff, each within their existing permissions. Viewing an in-app summary does not require an operating-email preference or notification-contact confirmation.
Operating emails are sent only for companies in which the recipient is currently an authorised Owner. They do not include sections available only through Manager or Staff access. Account and sign-in emails are unchanged.
When these email features are available, Opnori uses existing authorised workplace records to prepare fixed, functional email templates, not marketing or AI-generated email text. A daily digest is scheduled for 08:00 Europe/London, with at most one digest per person per London report date. Permitted sections from more than one company or store are combined into that person's digest, but only within their current Owner scopes. Reporting dates and generation times distinguish previous-day operating figures from today's scheduled staffing figures and current status. Missing, unavailable or restricted information is not presented as a known zero.
- Owners: permitted company, site, brand and channel labels; reporting dates and times; order, cancellation, exception and comparison counts; stock-count, count-policy, purchasing-suggestion and invoice-review counts; scheduled staffing counts and gaps against requirements; system-status labels; and links to the permitted workspace pages. These are scheduled staffing figures, not proof of attendance. Sales information follows the Owner's existing outlet permissions and field restrictions, separately from access to site operations. Owner operating emails do not include individual staff names, identifiers, shifts or hours.
- Owner alerts, where that feature is available: newly detected order-import stoppages, a supported forecast that stock may run out before an expected delivery, and gaps between today's published staffing and requirements, plus one supported recovery notice for that event. Continuing observations of the same unresolved event do not create repeated alert emails. These immediate emails and recovery notices are for currently authorised Owners only.
All operating email content excludes financial amounts, item names, stock or count quantities, customer details, order identifiers, supplier-document text or images, and credentials. Links require sign-in and current authorisation; they contain no sign-in, session or confirmation token. Templates have no attachments or tracking pixels. The recipient address, business labels and small-group counts can identify people: these emails are not described as anonymous. The email provider receives the recipient address, the permitted message content and delivery metadata as described in section 5. Provider acceptance does not prove inbox delivery or reading; Opnori does not use read receipts or tracking pixels to establish that.
Each eligible Owner's operating-email preference starts on, but sending also requires a current, explicit confirmation that their own account email address can receive operating notifications. An existing confirmation is reused only if it belongs to the same person and current address source; otherwise the Owner makes this declaration once in their own Settings. We record the confirmation's person, time and address-source binding, together with the preference and limited delivery/deduplication metadata. This declaration is not verification of mailbox ownership, a way to match accounts, a password-recovery method or a request for legal consent. Successful sign-in, a correctly formatted address or an Owner role is not enough. An email address displayed by Google or Microsoft is not silently stored as a notification contact.
Only the eligible Owner can change their own operating-email preference in their own Settings. Switching it off stops subsequent daily digests and Owner alert/recovery emails, without disabling ordinary workspace functions, in-app summaries and tasks, or account/sign-in emails. Address or permission changes, deactivation or switching off invalidate unsent intentions; current contact, Owner role, permitted Owner scope and preference are checked again before dispatch. No operating email is sent without a valid confirmed address, an active eligible Owner and permitted content for that Owner scope. An external send that has already started cannot be recalled. An email does not grant permission to act: the original page rechecks current access, and Staff in-app count tasks still depend on the current published shift and existing counting permissions.
Orders from delivery platforms
- If a restaurant connects Deliveroo or HungryPanda, customer personal details are removed by our order-receiving service before orders reach Opnori. Opnori stores only the order items, quantities, prices, status, times and the platform's order and store references, and does not store the platform's raw order message.
Cookies — three, all strictly necessary; no advertising or analytics cookies:
- `opnori_session` keeps you signed in (expires after 12 hours);
- `opnori_csrf` protects your actions against cross-site requests (same lifetime);
- `opnori_oidc_attempt` exists for 10 minutes, only while you connect or sign in with Google or Microsoft.
Security records
- Sign-in attempt counters, stored only as one-way hashes of your sign-in name and network address, deleted 24 hours after the last attempt.
- A record of devices that signed in successfully (also hashed), kept 30 days.
- A record of each sign-in, account connection and disconnection (no password or token), kept while your account exists and deleted when your account is deleted.
3. Why we use it (UK GDPR)
- To provide Opnori to the restaurant you work for (on the restaurant's instructions, under its contract with us).
- To keep accounts and data secure, including limiting repeated sign-in attempts (our legitimate interests).
- To meet legal obligations.
We do not sell personal data and we do not use it for advertising.
4. How the assistant and invoice reading work
Invoice reading uses OpenAI. When staff photograph a supplier document — a delivery note, an invoice or a receipt — in Opnori to read it, we send OpenAI that photo and a fixed instruction. We do not separately add your account details, the restaurant's name, staff records, or prices held elsewhere in Opnori. The photo itself may contain personal information, such as a supplier's name or signature. Photograph only the document, not people, and avoid unnecessary personal information. Before sending, we remove hidden photo metadata, such as location, device and time. The photo is included in the request, not uploaded as a separate OpenAI file. PDF files are not sent for invoice reading; staff enter them by hand. Staff check every extracted line before it is saved as a business record.
Noriclaw. When Noriclaw's external AI service is enabled for your restaurant, it answers workplace questions and prepares suggestions using the approved route selected for your brand: OpenAI, or the Value route operated by DigitalOcean, described below. On the OpenAI route, a request may include your current message, up to ten permitted earlier messages from your own conversation, and relevant workplace information you are currently allowed to view. That information may include orders, stock and supplier-document details, employee names and references, published rotas, shift times and availability. Where your role permits planning, it may include planning drafts and employees' availability. Staff cannot use the assistant to see planners' drafts or other employees' availability, but authorised published rotas may include same-store colleagues' names and shifts.
Noriclaw on the Value route (no staff information). On the Value route, DigitalOcean processes the permitted text of requests using the DeepSeek-V4 Flash model hosted on its infrastructure. This route does not call DeepSeek's own API. A request may include your current message, up to ten permitted earlier messages from your own conversation, and relevant workplace information you are currently allowed to view, limited to orders, stock, supplier-document details, menu items and prices, and store-level counts. Staff information is not sent on this route: no employee names or references that identify a person, no rotas (draft or published), shift times or availability, and no planning or other workforce information. You appear to the assistant by role, not by name. Assistant functions that return staff information are not offered on this route; a question about rotas or staff is answered with a plain statement that it is not available here, and it is not passed to another provider. Text you type yourself is sent as you wrote it and may mention a person. The existing role, scope and human-confirmation limits still apply. Where your brand uses the OpenAI route, OpenAI processes requests under the separate terms below. Voice notes and image reading stay on OpenAI on either route.
We may also send confirmed preferences or rules you have saved, relevant conversation context marked as unverified, and limited record references, versions and times needed to interpret the information. Requests include a fixed instruction and descriptions of the assistant functions available to your role. Information returned by those permitted functions may be included in a further request to answer the same question.
Original assistant attachments are not sent, except voice notes and images read through the approved OpenAI image route, both described in this section. If you select files for a table-extraction path in a Noriclaw message, the request may include a limited extraction from up to three ready files: recognised numeric, date and unit candidates from the first table, with at most twenty data rows per file. Original file bytes, filenames and file hashes are not sent. The extraction can include attachment references, versions and information about omitted rows or tables. Free-text cells and formulas are withheld. These limits apply to assistant attachments, not to the invoice photographs described above.
Images. Original images stay on the separately approved OpenAI image-reading route; they are not sent to the DigitalOcean Value text service. Permitted text extracted from an image by OpenAI may be included in a later Value text request. Extracted text can still contain personal or business information; it is not made anonymous simply by being extracted or filtered. Invoice photographs and any other approved image-reading use keep their existing limits and OpenAI's separate processing rules.
Voice notes are transcribed by OpenAI. When Noriclaw's external AI service is enabled for your restaurant and you record or attach a voice note for Noriclaw, we send that audio to OpenAI once to turn it into text. The request contains only the audio and the transcription settings; we do not add your name, the restaurant's name or other Opnori records, but your recording itself may contain personal information. The transcript is shown under your voice note and is used like a message you typed: a model answer is not a business transaction, and business changes still need your confirmation. The audio and its transcript are kept as your private attachment and are deleted when you forget that attachment, when it expires, or when your account is deleted. The training and retention conditions below also apply to voice notes.
Names, shifts and conversation text can identify people. Filtering does not make this information anonymous or guarantee that every piece of personal information is removed. Do not include passwords, contact details or health information in an assistant message. A model answer is not a business transaction: proposed business changes still require human confirmation and Opnori's permission and version checks. The ordinary product pages remain available when the assistant is unavailable.
Training and retention at OpenAI. OpenAI states that API inputs and outputs are not used to train or improve its models unless the customer explicitly opts in. We do not opt in to sharing your restaurant's API inputs or outputs for model training. We send requests with `store: false`, asking OpenAI not to store the response as a saved Responses API object. This is not a promise of zero retention. Under OpenAI's default API controls, abuse-monitoring logs may contain requests, answers and related metadata and are kept for up to thirty days, unless longer retention is required by law or reasonably necessary to protect OpenAI's services or a third party from harm. Separate model-specific application state, including encrypted prompt caches, may be retained for up to twenty-four hours under OpenAI's published API controls. Certain image-safety flags may also result in retention for manual review. These provider rules are separate from how long Opnori keeps your restaurant's records and files, described in section 6.
Training and retention at DigitalOcean (Value route). DigitalOcean states that it does not use these requests to train models or send customer content back to the model's original creator. Its service terms allow relevant content and metadata to be retained where reasonably necessary for safety, security or compliance investigations. Its hosted models use automatic prompt caching of internal model state, with eviction based on capacity and use rather than a confirmed fixed retention period. A fixed maximum retention period for that cache or investigation content has not been established for this route. This is not a zero-retention service, and cached internal state is not described as anonymous. These provider rules are separate from how long Opnori keeps restaurant records and files, described in section 6.
Before this route is enabled, Opnori requires DigitalOcean's optional, team-wide Signals collection to be verified off for the actual DigitalOcean team used by this route. The provider's default setting is not evidence of our account's current setting. Turning Signals off does not turn off automatic prompt caching or erase information collected while Signals was on. If it was previously enabled, that earlier collection must be assessed before this route is enabled; this notice does not claim that it never happened or that it has already been deleted.
5. Who helps us run Opnori
| Provider | What for | Where |
|---|---|---|
| DigitalOcean (application and database hosting) | Hosting the application and database; data at rest encrypted by the provider. This is separate from the Value inference service. | London, UK, for the existing hosting service. This hosting location does not identify where AI inference is processed. |
| DigitalOcean, LLC (Value inference) | Only when the approved Value route is enabled for the restaurant: processes the permitted Noriclaw text described in section 4 using hosted DeepSeek-V4 Flash, including permitted text extracted from images by OpenAI. It does not receive original images, voice notes or staff information. The training, investigation and caching rules in section 4 apply. | Inference and associated processing are separate from our London hosting. DigitalOcean's published Data Processing Agreement identifies DigitalOcean, LLC as the provider. The published Serverless Inference information does not specify the countries in which this route processes data, so we do not offer a UK-only, EU-only, US-only or North-America-only processing guarantee for it. For transfers from the UK, that agreement relies on the UK Extension to the EU-U.S. Data Privacy Framework, and provides for the Standard Contractual Clauses with the UK Addendum if that framework is invalidated or DigitalOcean's certification lapses. Staff information is not sent on this route. |
| Amazon Web Services | Off-site backups, encrypted before upload with a key we hold offline, so AWS cannot read them | London, UK |
| Resend (Plus Five Five, Inc., USA) | Delivering application emails on our behalf: account/sign-in links and the Owner-only operating emails in section 2. Resend receives recipient email addresses, fixed message content and delivery metadata. Operating content includes business labels and counts within the recipient's current Owner scopes, subject to section 2's content limits; it does not include individual staff shifts or hours. | Sending infrastructure in Resend's EU region; Resend's primary processing operations are in the United States, so this is not EU-only processing. The transfer relies on the applicable Resend data processing addendum incorporating the UK International Data Transfer Addendum. Its deletion provision of within 90 days of account termination is not a promise that each email is kept for 90 days. |
| Cloudflare | Domain name service, and running our order-receiving services for connected delivery platforms | Global network. The order records these services keep (items, quantities, prices, status and references only — no customer details) are stored in Cloudflare's Western Europe region for HungryPanda; the Deliveroo receiver's order records contain no customer details and are stored in Cloudflare's EU jurisdiction |
| OpenAI (OpenAI OpCo, LLC, USA) | Reads photographed supplier documents and, where enabled for the restaurant, provides Noriclaw's external AI service. It receives the photographs, voice notes or bounded assistant information described in section 4. The API training and retention conditions in that section apply. | Processing may take place outside the UK, including in the United States and other locations used by applicable OpenAI sub-processors. This service is not offered with a UK-only or EU-only processing guarantee. For UK personal data, we rely on the applicable OpenAI Data Processing Addendum, which incorporates the EU Standard Contractual Clauses as amended by the UK Addendum. |
| Google, Microsoft | Only if you choose to sign in with them | As set by the provider |
| Deliveroo | Only if the restaurant connects it, to receive its orders | As set by the provider |
| HungryPanda | Only if the restaurant connects it, to receive its orders; data we receive may come from its servers outside the UK | As set by the provider |
Processing locations for OpenAI depend on the applicable API configuration and its sub-processors, as described above. Processing locations and retention rules differ between OpenAI and DigitalOcean's Value route. London application hosting does not mean that AI requests stay in the UK. Where data leaves the UK, we rely on the safeguards UK law requires, such as adequacy regulations or the International Data Transfer Addendum. Choosing the Value route does not waive a restaurant's stricter agreed limits on countries, retention or data separation; a company is not enabled on a route that has not been shown to meet its applicable conditions.
6. How long we keep it
- Staff data: while you work for the restaurant, and for 6 months after you leave, then removed as described below.
- Applications: an unconfirmed application is deleted after 7 days (its e-mail address is cleared within a day after the confirmation link expires, after 24 hours); a declined application is deleted after 30 days, with the e-mail address cleared at the decision; an accepted application becomes the restaurant's account record and is kept under the rules above.
- Encrypted off-site backups: 30 days, then deleted automatically; deleted data leaves the backups as they expire, and if a backup is ever restored your deletion is applied again first. Copies on our server: 48 hours. Our database provider's point-in-time recovery: 7 days.
- Files attached to the assistant: 90 days, or earlier if the user removes them.
- Invoice photos (supplier documents photographed for invoice reading): 90 days, then the photo is deleted. OpenAI's own answer is not kept: only the details Opnori asks for (supplier, document number and date, amounts, and each line's item, quantity, unit and amounts) are saved as a suggestion on the document, and they stay with the restaurant's records like a delivery entered by hand.
- Security records: as set out in section 2.
When a staff member's personal data is deleted at the restaurant's request, or when a staff member or manager deletes their own account in the Opnori app, their profile name is replaced with a placeholder. Their sign-in name and password credential, linked sign-in methods, sessions, preferences, availability and assistant conversations are deleted, and their access to the restaurant is removed. Business and billing records remain under their existing internal references. Removing profile details does not make those retained records anonymous. The limited support views described in section 2 do not show or reconstruct the removed profile name or sign-in details. If a backup is restored, the deletion is applied again before use. Text other people wrote mentioning them (for example a manager's note) is not rewritten — ask us if you want it reviewed.
When a restaurant owner asks to close their account in the Opnori app, Opnori handles the request within 30 days and contacts them before anything is closed. Nothing changes until then, and the request can be withdrawn. How to delete or close an account: Account deletion.
7. Your rights
Under UK data protection law you can ask to access, correct or delete your personal data, to restrict or object to how it is used, and to receive a copy. For data in a restaurant's workspace, we will pass your request to the restaurant and help it respond. Contact privacy@eosaxis.com. You can also complain to the Information Commissioner's Office (ico.org.uk).
To delete your account, follow the steps on Account deletion, or email privacy@eosaxis.com from the address you sign in with.
8. Security
Data is encrypted in transit (HTTPS). Each restaurant's data is isolated in the database, not only in the application. Restaurant-workspace access is limited by role and store. Opnori platform access follows its current role and scope; the detailed support views described in section 2 additionally require a current company assignment and a short-lived, purpose-specific permission. Passwords are hashed, and sign-in attempts are rate-limited. Backups are encrypted and the backup key is held separately from the servers.
9. Google user data
Opnori's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use only your Google account identifier to let you sign in. The email address Google shows is displayed to you once to confirm the account and is not stored.
10. Children
Opnori is a workplace tool and is not intended for anyone under 16.
11. Changes
We will post any change on this page with a new effective date, and tell restaurant owners in Opnori before significant changes take effect.