V0-alpha early access
Clear consent before a run is published
LocalBench should make the data flow obvious before any local runtime is contacted or any benchmark result is submitted. That same plain-language posture now extends to waitlist capture, so the public alpha story stays consistent before broader access opens.
I understand LocalBench connects to the runtime I select on this machine.
I understand benchmark prompts and measurements may be sent to the runtime and then stored if I choose to submit a run.
I understand that if I join the waitlist, my email address will be stored in Postgres only to send alpha notifications.
I understand I can request waitlist removal or correction through the contact page.
I understand public sharing is separate from simply running a benchmark locally.
I understand I can stop before submission if I do not want to upload the result.
I understand this early-access disclosure copy is still subject to later legal review.
EEA / GDPR posture
The same choice should be visible to all visitors
Visitors in the EEA and UK should see the same explicit controls around local runtime access, publication, and opt-in sharing. If a correction or deletion request is needed, the contact page should be the route into that process.
Public pages stay open for review while benchmark routes remain admin-gated during pre-alpha validation.
Related pages