Privacy Policy

The controller currently responsible for processing personal data in connection with VenueHive is:

Tina Heidi Frenzel
VenueHive
[FULL STREET ADDRESS AND HOUSE NUMBER]
[POSTAL CODE] Zurich
Switzerland

Email: [CONTACT EMAIL]

VenueHive is currently in development and is not yet operated through a separate legal entity.

DISRPTV and Simon Deubele support VenueHive in concept work, product build and technical implementation. Where they receive access to systems, infrastructure or development processes, this is limited to the relevant technical or organisational role.

This Privacy Policy explains how VenueHive processes personal data in connection with its website, product, accounts, profiles, communications, integrations, calendar and social connections, public web enrichment and AI-supported functions.

It applies in particular to:

• visits to the website,
• contact requests,
• registrations and user accounts,
• creator and venue profiles,
• profile analysis and matching,
• messaging and protected collaboration areas,
• connected social and calendar services,
• uploads and imports, including ICS files,
• public web enrichment,
• AI-supported structuring, search, classification and recommendation functions.

VenueHive does not treat every category of data in the same way. The following distinction is central to how the product is designed.

This includes, for example, profile details, selected references, certain portfolio items, public-facing signals and other information intended for use in presentation, matching or collaboration within VenueHive.

This includes in particular:

• private messages,
• raw calendar data,
• content imported from ICS files,
• access tokens and connection credentials,
• other clearly private or sensitive user data areas.

These areas are treated more restrictively than generally visible profile or platform data.

VenueHive may derive structured outputs from existing inputs and signals, for example:

• categories,
• markets,
• profile and fit signals,
• availability windows,
• matching indicators,
• structured summaries,
• classifications, scores or prioritisation outputs.

Derived outputs are not the same as raw data and are not the same as user-declared information.

Depending on the feature and context of use, VenueHive may process in particular the following categories of personal data.

This includes, in particular, IP address, access timestamps, device and browser information, session and security data, error records, logs and similar technical metadata.

This includes, in particular, name, email address, login-related information, account status, role information, OAuth-related connection data and other information required for account management, authentication and access control.

This includes, in particular, name, screen name, location, languages, creator type, categories, specialisations, collaboration types, preferences, compensation preferences, roles and similar profile information.

Where users actively use these functions, VenueHive may process in particular:

• connected social accounts,
• handles and profile URLs,
• publicly visible profile information,
• linked or submitted content and media references,
• performance, activity and format signals,
• audience and reach indicators,
• text, visual or multimodal analysis outputs,
• structured or derived profile signals based on those sources.

Important: VenueHive treats publicly visible or intentionally connected social signals differently from private connection credentials. Access tokens, sensitive authentication data and similar secret connection information do not belong to the visible profile layer.

This includes, in particular:

• website,
• link-in-bio,
• LinkedIn,
• media kit,
• portfolio examples,
• uploaded assets,
• references,
• press or appearance links,
• known partner, venue or brand references,
• aliases or previous handles,
• public proof signals.

This includes, in particular, information about offered deliverables, collaboration modes, management involvement, platform-readiness confirmations, confirmed collaboration settings, message content and related status data.

Where users actively use such functions, VenueHive may process in particular:

• manual availability entries,
• connected calendar accounts,
• calendar sync metadata,
• uploaded ICS files,
• time and location data extracted from those files or connections,
• normalised presence windows,
• derived availability and market windows.

VenueHive is designed to distinguish between raw calendar data and derived availability or presence windows. Other users should not automatically see raw calendar or ICS content.

VenueHive may process publicly available information where relevant for identity resolution, professional footprint, public proof, hospitality relevance, market readability or matching. This may include publicly accessible websites, profiles, reference pages, publications and other openly available sources.

Where users contact support, report content, challenge decisions or notify rights infringements, VenueHive may also process the related submissions, statements, attachments and case-handling records.

VenueHive receives personal data in particular:

