Last updated November 21, 2026
Privacy Policy
EventQuest helps you discover places and events near you, share public posts with the EventQuest community, organize events, and chat privately with friends.
The app has five areas: Home, Map, Pulse, Events and Chat. It is available for iPhone and Android, and as a web version at eventquest.ai. This policy explains what we collect, why, who can see it, who processes it for us, how long we keep it, and how to delete it. EventQuest (“we,” “us”) can be reached at roomquestgame@gmail.com.
Signing in
- You sign in with Google. On iPhone you can also use Sign in with Apple where the app offers it.
- Google: sign-in happens on Google’s page in your browser. Google tells our authentication provider (Supabase Auth) your Google account identifier and your email address, and, under Google’s standard sign-in permissions, your name and profile picture link. Supabase Auth stores what Google returns with your EventQuest account.
- Apple: we ask Apple only for your email address, not your name. With “Hide My Email” Apple gives us a private relay address.
- We use this information only to sign you in, keep your account across devices, recover it, and confirm it as a verified account. We never show your email, your Google name or your Google picture to other members, and we never use your email for marketing. Other members see only the nickname you choose.
- Email sign-in is off, and the app no longer creates guest accounts.
- Account status: your account tier (a signed-in Google or Apple account is “verified”), whether and when you accepted the community rules, and your plan (Free or Premium) with its expiry.
- Minimum age: at sign-up we record that you confirmed you’re 13 or older and when you confirmed it. Older accounts may retain a prior age group. We do not collect a birth date.
- Welcome message: we keep the version of the welcome message you dismissed and the dismissal time privately with your account so it stays dismissed across devices. Your device also keeps a dismissal marker and retries saving it when a connection is available. This is used for app functionality and is removed when you delete your account data.
Your profile
- Profile name (2–80 characters): collected during first sign-in on iPhone and kept with your account in Supabase Auth. It stays private; other members see your nickname.
- Nickname (2–20 characters): shown to your accepted contacts, to people who look you up by your exact nickname or friend code, to people shown you under “Suggested for you” (unless you turn that off), to members who see your Pulse posts or comments or your event comments, and to people you played with in earlier versions of the app.
- About Me (optional, up to 500 characters): shown only to your accepted contacts.
- Profile photos (optional, up to 5; verified members only): photos you pick from your library. The app resizes them and re-encodes them as JPEG before upload. They’re stored privately and shown only to you and your accepted contacts, through links that expire after 30 minutes. Your first photo is your account picture. Profile photos never appear in Pulse.
- Profile picture (optional during first sign-in or in Edit Profile): resized and re-encoded as JPEG, then stored in a separate storage area at a public link that does not require sign-in to open. It appears as your account picture and beside your public Pulse posts. You can change it from Edit Profile. It is deleted when you delete your account.
Friends and Chat
- Contacts: friend requests you send, receive and accept, and your accepted contacts.
- Friend code: a random 8-character code, shown only to you, that you can give to people so they can find you.
- Friend searches: you can look people up only by exact nickname or friend code. We keep who searched, what was found and when for 1 day, to limit searches and to check that a friend request follows a search.
- People you played with: if you played games in an earlier version, the app can list those players so you can add them; this comes from retained game history (see “Data from earlier versions”).
- Suggested for you: the app suggests up to 10 people you may know, worked out on our server from friends you have in common, Pulse follows in either direction, people you played with, and (for adults only) events you both said you were going to that have already ended in the last 180 days and the event categories you each go to most. Event signals only reorder people you’re already connected to in one of the other ways; they never put a stranger in front of you. A suggestion shows only the person’s nickname, how many friends you have in common and a general reason (“3 mutual friends”, “Goes to similar events”, “Likes similar things”, “Connected on Pulse”, “Played together”); it never says which friends or which events. People you already have a friend request with (sent, received, accepted or declined), people either of you blocked, suspended accounts and people in a different age group (adults and 13–17s are never suggested to each other) are never suggested. 13–17s see suggestions only from friends in common and people they played with. Show me in friend suggestions (Account → Settings) is on by default for adults and off by default for 13–17s; turning it off removes you from everyone’s suggestions at once. Tapping × on a suggestion hides that person from your suggestions for good; we keep who you hid until you delete your account. Suggestions are computed when you open them and aren’t stored.
- Direct messages (1–1,000 characters) between accepted contacts. Only the two of you can read them. If either of you removes the other as a contact, you can both still read past messages. If either of you blocks the other, the conversation is hidden from both of you. You can delete a message you sent at any time (long-press it); it is deleted for both of you.
- Shared cards: an event, a place or a Pulse post you send in a message. Your friend sees the card’s details only while they are allowed to see that event or post; otherwise it shows as unavailable.
- Photos in messages: one photo per message, picked from your library and resized and re-encoded as JPEG on your device (up to 5 MB). It is stored privately and shown only to you and that friend, through links that expire after 10 minutes, and never across a block.
- Read markers: when you last read each conversation, to show unread counts. Never shown to anyone else.
Messages, cards and photos are kept until you delete them or either of you deletes your account (or the account is deleted for inactivity). Photo files are then removed by a daily cleanup job, normally within about a day. A reported message or photo may be kept as report evidence (see “Safety and moderation”).
Pulse
- Who can see it: Pulse is visible to signed-in, verified EventQuest members, including members aged 13–17. It isn’t published on the open web. Posts by banned members or members under review are hidden, blocks hide content in both directions, and you don’t see items you reported.
- Posts (up to 3,000 characters) and comments (up to 1,000), shown with your nickname and its first letter as your picture. A post can mention one public place, one EventQuest event, or one public event from an outside source. For an outside event the post keeps a copy of that event’s public details (title, times, venue and its map position, source name and link).
- Pulse photos (optional, up to 4 per post, up to 5 MB each): the app resizes and re-encodes them as JPEG, and our server removes all embedded metadata (including EXIF and GPS location, XMP and IPTC data and comments) before anyone can see them. They’re stored separately from private profile and chat photos, and viewers get links that expire after 5 minutes.
- Likes and follows: posts you like, and members whose posts you follow. Following is one-way: it doesn’t make you contacts, and it doesn’t give access to anyone’s About Me, profile photos, friend code or messages. Blocking someone removes follows in both directions.
- Search: text you type into Pulse search (up to 200 characters) is used to run the search.
- Limits: to prevent spam we count your recent posts, comments, photos, changes and reports (counts and times, not content) and delete these counters after 2 days.
Posts, comments, likes and follows are kept until you delete or undo them or delete your account. Deleting a post deletes its comments, likes and photos. Unused photo files are removed by the daily cleanup job.
Events
Events are for verified members aged 13 and over.
- Events you host: title (up to 60 characters), optional description (up to 1,000), one to three categories, start time, optional end time, who can join, a record of time and place changes, and where it is: either a public place you pick (a business or point of interest, shown with its name, address and exact map position) or a map square of about 1.2 × 0.6 km (from a pin you drop or “near me”; we keep only the square and its centre, never the point itself or your own position).
- Web search: hosts may opt eligible public events at a public venue into web search. Search engines can receive the title, description, dates and public venue details and display them in search results. This setting starts off; friends-only events, personal map areas, host identity, attendance, comments and private photos are excluded. Visitors still sign in and must meet event access requirements. Turning this off stops new crawler access, but existing search results can take time to disappear.
- Repeating events: if you make an event repeat (daily, weekly, every 2 weeks or monthly, until a date up to 60 days ahead), we store the repeat rule, its time zone and end date, and each occurrence as its own event.
- Private saved plans: tapping an event’s heart saves a private bookmark with your account. Events you heart and events you host appear in Your plans across your devices. Other members cannot see your saved list, and saving does not confirm attendance. Unhearting removes the bookmark. Bookmarks disappear when their event or your account is deleted; ended events stop appearing in current plans.
- Optional RSVPs: a host can choose to accept RSVPs. Choosing RSVP separately confirms attendance; cancelling it does not remove your heart. Other members see attendance counts. Your nickname and picture appear in an event’s “Who’s going” list only to you and your accepted contacts; everyone else is shown only as a count. The host’s nickname is shown only to accepted contacts.
- Public or friends only: a host chooses visibility when creating or editing an event. A friends-only event is visible to the host and accepted friends who meet the event access requirements. A shared link does not grant access. Pending friend requests do not count; ending a friendship removes future access. The same access checks protect event locations, photos, comments and chat cards. Friends-only events are excluded from public activity counts and cannot be newly attached to a public Pulse post.
- “For you” order: the Events list can be sorted “For you”. That order uses your own Going and Interested answers, the events you host and the events you commented on (from the last 180 days, by category), and whether your accepted contacts said Going or Interested, along with how soon, how near and how popular each event is. It’s worked out on our server when results refresh; no additional server record is stored, and it isn’t used for ads or shared with anyone. The list never shows which of your contacts are going beyond the existing “Who’s going” rules. You can switch to the non-personalized “Date” or “Distance” order at any time; the app remembers only which order you picked, on your device.
- Event comments (up to 500 characters): shown with your nickname to everyone who can see the event, except people you blocked or who blocked you. The host can delete any comment on their event. To prevent spam we keep the time and count of your recent comments (not their text) for up to about an hour.
- Event photos: the host can add up to 4 photos, resized and re-encoded as JPEG on the device. They’re stored privately and shown only to members who can see the event, through links that expire after 10 minutes.
- Calendar and directions: on supported iOS builds, Apple Calendar opens a system event form for you to review and save. Google Calendar opens its app composer on iOS, or an installed calendar editor/chooser on Android, with a web draft as fallback when unavailable. Web opens prefilled Google Calendar and Outlook websites. EventQuest does not request calendar-reading or reminders access. Your chosen calendar receives the event details when you choose that action. Directions share the public venue location with Google Maps, Apple Maps or Waze. Each service has its own privacy policy.
- Ride: when you choose Continue with Uber or Continue with Lyft, EventQuest opens your selected ride provider’s app or website with the event or place’s exact public destination coordinates and, where supported, its name and available address. EventQuest does not read your device location or collect a pickup location for this action, and the link does not contain your account details, itinerary or provider credentials. EventQuest does not use a ride-provider SDK or book the ride. Your selected provider handles pickup, fare, payment and final ride confirmation under its own privacy policy.
An event, with its answers, comments and photos, is deleted 30 days after it ends (an event without an end time counts as ended 3 hours after it starts), or earlier if the host deletes their account. A cancelled event follows the same rule. Photo files are removed by the daily cleanup job. A reported comment or photo may be kept as report evidence.
Civic and public services
You can browse public service notices by town, county or state and follow up to ten areas. Your followed area IDs and names are saved on this device, separately for each signed-in account. Your area search and selected IDs are sent to our authenticated service to return public notices. Opening an area can also request an official-source refresh using our existing account rate limits and shared source demand records. When you save a Civic date, this device keeps the public occurrence ID for the signed-in account and requests its current details to show in My Events. Follows and saved Civic dates are device-specific and are removed from this device when you delete the account.
Following an area does not establish that a particular collection route serves your household. EventQuest does not request your household address for this feature. If you choose an official address lookup, the provider’s website handles the information you enter under its own privacy terms. Adding a service occurrence to a calendar is an explicit action that shares its public details with the calendar or file destination you choose. Following an area does not enable automatic reminders or calendar access.
Personal day plans and friends going
Your day plan is private to your account. We store the selected day and time zone, references to events or Google Place IDs, and the arrival and departure times you choose. Your devices may keep account-scoped plan references and pending changes so they can sync after reconnection. Removing a stop removes it from the plan; deleting your account deletes the plan. A plan or heart does not mark you as Going.
Choosing I’m going on an imported public event stores a separate attendance choice linked to your account and that event’s stable EventQuest link. Accepted friends who can currently access the event can see your Quest Name and profile picture on its card and details. Pending requests and blocked relationships do not qualify. Pictures use short-lived, viewer-authorized links and are not included in public discovery data or offline event snapshots. You can undo Going; it is also removed when your account is deleted.
Send to a friend sends an event card and any message you enter to the accepted friend you select, through existing private chat. Sharing does not grant access to a restricted or withdrawn event. Shared links are checked again when opened, and messages follow the Chat retention and deletion rules.
Searching for places in Plan a day uses the Places service described below. When you open the trip map, Google Routes receives the adjacent public stop coordinates or Place IDs, your chosen travel mode and planned departure time to estimate travel. We do not include your Quest Name, email, friend list or account ID in that provider request. Place names, business details and route geometry are held only in the current view; the saved plan keeps references, your visit times and the driving or walking choice for each connection between stops. Opening the planner does not request your device’s location. Google handles provider requests under its own privacy policy.
Places and maps
- Maps are shown with Google Maps. Your device loads map images from Google. On iOS, Google’s Maps SDK can also send Google device and service identifiers, map interactions and other technical data, crash reports, and performance measurements for app functionality and analytics. This SDK data is separate from optional Sentry crash reporting.
- Place search goes through our server to Google Places: we send Google the search text (up to 120 characters), the map area you’re searching (its centre and radius; when you search around your own location, the centre is that location), a session token and the category. We don’t send Google your account ID. We don’t store the search or Google’s results. Place photos load on your device directly from Google.
- Choosing an area by name (for example a city) sends the name you type, and your location rounded to about 11 km if you’ve allowed location, directly from your device to Photon, an OpenStreetMap search service run by Komoot.
- Places on posts and events: when someone tags a place, we save that place’s public details (Google place ID, name, address, category and map position) so posts and events can show it. We don’t record who added it.
- Usage limits: to control misuse and cost we count your place searches per minute and per day, and keep overall daily counts without user IDs. The counters contain no search text or location.
Public events from other sources
For community calendars, our server sends public event street addresses to Geocodio to verify venue coordinates. These requests contain no account ID, sign-in token, device location or location history. We retain verified US venue coordinates and address evidence for reuse. We resolve public venue names against publisher event and venue pages, cache verified address matches, and reuse them for future events. Listings without verified coordinates stay out of geographic discovery. Community-event pictures are discovered from public feeds and event pages; we check image URLs and file types and retain reusable image links. Your device loads these pictures from the publisher or its image host. No account ID, sign-in token or personal location is sent with server-side venue or image checks.
Scheduled calendar imports from Localist use a separate private recovery store for public event and cancellation details. Recovery use ends at the source's refresh deadline, within 96 hours of capture. Details are cleared after processing, completion or replacement, or by bounded cleanup after expiry. One latest status and progress record per calendar source, including hashes and timestamps, remains until a newer snapshot replaces it or the calendar source is deleted.
Events lists can include public listings from outside sources.
- Our server, not your device, contacts these sources, so they don’t see your device’s IP address, and we never send them your account ID or sign-in token.
- Before any request, the server rounds the search centre to about 11 km (0.1°). Ticketmaster receives that rounded point, the selected radius with bounded extra coverage for rounding, and a date range. FindLocal receives a point on an even coarser grid (0.2°) and the selected distance with bounded extra coverage, at most 200 km. The National Park Service receives no location: our server downloads the full list of parks and picks the nearby ones itself. NYC Parks receives no location, only date filters, and is asked only for searches near New York City. Approved geographic Localist calendars receive the rounded point; whole-calendar feeds receive no location.
- Public listings are shared by people searching the same coverage area. Successful source checks are normally reused for up to four days and refreshed when someone searches that area. Each successful check updates event details and available image links together; FindLocal and NC State Parks use a shorter 24-hour refresh schedule. Upcoming and ongoing facts can remain available until the event ends, subject to cancellation, review and provider restrictions. FindLocal facts stop displaying after 24 hours without a new check. Approved image links normally remain valid for up to four days after the source check; FindLocal and NC State Parks retain shorter 24-hour image limits. Image validity is separate from factual event visibility. Shared provider caches identify the public source, coarse area and applicable radius/date window, without your account ID. To limit refreshes we keep, per account, the time and count of your recent refreshes, removed after about an hour.
- Background search progress: while local calendars finish, we keep one private progress receipt for your account. It contains a random reference, a digest of the coarse search area and radius, the relevant public calendar identifiers, and creation/expiry times. It contains no exact coordinates or search text. It expires after 15 minutes and is removed by routine cleanup, replaced by a later search, or deleted with your account. The app checks this receipt while Map is active so new results can appear without repeating the calendar request. It is not shared with publishers or other members.
- You can comment on a public listing the same way as on a EventQuest event (up to 500 characters, shown with your nickname, subject to blocks and reports). These comments are deleted 30 days after the listing's start time, or when you delete them or your account. You may also create your own Pulse post about a public event. Event cards in Pulse reference their event by ID. Referenced past or cancelled events retain their title, dates, venue and description for a read-only history view, including after the browsing cache expires. Expired provider images are not included in this history view. We recheck event and post permissions each time; hidden or restricted details remain unavailable. Provider restrictions, including FindLocal’s 24-hour factual limit, still apply to history views. Deliberately removed events leave only an unavailable-content notice in the post.
- Some listings include an image that your device loads from the source’s own server. Opening a ticket or publisher link takes you to that site, under its own privacy terms. Saved imported events: tapping a heart stores the listing’s internal event ID alongside your EventQuest account, so the private bookmark appears in My Events across devices. The bookmark does not contain the publisher’s descriptions or images and remains until you remove it, delete your account or the provider row is removed. A listing may not display while its provider cache is expired. Saving is not a ticket purchase, RSVP to the publisher or registration.
Permanent shared links and sitemaps can identify eligible public provider events. We keep provider identity keys and a content fingerprint so a link can recover after a cache row is replaced, without retaining the expired description or image. Crawler requests do not start provider searches or use a visitor’s location.
Cached public event and activity searches
To make public event and Things To Do searches in the app and website faster and reduce repeated database transfers, we temporarily store public event and activity results and their version hashes in private Vercel storage. Results can include distances calculated for the search area. Cache entries are not linked to an account and do not include authentication tokens, private events, private saved activity data, personal RSVP state, raw search coordinates or search text. A cryptographic key identifies the search. Public Things To Do searches from the website and installed apps pass through Vercel without account credentials. Vercel processes the search parameters to return public results.
We normally check external-event results for changes after 24 hours, with shorter checks for access-sensitive or time-dependent results. Public Things To Do facts are reused for up to 24 hours only while a separate permission check remains valid for at most 60 seconds. Activity images and time-limited information keep their original expiry deadlines. We remove ended events and expired images from served results. Stored cache objects expire within two days of their last cache write; a refresh can replace or renew an entry. This cache supports event and activity search functionality and is not used to build an account-linked location history or for advertising or analytics.
For guest event searches in the installed mobile app, complete public result pages can also be stored in the app's existing SQLite public-cache database. Each page is keyed by a hash of the exact query and stores public event facts, which may include venue coordinates and distances calculated for that search, together with page order and opaque version hashes. These snapshots contain no raw search coordinates or text, account credentials, private content or personal RSVP state. They keep the server's original freshness deadlines; receiving or reopening them does not restart those deadlines. Snapshots have a maximum seven-day retention period from their original server generation time for comparing updates, separate from how long they can be displayed as current results. Event and source expiry limits still apply, and cache limits may remove entries sooner. Image URLs are removed from the SQLite pages. Approved backup-photo identifiers can remain, and the app requests current media through Vercel when needed. The separate approved image cache described below continues to use its own expiry and access rules. These public pages do not replace signed-in searches that require account-specific access checks.
Stable backup photos
Some event and Community reads from the app and website pass through Vercel before reaching our existing database. This relay processes the request parameters, sign-in access token when present, and the response the caller is authorized to see. Signed-in responses are not stored in the shared public event cache. We do not add access tokens, request bodies or private response content to application logs or backup-photo records.
To keep an event's illustrative backup consistent, private Vercel storage retains a small record containing a hashed event identity, an approved photo identifier or neutral choice, a schema version and a retention deadline. It contains no title, description, venue, account identifier, RSVP or photograph. It survives ordinary search-cache refreshes and is normally scheduled to expire after the event with a short cleanup margin. For events more than two years in the future, cleanup is scheduled when a later read brings the record within the storage service's supported expiration range; an unread record may remain longer. An authorized event-supplied photo takes priority over this illustration. These records support display consistency, not analytics or advertising.
Location
- Location is off by default. EventQuest asks only for permission while you use the app, and never uses your location in the background. Ordinary discovery uses an approximate position (about 100 m accuracy); public heatmap sharing requests higher foreground accuracy for the place check described below. You can turn location permission off at any time in your device settings; the rest of the app still works, and you can choose an area by name instead.
- Finding things near you (Home, Map, Pulse, Events): the app keeps your position or chosen area in memory and sends it with each search for places, posts, events and Things To Do within up to 100 miles. We do not keep an account-linked location history. Public website event searches and public Things To Do searches use the temporary, query-derived cache described above; raw search coordinates and search text are not added to that cache. On the website, the last city or map area you chose (never your device's position) is remembered in that browser, rounded to about 100 metres, so the map can reopen there; it never leaves your device and is removed when you sign out. Before the browser asks for location access, the website explains why. Place searches send it to Google as described in "Places and maps".
- Your position on the map is shown only to you, on your device.
- Events near you: your position is used once to work out distances, shown as rough bands, and isn’t stored. If you create an event “near me” or with a pin, we keep only the map square of about 1.2 × 0.6 km.
- Event alerts near you (off by default; verified members): if you turn on alerts for new events near you, the app sends your position when you turn it on and at most once a day while the app is open. We keep only a map square of about 5 × 5 km, never the position, and use it to tell you about new events in or next to that square. It is deleted when you turn the setting off, when you delete your account, or 14 days after the app last updated it.
- Activity sharing for the Public Heatmap uses the location permission and Heatmap setting described next.
Public Heatmap
When Public Heatmap participation is on, we request a more accurate foreground location to check for a nearby public place. Our server sends the unrounded position, without your account ID, to Google Places. We use categories and a small proximity limit to reject residential and uncertain matches where detected; this is a best-effort check, not a property-boundary guarantee. Only a coarse, randomly offset location is stored with your account, along with the verification time, for up to 10 minutes. Google results and your exact position are not stored by EventQuest. Authorized private Test sharing skips this Google check and works anywhere, including homes, without a minimum group size.
The Map can show where activity is, as rough areas rather than people.
- Opt-in: When you grant location access in the app, eligible accounts can contribute to the Public Heatmap while the app is open. Turn participation off in Account → Settings.
- What the app sends: while sharing is on and the app is open on screen, the app sends your position about every 45 seconds. Our server immediately rounds it to a grid of about 150 m and shifts it by a random amount of up to about 150 m in each direction (a new shift each time you start sharing). Only that shifted point is stored with your account, never your exact position, and it moves at most once a minute. It counts as current for 2 minutes and is deleted after 10 minutes, or as soon as you turn sharing off or the app goes to the background.
- What others see: never your position or your name. Every 5 minutes the server counts how many different people are sharing in each area of about 1.2 × 0.6 km; these counts contain no user IDs. An area appears only if at least 5 different people were in it within the last hour, and only as a band (5–9, 10–24 or 25+) after a small random adjustment, never an exact number. Zoomed-out regions follow the same rules. The 5-minute working counts are deleted after 1 hour, and the area and region results after 24 hours.
- On your device: if you turn sharing off while offline, the app remembers that until our server confirms it, and sends nothing in the meantime.
- Limits: to prevent abuse we keep the times of your recent map requests and position updates (not locations) for about 10 minutes.
Event sharing and reminders
Choosing Post → Facebook or Post → X opens the selected service with the event link and, for X, its title so you can review and publish there. EventQuest does not publish the post, request a social account token, or read your social contacts. These services receive the details you choose to share and handle your account under their own privacy policies. Friends-only events do not offer these public posting options. Copy link and Email use your clipboard or chosen email application; the mobile Share action uses your phone’s sharing menu.
Weather opens an external provider only when you choose it for an event at a known public venue. On iOS, eventQuest attempts to open Apple Weather without sending event details; the app may show its previously selected location. On Android, eventQuest opens a Google weather search containing the public venue address or name. On the web, and through the mobile fallback, weather.com receives the public venue coordinates rounded to three decimal places. These handoffs omit your eventQuest account details, the event title and date, device location and location history. The selected app or website handles the visit under its own privacy policy. A weather.com option for the event’s location remains available on mobile, and no new device-location permission is requested.
Some earlier app versions retrieve weather through eventQuest’s server from the U.S. National Weather Service using the public venue coordinates rounded to three decimal places. That older endpoint remains available for those clients and caches the forecast for reuse. It receives no event title or date, account information, device location or location history. New Weather actions do not call that endpoint.
Remind me saves an account-private choice for one event occurrence: its identifier, selected lead time or Off, scheduled start and reminder time, and delivery/change markers. The choice syncs across your devices and does not change your heart or Going status. You can change it or turn it off. A chosen time replaces the automatic reminder for that occurrence. Reminders appear in EventQuest Notifications; phone alerts use your existing notification preferences and device permissions. Cancelled, unavailable and inaccessible events do not send a new reminder. Records are removed with the event identity or account, and routine cleanup removes records more than 90 days after the event’s scheduled start. Notification delivery uses the providers described below.
Notifications
- EventQuest asks before turning notifications on, never at first launch: an in-app explanation comes first (when you first open Chat, or from Settings), then your phone’s own prompt. The web version doesn’t send notifications.
- What we store for each phone (up to 10 per account): the push token issued by Expo, Apple and Google for this phone, the platform (iOS or Android), the app version (so event notifications go only to app versions that can open them), and when the app last checked in. With your notification settings we store your phone’s time zone name (such as “Europe/Berlin”, not a location).
- Your settings: which kinds of notifications you want, whether to show message text, and quiet hours for event notifications (22:00–08:00 unless you change them).
- Kinds: new messages and friend requests; for events, reminders 15 minutes before an event you’re going to (the host gets one too), changes to the time or place, cancellations, comments on an event you host (at most one per event per hour), when a contact says they’re going, and, only if you turn it on, new events near you. During quiet hours, contacts’ and nearby-event notifications are held back. At most 3 event notifications are sent per day; changes, comments, cancellations and the host’s reminder don’t count toward that.
- Message text stays private by default: a message notification says only who wrote or what kind of thing they shared, unless you turn on Show message text. Event comment notifications show the comment only with that setting.
- Delivery: notifications go through Expo’s push service and Apple’s or Google’s push service, which receive the push token and the notification’s title and text. Queued notifications and their send times are deleted within 1 day.
- A push token is deleted when you sign out, turn notifications off for this phone in Settings, delete your account, after 180 days without the app checking in, or when the push service reports it’s no longer valid.
Safety and moderation
- Blocking: you can block anyone. Blocks work in both directions: you stop seeing each other’s content and messages. You can review and undo blocks in Account → Settings → Blocked Users.
- Reports: you can report a member, a message, a shared card, a photo, a Pulse post or comment, an event, or an event comment or photo. A report stores the reason, optional details (up to 500 characters for Pulse reports) and where it was filed. We never tell the reported member who reported them.
- Evidence: so moderators can see what happened even if it is later edited or deleted, a report keeps a copy of the reported content: for a report from a conversation, a card or a photo, the last 10 messages between you and that member (and the reported photo); for a Pulse post, the post and its photos; for a Pulse or event comment, the comment; for an event photo, the photo. Only moderators can see evidence; photos through short-lived links.
- Automatic hiding: a post, comment or photo reported by 3 different people within 7 days is hidden while we review it. A member reported by 3 different people within 7 days may be hidden while we review.
- Moderator actions: warnings (a reason category and a private moderator note), review holds, bans and a log of moderator actions. If action is taken on your account, the app shows you the reason category and dates, never the moderator’s note.
- Text cleaning: we remove invisible and control characters from text you post, and block certain terms in nicknames, event comments and place names.
- How long: reports and their evidence, warnings and the moderation log are deleted 12 months after they’re created. A ban is deleted 12 months after it ends; a ban in force is kept while it applies. Review holds are kept until a moderator releases them. These records stay for that period even if the content or the account is deleted; if you delete your account, reports you filed are kept without your account ID.
Website analytics
On the public eventquest.ai website we use Google Analytics 4 (measurement ID G-4NYMKNBHSC) alongside Vercel Web Analytics. These services help us understand visits, browser/device types, broad traffic sources, pages viewed, navigation and engagement. Google Analytics may use cookies or other browser identifiers, browser/network information, approximate network-derived location, and page URLs or search parameters included in visited URLs. We do not deliberately add EventQuest account IDs, private messages, exact device coordinates or private profile information to our own web analytics events. The GA4 tag is limited to our live domain, with Google Signals and advertising personalization disabled in code. Web tracking is separate from native Firebase Analytics. See Google’s Privacy Policy and Vercel’s Privacy Policy.
Website advertising and consent
Privacy choices
Paid website ads are currently off. For a privacy request, contact EventQuest.
The EventQuest website contains clearly labeled Advertisement spaces among public event listings. We have registered eventquest.ai with Google AdSense and are preparing Google's Privacy & messaging consent tools. As of November 19, 2026, Google has not yet approved the website and paid AdSense ads remain disabled; an Advertisement space may be empty.
If website advertising is enabled, Google and its approved advertising technology partners may process IP address, browser/device characteristics, approximate network-derived location, the public page address, interactions with ads, and cookies or other device identifiers where permitted. These details support ad selection, delivery, measurement and fraud prevention. Under some US privacy laws, some of this processing may constitute sharing for cross-context advertising. We do not intentionally send EventQuest account IDs, email addresses, friends, private messages, saved itineraries, precise device GPS coordinates or non-public event details to advertisers, or use these private records to select ads. Public page URLs may still be available to ad services.
For eligible visitors in the European Economic Area, UK and Switzerland, Google's consent management platform is configured to offer Consent, Do not consent and Manage options. Consent choices can be revisited through a Privacy and cookie settings link when Google's message is available. Google's consent message is shown only once the necessary publisher tag is installed and eligibility conditions are met; publishing it in the AdSense console alone does not activate ad scripts on EventQuest. We will review applicable US-state advertising privacy options before enabling paid ads.
See Google's Privacy Policy and My Ad Center for further information about Google's processing and ad choices. Questions or applicable privacy rights requests can be sent to roomquestgame@gmail.com. Google's website analytics are separate from advertising, and our GA4 Google Signals and advertising personalization settings are disabled.
Native test advertising in internal EQ Preview
Internal EQ Preview builds for iPhone, iPad and Android include Google Mobile Ads (AdMob) to test native ads. They request Google's test ad units, with nonpersonalized ad requests. Paid native ads are not enabled. The EventQuest Production apps distributed through the App Store and Google Play remain excluded from this SDK.
Before initializing Mobile Ads or requesting a test ad, Preview checks Google's User Messaging Platform (UMP) consent information and presents any required privacy form. Ads are requested only when UMP reports they are allowed; otherwise a test status card may appear. An Ad privacy choices control is available when UMP requires it. Consent checks themselves communicate with Google. Test ads and nonpersonalized settings do not mean the SDK is offline or that Google processes no data.
Google's SDKs can process IP addresses and approximate network-derived location, app/device information and available device or app identifiers, ad views and interactions, and crash/performance diagnostics. These support ad delivery, measurement, analytics and fraud prevention. The app does not deliberately supply EventQuest account IDs, private messages, saved plans or precise GPS coordinates to test-ad requests.
Google handles SDK data under Google's Privacy Policy. See Google's iOS SDK data disclosure and Android SDK data disclosure.
App usage analytics (native iOS and Android)
In mobile builds where it is enabled, Google Firebase Analytics helps us understand app use and improve navigation, discovery and reliability. Some builds have this collection disabled. When enabled, Firebase can collect a pseudonymous app-instance identifier, app and device details (such as app version, device model, operating system and language), general location inferred from network information, and usage information such as app opens, sessions, screen views and engagement. Google processes this information to provide usage reports; its retention depends on our Google Analytics property settings and Google’s policies.
Our own screen-view events use only broad section labels, such as Events, Map or Chat. We do not intentionally include your EventQuest account ID, name, email address, search terms, specific event or place IDs, precise location, photos, or private message content in these analytics events. The iOS Firebase integration is configured without advertising-ID support. We do not use these events for personalized advertising or to track people across other companies’ apps and websites.
Firebase Analytics is separate from our website analytics and from EventQuest account data. Deleting an EventQuest account does not automatically guarantee deletion of analytics already retained under an app-instance identifier. For questions or applicable requests about your information, contact roomquestgame@gmail.com. See Google’s Privacy Policy for more information about Google’s practices.
Crash reports
When crash reporting is turned on in the app, errors and crashes are sent to Sentry: the error message and where in the code it happened, the app version and update, the release channel, the device model and operating system version, and the last screens visited and network requests made (method, status and address without any query). Before sending, the app removes account IDs, email addresses, sign-in tokens and push tokens from the report. Crash reports don’t include your IP address, account, nickname, messages, photos or screenshots, and we don’t use Sentry to track sessions, usage or performance. Sentry keeps them only for the retention period set for our account.
Technical data
When the app or website talks to our servers, our providers receive your IP address and standard request information (time, address requested, app or browser type), which they log for security and to run the service: Supabase for the app’s data, Expo when the app checks for updates at launch, Google when maps load, and Vercel for the web version, this website and supported app event and activity reads. These logs are kept according to each provider’s retention settings.
On your device
The app stores on your phone (in the system’s secure storage; in browser storage for the web version): your sign-in session, your push token and notification choices for this phone, your Light or Dark appearance choice, a pending “stop sharing activity” marker, the time it last updated your event-alert area, and, if you used a guest account in an earlier version, a marker for it. These stay on the device until you sign out, clear the app’s data or uninstall it.
The mobile app also keeps previously viewed account details, conversation text and event content in a private database inside the phone’s app storage, separated by account. A local queue holds pending direct messages, Pulse room text messages and event bookmark changes. The app saves a change on your phone before reporting it as queued, then sends it after reconnection through the existing server authorization checks. Previously loaded content may be out of date; event visibility and source expiry limits still apply.
Signing out deletes that account’s local cached content and pending changes; the app warns before discarding pending work. Switching accounts clears the previous account’s private data and does not send its queued changes under the new account. Server delivery acknowledgements prevent duplicate retries and contain command identifiers and results rather than message bodies; they are removed when the account is deleted. Photos and map tiles are available offline only when their existing caches contain them; photo uploads and other uncached remote actions require a connection. The separate public browsing and image caches are described below.
Data from earlier versions
Earlier versions of EventQuest offered games (chess, Trivia, QuipLine, Campus Rumors, MALICE and the Daily Challenge), a “Players Nearby” screen, guest accounts and game invites. The current app doesn’t offer them and collects no new data for them. Game records, game chat and scores from those versions stay on our servers until you delete your account or it is deleted for inactivity (Daily Challenge answers are deleted after 90 days). When you delete your account, games only you played are deleted, and games you played with others stay in their history without your account ID or nickname.
Who we share data with
- Other members see what you choose to share, as described above: your nickname, your Pulse posts, comments and photos, your events and event comments, and, only for accepted contacts, your About Me, profile photos and messages.
- Service providers process data on our behalf: Supabase (Supabase, Inc.) for our database, sign-in, file storage and server functions; Google for Google sign-in, Google Maps, Google Places, Google Analytics on our website, Firebase Analytics in supported app builds, Google Mobile Ads and UMP for internal EQ Preview test ads, AdSense site verification and (when activated) web advertising and consent messaging, and Firebase Cloud Messaging for Android notifications; Apple for Sign in with Apple (where offered) and Apple Push Notification service; Expo (650 Industries, Inc.) for push notifications and app update delivery; Sentry (Functional Software, Inc.) for crash reports, when turned on; Vercel (Vercel Inc.) for hosting the web version and this website, authorized event-read processing, public activity searches and caching, and retained backup-photo identifiers; and Photon (Komoot) for searching for an area by name.
- Public event sources (Ticketmaster, the U.S. National Park Service, FindLocal, NYC Parks and approved calendar publishers) receive only the coarse search information described above, never personal data.
- Services you choose to open, such as Google Calendar, Outlook, a maps app for directions, Uber or Lyft for a ride, or a ticket page, receive what’s needed to fulfil your request under their own privacy policies.
- Legal: we may disclose data if the law requires it or to protect the safety of our members.
What we don’t do
- We do not sell the EventQuest account database or deliberately send private profiles, messages, saved plans or precise device locations to advertisers. Website advertising, when enabled, may involve third-party browser data processing described in “Website advertising and consent,” including activity treated as sharing under certain US privacy laws.
- The Production store apps exclude the AdMob SDK. Internal EQ Preview uses Google's test ads as described in the native test advertising section. Website ad consent and GA4 analytics are separate from native app analytics and the iOS map provider’s technical diagnostics.
- We don’t ask for your phone number, your birth date, your phone’s address book, or background location.
- The system photo picker gives the app only the photos you select. Optional Pulse room still-photo capture requires camera permission and uploads only when you press Send. The app does not use the microphone or record video.
Deleting your account
- In the app: Account → Settings → Delete my data. The app first deletes your profile photo files, then our server deletes your account.
- If you signed in with Apple on iPhone: before deleting, the app asks you to confirm with Apple once more. It sends Apple’s one-time authorization code to our server, which asks Apple to revoke eventQuest’s access. The code and Apple tokens are not stored or logged. Cancelling or a failed revocation does not stop account deletion; you can also remove eventQuest in Apple’s Sign in with Apple settings.
- By email: write to roomquestgame@gmail.com from the email address of your Google or Apple account, or include your nickname, and we will delete it for you.
- What is deleted, at once: your account and sign-in record, nickname, age group and account status, About Me and profile photos, contacts and friend requests, friend code and searches, your friend-suggestion setting and the people you hid from suggestions (and other members’ hiding of you), direct messages you sent or received (with their cards and photos), read markers, push tokens, notification settings and queued notifications, your event-alert area, activity-sharing data, blocks (yours and other members’ blocks of you), the events you host (with their answers, comments and photos), your RSVPs, private saved-event bookmarks and explicit event reminders, your event comments, your Pulse posts, comments, photos, likes and follows in both directions, and your rate-limit records. Data from earlier versions is handled as described above.
- Shortly after: photo files are removed from storage by a daily cleanup job, normally within about a day.
- Kept: reports and their evidence, warnings, holds, bans and the moderation log, for the periods in “Safety and moderation”; reports you filed are no longer linked to you. Public places and public event listings stay because they don’t identify anyone.
- If the app reports that your account couldn’t be removed, contact us and we will finish the deletion.
Inactive accounts are deleted automatically, without notice, in the same way, after 24 months with no sign-in and no messages, profile changes, Pulse activity or (earlier versions) game activity. Accounts of EventQuest’s administrators are excluded.
Children and teens
EventQuest is for ages 13 and up and isn’t directed to children under 13. We don’t knowingly collect personal information from children under 13; if you believe a child under 13 is using EventQuest, contact us and we will delete the account.
Security
Data is encrypted in transit (HTTPS). Database access is restricted so members can read only what they’re allowed to see. Private photos are stored without public links and shown only through short-lived links issued after an access check.
Your rights
Depending on where you live (for example the EEA, the UK or California), you may have rights to access, correct, delete or export your data, or to object to its processing. Contact us at roomquestgame@gmail.com to exercise them.
Changes
We’ll update this policy when our practices change and revise the date above. For significant changes, we’ll tell you in the app.
Who we are
EventQuest. Contact: roomquestgame@gmail.com.
Temporary browsing cache
To make browsing faster, the phone temporarily caches recent results in memory. It also keeps small, short-lived previews of public external events in its disposable cache directory. Those previews contain public event facts and venue locations, not private messages, profile photos, precise device coordinates or personalized rankings. They expire for display after five minutes and refresh when you return.
For approved public event images, the phone can also keep a limited local copy: up to 200 images or 20 MiB, whichever limit is reached first. It downloads an image only when a screen asks to display it, from the original publisher or image host, without adding your account ID or sign-in token. Each copy belongs to the current event record's source check and image link. It stops being used at the server's image deadline, normally within four days of that source check and within 24 hours for FindLocal and NC State Parks. Opening or downloading it does not extend that deadline. A publisher's shorter expiry or instruction not to store the image also applies. A new source check or changed image link requires a new cache version.
Signing out, switching accounts or losing access clears applicable cached content. Expired image files are removed when the app starts, resumes, accesses the cache or performs foreground cleanup; the operating system may suspend the app between uses, so file deletion cannot run while it is suspended. The system may remove cache files sooner. This image cache excludes private and member-uploaded event photos, chat and profile photos, and Google Places images. The web version uses the browser's normal HTTP cache rather than this phone file cache.
Live event rooms
Pulse Live event rooms use your public Quest Name and shared messages/photos. We store an account-linked, short-lived room-presence heartbeat to show a count of people currently in a room; it does not establish physical attendance. Presence stops counting after about one minute without a heartbeat and stale entries are removed by scheduled cleanup. Nearby room discovery reuses your selected area; room participants do not receive your coordinates or sign-in email. Messages and moderation evidence follow the existing content and account-deletion rules.
You can choose a photo from the system picker or take an optional still photo for a Pulse room. Taking a photo requires camera permission. The photo stays on your phone until you press Send; cancelling or discarding it does not upload it. Sent photos are resized and re-encoded, then follow the existing room access, moderation and deletion rules. Photo uploads require a connection. The app does not record video or use the microphone.