FrankensteinProtocol™

Privacy

Data handling for the public access queue.

This page explains the current public website data flow for Frankenstein Protocol™ while the software remains under construction.

01

Waitlist Data

The access queue collects the email address submitted through the form, the source or host associated with the request, the request timestamp, and technical metadata where applicable for verification, abuse prevention, and operational review.

02

No Wallet Credentials

The public website is not designed to collect private keys, seed phrases, wallet signatures, wallet approvals, or custodial wallet credentials. Do not submit those materials through any website form or email.

03

Turnstile Verification

Cloudflare Turnstile may be used to verify that a request appears legitimate before the waitlist form is accepted. Verification data is handled by Cloudflare according to its own service terms and policies.

04

Email Delivery

Resend may be used to deliver confirmation or operational email related to the access queue. Email delivery metadata may be processed as part of that service.

05

Cloudflare D1 Storage

Waitlist submissions may be stored in Cloudflare D1 so duplicate protection, request status, and access queue review can work consistently.

06

No Sale Of Personal Data

Frankenstein Protocol™ does not sell personal data collected through the public waitlist. Data is used for access queue operation, verification, abuse prevention, and direct project communications.

07

Under Construction

The software and public privacy documentation are still being refined. This page describes the current public website data flow and will evolve as the project surface changes.