Legal documents
Data Protection Notice
Last updated: 14 November 2026
How we process personal information for the businesses that use Reinfluence. For business owners and managers, who decide why Customer and staff data is used.
1. Who is responsible for what
A business that uses Reinfluence decides why and how the personal information of its Customers and staff is used. That makes the business the controller. Olympus Group Holdings, Inc. ("we") processes that information for the business, on its instructions, to provide the Service. That makes us the processor. For the personal information of the people who hold Reinfluence accounts, and of visitors to our website, we are the controller. The Privacy Policy covers that. This notice is part of the Terms of Service. It applies for as long as we process personal information for a business.
2. What we process, and about whom
We do not ask for, and the business should not put into the Service, special categories of personal information such as health details. Allergen or ingredient information about products is not personal information about a person. If a Customer tells staff about their own allergy, the business should not record the person's name against it in Reinfluence unless it has a proper basis.
| People | Information | Why it is processed |
|---|---|---|
| Customers who order from their phone | The items ordered, the table, the time, and a random session identifier kept on their phone so they can see and pay for their own lines. A name or email if the Customer chooses to give one for a receipt. | To take, prepare, serve and bill the order |
| Customers who pay | Amount, method, tip and time. For a mobile money payment recorded at the till: the payer's name, identity number, the phone number it was sent from and the transaction ID. For a card payment: only the approval code shown on the card machine. Card numbers never enter Reinfluence. | To record and reconcile the payment, and to issue receipts and tax invoices |
| Customers who ask for a receipt or invoice | Name, email address, and for company accounts the business name, tax number and contact details. | To send the receipt or tax invoice and keep it on record |
| Staff | Name, role, email or staff ID, a hash of the password or till code, and what they did in the Service. | To give access, control permissions and keep an audit trail |
| People named as owners or managers | Name, role, share owned and email, as the account holder entered them at sign-up | To know who is behind the account and to prepare a payment partner's checks |
| Customers on company accounts | Business and contact details, their tab and invoices. | To run the account and issue invoices |
3. Our commitments as processor
- We process personal information only on the business's documented instructions, which are these Terms and what it does in the Service, unless the law requires otherwise. We will tell the business if we think an instruction breaks the law.
- People who can reach the information are bound by confidentiality and given access only as their job needs.
- We keep the information secure with the measures in section 4, and review them as the Service changes.
- We use sub-processors only as section 6 allows, and we make them keep to duties no weaker than ours.
- We help the business answer requests from people who want to access, correct, delete, restrict, port or object to the use of their information, so far as the Service allows.
- We tell the business without undue delay, and in any case within 72 hours, after we become aware of a personal-data breach affecting its information, with what we know, and we help it notify the authority and affected people.
- When the business's account ends, we return the information on request for 30 days and then delete or anonymise it, as the Terms of Service say. We keep only what the law requires us to keep, and we tell the business what that is if it asks.
- We give the business what it reasonably needs to show that we keep to this notice, and we allow an audit on reasonable notice no more than once a year, at the business's cost, subject to confidentiality and without exposing other customers' data.
4. Security measures
- Passwords and till codes are stored only as salted hashes, and sessions as hashes of random tokens.
- Data is encrypted in transit. Integration keys are encrypted at rest and never shown again.
- Every record belongs to one organisation, and every query is limited to the signed-in organisation.
- Role-based access with six staff roles. Voids and cancellations need a supervisor and a reason.
- An audit log records orders, voids, payments, team changes, till sign-ins and account changes, with who did them and when.
- Repeated wrong passwords and till codes are rate limited and locked.
- Invoice and receipt links are long random addresses that search engines are told not to index.
- Webhooks we receive from a payment partner are checked against a signed secret before they are believed, and a verified event only prompts us to ask the partner for the truth.
5. The business's duties
- Have a lawful basis, and give every notice and obtain every consent the law requires, before putting personal information into the Service. Show the Customer Notice, or your own, where Customers order or pay.
- Put in only what you need, and keep it accurate.
- Manage who has access to your account and remove people who leave.
- Do not use the Service to record identity numbers or other sensitive details unless the law or a payment partner needs them for the payment, and keep them no longer than needed.
- Respond to people's requests, and tell us if you need our help.
6. Sub-processors and transfers
We use the providers on the Sub-processors page to host the application and database, deliver email, and, if you connect it, to handle payments. The business gives us general permission to use them. We will tell account holders of a new sub-processor at least 30 days before it starts to handle their information, and a business may object on reasonable data protection grounds, in which case we will talk about the options, including ending the Service for that business. The application and database are in Ireland. Our staff and providers may access information from other countries, including the United States and Botswana, under safeguards the law recognises, such as contractual clauses.
7. Requests from people
If a person asks us directly to access, correct or delete information we hold for a business, we will not answer the substance. We will tell them to contact the business and, where we can, pass the request on. Send requests that need our help to privacy@olympuspay.co.
8. Records of what we do
We keep a record of the processing we do for businesses, and of the sub-processors and security measures above, and will give it to a business or an authority that is entitled to see it.
9. Contact and complaints
Questions about this notice: privacy@olympuspay.co. A business or a person may also complain to the data protection authority that applies to them.
Olympus Group Holdings, Inc.
SEC file number 10088587. 1111B S Governors Ave, STE 25834, Dover, DE 19904, USA.
Legal notices: legal@olympuspay.co. Privacy and data requests: privacy@olympuspay.co. Complaints: complaints@olympuspay.co. Security: security@olympuspay.co. Support: support@olympuspay.co.
