Last updated November 21, 2026

Privacy Policy

Privacy choices

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

Your profile

Friends and Chat

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

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.

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

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.

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

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.

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

Safety and moderation

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

What we don’t do

Deleting your account

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.

Coverage requests and the public map

Coverage requests include the town you select, search radius, optional interests, suggested calendars and notes. Administrators can review these details to expand coverage. If you request updates, we retain your contact email for that purpose. Signed-in users may separately opt in to showing their Questname beside the requested town on the public Coverage map; this is off by default and can be withdrawn under Coverage → My requests. Pins use verified town centers, never your device location. The compass uses foreground location only to help you choose a town. Guest requests have no public Questname. We use keyed network identifiers, expiring verification challenges and rate limits to reduce spam. Coverage emails provide an unsubscribe link. Account deletion removes account-associated requests and contact data; guests may contact roomquestgame@gmail.com about their request data.

Public town coverage aggregates

Selecting a named public town may add its canonical town center and aggregate 75-mile peak event count to the public coverage map. These coverage records retain no visitor identity, device coordinates, individual search history or search frequency.