Privacy Policy
This policy explains how information is handled while Beerlicity tests real accounts and a simulated rewards experience.
1. Who is responsible
The final legal operator identity, business address, privacy contact and public support contact are not yet published. They will be published before Beerlicity opens real reward or payout services to the public. This page does not invent those details while they remain undecided.
2. What is live now
Beerlicity currently enables pre-launch account creation, email verification, sign-in, sign-out and password recovery. Supabase Auth is used for these account functions. The Beerlicity frontend sends the email address and authentication information needed for those functions to Supabase. Beerlicity does not store plaintext passwords in its demo reward state or demo localStorage.
Netlify hosts the current website. Hosting and authentication providers may process ordinary technical information needed to deliver and secure their services, such as network, browser, request and security data, under their own service arrangements.
3. Information used during account testing
- Account information: email address, optional display name, account identifier, email-verification status and authentication/session information.
- Policy acceptance: when the registration flow records acceptance, Beerlicity stores the account identifier, accepted Terms/Privacy/Rewards policy versions and a server-generated acceptance timestamp. This record is separate from the reward Ledger.
- Browser preferences: local settings such as onboarding choices, notification-read state and demo preferences.
- Demo reward state: simulated Pints, demo offer completions, demo payout history and demo Missing Pints cases may be stored in the browser's local storage. They are not authoritative financial records and are not tied to the real signed-in account.
4. What is not live yet
Beerlicity is not currently operating live offerwall/provider tracking, real Pints, production payout processing or live Missing Pints delivery. Provider names and payout methods shown in Demo Mode are examples used to test the experience and do not by themselves establish a live commercial integration.
5. Why information is used
Current account information is used to create and secure test accounts, verify email addresses, maintain authenticated sessions, support password recovery, record accepted policy versions, debug account flows and protect the service from abuse. Demo browser data is used only to make the simulated reward experience function.
6. Sharing and service providers
Current account testing relies on service providers including Supabase for authentication/database services and Netlify for website hosting. Beerlicity does not currently send demo reward completions or demo support claims to the example offer providers or payout methods shown in the interface.
If live survey, advertising, analytics, identity-verification, communications or payment providers are later enabled, this policy and any required consent controls will be updated before those systems are used for public reward activity.
7. Advertising, sale/sharing and analytics
The current demo does not contain production offerwall tracking or cross-context behavioural-advertising functionality. Beerlicity has not enabled a production advertising/analytics stack for the reward service. If future activity constitutes regulated “sale,” “sharing,” targeted advertising or consent-requiring analytics, the required notices and controls will be implemented before use.
8. Browser storage
Beerlicity uses browser storage for demo state and preferences. Signed-in account testing may also use authentication/session storage managed by Supabase so a session can continue safely between page loads. See the Cookie & Storage Policy for the current inventory.
9. Retention
Account-testing data is retained only as needed to operate, secure and evaluate the account system and to meet applicable obligations. A final production retention schedule has not yet been adopted. Policy-acceptance records may need to be retained as evidence of the version accepted. Demo localStorage remains on the user's device until cleared by the user/browser or removed by Beerlicity code.
10. Security
Beerlicity uses access controls and authenticated service boundaries appropriate to the current testing stage. Supabase Row Level Security is used for protected database data. Authentication credentials, tokens and privileged service-role secrets must not be placed in the public reward Ledger or demo localStorage. No system can guarantee absolute security.
11. Your privacy choices and rights
Depending on where you live, applicable law may provide rights to access, correct or delete information, obtain portability, withdraw consent, object or restrict certain processing, or complain to a regulator. The final public privacy-request contact/method is not yet published. It will be provided before real reward or payout services open to the public.
The current My Data & Account controls are marked as preview/coming later where the corresponding authenticated backend workflow is not yet connected.
12. Children and teens
The final minimum age for public Beerlicity reward participation has not yet been set. Users under 13 are not permitted to create an account. If the final launch rule or a provider requires a higher age, Beerlicity will enforce and disclose that rule before the relevant reward service is enabled.
13. Fraud and automated review
Security signals may help detect suspicious activity, but shared household, IP, workplace, school, hotel or carrier-network use is not by itself proof of fraud. Future materially significant automated decisions will include the review, explanation or appeal protections required by applicable law.
14. Communications
Authentication-related messages such as email verification and password recovery may be sent as part of account testing. Marketing is not required for the test account. Future marketing will be subject to applicable consent and unsubscribe rules.
15. International processing
Service providers may process information in other jurisdictions. Applicable transfer, disclosure and privacy requirements will be addressed as the production service and final operating entity are configured.
16. Changes
The “Last updated” date and policy version will change when material privacy practices change. Where law requires notice or renewed consent, Beerlicity will provide it.