Privacy Policy

3.1 When you use our website

• Waitlist form. Your name, work email address, company name, roughly how many branches you operate, and your phone number if you choose to give it.
• Rate-limiting record. When the waitlist form is submitted we store a one-way keyed digest derived from the sending IP address, and keep it for one hour, so that one sender cannot flood the form. We do not store the address itself. The digest is pseudonymised rather than anonymous: it cannot be turned back into an address, but the same address always produces the same digest.
• Technical records. Our hosting provider records the IP address, browser type and page requested for each visit, in order to serve the site and defend it against abuse.
• Performance measurement. We use Vercel Speed Insights, a service from our hosting provider that records anonymous page-timing data so we can see which pages load slowly. It sets no cookies, builds no profile of you, and is not used for advertising.
• We do not use advertising cookies or third-party tracking pixels on my-idara.com.

3.2 When you hold an Idara account

• Identity. Your name and email address, and an identifier from Google or Microsoft if you sign in with one of those. Access is by invitation only; we never create accounts from public sign-ups.
• Authentication. Session records, and tokens issued by your sign-in provider.
• Activity records. Idara keeps an audit log of actions taken in the system — who changed what, and when — because a shared operations system is unusable without one.
• Fault records. When something fails, we record what failed and where. Secrets and credentials are stripped from these records before they are stored.

3.3 Information a restaurant group enters into Idara

Our customers use Idara to run their operations, and in doing so store information about other people. Depending on which parts of Idara they use, this can include:

• Their employees — names, roles, positions, assessments, disciplinary records, identity document numbers, and health cards. Health cards contain medical information, which is sensitive.
• Their guests — names, phone numbers, and the substance of complaints, together with any message sent in reply.
• People on a waiting list — a name, a phone number and a party size, given in order to hold a table.

We hold this information on the customer's behalf and act on their instructions. We do not use it for our own purposes, and we do not sell it.

3.4 Information from services a customer connects

An administrator at a restaurant group may connect Idara to services that group already uses. Nothing is connected without that deliberate act, and each connection can be revoked at any time.

5.1 What we ask for and why

Idara requests a single Google API permission:

We use it for exactly three things:

1. Matching branches to locations. We read the business locations on the connected profile so an administrator can say which Idara branch corresponds to which Google location.
2. Bringing reviews into one queue. We read reviews for the connected locations so a customer-service team can see and answer them alongside complaints from other sources, rather than logging into several dashboards.
3. Replying to reviews. When a member of the team writes or approves a reply, we post it to Google as the business. Google stores one reply per review; posting again replaces the previous one.

Signing in to Idara with a Google account is separate from the above. That gives us your name, email address and Google account identifier, and nothing else.

5.2 Limited Use

In plain terms, and without exception:

• We use Google data only to provide and improve the features described in 5.1, which are the features the user granting access asked for.
• We do not transfer Google data to anyone except as set out in section 5.3, and never to a data broker, an advertising network or an information reseller.
• We do not use Google data for advertising of any kind, including retargeting or personalised advertising.
• We do not sell Google data.
• We do not use Google data to develop, improve or train generalised artificial-intelligence models. Section 5.3 explains the narrow, feature-specific model use that does occur, and how it is contractually restricted.
• No human reads Google data except: with the explicit consent of the customer whose profile it came from; where it is necessary for security purposes such as investigating abuse; to comply with applicable law; or where the data has been aggregated and made anonymous.

5.3 Automated processing of review content

Two optional features send review text to an artificial-intelligence provider — Anthropic or OpenAI, whichever the customer selects. A customer who leaves these features switched off has no review content sent anywhere.

• Classification. The review text is sent so it can be labelled by subject — food, service, speed and so on — for reporting.
• Draft replies. The review text is sent so a reply can be drafted. Whether that reply is posted automatically or held for a person to approve is a setting the customer controls.

We send the review text and its star rating. We do not send account credentials or access tokens. These providers act on our instructions, are contractually prohibited from using the content to train their models, and retain it only as long as needed to return a result.

5.4 Keeping and deleting Google data

• Reviews we have retrieved are stored in our database so they can be displayed, searched and reported on. A nightly reconciliation compares what we hold against Google; a review deleted at Google is marked as removed on our side.
• An administrator can disconnect the Google connection at any time from System → Integrations → Google. Doing so stops all further access immediately.
• Access can also be revoked directly at myaccount.google.com/permissions, which we honour immediately because our tokens stop working.
• Disconnecting destroys the stored credential and the cached list of locations. Reviews already retrieved — their text, the reviewer's display name, any attached media and our replies — stay until you ask us to erase them. Write to systems@mao-sa.org and we erase them within 30 days, other than anything we must keep to meet a legal obligation.
• Access tokens are encrypted before storage. Where no encryption key is configured, the system refuses to store the credential rather than storing it unprotected.

