Privacy

What we store about guides

Public event data (venue, times, posted policies) and the URLs we sourced it from. No guest accounts are required for /e/<slug>. Guides are anonymous reads.

Concierge questions and personalization

A question is sent to Aventic and, when enabled, an AI provider so we can answer it from the published event facts. Aventic does not retain the raw question or conversation history in its learning dataset. Anonymous goals and preferences are used for the current response only. Seat, row, and section notes stay in local browser storage and are not sent by the public guide. If you turn on step-free priority, the guide sends an ephemeral yes/no preference with recommendation requests; it is not added to venue learning or retained as an individual accessibility profile.

Anonymous guide learning

The guide records coarse counters such as whether a recommendation was shown, a task was completed, content was helpful, or a shared guide was opened. Counters are combined into five-minute event buckets without account IDs, session IDs, raw questions, exact paths, or device fingerprints. Aventic requires at least ten relevant opportunities before a group can influence durable venue learning. Event buckets are retained for up to 120 days.

Official video and YouTube

Some guides show official videos using YouTube API Services. Aventic stores limited public metadata such as a video ID, title, channel, category, playback eligibility, and freshness dates. We refresh or delete this API data within 30 days and do not copy the audiovisual content. The initial Vibe Reel does not request a YouTube thumbnail, script, or player. When you tap play, the privacy-enhanced player loads and YouTube may receive standard request information and use cookies or similar technologies under the Google Privacy Policy. Aventic records only anonymous five-minute counts of starts, completions, and failures for media quality. A count below ten is deleted after 30 minutes; all media counts are deleted within 30 days. They do not affect arrival, safety, accessibility, or next-best-action ranking.

What we store about API clients

Account email, hashed API keys, monthly call counts, and decision/outcome rows used to learn per-venue posteriors. We don't store end-user identifiers from API calls.

Location data

Event discovery uses coarse city or regional location supplied by our hosting network from your connection. Aventic does not return or retain your raw IP address for event discovery, and you can replace the detected area with a city. Precise browser location is optional. Your browser computes distance from the venue on your device; exact coordinates are not sent to Aventic. When you enable live location context, the guide may send a coarse state such as “approaching” or “at venue,” with a short-lived observation time. Venue coordinates can come from Google Places and are retained only for the period allowed by provider terms.

Sharing and offline use

Guide and QR links contain an opaque event-session code. Aventic stores only a hash of that code, its event, how it was created, its parent session when shared, open times and count, and its expiry. A group share creates a distribution session, then each recipient receives a separate child session when they open it. Links and lineage never include seat notes, location, preferences, chat history, device details, or account identity. Session lineage expires no earlier than 24 hours and normally seven days after the event. The browser may cache public pages and assets for offline use; viewer-specific routes are excluded. Failed aggregate counters may remain in a privacy-safe local retry queue for up to 24 hours.

Cookies

Operator sign-in stores a Supabase session in the operator's browser. Public guide pages do not use Aventic advertising or cross-site tracking cookies. A third-party media provider may store data after you choose to activate its embedded player, as described above.

Your data

Email hello@aventic.app for access, correction, or deletion requests. See also our Terms.