Privacy Policy
Last updated: 23 October 2026
VenueWiki (“we”, “us”, “our”) is operated by Evolved Yeti Pty Ltd (ABN 27 671 354 789), 892/27 Attunga Road, Blaxland NSW 2774, Australia.
1. Information We Collect
We collect information you provide when you create an account, including your name, email address, and Google profile information through Google Sign-In. We also collect usage data such as pages visited, features used, and interaction patterns to improve our service.
2. How We Use Your Information
We use your information to provide and maintain the VenueWiki service, process membership subscriptions, send service-related communications, and improve user experience. We do not sell your personal information to third parties.
3. Data Storage & Security
Your data is stored securely using Google Firebase infrastructure. Payment information is processed and stored by Stripe — we do not store your credit card details on our servers.
4. Third-Party Services
We use the following third-party services: Google Firebase (authentication & database), Google Analytics (website usage analytics), Stripe (payment processing), Resend (email delivery), Google Maps Platform (venue data), and Meta (Meta Platforms, Inc. — Meta pixel and Conversions API, for ad measurement). Each service has its own privacy policy governing data handling.
5. Google Calendar (Calendar Sync)
If you connect the optional Calendar Sync feature, VenueWiki accesses your Google Calendar using Google’s official APIs and only with your explicit permission. Specifically:
- What we access. With your consent, we read the list of calendars in your Google account so you can choose which one to sync, and we read and write events on the single calendar you select. We do not access any calendar you have not selected.
- How we use it. We use this access only to operate Calendar Sync: writing your confirmed gigs and shifts from your connected scheduling tool (such as Rentman, Deputy or Humanity) into your chosen Google Calendar, and reading entries you mark in that calendar so we can push your unavailability back to that scheduling tool. We do not use your Google Calendar data for advertising, profiling, or any purpose unrelated to this feature.
- How we store it. We securely store the authorisation tokens that keep your calendar connected, the ID of the calendar you selected, and minimal technical records (such as event identifiers) used to keep the two sides in sync and avoid duplicates. We do not sell your Google data, and we do not share it with third parties other than passing the necessary scheduling information to the scheduling tool you have connected.
- Your control. You can disconnect Calendar Sync at any time from your VenueWiki account. Disconnecting revokes VenueWiki’s access to your Google Calendar and removes the stored authorisation tokens. You can also review or revoke access directly in your Google Account security settings.
VenueWiki’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6. Your Rights
You may request access to, correction of, or deletion of your personal data at any time by contacting us at legal@venuewiki.net. Under Australian Privacy Principles, you have the right to know what data we hold and how it is used.
7. Cookies and analytics
We use essential cookies for authentication and session management.
We also use Google Analytics and the Meta pixel. Both set cookies in your browser and are used for measurement and advertising — to understand how VenueWiki is used, and to see which of our ads lead people to sign up or buy a membership.
Through these tools, Google and Meta receive the pages you visit, browser and device information, your IP address, cookie identifiers, button clicks, and events such as creating an account and connecting a calendar sync source.
The Meta pixel may detect contact details entered into forms or shown on pages, such as email address, name, phone number, city and postcode. It hashes them in your browser (SHA-256) before they are sent to Meta, which uses them to match activity to Meta accounts. This can include details you enter about another person, such as when adding crew.
Meta may also collect information about the pages you view, such as page titles, text and structure, to describe the activity it measures. Because the pixel runs on pages viewed while signed in, this can include information shown on those pages.
When you make a payment, we share the plan, amount and currency with Meta for ad measurement, along with a SHA-256 hash of your email address (a scrambled version that can’t be read back), the IP address and browser details from checkout, and Meta’s cookie IDs.
Our own code sends Meta only hashed email addresses and the checkout details described above. Contact details picked up by the Meta pixel are hashed before they leave your browser. Payment card details are handled by Stripe and are never shared with Meta.
Google Analytics and the Meta pixel measure your use of the VenueWiki website only. Neither receives your Google Calendar data directly. Google Analytics does not receive your roster or shift information or venue documentation. The Meta pixel’s page information, described above, can include what is shown on a page you view while signed in, such as shifts or venue documentation.
VenueWiki advertises on Meta and uses this data to measure which ads lead to sign-ups and purchases. We do not sell your data.
Google Analytics is configured with Google Signals enabled. If you are signed in to a Google account and have personalised ads turned on with Google, Google may associate your visit with that account and give us aggregated information about our audience — for example age range, general location, and broad interests. We use this to understand who VenueWiki is reaching.
You can control this yourself at any time in Google’s own ad settings at myadcenter.google.com, and in Meta’s ad preferences at facebook.com/adpreferences. Those settings apply across every site that uses these tools, not just ours.
If you would rather not be measured, you can install Google’s official opt-out browser add-on at https://tools.google.com/dlpage/gaoptout, or block analytics and advertising cookies in your browser settings or with a content blocker. VenueWiki works normally either way.
Questions about cookies and analytics: legal@venuewiki.net
8. Changes to This Policy
We may update this policy from time to time. We will notify registered users of material changes via email.
9. Contact
For privacy inquiries, contact: legal@venuewiki.net