Privacy policy

Effective 8 September 2026, updated 26 September 2026. Radeux US LLC, a Delaware limited liability company.

This policy explains what information Radeux collects, why we collect it, how we use and protect it, and what rights you have. It covers this website, the Radeux Profile Manager application, which is the software we use to manage Google Business Profiles on behalf of businesses, and the menu service we are building for restaurants, including its connection to Uber Eats.

Who we are

Radeux US LLC, 131 Continental Drive, Suite 305, Newark, Delaware 19713, United States. We are the controller (the responsible party, under South Africa's Protection of Personal Information Act) of the personal information described below, except where we handle business profile or menu information on the documented instructions of a business or its agency. In that case the business is responsible for that information, and we act as its processor (its operator, under that Act).

You can reach us at ops@radeux.co about anything in this policy, including requests to access or delete your information.

Information we collect

Information you give us

If you contact us or request an audit, we receive your name, email address, company name and whatever else you choose to put in your message. If you become a customer we collect billing contact details. Card details are handled by Stripe and never reach our systems.

Consent and authorisation records

Before we act on any Google Business Profile we record who granted permission, for which business, which specific activities were permitted, the wording that was shown at the time, and when it happened. Google requires this record and so do we. It is kept for as long as we manage the profile and for six years afterwards, so that either party can establish what was agreed.

Information from Google

When a business or its agency grants us access to a Google Business Profile, we read and write information about that business through Google's Business Profile APIs. This includes the business name, address, telephone number, opening hours, categories, services, attributes, website, photographs, posts, questions and answers, reviews and review replies, and profile performance figures such as views, searches, calls and direction requests.

Where a Google account is used to authorise that access, we receive the account's basic profile information and an authorisation token. We do not read the account holder's email, files, contacts or calendar, and we have no ability to do so.

Menus, and Uber Eats

If a restaurant uses Radeux for its menu, we hold the menu it gives us or approves: sections, items, descriptions, prices, options, availability and photographs. We keep each version the restaurant approved, so that an earlier menu can be put back. To bring in its first menu, a restaurant can photograph or upload its printed menu; we use those images only to prepare a draft for the restaurant to check, and delete them once the first menu is published, or after thirty days. We also record which member of the restaurant's team published each version.

Where a restaurant connects its Uber Eats store, the owner signs in on Uber's own page and approves the connection there. We receive an authorisation token and the list of stores that owner manages, and through Uber's APIs we read and update the chosen store's details and menu. We do not receive orders, customer names, customer phone numbers or payment information, and we have no ability to. When an order is placed, Uber sends our system a short notice that it exists; we keep only a record that the notice arrived, and do nothing else with it. We never ask for, and never receive, the owner's Uber Eats password.

Information this website collects

This website sets no advertising cookies, runs no advertising trackers and does not build profiles of visitors. Typefaces are loaded from Google Fonts, which means Google receives the IP address of your device in order to serve them. Our hosting provider keeps standard server logs, including IP addresses, for security and reliability purposes.

How we use information

To perform the service: publishing posts and photographs, replying to reviews, answering questions, correcting listing information and monitoring profiles for changes.
For restaurants, to keep the approved menu current on Google, on the restaurant's website, on its QR code menu and, where connected, on Uber Eats, and to check that each one still matches the version the restaurant approved.
To produce reports for the business and its agency showing what work was done and what changed.
To communicate with agencies and business owners about onboarding, access, consent and service issues.
To take payment and keep accounting records.
To detect and prevent abuse, and to comply with law and with Google's policies for third parties managing Business Profiles.

Where the UK GDPR or the EU GDPR applies, our legal bases are performance of a contract, our legitimate interests in operating and securing the service, compliance with legal obligations, and consent where consent is what we relied on. Where South Africa's Protection of Personal Information Act applies, we rely on the matching grounds in its section 11.

Giving us contact details is voluntary, but we cannot answer an enquiry or provide the service without them. Connecting a Google Business Profile or an Uber Eats store is optional, and we cannot manage a place that is not connected.

Information received from Google APIs

Radeux's use and transfer to any other application of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

In particular:

We use Google user data only to provide and improve the Business Profile management service the customer asked for.
We do not transfer Google user data to third parties except as necessary to provide that service, for security purposes, or to comply with applicable law.
We do not use Google user data for advertising, and we do not sell it.
We do not allow humans to read Google user data unless we have the customer's explicit permission, it is necessary for security or to comply with law, or the data has been aggregated and made anonymous.
We do not use Google user data to develop, improve or train generalised artificial intelligence or machine learning models.

The permission we request, and why

Radeux Profile Manager requests the https://www.googleapis.com/auth/business.manage permission. This is the only permission that allows an application to read and update a Google Business Profile, which is the entire purpose of the service. We use it to publish posts and photographs, reply to reviews, answer questions, read and correct listing information, and read profile performance figures for reporting. We use it for nothing else.

You can review and withdraw an application's access to your Google account at any time at myaccount.google.com/permissions, and you can remove a manager from your Business Profile directly, from the People and access screen of that profile.

Who we share information with

We do not sell personal information and we do not share it for advertising. We use a small number of service providers to run the business, each of which processes information only on our instructions:

Google, for the Business Profile APIs, hosting, and our own company email.
Stripe, for payments and billing.
Providers of artificial intelligence services, used to draft posts and review replies, to read a restaurant's menu from the photos or PDF it uploads, and to suggest dish descriptions when the restaurant asks. We send them only what the task needs. These are used under agreements that prohibit the provider from using the content to train their models.
Meta Platforms, where a customer chooses to connect a Facebook Page or Instagram account as a source of media for their profile.

Where a restaurant connects its Uber Eats store, we send its menu and store details to Uber at the restaurant's direction. Uber's use of that information is governed by the restaurant's own agreement with Uber.

We may also disclose information where we are legally required to, or to establish or defend legal claims.

Where information is held

Information is processed in the United States and in the European Union, depending on the provider, and is also accessed from South Africa, where Radeux is run. Where personal information is transferred out of the United Kingdom or the European Economic Area, that transfer is made under an adequacy decision, the standard contractual clauses or another lawful transfer mechanism. Where personal information is transferred out of South Africa, we do so only as section 72 of the Protection of Personal Information Act allows, such as to a recipient bound by law or a binding agreement to protection substantially similar to that Act. Write to us for details of the safeguard used for a particular transfer.

How long we keep it

Consent and authorisation records: for the life of the engagement and six years afterwards.
Content we retrieve from Google's APIs, such as review text and performance figures: no more than thirty calendar days, as Google's policies require. Our own records of the work we performed, including the text we published and the replies we wrote, are not Google content and are kept for the life of the engagement and two years afterwards.
Menus, and each version a restaurant approved: while the service is active, so that an earlier version can be restored, and deleted within ninety days after it ends, unless the restaurant asks for an export or the law requires a record to be kept. Menu and store information read from Uber Eats: no more than thirty calendar days, apart from the confirmation that a publish matched what was approved, which is kept with that version.
Photos and documents uploaded to bring in a first menu: deleted once the first menu is published from them, or after thirty days.
The working logs our systems keep of each task they run: no more than thirty days.
Backups: information deleted from our systems can remain in backups until they are replaced, which happens within ninety days. It is never restored except to recover from a failure.
Authorisation tokens: deleted when access is withdrawn or the engagement ends.
Billing and accounting records: seven years, as required for tax purposes.
Enquiries that do not become customers: two years.

Security

Access to production systems requires multi factor authentication. Authorisation tokens are encrypted at rest and are never stored in a customer facing system. Access to customer data is limited to the people who need it to do the work. We will tell affected customers and the relevant authority about a personal data breach within the timescales the law requires.

Your rights

Depending on where you live, you may have the right to ask us for a copy of the personal information we hold about you, to correct it, to delete it, to restrict or object to how we use it, to receive it in a portable form, and to withdraw consent you previously gave. You will not be treated differently for exercising any of these rights.

Write to ops@radeux.co and we will respond within thirty days. If you are in the United Kingdom you may also complain to the Information Commissioner's Office. If you are in the European Economic Area you may complain to your local supervisory authority. If you are in South Africa you may complain to the Information Regulator at POPIAComplaints@inforegulator.org.za.

If your Business Profile is managed through an agency, that agency may also hold information about you, and their own privacy policy will cover it.

Children

This service is sold to businesses and is not directed at children. We do not knowingly collect information from anyone under sixteen.

Changes to this policy

If we change this policy we will update the date at the top and, where the change is significant, tell customers directly before it takes effect.

Contact

Radeux US LLC, 131 Continental Drive, Suite 305, Newark, Delaware 19713, United States. ops@radeux.co