Effective date: [EFFECTIVE DATE]
1. What this page covers
This page explains how VenueHive uses or may later use cookies and similar technologies.
This includes in particular:
- cookies,
- local storage,
- session storage,
- token storage,
- similar browser or app technologies,
- technically embedded security or preference mechanisms.
2. VenueHive's general approach
VenueHive follows a restrained approach:
- strictly necessary technologies where they are required for operation, security, login or protection functions,
- non-essential technologies only where they are actually activated and the necessary transparency and preference tools are in place.
3. Current target state in dev and early live setup
As long as VenueHive does not provide a fully active consent and preference layer for non-essential technologies, only those technologies should be active by default that are necessary for operating the service.
This includes in particular:
- login and session functionality,
- security and anti-abuse functions,
- technical stability,
- storage of required user choices,
- language or basic display preferences where technically necessary.
4. Categories of technologies
a) Strictly necessary technologies
These are required to provide VenueHive securely and functionally, for example for:
- authentication,
- sessions,
- access control,
- security functions,
- load balancing,
- error protection,
- storage of essential settings.
These technologies generally cannot be switched off while the relevant service is being used.
b) Preference technologies
These help remember user-selected settings or convenience preferences.
c) Analytics technologies
These are used to understand usage, interactions or product behaviour in order to improve VenueHive.
Such technologies should only be used where the necessary legal and technical requirements are met.
d) Marketing or profiling technologies
These would in particular be used to analyse user behaviour for advertising or profiling purposes or to integrate third-party marketing services.
VenueHive should not activate such technologies silently. If they are introduced later, this will happen only with an appropriate transparency and control model.
5. Examples of technically necessary product technologies
Depending on the final setup, technically necessary technologies may in particular be connected to:
- Supabase Auth and session handling,
- access protection,
- security and anti-abuse mechanisms,
- form and login protection,
- storage of essential preferences,
- error and stability functions.
6. Third-party involvement
Where third parties are integrated and use cookies or similar technologies, this will be described on this page or in the Privacy Policy once the relevant use is active in production.
Before public go-live, a final technology and vendor matrix should be documented for this purpose.
7. Settings and control
As soon as VenueHive uses non-essential technologies, a user-friendly mechanism will be provided through which the relevant preferences can be reviewed and adjusted.
Until then, users may also use their browser or device settings, where relevant, to block or delete certain technologies. Doing so may limit some functions.
8. Changes to this page
This page will be updated as soon as VenueHive activates new technologies, new technology categories or new third-party services in production.