At a glance
Explore without a wallet. Your personal plans and memories stay in this browser; export a backup in Settings. Event correction reports are sent privately to WRST administrators. External event images and aggregate analytics make network requests. Shared member features remain closed.
The current preview
The public website and personal tools can be used without connecting a wallet. Personal profile fields, saved nights, plans, festival set selections, local posts, crew notebooks, and memories are stored in your browser. They are not published by those personal tools.
Local storage and offline files
Submitted personal data uses localStorage. Selected festival sets and saved schedule snapshots are included in your WRST data export; clearing local data removes them. Individual set choices are not sent to promoters or WRST servers. Offline pack refresh requests send public event IDs to retrieve current details; they do not upload private notes or set choices. Saved snapshots include a download time. App files are cached for offline use; account and admin API responses are not stored in that cache. Unsaved drafts use sessionStorage, with an in-memory fallback if storage is unavailable. Community-form drafts also stay in this tab’s session storage, separately from personal drafts, and are scoped to the signed-in account. They are sent only on submission and clear after successful submission, explicit discard, sign-out, or account deletion. Wallet signing and registration fields are excluded. Community drafts are not included in server account exports. Known static pages, fonts, and artwork can be cached for offline loading. Clearing browser storage or losing the device can remove these copies. Save forms before exporting if you want draft content included in the export.
Wallet connection
You may connect an installed compatible wallet to display its shortened public address on this page. Connection alone does not send the address to the WRST API, authenticate an account, verify membership, or authorize a transaction. The wallet extension may apply its own permissions and privacy practices.
Founder/admin sign-in
Wallet sign-in is currently limited to the configured WRST Team administrator wallet. Approved promoter accounts use separate email/password access described below. It sends a public address and a signed one-time message to this site. Challenges expire after five minutes; sessions expire after one hour or can be ended by signing out. Administrator accounts, reviewed event corrections, and correction audit history are stored on the server. Approved correction content and artwork may appear publicly on event listings. Public member sign-in and shared community activity remain closed.
When the shared service is enabled
Wallet sign-in sends the public wallet address and a signed, short-lived challenge to the same-origin server. The server verifies wallet control and stores revocable session digests. It does not receive a seed phrase or private key. A functional HttpOnly session cookie keeps you signed in. Shared profile fields, posts, replies, likes, crew memberships, invitations, messages, attendance, blocks, and reports are stored by that service.
Visibility and community controls
Profiles and cities are private by default. Shared posts are visible to eligible members. Crew messages are visible to permitted crew members, subject to blocking and moderation. Attendance is private by default. Public numbered profiles require an explicit visibility choice. Blocking changes member interactions; it does not make an already-public profile secret from anonymous visitors.
Your controls
Personal data can be exported, restored, or reset in local Settings. Signed-in server accounts have separate export, visibility, sign-out, blocking, and deletion controls. Server account deletion also deletes crews the account owns. Removing attendance and your own shared content remains possible after membership eligibility changes.
Event correction reports
You can report an incorrect event without signing in. We store the event snapshot, issue category, your explanation, optional evidence link, and administrator review history. Reports are private to administrators and do not automatically change listings. Keyed IP hashes and request identifiers help limit abuse and duplicate submissions; raw IP addresses are not stored in the event-report table. Do not submit wallet secrets or unnecessary personal information. Contact support@wrst.club for privacy requests.
Promoter pilot
Promoter applications store organizer name, email, official website, city, description, private role-verification evidence and review decisions on the server. Administrators review this information; approval makes the organizer name, website, city, description and assigned event listings public. Contact email and verification evidence remain private. Promoter sign-in uses a separately salted scrypt password hash and an HttpOnly, same-site session cookie expiring after eight hours. One-time activation links expire after 48 hours. Issuing a replacement link revokes existing promoter sessions and earlier invites. Sessions and invites are stored as digests. Event proposals, correction requests and review notes are stored on the server and visible to the submitting organizer and administrators. Promoters do not receive visitors’ private plans, crew notes or memories. Promoter-specific analytics and billing are not active. Promoters can export their own profile, application, assignments and requests from Promoter Desk. Profile updates and event ownership claims enter review; only an explicit verified administrator decision publishes a profile change or assigns an event. Pending requests can be withdrawn before review. Event form drafts and retry identifiers are saved in this tab’s sessionStorage, scoped to the promoter account; passwords and activation tokens are excluded, and signing out clears that account’s promoter drafts. Closing the tab can remove these drafts. Promoters can sign out all devices. Contact support@wrst.club for manually reviewed account recovery, contact-email changes or deletion. Application and review records remain until a deletion request is processed or WRST removes them; no fixed automatic retention period is currently applied. Deletion from encrypted backups follows backup expiration, and stored security/audit evidence may need separate review.
Network and hosting information
Fonts and WRST graphics are served from this site. Matched event images can load from Ticketmaster, TicketWeb, Eventbrite and Resident Advisor image servers, which receive normal network information such as your IP address; image requests omit the page referrer. Clicking a ticket seller or event-source link opens that provider and its privacy practices apply. WRST uses Cloudflare Web Analytics to measure aggregate visits, page views and page performance. The Cloudflare script receives page and browser/performance information and normal network information to process those measurements. WRST does not intentionally send wallet addresses, account identities, private notes, plans or message contents as analytics fields. This analytics service is not used for advertising. Browser blockers or network failures can prevent measurement; visitor totals are estimates. See Cloudflare’s analytics collection details. Hosting infrastructure may process request metadata to deliver pages. The API uses keyed hashes for rate-limit buckets and short-lived authentication challenges. Live operators must finalize retention, backup, and deletion procedures before enabling the service.
Shared write recovery and exports
When the shared service is enabled, creation requests may store a per-account request identifier and content fingerprint to prevent duplicate posts, replies, crews, or messages after a retry. These records are removed with active account deletion. Server exports include your submitted content and applicable likes, blocks, reports, invitations, and write-receipt identifiers; they do not include session credentials or another author’s reports.
Operator and contact
WRST Team — public operator name.
support@wrst.club
Before live launch
This notice describes the current early-access service and founder/admin access approved by WRST Team. Shared member access remains closed. For privacy requests, contact support@wrst.club; for security reports, use security@wrst.club. The remaining community launch requirements must be completed before broader activation.
Google AdSense
WRST loads Google AdSense on public pages for publisher verification and advertising setup. Google receives normal network information, including your IP address and browser information, when its script loads. Advertising services may use cookies or local storage. Personal planning notes and account credentials are not intentionally sent as advertising fields. See Google advertising privacy information.