6.1 What we ask for and why

Access is granted by an administrator at a restaurant group, through Facebook Login for Business, for that group's own Pages and Instagram accounts. The permission set is fixed by our login configuration rather than chosen per sign-in, so an administrator sees the same list every time. It is never requested from members of the public and never from people who comment on a post.

We use them for exactly four things:

1. Listing what was granted. We read which Pages and Instagram accounts the administrator granted, so they can point each one at the right brand inside Idara.
2. Publishing what the team writes. When a member of the team publishes a post through Idara, we send it to the Page or Instagram account they chose. Nothing is ever published without a person asking for it.
3. Reading and answering engagement. We read comments and messages on the connected accounts so a customer-service team can see them beside complaints from other sources, and post the replies that team writes.
4. Reporting. We read the insights Meta publishes for the connected accounts so a manager can see how a brand is performing without opening a second dashboard.

Advertising accounts are a separate grant, made separately, and used only to read and manage the campaigns of the group that granted it.

6.2 What we never do with it

In plain terms, and without exception:

• We use Meta data only to provide the features described in 6.1, which are the features the person granting access asked for.
• We do not sell Meta data, and we never transfer it to a data broker, an advertising network or an information reseller.
• We do not use Meta data for advertising of any kind, including retargeting or building audiences from it.
• We do not use Meta data to develop, improve or train generalised artificial-intelligence models.
• No human reads Meta data except with the explicit consent of the customer whose account it came from, where it is necessary to investigate abuse or a security problem, to comply with applicable law, or where it has been aggregated and made anonymous.

6.3 Keeping and deleting Meta data

• Posts, comments and messages we have retrieved are stored in our database so they can be displayed, searched and reported on.
• An administrator can disconnect the connection at any time from System → Integrations → Social media. Doing so stops all further access immediately and destroys the stored credential.
• Access can also be revoked directly at facebook.com/settings → Business integrations, which we honour immediately because our tokens stop working.
• Disconnecting stops access; it does not by itself erase what was already retrieved. Our data deletion page is the route for that, and it is the address we give Meta as our deletion instructions.
• Access tokens are encrypted before storage. Where no encryption key is configured, the system refuses to store the credential rather than storing it unprotected.

7.1 What we ask for and why

Access is granted by an administrator at a restaurant group, for that group's own TikTok account. It is never requested from members of the public and never from people who comment on a video.

We use them for exactly three things:

1. Naming the account that was granted. We read the account's display name, handle and avatar so an administrator can confirm which account they connected and point it at the right brand.
2. Reporting. We read the account's follower and video counts so a manager can see how a brand is performing beside its other channels.
3. Listing the account's own videos. We read the list of videos the connected account has published, so its performance can be reported on inside Idara.

TikTok for Business — the advertising side — is a separate application with a separate sign-in, granted separately, and used only to read and manage the campaigns of the group that granted it.

7.2 What we never do with it

In plain terms, and without exception:

• We use TikTok data only to provide the features described in 7.1, which are the features the person granting access asked for.
• We do not sell TikTok data, and we never transfer it to a data broker, an advertising network or an information reseller.
• We do not use TikTok data for advertising of any kind, including retargeting or building audiences from it.
• We do not use TikTok data to develop, improve or train generalised artificial-intelligence models.
• No human reads TikTok data except with the explicit consent of the customer whose account it came from, where it is necessary to investigate abuse or a security problem, to comply with applicable law, or where it has been aggregated and made anonymous.

7.3 Keeping and deleting TikTok data

• Profile figures and the video list we have retrieved are stored in our database so they can be displayed and reported on.
• An administrator can disconnect the connection at any time from System → Integrations → Social media. Doing so stops all further access immediately and destroys the stored credential.
• Access can also be revoked directly in the TikTok app, under Settings and privacy → Security and permissions → Manage app permissions, which we honour immediately because our tokens stop working.
• Disconnecting stops access; it does not by itself erase what was already retrieved. Our data deletion page is the route for that, and it is the address we give TikTok as our deletion instructions.
• Access tokens are encrypted before storage. Where no encryption key is configured, the system refuses to store the credential rather than storing it unprotected.