Privacy for product testing.
Public discovery stays open. Proof screenshots and tester emails stay scoped.
Short version
BetaLoop separates public launch data from private tester proof and email consent.
Product pages, screenshots, tester counts, and average ratings are public for active launches.
Feedback proof screenshots are not public; they are for the tester and product owner.
Email contact with a creator is opt-in per feedback submission and can be disabled globally.
Public
Private
Account controls
Signed-in users can control public profile fields, contribution logs, LinkedIn link visibility, and creator-contact preference.
Screenshot scope
Creator app screenshots can be public. Tester proof screenshots are stored separately and scoped to the tester plus product owner.
Opt-in contact
Creators see email contact only when a tester explicitly asks for product updates and keeps creator contact allowed.
Supabase security
Database rows and storage objects are guarded with Supabase Auth, row-level security, and bucket-specific upload policies.
What BetaLoop stores
Data is tied to the core testing workflow rather than broad identity verification.
Account data
Email, optional profile fields, LinkedIn status, credits, and reputation counters.
Launch data
Project copy, testing links, screenshots, category, target testers, and launch status.
Feedback data
Ratings, comments, opt-in consent, task status, and proof screenshots.
Operational data
Timestamps, storage paths, and aggregate dashboard/public stats.
How privacy decisions are applied
The controls map to concrete product behavior, not just static policy copy.
Browse without login
Visitors can view active products, screenshots, tester counts, and average ratings without creating an account.
Login before feedback
Submitting feedback requires authentication, one feedback per app, category ratings, and proof upload.
Private proof by default
Feedback proof images use the private feedback-proof bucket and signed URLs for allowed viewers.
Public profile choice
Users can hide role, company, LinkedIn link, development log, and testing log from their public page.
No automatic campaigns
Opt-in is stored for owner visibility; BetaLoop does not send marketing email campaigns in this pass.
No service key in client
Privileged Supabase access stays server-side and is never exposed through NEXT_PUBLIC variables.
Best-practice basis
Product guidance, not legal advice: collect only what the testing workflow needs, protect proof, and make sharing explicit.