• directly from users,
• from user accounts and profile submissions,
• from intentionally connected third-party services or imported files,
• from publicly available sources,
• from interactions within the platform,
• from technical, security and platform operations.

Where data is not collected directly from the data subject, this is done only within the framework of applicable law and for the purposes described in this Privacy Policy.

VenueHive processes personal data in particular:

• to provide and operate the website and platform,
• to manage user accounts, authentication and permissions,
• to create and make creator and venue profiles usable,
• to structure profiles, references, content and public signals,
• to support search, matching, selection and collaboration workflows,
• to enable communications between users,
• to provide social, calendar and import features,
• to derive relevant presence windows and availability signals from calendar and import data,
• to better assess professional footprint, public proof and hospitality relevance,
• to provide AI-supported structuring, analysis and recommendation functions,
• to ensure security, prevent misuse, diagnose errors and maintain platform stability,
• to provide support, moderation and complaint handling,
• to comply with legal obligations and protect legitimate interests,
• to improve and develop VenueHive.

Not every piece of information processed by VenueHive is automatically visible to other users.

VenueHive generally distinguishes between:

for example selected profile details, certain portfolio elements, released references or visible matching-relevant information;

for example information made visible to the relevant counterparty as part of an application, briefing or concrete collaboration;

for example private messages, raw calendar data, raw ICS content, credentials, tokens and comparable sensitive data.

Other users should in particular not automatically see:

• raw calendar data,
• ICS contents,
• private messages,
• secret connection data,
• unreleased sensitive metadata.

VenueHive applies heightened security expectations to especially sensitive private data areas.

This includes in particular:

• private messages,
• raw calendar data,
• ICS-import contents,
• authentication and connection tokens,
• comparable sensitive private content and connection data.

For such areas, VenueHive's intended security model includes in particular:

• encrypted transmission,
• encrypted storage where appropriate and technically implemented,
• restrictive role and access logic,
• separation between visible profile information and protected raw data,
• no sale and no unrestricted disclosure for advertising or data brokerage purposes,
• no use of these protected private areas to build general advertising profiles.

Important claim guard:
A public statement such as "not even VenueHive can read these contents in plain text" should only be published if the production architecture truly enforces that result technically. Until that is finally verified, VenueHive describes such data areas as especially protected, encrypted and strictly access-restricted, rather than technically absolute operator-blind.

Depending on the activated function, VenueHive may support connections or imports from services and formats such as:

• Instagram,
• TikTok,
• YouTube,
• Apple Calendar,
• Google Calendar,
• Microsoft Calendar,
• ICS files,
• comparable connected or imported data sources.

Which data is processed in any individual case depends on:

• the connected platform,
• the permissions granted,
• the function that is technically active,
• and the way the user actually uses that function.

VenueHive processes such data only within the scope of the user-requested function and not as a general-purpose data source.

Under the currently known setup, VenueHive uses Supabase in particular for:

• database functions,
• user accounts,
• authentication,
• OAuth and login flows,
• session and access management,
• technically protected data processing.

Where users use logins, connected accounts or OAuth-based functions, the account, session and technical metadata necessary for those functions may be processed through that infrastructure.

Before go-live, VenueHive should document in particular:

• the final modules in use,
• the regions used,
• any subprocessors,
• the concrete security architecture,
• the technical implementation of especially protected private data areas.

VenueHive may assess publicly available web information to improve profile context, relevance signals, search quality, public proof and market readability.

Under the currently known setup, this may include the use of Brave Search / Brave Search API.

Such public web enrichment is intended in particular to:

• identify public-facing references,
• assess professional footprint and public proof,
• improve hospitality relevance and market readability,
• support the quality of search and matching processes.

Public web enrichment relates only to publicly available information. It does not mean that VenueHive freely reads or discloses private content from connected accounts.

VenueHive may use AI-supported functions to structure data, improve profile readability, enrich public signals, identify categories or markets, generate relevance and matching signals, or create summaries, recommendations and prioritised outputs.

