Terms of Service

21/09/2026 [21/09/2026]

These are the rules for using G-Reader. Plain language on purpose — you should be able to read this once, at the counter, and know where you stand. The service is run by [G-Reader], registered in [Finland], [Support Ticket System]. Contact:

How we handle information is a separate document: the privacy policy. It's part of this agreement too. So is the data processing agreement at the end, which is what covers your guests' details specifically. Where the two disagree about guests' information, the data processing agreement wins. Where the law says something different from any of it, the law wins.

Who can sign up

• This is a tool for businesses. You're signing up on behalf of a restaurant or similar business, and you're allowed to make decisions for it. That includes a sole trader buying for their business.
• You must be 18 or over.
• The inbox you connect must be one you're entitled to give access to. Connecting someone else's mail without their say-so is not something we can fix afterwards, and it ends the account.

We offer this for business use, not personal use. If consumer law turns out to apply to you anyway, the rights it gives you still apply — accepting these terms doesn't sign them away.

What you get

We watch one connected inbox and show the payments, bookings and orders we find on your board, for as long as your subscription is running. That's what you're paying for. We may improve it, change how it looks, or add to it; if we ever take away something you rely on, we'll tell you before we do.

It is a helper, not the official record. Your board is a convenient view of mail that lives in Gmail. We don't check whether money actually arrived — we show you what the email said. Mail can be delayed, worded unexpectedly, matched wrongly, or be fraudulent in the first place. If something is missing from the board, the mail is still in your inbox. For anything that matters, check with Epassi, Edenred or whoever sent it. Please don't run a full house on the assumption the board can't miss anything.

We're not a bank, a payment company, a booking agent or an accounting system. We don't take your guests' money, fulfil their orders, guarantee their reservations, or settle arguments between you and them.

Paying

• The price, the billing period and any tax are shown before you commit. It's a monthly subscription.
• Stripe takes the payment. Your card details go to Stripe, never to us.
• It renews automatically each month until you turn that off. You can turn it off any time in Settings → Renewal, with one switch.
• Turning off renewal keeps everything you've already paid for. The service runs to the end of the period you've paid, then stops.
• If a payment fails we'll say so in the app and try again. If it keeps failing, we stop reading your inbox and, a week later, hand our access back to Google. Your account is still there — fixing the card brings it back.
• If we raise the price, you'll get at least [30] days' notice and it won't apply before a renewal after that. You can cancel first.

Disconnecting Gmail, removing our permission in your Google account, closing the browser or simply not using the service does not cancel billing. Turning off renewal does. So does deleting your account. If something goes wrong on our side and a charge appears after you've cancelled, tell us and we'll refund it — see below.

Refunds

Refunds are not automatic, and they're not issued just because a month has been paid for and gone unused. Turning off renewal is the way to stop paying; a refund is for when something actually went wrong.

We do look at every request, and we say yes to the fair ones:

• Charged by mistake — a duplicate charge, a charge after you cancelled, a charge for an account you never set up. Tell us as soon as you notice and we'll sort it out. There's no deadline on getting a wrong charge corrected.
• The service didn't work and we couldn't put it right in a reasonable time after you told us — we'll refund the part you couldn't use.
• We stopped offering it, or ended your subscription for our own reasons — we refund whatever you'd paid for beyond that.
• Everything else is reviewed one by one. We look at what was charged, what was used, and what happened, and we tell you the answer with the reason. We aim to reply within [5] working days; the bank may take longer than that to move the money.

A refund goes back to the card that was charged. We won't ask you to drop a genuine complaint, a lawful chargeback, or any right the law gives you as a condition of getting one.

How to ask for a refund

1. Open the help button in the app — bottom-left corner, on any screen.
2. Choose Refunds.
3. Write which charge it is — the date and the amount are enough to find it — and what went wrong. You don't need to find an invoice number.
4. Send it. You'll get a ticket number straight away. Keep it; it's how you refer to this later.
5. We reply in that same conversation. It stays under Messages in the help panel, so you don't have to search your mail for it.

If you can't sign in, write to [[email protected]] instead. We won't make account access a condition of cancelling or of getting a charge corrected.

Invoices and receipts

Every payment is recorded. In Settings you'll see the list: the date, the amount, and whether it went through. If you need a proper invoice — with your company name, business ID, or a different billing address on it:

1. Open the help button and choose Invoices.
2. Say which payment it's for (date and amount).
3. Write the details exactly as they need to appear on the invoice.
4. We send it back in the same conversation.

If you need something from a payment made a long time ago, ask anyway — the billing record is kept, so we can find it.

Using it properly

Don't do any of this:

