Fetch Portal
Privacy notice
This notice explains what personal information the Fetch Portal holds, why, who sees it, how long we keep it and what your rights are. It is written to be read, not filed: if anything in it is unclear, ask us.
- Who we are
- Who this covers
- What we hold and where it comes from
- Why we use it, and the legal basis
- Who we share it with
- Where it is stored and transfers abroad
- How long we keep it
- Cookies and local storage
- How we protect it
- Your rights
- Complaints
- Changes to this notice
1. Who we are
The data controller — the organisation responsible for your personal information in this portal — is Fetch Technology Group Ltd, a company registered in England and Wales, company number 11071470, of Printing House, 66 Lower Road, Harrow HA2 0DH, United Kingdom.
The portal is built and run on Fetch's behalf by FFO (Lowry Group), a UK firm that provides Fetch's finance function. FFO acts on Fetch's written instructions as a processor: it does not use the information for its own purposes.
ICO registration: to be confirmed. Privacy contact: privacy contact address to be confirmed — until then, write to the postal address above or to your usual Fetch contact. We do not have a statutory Data Protection Officer; the privacy contact handles every question in this notice.
2. Who this covers
- People at hotels and hotel groups that Fetch works with or is talking to: the contacts named on a proposal or agreement, the person who signs it, the person invoices go to, and anyone given a portal login to follow their onboarding.
- Staff of Fetch and FFO who use the portal.
Much of the information about hotel contacts is not collected from the person themselves: it is entered by Fetch's sales team from a conversation, taken from a signed agreement, or comes back from DocuSign or Xero. If that is how we came to hold yours, this notice is how we tell you, and we aim to point you to it within a month of first recording your details and no later than the first time we write to you.
3. What we hold and where it comes from
| Information | Where it comes from |
|---|---|
| Name, work email address, work phone number, job title and employer | You, a colleague of yours, or Fetch's sales team |
| Notes of conversations and meetings about a proposal, contract or onboarding | Fetch's sales and onboarding staff |
| Signed agreements, including your signature and DocuSign's record of when and from where it was signed | DocuSign, when an agreement is signed; or a signed copy uploaded by Fetch staff |
| Invoices, payment terms and payment status for your organisation, with the billing contact's name and address | Xero, Fetch's accounting system |
| What your organisation gives us in its onboarding portal: the project champion and the billing contact (name, work email, work phone and job title), the name of whoever signs off a design, a test or going live, and when they did, and the files uploaded for onboarding (menus, designs, training material) | You or a colleague of yours, in the portal; or Fetch's onboarding staff, from what you sent them |
| For portal users: sign-in name, hashed password, the date and time you last signed in, and the invitation that created your account | You, and the portal itself |
| Technical records: the address your device connects from and the pages requested, in the server's logs; after a failed sign-in, that address and a count of failures, to stop guessing | Your browser, automatically |
We do not hold payment card details, personal (non-work) addresses, or any special-category information, and we do not want them: please do not type them into the portal.
4. Why we use it, and the legal basis
| Purpose | Legal basis (UK GDPR Article 6) |
|---|---|
| Sending your organisation quotes (made in Xero and emailed to the contact who asked for one), recording the answer given with the email's Accept or Decline buttons (the answer, when it was given, and any note written with it), and preparing, sending, signing and storing agreements between Fetch and your organisation | Performance of a contract with your organisation; where you are not a party yourself, our legitimate interest in contracting with your employer |
| Invoicing your organisation and collecting payment | Performance of a contract; and legal obligation, for the tax and company records we must keep |
| Running the onboarding of your outlets and telling you what is needed next | Performance of a contract with your organisation |
| Managing the sales relationship and pipeline: who we have spoken to, about what, and when to follow up | Legitimate interests: running a business-to-business sales function. You may object (section 10) |
| Giving you a portal login, keeping it secure (including the emailed sign-in code) and knowing who did what | Legitimate interests: security of the service and of everyone else's information |
| Keeping the records the law requires and dealing with disputes | Legal obligation; legitimate interests |
We do not use the information for marketing, we do not profile anyone, and no decision about you is made by software alone.
5. Who we share it with
Only with organisations that help Fetch run the service, each bound by a contract that limits what they may do with it:
| Who | What they do | Where |
|---|---|---|
| FFO (Lowry Group) | Runs the portal and Fetch's finance function | United Kingdom |
| Amazon Web Services | Hosts the portal and sends its emails (sign-in codes, invitations, password resets, quotes, notices) | London region (eu-west-2), United Kingdom |
| DocuSign | Electronic signature of agreements | data region to be confirmed |
| Xero | Accounting: quotes, invoices and payments | New Zealand, Australia and the United States |
We may also share information with professional advisers, insurers, courts or regulators where the law requires or allows it. We never sell personal information and there is no advertising in the portal.
6. Where it is stored and transfers abroad
The portal, its database and its backups are kept in the United Kingdom. Where a supplier processes information outside the UK, we rely on the UK's adequacy regulations (New Zealand, the European Economic Area) or on the UK International Data Transfer Addendum to the EU Standard Contractual Clauses (Xero; DocuSign where its region is outside the UK or EEA), with a transfer risk assessment on file. Your own organisation's authorised users may open the portal from anywhere in the world; that is your organisation looking at its own information, not a transfer by us.
7. How long we keep it
| Information | Kept for | Why that long |
|---|---|---|
| Signed agreements, invoices and payment records | 6 years after the end of the financial year they relate to | Companies Act 2006 and HMRC record-keeping rules; limitation period for contract claims |
| Contact details and notes about the relationship | For the life of the relationship with your organisation and 6 years after it ends | Limitation period for contract claims |
| Prospect contacts where no agreement follows | 2 years after the last contact | Long enough for a paused conversation to resume; no longer |
| Portal accounts | Until your organisation tells us you no longer need access, or your account has not been used for 12 months, after which it is disabled and then removed | Security: dormant logins are a risk to everyone else's data |
| Sign-in codes; sessions | 10 minutes; 30 days from signing in | Only as long as they are useful |
| Counts of failed sign-ins (per connecting address, per account, and per name typed, kept only as a one-way hash) | 15 minutes; wrong sign-in codes 24 hours | Long enough to make guessing pointless |
| Server logs, including connecting addresses | 90 days | Long enough to investigate a security incident |
| Backups of all of the above | Up to 35 days, then deleted | So that a mistake or a failure can be undone; a backup never extends how long something above is kept |
8. Cookies and local storage
The portal sets one cookie, ffo_session, which is how it knows you are signed in. It is marked HttpOnly and Secure, lasts 30 days from when you signed in, and is removed when you sign out. It is strictly necessary for a service you asked for, so no consent banner is required for it (Privacy and Electronic Communications Regulations, regulation 6(4)).
The portal also keeps a working copy of the records you have opened and edited, and your display preferences (the menu, and light or dark), in your browser's local storage, so that a refresh does not lose your place. That copy stays on your device, goes nowhere but back to this site, and is cleared when you sign out, once everything in it has been saved. There are no analytics, advertising or tracking cookies, and the site loads nothing from anyone else's servers: even the typeface is served from here.
The page a quote email's Accept and Decline buttons open sets no cookie and keeps nothing in your browser. Its link is unique to that email, is not tracked, and stops working once the quote is answered, expires or is replaced by a newer version.
9. How we protect it
Everything travels over HTTPS. Passwords are stored as one-way hashes, never in clear. Signing in needs a password and a one-time code sent to your email address. Each account sees only what its role and its organisation allow, and the server enforces that, not just the screen. Access to the server is limited to named FFO staff. The portal records which account changed what, and when, and everything it holds is backed up every night. If, despite this, a breach were to put you at risk, we would tell you and the Information Commissioner's Office without undue delay, and the ICO within 72 hours of becoming aware.
10. Your rights
Under UK GDPR you can ask us to: tell you what we hold about you and give you a copy (access); correct anything wrong (rectification); delete it where we no longer need it (erasure); pause using it (restriction); stop using it where we rely on legitimate interests, such as sales notes (objection); or hand it to you or another organisation in a usable format (portability). None of these costs anything. Write to the privacy contact in section 1; we will answer within one month, and tell you if we need longer for a complex request. We may ask you to confirm who you are first. Where we must keep something by law — a signed agreement, an invoice — we will explain that rather than delete it.
11. Complaints
If you think we have handled your information badly, please tell us first so we can put it right. You also have the right to complain to the UK regulator: the Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow SK9 5AF; ico.org.uk/make-a-complaint; 0303 123 1113. If you are in the European Economic Area you may instead complain to the supervisory authority where you live or work.
12. Changes to this notice
This is version 1.5, dated 30 September 2026. When we change it in substance we will update the version and date here and tell portal users by email; earlier versions are available from the privacy contact.