Outside.
Outside.
Outside is a free hobby project for discovering local events, launching first in Grand Rapids.
You can browse events, use filters, and open directions without an account.
An optional account is required for Down marks, friends, and sharing. Those features require acceptance of the Terms and acknowledgement of this Privacy Policy.
Outside does not request, receive, or store device geolocation.
Outside uses a city preference cookie only to route you back to your selected market.
Matching alert intent can be saved on this device, but automatic delivery is not active yet.
Planning features may use Clerk identity, Down records, friend links, sharing settings, and alert intent as described below.
Outside uses event and deal information from configured local sources to show tonight's options. The selected city determines which market's event inventory is displayed.
Outside does not accept neighborhood or custom-place origins. Legacy custom-location parameters are removed from page URLs and are not used for directions.
If you choose Boston or Grand Rapids, Outside stores that selected market in a cookie named outside-market and in browser local storage so the root domain can route you back to the same city.
Outside does not call the browser geolocation API or calculate travel estimates. When you click Directions, Outside sends the event's coordinates or its venue-and-address text to Apple Maps on Apple devices and Google Maps on other devices. The maps provider handles the trip origin, live location permission, route mode, and its own data practices.
If you choose to create an account or sign in, Clerk processes your sign-in details and uses authentication cookies to maintain your session. Outside uses your Clerk user ID to connect your account records. Public event browsing does not require sign-in.
Before Down, friend, sharing, or account alert features are enabled, Outside stores your Clerk user ID, the accepted Terms version, the acknowledged Privacy version, and the acceptance timestamp. A new acknowledgement is required when either current version changes.
If you use friend features, Outside stores a friend-only display name you choose. It is not a public-search profile. Accepted friends can see it, and a reusable-link owner can see it while reviewing your pending claim.
Admin poster and PDF OCR uploads are stored as private review-only source material. Upload review records can include the uploaded text, source URL, attribution notes, file metadata, review status, and admin audit details such as actor, action, reason, and timestamp.
Your selected market is stored in your browser under the key outside-market. It is used only to remember whether you chose Grand Rapids or Boston.
Matching alert intent is stored only in your browser under the key outside.matchingEventAlerts. It records interest on this device; Outside does not currently deliver automatic matching-event alerts.
Older versions stored transport, category, student eligibility, group category, and local group-invite preferences. Current discovery ignores those retired values, but they may remain until you clear site data.
You can clear this saved preference by using your browser's site data controls or by changing and saving the preferences again.
Outside does not sell personal information. Outside does not share matching alert intent with advertisers, data brokers, analytics providers, social networks, or friends. Account Down marks are private unless you enable sharing and choose specific friends.
Outside uses Clerk as the single identity provider for consumer accounts and admin access. Outside stores product-specific profiles, link claims, friendships, Down sharing, match, and audit records separately from Clerk identity.
Admin-uploaded source material and listing candidates are kept for review and are not published until an admin approval workflow converts them into source-attributed event records.
A reusable friend-link record stores both a token hash and the private share token so its owner can copy the same link again. Anyone who receives or is forwarded that link can submit a separate request. The link remains active until its owner replaces or disables it; rejecting a claimant does not automatically replace the link.
Claiming a valid friend link creates a pending request and shows the claimant's Outside display name to the link owner. It does not create a friendship. A friendship is created only if the original link owner explicitly approves that claim. A claimant can withdraw a pending request, and either friend can later remove the friendship.
If you enable automatic Down sharing, Outside stores that account-level setting, but it does not share any Down marks until you also select accepted friends for sharing. Removing a friend from that selection stops future sharing with that friend without deleting the friendship or your private Down marks.
Outside stores the accepted friends you select for automatic Down sharing. Clearing a selection or turning automatic sharing off stops future sharing without deleting the friendship or your private Down marks.
Outside uses accepted friends' Outside display names—not Clerk names, usernames, or email addresses—to label sharing choices and matching Down marks.
When both friends mark the same event Down and one friend has explicitly selected the other for sharing, Outside stores a directional match record containing the recipient, sharing friend, event, status, match and update times, and expiration. Only the authorized recipient sees that friend's display name for the match.
The outside-market cookie can remain for up to one year unless you clear site data or choose another supported market.
The local-storage market preference, device-local alert intent, and retired preference values remain in your browser until cleared. Outside does not store a custom trip origin or device location.
Consumer and admin account session retention is handled by Clerk when you choose to sign in.
Legal acceptance records remain in Outside product storage until the account records are deleted or the record is replaced by acceptance of newer Terms or Privacy versions.
Account records are kept to provide the features you use until updated, removed, or deleted with your account. Expired Down marks and disabled links stop being usable but may remain in storage until cleanup or account deletion.
Admin upload review source material, poster listing candidates, and audit records are stored in Outside server-side storage. In production, they use PostgreSQL when a database is configured.
Outside is maintained by Paul Kumswa as a personal, noncommercial hobby project. Event corrections, privacy and deletion requests, copyright or takedown requests, security reports, and accessibility feedback can be sent topaul.kumswa@gmail.com.
Outside collects public event facts from reviewed venue, institution, tourism, and organizer calendars. It stores normalized current facts, source attribution, direct event URLs, review decisions, and sync history.
Source, ticketing, maps, transit, rideshare, micromobility, and other provider links take you to services governed by their own privacy practices. Outside does not control data those services collect after you leave.
Clerk processes identity and session data for optional accounts. Northflank hosts the application and PostgreSQL product database. Cloudflare provides domain services and may process requests when its proxy is enabled. Infrastructure providers may process IP addresses, browser information, request URLs, timestamps, and errors to deliver and secure the service, including when you browse without an account. Hosting location headers may be used to choose an approximate city; they are not saved in account records.
Outside does not use advertising pixels or behavioral analytics. Infrastructure logs and backups follow the providers' configured retention settings; account deletion may not immediately remove backup copies.
Gemini may review public event text for audience suitability only when the server-side Google provider is configured. Private admin uploads, account data, and friend data must not be sent through that review path. Outside does not expose Gemini keys to the browser.
Outside is designed for college students, recent graduates, and young professionals, and is not directed to children under 13. Do not use Outside if you are under 13. Explicitly child-only events are excluded from discovery when source evidence identifies that restriction.
Contact Outside to request access to, correction of, or deletion of your account and records, including display names, friend links and claims, friendships, Down marks, sharing choices, and match records, or to appeal a request decision. Use the email associated with the account when possible and identify the relevant records. Outside may request limited verification before acting on account data.
Account deletion is handled manually and includes Outside product records and the Clerk identity. We aim to acknowledge requests within seven days and complete verified requests within 30 days, subject to any applicable legal deadline. We will tell you if more time or limited retention is necessary.
Support email is processed by Gmail. Send only the details needed to handle your request. We keep request correspondence as needed to resolve it and document the outcome.
Browser-only preferences can be removed through browser site-data controls. Event-source corrections and attribution requests should include the Outside URL and authoritative source URL.
Outside uses server-side access checks, scoped scheduler tokens, reviewed source activation, and private server-side storage boundaries. No online service can guarantee absolute security; report suspected issues through the contact channel without sending secrets or unnecessary personal data.
We update this page and its effective date when our practices change. Account users are asked to acknowledge the current version before using personal features. Event browsing remains available without acknowledgement.