FRENZY
Local beta · updated 10 October 2026
Privacy notice
This notice describes the data used by the Frenzy local beta. The person or organization running this installation controls its campaign data. A campaign offer must identify its owner and publish a contact route before participants are invited.
Information recorded
- Requests: an email, beta or quote request, selected plan, billing preference, optional referral reference, and request identifier. A saved request does not create a subscription or send an email.
- Account and participation: verified account identity, campaign display name, campaign membership, referral code, attribution, leaderboard preference, and join time.
- Campaign and rewards: qualifying action references, reward amounts and states, review reasons, appeals, and provider-confirmed payment references when an integration is used.
- Optional profile evidence: a submitted public profile handle, relevant public profile facts and posts, consent choices, evidence timestamps, and assessment results when you explicitly enable supported assessment services.
- Service records: sessions, security checks, provider webhook receipts, and subscription metadata required by configured integrations. Browser pages do not receive upstream service credentials.
Why the data is used
The installation uses these records to keep account access private, attribute a referral, check qualifying actions, explain a reward, resolve an appeal, and prevent duplicate credit. Optional audience assessments help review campaign fit. Joining a campaign does not by itself consent to an AI profile assessment.
A forecast is an estimate of campaign outcomes. An influence score is an assessment index, not a fact about your worth. A prediction alone does not confirm a qualifying action or a payment.
Who can see information
Campaign owners and authorized reviewers can see their campaign participants and reward records. Participants see their own memberships, direct referrals, and rewards. The public leaderboard shows only the display names and counts of participants who opt in.
If optional services are configured, the relevant provider receives the inputs needed for that requested service. Public profile retrieval uses the profile network; audience assessments use the configured AI provider; subscription checkout and payouts use the configured payment service. Provider availability and consent are shown before a request. Provider policies apply to data received by those providers.
Your choices
You can change your campaign display name and leaderboard preference in Your links. Profile retrieval and AI assessment require the choices shown on Profile consent. Removing profile evidence stops that saved connection from being used by future requests; previously recorded campaign outcomes, review records, and provider-held data are separate records.
The beta has no automatic account export, account deletion, or provider deletion workflow. Ask the installation operator about access, correction, removal, and any records that must remain to resolve a reward. Do not assume that signing out deletes an account or that an assessment withdrawal erases a provider's records.
Storage, retention, and browser preferences
Campaign data is stored by the installation until the operator removes it. No automatic campaign retention deadline or scheduled deletion is implemented. The operator must establish its retention criteria and backup handling before collecting real participant data.
Account sessions use an application cookie. The theme setting is stored in your browser so your light or dark preference survives navigation. The site also requests its display fonts from Google Fonts; those requests go to Google's servers. No advertising tracker is deliberately added by the application.
Contact and complaints
For this local installation, contact the person who gave you access. For a campaign, use the contact route published in its offer. The operator must replace this local notice with its identity, privacy contact, relevant rights and complaint routes, transfer information, and retention terms before a public beta.
The ICO's privacy-information guidance is one reference for an operator preparing those details; this page does not determine which jurisdiction applies.