These functions may generate, among other things:

• classifications,
• scores,
• rankings,
• relevance signals,
• market and category assignments,
• summaries,
• prioritisation suggestions,
• matching recommendations.

VenueHive treats these outputs as supportive structuring and decision-support tools, not as absolute truth.

Where VenueHive uses AI functions, the following principles apply in particular:

• a clear processing purpose,
• a clear distinction between raw data and derived outputs,
• a restrained approach to protected private data areas,
• no sale or free exploitation of protected private data areas for advertising or data brokerage,
• no independent third-party use of protected private areas outside the VenueHive purpose,
• human review where AI outputs may have material consequences.

If VenueHive later introduces automated individual decisions with legal or similarly significant effects, affected persons will be informed and may — where the law provides for it — request human review.

Further information is available on the page AI & Matching Transparency.

VenueHive discloses personal data only where functionally, technically or legally necessary.

This may include, in particular:

• technical infrastructure and hosting providers,
• database, authentication and security providers,
• search and enrichment providers,
• calendar or social platforms within the scope of user-initiated connections,
• support, development or moderation partners acting in their respective roles,
• AI service providers, where such functions are used in production and the provider is necessary for that function,
• public authorities or other bodies where disclosure is legally required.

VenueHive does not sell personal data.

VenueHive does not disclose protected private data areas for general advertising, data brokerage or similar independent commercial reuse by third parties.

Depending on the final infrastructure and vendor setup, personal data may also be processed outside Switzerland or disclosed abroad.

Before public go-live, VenueHive should document in particular:

• which countries or regions are affected,
• which service providers are involved there,
• in which role those providers act,
• and on which legal basis any international transfer takes place.

Where international transfers occur, they are made only in accordance with applicable legal requirements.

VenueHive does not retain personal data longer than necessary for the relevant purpose.

From an operational perspective, the retention model should distinguish in particular between:

• security and error logs,
• contact and support data,
• account data,
• visible profile data,
• portfolio and proof data,
• messages,
• calendar and import data,
• derived presence windows,
• publicly enriched signals,
• backups and recovery states.

Before go-live, a concrete retention plan with fixed periods or clear retention criteria should be defined. This should in particular provide that:

• raw calendar and import data are retained only as long as necessary,
• presence windows are retained only while relevant for the user-requested availability function,
• messages and protected content are retained only within the scope of the user-requested function and technical necessity,
• deleted content is removed from active systems without undue delay and only remains in backups to the extent technically necessary.

VenueHive is intended to take privacy into account at the planning and system-design stage.

This includes in particular:

• data minimisation,
• separated data layers,
• restrictive default settings,
• role-based access,
• protection against unnecessary visibility,
• limiting data access to what is required for the relevant function.

VenueHive takes appropriate technical and organisational measures to protect personal data.

This includes in particular:

• transport encryption,
• encrypted storage where appropriate and technically implemented,
• role and permission concepts,
• access restrictions,
• logging of security-relevant events,
• protection of authentication and connection tokens,
• privacy-friendly system configuration,
• restrictive handling of especially protected data areas.

Subject to applicable law, data subjects have in particular the right:

• to request information about whether and which personal data is being processed,
• to have inaccurate data corrected,
• to request deletion or destruction of data, unless overriding obligations or interests prevent this,
• to object to or request restriction of certain processing, where the law provides for it,
• to receive or request transfer of provided data in a common electronic format where the legal requirements are met,
• to withdraw or disconnect connected accounts or consents within the scope of the available product functions,
• to request human review in the case of relevant automated individual decisions, where such a right exists.

Privacy requests may be sent to:

Tina Heidi Frenzel
VenueHive
[FULL STREET ADDRESS AND HOUSE NUMBER]
[POSTAL CODE] Zurich
Switzerland

Email: [CONTACT EMAIL]

This Privacy Policy may be updated where this is necessary due to technical, organisational, legal or regulatory developments. The published version in force at the relevant time shall apply.