BUMP FOR PROMOTERS · UPDATED 14 SEPTEMBER 2026

Your privacy.

What this platform stores

We use your Bump account email and identity to sign you in. Promoter organisations, memberships, event drafts, approved public listings, billing references and performance data are stored in a separate promoter area of the Bump database. Public listings include the contact information you choose to publish.

Public and private information

Approved event pages and organiser names are public. Drafts, workspace members, billing details and moderation records are restricted to authorised users and Bump operators. Your existing private Bump app events are not published by this platform.

Optional analytics

Public event pages ask before recording optional analytics. If you agree, we store a browser session identifier and record page views, link clicks, calendar downloads and share actions. Identifiers are hashed on the server. Raw action receipts are retained for up to 30 days; daily aggregates for up to 13 months. Aggregate lifetime event totals remain available to the workspace. You can change analytics preferences on an event page.

Essential processing and payments

Authentication cookies are necessary to keep you signed in. Hashed network identifiers help limit abuse. Stripe processes payment information when paid checkout is enabled; Bump stores customer and subscription references, not card numbers. Supabase provides database, account and media services.

Your choices

Workspace owners can export workspace data in Settings. You can correct event and organisation information through the dashboard. Contact Bump through the main website for access, correction, deletion or other privacy requests. Shared account deletion may affect the Bump app and is handled separately from this workspace.

Launch information

This platform is in prelaunch. Before commercial launch, Bump will publish its legal entity, privacy contact, retention details for account records and applicable processor and international transfer information here.