← Back to RaveBuddy

Privacy Policy Public MVP Preview

Last updated: May 31, 2026 · RaveBuddy MVP demo/public preview · Powered by JK Automations

Short version: anyone can browse the public fixture feed. If you create or use an account, RaveBuddy stores only the minimum account data needed for saves, squad-plan checkboxes, and demand-signal toggles. Event listings, ticket prices, social proof, guestlist/VIP items, and concierge answers remain fixture/demo content and are not live bookings or real event guarantees.

1. Information We Collect

RaveBuddy collects limited information for this MVP preview:

RaveBuddy does not currently collect phone numbers, real names, precise location, payment data, ticket purchases, hotel bookings, rideshare bookings, health data, or private chat messages.

2. How We Use Information

We use account information and account-owned app state to provide real login, persist your saves across sessions/devices, unlock account-only features, and keep demand signals tied to a profile instead of anonymous public controls.

Fixture event data is used only to demonstrate the product loop. The concierge and recommendation outputs are deterministic demo guidance, not professional advice or live availability.

3. Sharing and Third Parties

RaveBuddy uses Supabase for authentication and account-owned data storage. We do not sell personal information. We do not currently use advertising pixels, social media widgets, payment processors, ticketing providers, hotel providers, rideshare providers, or third-party product analytics in this preview.

4. Data Retention and Deletion

Account data remains until the account or stored state is deleted. The in-app reset control can clear saved events, squad plans, and demand-signal state for the current signed-in account. For account deletion, correction, or export requests, contact JK Automations through the normal owner/support channel and include the account email address.

5. Cookies, Sessions, and Local Storage

Supabase Auth stores browser session information so login can persist. RaveBuddy may also use localStorage for local UI preferences and instant state updates. Clearing browser data or logging out removes local session/UI state from that browser, but server-side account records may remain until deleted.

6. Security

Account-owned tables use Supabase row-level security so signed-in users can access their own saved event, squad, and demand-signal records. Private service-role credentials are not shipped in the browser bundle. No system can be guaranteed perfectly secure; this MVP should not be used for sensitive personal information.

7. Children and Age-Restricted Events

RaveBuddy is not intended for users under 18. Nightlife events may be 18+ or 21+ depending on the venue and jurisdiction. Users are responsible for following applicable age, ID, venue, transportation, and safety rules.

8. California and International Rights

If applicable law gives you rights to access, correct, delete, or restrict use of personal information, contact JK Automations through the owner/support channel. RaveBuddy is operated from the United States and this preview is not yet localized for every jurisdiction.

9. Changes to This Policy

We may update this policy as RaveBuddy moves from MVP preview to public beta or production. Material changes should be reflected on this page before broader launch.

10. Contact

Contact JK Automations through the normal owner/support channel for privacy, account deletion, correction, or export requests. Do not send passwords or other secrets in support messages.