Cookie 与追踪声明

Version: 1.0
Effective Date: [Launch Date]
Last Updated: 18 September 2026
Applies to: Eleat Technologies Inc. (Alberta, Canada) and Eleat Technologies Limited (Hong Kong)

1. Current position

Eleat does not currently implement a cookie-consent mechanism in the Eleater prototype or web code reviewed for the 18 September 2026 data inventory. Eleat therefore does not claim that it has a cookie banner, that optional tracking is consent-gated, or that an Eleater’s tracking preferences are currently recorded.

2. Analytics

Eleat has an analytics-event endpoint that can receive events from both signed-in and signed-out traffic. The event can include event name, restaurant, deal, menu item, campaign, sports event, carousel information, source screen, search query, platform and arbitrary metadata supplied by the client screen. The endpoint is rate-limited, but there is no tracking-consent gate in the current backend.

3. What is not implemented

No cookie-consent banner is implemented in the reviewed Eleater prototype or web code.

No backend process reads or writes the behavioral_tracking_consent field.

No screen currently records data-processing or marketing consent fields.

No claim is made that analytics is consent-based in this version.

4. Authentication and essential storage

Eleat uses authentication tokens for signed-in access. The current configuration gives a JWT a 30-day expiry and uses a token-version value to invalidate older tokens after certain events. This statement does not claim a particular browser-cookie implementation because the data inventory does not establish one.

5. Third-party pages

When an Eleater leaves Eleat for a reservation provider or a Restaurateur enters a payment processor’s hosted checkout, that third party can use its own cookies, SDKs or tracking technologies. Those technologies are controlled by that provider and are covered by the provider’s own privacy and cookie notices.

6. Before launch

Before launch, Eleat should decide which analytics are strictly necessary, whether any optional tracking requires prior consent in a target market, how those preferences will be stored and how an Eleater can change them. If Eleat later introduces cookies, advertising identifiers, analytics SDKs, pixels or similar technologies, this statement must be updated to name them and explain their purpose.

7. Contact

Questions about tracking should be directed to the privacy contact published in the Eleat Privacy Policy.

Revision history

Version

日期

更改

店主

1.0

18 September 2026

Initial statement based on current implementation.

Eleat Technologies