Public build log
What is live. What still blocks real payments.
The public beta exercises the complete product flow with real pages and persistent votes. Its $1 checkout is sandboxed and cannot charge a card.
Product mechanism
Pairwise comparisons, equal-exposure scheduler, Wilson scoring and deterministic tie-breaks are specified.
Public beta controls
Page creation, sandbox checkout, reports and voting are independently controlled and are active for end-to-end testing.
Data and API model
D1 schema, prepared statements, unique constraints, rate limits, audit events and content validation are implemented.
Named operator
Legal name, registered address, tax/VAT details and public support/privacy contacts must be supplied.
Italian legal opinion
Counsel must classify the paid placement and competitive visibility under DPR 430/2001 and other applicable rules.
Provider approval
The selected payment provider must approve the exact business model in writing before credentials are connected.
Production controls
Live Turnstile keys, Access/MFA for moderation, provider webhooks, restore drill and final penetration tests remain required before charging money.
Why the legal gate is real
The Italian Ministry describes prize competitions broadly enough to include outcomes based on skill and judgement, not only chance. It also states that participation in a prize competition is free apart from ordinary communication costs. That makes a paid-entry visibility contest something to classify with specialist counsel—not something to rename and quietly launch.
Primary references: MIMIT: concorsi a premio, DPR 430/2001 on Normattiva and MIMIT’s current FAQ. This is risk identification, not a legal opinion.
Security boundary
The browser never decides whether a page was paid, whether a comparison counts or who wins. During the beta, a server-side sandbox order authorises publication without accepting card data. A future hosted checkout and signed idempotent webhook will replace that single step. Pair tokens are server-issued, short-lived and one-use. User content is plain text; destinations are HTTPS-only; no external metadata is fetched.
Privacy boundary
No marketing analytics or profiling cookies are planned. Granular integrity identifiers are retained briefly, result aggregates remain public, and financial records follow mandatory retention. Public beta collection uses a strictly necessary anonymous device session. The controller identity and working contacts remain mandatory before commercial activation.
Four independent kill switches.
Commercial checkout, beta submissions, voting and report intake can each be disabled without taking the public archive offline.
Read the privacy draft