How ACC handles information.

1. Scope

This notice covers the public ACC website and the ACC messaging software used by participating restaurants. A restaurant controls its customer relationship and decides why it uses customer information. ACC supplies the software used to process those conversations and restaurant operations.

2. Information involved

Public website

The public site records a small allowlisted set of events such as a page view, product-example interaction, contact click, WhatsApp click, or successful tester access. The event contains the page path, a fixed event label, a fixed target label, and a random session identifier. It does not include form contents, message contents, names, email addresses, phone numbers, advertising identifiers, or a persistent cross-session identifier.

Restaurant customer conversations

Depending on what a customer sends and what the restaurant needs to fulfil the request, ACC may process messaging identifiers, profile information, messages, voice media, order or reservation details, delivery details, timestamps, and service records.

3. Voice messages

When a customer sends a voice message, a transcript is supplied to the AI so it can process the request. Restaurant staff can play the customer’s original voice message normally in Customer Support. The transcript is not displayed to staff beside that voice message in Customer Support.

4. Why information is used

• To answer restaurant customer questions and process orders or reservations.
• To confirm pickup or delivery details and provide the result to the restaurant team.
• To let restaurant staff manage customer support and restaurant operations.
• To protect, troubleshoot, and improve the service.
• To understand public-site interest without third-party advertising trackers.

5. Public-site measurement

ACC does not set an analytics cookie. The browser keeps the random analytics identifier in session storage, so a new browser session receives a new identifier. Events are sent only to an ACC first-party endpoint and rejected unless their event, page, target, origin, and session format match the allowlist.

The measurement dataset is designed to retain event rows for up to three months. Infrastructure providers may process normal request metadata, including an IP address, to route and protect requests. ACC does not add the IP address or full user-agent string to its custom event payload.

6. Service providers and access

ACC relies on providers for messaging delivery, hosting, database infrastructure, transcription, and AI processing. Restaurant information is made available to the restaurant staff who need the ACC dashboard. Technical providers process information as required to operate their services. This draft does not claim a particular certification or contractual status that has not been verified.

7. Retention and requests

Different records may need different retention periods for active restaurant operations, support, security, backups, disputes, and applicable legal obligations. A final retention schedule still requires legal and operational review.

For access, correction, deletion, or another privacy enquiry, contact the restaurant involved when the request concerns its customer records. You may also contact ACC at bakerjammoil@gmail.com. ACC will assess and respond to requests under applicable law and the restaurant relationship.

8. Changes

ACC may update this notice when the service or its data handling changes. The date at the top identifies the current draft.