This is an independent site, not a Meta service. It does not ask visitors to create an account. Public code submissions contain the code and an optional self-reported remaining amount; they do not require a name, email address, or social account.
Information used to run the site
- Necessary anonymous browser identifier. A first-party, secure, HTTP-only, SameSite cookie can distinguish a browser environment for abuse prevention and feedback deduping. It is not proof of a person’s identity and is designed to expire after 90 days. The application stores a keyed digest rather than the cookie value.
- Security and rate-limit signals. The application may derive keyed HMAC summaries from a trusted network address, browser identifier, and limited user-agent information. Raw IP addresses are not stored in the application business database. Hosting and security providers may keep their own operational logs according to their settings.
- Code and feedback records. The site stores public codes, their moderation and display status, copy events, and visitors’ current “Worked” or “Didn’t work” feedback. Feedback is a report, not an official redemption record. A report form may use Cloudflare Turnstile to reduce automated abuse.
- Local preferences. A visitor’s choice of audience path can be remembered on the device for up to 30 days. A recent copied-code reminder stores a public code ID and time for up to 24 hours, and is cleared after feedback or dismissal.
Retention periods
- Business events and IP/user-agent abuse-prevention summaries: 30 days.
- A feedback subject digest and the current feedback: while the code remains in the system, then up to 90 days after permanent retirement. Feedback-linked IP/user-agent summaries are removed after 30 days.
- Administrator audit records: 180 days.
- Detailed reports: 90 days after the report has been handled.
- Unpublished submissions left unresolved: up to 90 days, after which they are designed to be deleted.
- Aggregated counts that no longer identify a browser or person may be kept for long-term operations.
Hosting and security providers may keep their own operational logs according to their settings.
Analytics and consent
When Google Analytics 4 (GA4) is configured, it is limited to public pages. It is not loaded on private management or administrator pages. Before any GA4 configuration or event, advanced Consent Mode sets analytics_storage, ad_storage,ad_user_data, and ad_personalization to denied. Accepting analytics changes only analytics_storage; advertising-related states remain denied.
Visitors in the EEA, United Kingdom, or Switzerland are shown a small choice banner. In other recognized regions, analytics defaults to allowed unless a visitor has saved a rejection. If the region cannot be determined, consent remains denied. An explicit rejection is retained for 180 days and takes precedence over a regional default.
With analytics storage denied, Consent Mode may still send limited cookieless signals. Rejecting analytics therefore does not mean that no signal is sent. Google’s modeled reporting is not a record of individual visitors and is not guaranteed to fill in missing data.
Public-page analytics measures visits and basic actions such as a successful clipboard copy, a submitted feedback result, a code submission result, or a click to Muse. Invite-code text, management links or tokens, visitor digests, raw IP/UA summaries, report text, and contact details are not sent as analytics event data.
Service providers and external links
The site may rely on Cloudflare for hosting and abuse protection, Neon for its application database, and Google for public-page analytics. Their processing is governed by their own policies and the site’s production configuration. Following an external Muse or third-party link takes you to a separate service.
Contact
For a privacy question, write to support@museinvitehub.org. This is the public support address; the private administrator address is not published here.