Cookie Policy

Cookies are small files or identifiers stored on or read from a browser or device. They help websites remember sessions, preferences and activity.

Some technologies are placed by Rego and others by service providers such as payment, map, analytics, advertising, social-login or customer-support companies.

These support sign-in, account security, fraud prevention, booking flow, load balancing, language, cookie choices and other functions required for the Platform to work.

They generally cannot be disabled through the Rego consent tool, although blocking them in the browser may prevent important features from working.

These remember preferences such as language, region, recent searches, map settings and accessibility options.

Disabling them may make the Platform less personalized.

These help Rego understand visits, navigation, errors, loading speed and feature usage so the Platform can be improved.

Where required, Rego will request consent before placing non-essential analytics technologies.

If used, these measure campaigns, limit repeated advertisements, support audience selection and enable social-media features.

They may allow third parties to recognize a browser or device across services. Rego should activate them only after the consent required by applicable law.

The mobile application may use device identifiers, local storage, push-notification tokens and location permissions. These can be controlled through app and device settings.

Precise location should be collected only when the user enables a feature that needs it, such as nearby search, map navigation or roadside assistance.

Use the Rego cookie banner or privacy settings to accept, reject or adjust non-essential categories.

Browser and device settings can delete or block cookies, limit tracking and revoke location or advertising permissions. Some features may not work correctly after blocking essential storage.

Where available, a “Do Not Sell or Share” or equivalent control will be provided if required by the user's jurisdiction.

Before publication, Rego must maintain an accurate cookie table naming each cookie or technology, provider, purpose, category and expiry. The live table should be generated from the technologies actually deployed.

Suggested columns: Name; Provider; Purpose; Category; Duration; First-party or third-party.

Session cookies expire when the browser closes. Persistent cookies remain for the period stated in the live cookie inventory unless deleted earlier.

Rego should avoid retaining identifiers longer than necessary for the stated purpose.

This Policy may be updated when technologies or vendors change. The effective date will be revised.

Cookie and privacy questions: privacy@rego.services.