• Try to reach another customer's account, board, bookings, or support conversations — or test whether you can.
• Attack, probe, or overload the service; try to get around the security checks; or send it made-up requests pretending to be someone else. Security testing needs our written permission first.
• Connect an inbox you aren't entitled to connect.
• Share one account across separate businesses to avoid paying for each, or resell the service as your own.
• Use it to collect people's information for anything other than running your restaurant.
• Automate hammering the service, or run it at a volume that degrades it for everyone else.

If you find a security problem, please tell us privately at [PUBLIC EMAIL ADDRESS] rather than publishing it. We'd much rather hear from you.

Keep the personal details in your matching rules, custom fields and support examples to a minimum. Don't route card numbers or identity documents through the service.

What happens if you do

Depending on what happened and how bad it is, we may do any of the following. We'll normally tell you which one and why — unless telling you would help whoever is attacking the service, or the law stops us. If it's something you can put right, you'll normally get [14] days to do it before we go further; we can act straight away where people or the service are at risk.

• Paused We stop reading your inbox for a while. Your account and everything in it stay as they are. Usually this is us being careful about something we've noticed, and it's lifted once it's understood.
• Restricted The account keeps working, but something specific is limited — how often it can do a thing, or a feature that was being misused. Billing continues as normal.
• Suspended You can't sign in. This is for serious or repeated abuse. A suspended account is not refunded, including the part of the month it hasn't used. You can still write to support to argue your case, and if we got it wrong we'll put it right and refund the time you couldn't use.
• Disabled The end. Access is finished, the subscription is cancelled, and your data is deleted on the schedule in the privacy policy. Kept for the worst of it — attacking the service, or using it against other people.

If you think we've got it wrong, say so — in support, or at the public address above if you can't sign in. We read those, and reversing a wrong decision costs us less than keeping an unfair one. Complaining, or making a privacy request, is never itself a reason for us to act against you.

Your guests' information

Bookings and orders contain your guests' details. Those are yours and you're responsible for them: for being entitled to collect them, for telling people what you do with them, and for keeping them to a minimum. We only hold them to show you your board, we only do what you ask with them, and we delete them on the schedule in the privacy policy. If you need a particular booking removed sooner, ask in support.

The detail of that arrangement is the data processing agreement below.

When it's not available

We work to keep it running, but we don't promise it will never be down. Google can be slow or unavailable, servers need updating, and connections break. We don't promise a specific uptime figure, and we'd rather say that than print a number we can't stand behind. Your mail is unaffected by any of it — it's in Gmail the whole time.

Neither of us is responsible for a delay caused by something genuinely outside our control, as long as we do what we reasonably can to limit the damage. That doesn't excuse us from repaying you for service you paid for and never got.

Who owns what

We own the software, the design of this site, the documentation and the branding we made for this service — except for third-party components, which belong to whoever owns them. While your subscription is running, your business may use the service for its own operations. You may not resell it, sublicense it, redistribute our software or site content, remove ownership notices, or present it as your own product.

Your mail, your business records and anything you supply stay yours. You give us only the permission needed to run the service for you. We claim no ownership of your guests' information. You're welcome to keep a copy of these terms and the privacy policy for your records.

Google, Gmail, Stripe, Cloudflare, Epassi and Edenred are other companies' names and marks. We mention them to say what we work with — it doesn't mean they endorse us or are connected to us.

Where we stand if something goes wrong

If we're at fault, what you can claim from us is limited to what you've paid us in the twelve months before it happened. We aren't liable for business you lost, bookings you missed, or profit you didn't make, because a payment or booking didn't appear on the board. Please take the obvious steps to limit avoidable damage — checking disputed payments at the source, keeping your own records.

That limit doesn't apply where the law says it can't — for anything we do deliberately, for gross negligence, for death or personal injury caused by negligence, or for anything else that can't be limited by agreement. It doesn't remove the refunds promised above, anyone's right to compensation under data protection law, or a regulator's powers. Neither of us can contract out of our own data protection duties.

If you deliberately misuse the service, connect an inbox you had no right to, or put material into it that infringes someone's rights, and a third party comes after us for it, you cover our reasonable direct costs to the extent you caused it. That doesn't apply to anything caused by our own breach or negligence, and it doesn't move our regulatory responsibilities onto you.

Ending it

• You: turn off renewal any time in Settings. To go further, Settings → Delete my data removes everything and gives you a reference confirming it.
• Us: we can end this with [30] days' notice, and we'll refund whatever you've paid for beyond that. We can end it immediately in the abuse cases above.
• Whichever way it ends: our access to your inbox is handed back to Google, and your data is deleted on the schedule in the privacy policy.

Before you close the account, tell us if you need a copy of anything we're still holding for you — once it's deleted we can't get it back, and we don't keep backups. Keep your own payment, booking and accounting records; board entries expire while a subscription is running and after it stops.

Changes to these terms

