Privacy Policy

EventBosh is operated by Jake Rose, Melbourne, Victoria, Australia. This page describes data used by the app and website. For privacy, account deletion, data-rights or Terms correspondence, contact privacy@eventbosh.com.

You must be at least 16 years old to use EventBosh. This is the product minimum age. If you believe someone under 16 has supplied personal information, contact the privacy address.

Account and feature data

• Sign-in uses your email, authentication provider identity, account identifier and session credentials. Your display name and avatar can appear to people who can access the relevant profile, event or group. Website default avatars are first-party images with no identifying URL seed. Legacy DiceBear URLs are not loaded. Custom image hosts receive requests when their images are used. This does not establish deletion of data previously sent to a provider.
• Saved events, attendance, followed categories and worlds, city preferences, search alerts and plans support your requested features. Signed-in preferences can be stored on the server and synchronised across devices.
• Friends, groups and chats store relationships, memberships and messages. Content you send is available to the people with access to that conversation or shared resource. Blocks and reports support safety features.
• Created events, venue requirements, accessibility preferences, shortlists and enquiries can contain information you enter. Relevant information is shared with the people or recipients involved in that workflow. A venue match or enquiry is not a confirmed booking or proof of live availability.
• Photos or other media you upload, and their ownership information, are processed to display and manage that content. Reports may include text, event or user references and details needed for review.
• If you enable push notifications, device tokens and notification content are processed for delivery. Calendar actions add an event at your request; the website offers a calendar file without reading your existing calendar.

Location and maps

You can choose a city without granting location access. With location permission, the website caches coordinates for nearby results; entries older than 24 hours are removed when the cache is read. Map viewports and search requests can include precise coordinates. Mapbox receives map and reverse-geocoding requests, including map-centre coordinates. These can reflect your location when you centre the map on yourself. Precise location is not limited to on-device processing.

The native apps use their configured map and notification services, including Apple MapKit/APNs and Android Mapbox/Firebase Cloud Messaging. Browser or device settings let you change location and notification permissions.

Loading an interactive map also lets Mapbox store a browser identifier and service-event state for map usage and billing. These functional provider requests are separate from the optional EventBosh and Google analytics controls below. The website disables Mapbox's optional performance-metrics collection. Browser site-data controls can clear Mapbox storage.

Website storage and optional data

Authentication cookies keep you signed in and are sent to the authentication service when needed. Local storage remembers appearance, language, followed categories, recent searches, the feature-tour choice, location and feedback prompts. These feature preferences are separate from optional analytics. Local preferences without an expiry remain until cleared; sign-out removes the account-related caches described below. The service worker retains the offline page and static application assets, without caching private page navigation.

Optional website analytics is disabled for the initial release. If offered after a future processor and disclosure review, EventBosh can receive recommendation interactions and feedback with a browser identifier, account identifier when signed in, event/category, screen, time and supplied feedback. Google Analytics, when configured, receives page visits and app-link interactions and can set analytics cookies. These events are not described as anonymous. Advertising signals and advertising personalisation are disabled in this website integration.

Optional website diagnostics is also disabled for the initial release. If offered after a future processor and disclosure review, Sentry receives browser errors and performance information. Browser replay is disabled. Website Sentry is also disabled on the server and edge for this release. Hosting operational logs are separate from optional website telemetry.

Services and external destinations

The service uses configured authentication, storage, database and hosting services to operate its features. Supabase is integrated for authentication and owned media storage; the application database stores account and feature records. Sentry is integrated for diagnostics. An integration can be disabled by configuration; this page does not assert that every integrated service is active in every release.

Map providers, avatar or event-image hosts and external links receive requests when used. Ticket links leave EventBosh; the destination controls its purchase, payment, refund and privacy terms. EventBosh does not sell tickets or process ticket payments. Some ticket links may earn EventBosh a commission; any ticket price or additional fees are set by the ticket provider. Event availability and source coverage vary. A listed source is not an endorsement or partnership claim.

Deletion and retained records

Use Settings → Account → Delete account or read the public account-deletion instructions. You can also request help by email without reinstalling the app.

Account cleanup disables access and removes account-owned profile, saves, preferences, notification tokens, Terms acceptances, friendships, blocks, authored chat messages and applicable private planning records. Account-linked analytics and session rows are removed using the account identity and verified current legacy email alias. Anonymous or other people's records are not broadly erased; older changed-email associations may require further review.

Reports have identifying account links detached, but report text/details remain for moderation and can themselves contain identifying prose. Some shared event or venue content can remain with ownership links removed. Account-denial and deletion-progress records retain an account identifier for security and cleanup retries. We do not promise that report text, shared prose, logs, diagnostics or backups are immediately erased, or promise a numeric retention period without a confirmed policy.

Website sign-out, account switching and accepted deletion reset optional browser choices and remove the analytics identifier, local category cache, location, recent searches and feedback history. A local account identifier lets the website check cache ownership when you return; expired or different sessions clear the previous account's data before it is used. Anonymous choices do not transfer into a signed-in account. Display/language and tour preferences remain. Clear site data in your browser to remove these. Turning optional processing off stops new optional collection; use the privacy contact to request review of data already sent.

Privacy requests and questions

You can ask about access, correction, deletion or other privacy rights that apply to you by contacting privacy@eventbosh.com. We may need to verify account ownership. Do not send passwords or sign-in tokens. Ask us about service providers, processing locations, transfers or retention if you need further information about your data.

Terms of Service · Support · Privacy settings