Legal
Privacy Policy
This draft explains the current Scalp Sentry handling for account/session cookies, device-level service state, anonymous review history, and optional analytics controls. It still requires counsel review before production launch.
Draft notice
Implementation placeholder only. Replace this draft with counsel-approved language before production launch.
Information We Collect
Scalp Sentry currently collects the review details you enter, such as product selections, ratings, reactions, notes, tags, and product request submissions.
When you use the app without signing in and choose to save progress, Scalp Sentry creates an anonymous identifier so review history and recommendation progress can persist on the same device.
How We Use Information
The current product experience uses your saved review history to calculate recommendation previews, scalp profile signals, and progress state across the anonymous flow.
Operational analytics and feedback submissions may also be used to monitor product usage, troubleshoot issues, and improve the review and recommendation experience.
Cookies And Local Storage
The current implementation uses three categories of browser storage: essential auth/session cookies, essential service-state storage created after you start a save flow, and optional analytics storage.
- Essential auth/session cookies support admin login, Supabase session handling, and authenticated account continuity.
- Essential service-state storage is created only after you start a review, recommendation, request, or similar save flow, and may include your anonymous account key or in-progress draft state.
- Optional analytics remain off until you explicitly allow them in regions where consent is required, and can be changed later from Cookie Settings in the footer or legal links.
- Signing in may migrate anonymous history into your authenticated account.
- Clearing browser storage can remove device-level access to anonymous progress that has not been linked to an account.
Sharing And Retention
This draft does not yet define final production retention periods, subprocessors, or legal disclosures. Those sections must be completed before launch.
Until then, treat this page as a product placeholder that documents the current implementation shape rather than a final legal commitment.
Your Choices
Today, your controls include choosing what you submit, deciding whether optional analytics are enabled where required, signing in to back up progress across devices, and clearing browser storage if you want to reset local anonymous state.
A final production policy should also describe contact details, deletion handling, and any jurisdiction-specific privacy rights.