If we change anything that matters, we'll tell you in the app at least [30] days before it takes effect, unless an urgent legal or security reason means we can't. Carrying on using the service after that means you accept the new version. If a change makes something you already paid for materially worse and you say so before it starts, you can end the agreement and get the unused part back. Where the law requires us to ask again rather than assume, we'll ask.

The legal bit

This agreement is governed by the law of [Finland], and disputes belong to the courts of [Finland]. Where the law gives you a different court or a right you can't sign away — including data protection complaints — that still applies. Please talk to us first if you can, but you don't have to before exercising a legal right.

If any part of this turns out not to hold, the rest still stands. Not enforcing something once doesn't mean giving it up. If we transfer this agreement, it must not leave you worse off, and anything derived from Google stays bound by Google's rules. The parts about ownership, confidentiality, money owed, lawful retention and any live dispute carry on after the agreement ends.

Data processing agreement

This section is the agreement required by Article 28 of the GDPR. It applies to your guests' and correspondents' personal data that we handle on your behalf, for as long as we hold it. You are the controller of that data; we are your processor. It does not cover the information we handle for our own purposes — your account, your billing, our legal obligations — which is in the privacy policy.

What we do, and on whose instructions

Purpose: showing and managing your restaurant's payments, bookings and orders.
What we do with it: retrieve it from the mailbox you authorised, examine it automatically, extract the relevant fields, store them temporarily, display them to you, let you correct or add entries, support you, and return or delete it.
How long: continuously while monitoring is on, then the retention and deletion set out in the privacy policy.
Whose data: diners, people who book or order, payers, staff and anyone else appearing in the messages examined for this purpose.
What data: message content examined in passing; and stored senders, subjects, short extracts, identifiers, timestamps, names, contact details, amounts, booking and order details, notes, the fields you configure, and the connection records needed to keep it running.

Your instructions to us are: this agreement, the settings and rules you configure in the app, and anything else we agree in writing through support. We process on those instructions only, unless EU or national law requires otherwise — in which case we'll tell you first, unless that law forbids it. If we think an instruction breaks data protection law, we'll say so and may hold off on that part until it's sorted out.

Sensitive data isn't asked for and isn't wanted. If it ends up in a booking note anyway, establishing the legal condition for it and keeping it to a minimum is yours.

Confidentiality and security

Anyone here with access is under a duty of confidence. We keep security measures appropriate to the risk, as Article 32 requires — encrypted connections, encrypted storage of the mailbox permission, restricted access, separation between accounts, monitoring for misuse, keeping things patched, and reviewing all of it. We'll share the detail you reasonably need on request, without publishing the parts that would help an attacker.

We do not keep separate backups of the application database. That is a deliberate trade for holding less of your data, and it means we cannot restore something that has expired or been deleted.

Other companies we use

You give general written authorisation for the providers listed in the privacy policy, for the purposes described there. Before we add or swap one, we'll tell you who they are, where they are, what they'd do and what safeguards apply, at least [30] days ahead, so you have a real chance to object on reasonable data protection grounds.

If you object, we'll look for a workable answer. If there isn't one, you can end the affected service before the change and get the unused part back. Anyone we use is bound to equivalent obligations, and we stay responsible to you for what they do. Sending data outside the EEA needs a lawful mechanism under Chapter V of the GDPR; this agreement alone isn't one.

Helping you, and telling you when something goes wrong

We'll help you answer people exercising their rights, using appropriate measures and taking account of how the processing works. If a request reaches us instead of you, we'll pass it on promptly and won't answer on your behalf unless you've asked us to or the law makes us. We'll help with security, with breach notifications, and with impact assessments or prior consultation, as far as the information available to us allows.

If there's a personal data breach affecting your data, we'll tell you without undue delay after we become aware of it — what happened, what data and roughly how many people, what we think it means, what we're doing, and who to talk to, with more as we learn it. We won't sit on it until the investigation is finished. Notifying the authority and the people affected is yours to do as controller, and we'll help.

Showing our working

We'll give you the information you need to show you're complying, and allow and contribute to audits or inspections by you or an auditor you appoint. We may ask for sensible arrangements to protect other customers' confidentiality and keep the service running, but not ones that stop a real audit or a regulator getting what they need.

Getting it back, and getting rid of it

The short retention periods in the privacy policy are your standing instruction to us to delete as we go. When the processing ends you choose: have what's left returned, or have it deleted. Tell us before you close the account if you want it returned, and we'll send it securely in a common format without undue delay, then delete our copies unless the law requires us to keep something. Choosing "Delete my data" in the app is an instruction to delete.

Our own billing and compliance records follow the separate periods in the privacy policy. We don't keep your guests' messages around as a just-in-case archive, and a complaint or a restriction on your account isn't a reason for us to hold on to them indefinitely. These obligations outlast your subscription.