Privacy
Your waitlist information.
The waitlist is for pilot invitations and Prontera release updates. It asks for an email address, with an optional name and a short description of how you would use Prontera.
Implementation notice updated 14 September 2026.
What this notice covers
This notice describes the website and its waitlist implementation. It does not describe a running Prontera Cloud application. Joining the waitlist creates no Cloud account, paid plan, or access to customer infrastructure.
Ramon Oliveira is building Prontera and handles project and waitlist requests. Contact: prontera@ramonoliveira.xyz.
Information in the waitlist
The application stores:
- Your email address and any optional name or use-case answer you submit.
- A random request identifier, the first request time, and the date the record expires.
- Temporary rate-limit counters under keyed hashes of network addresses and email addresses. Raw IP addresses are used while processing the request and are not stored in the application database.
Optional answers help us understand possible pilot use cases. They are not required to join. Please keep credentials, source code, and sensitive customer information out of this short answer.
Purpose and signup
Submitting the form requests pilot invitations and Prontera release updates. The server saves the request directly. Submission does not send an email or verify that you control the address.
A repeated signup returns the same response and does not replace existing optional details or extend an existing record’s retention period.
Hosting and storage services
The website implementation uses Cloudflare Workers Static Assets for the public pages, a Worker for waitlist requests, and Cloudflare D1 for waitlist records. Cloudflare receives network request information as the hosting provider. The application does not write form bodies or addresses into generic request logs. Collecting a waitlist request does not send its details to an email delivery service.
Cloudflare’s processing follows the provider account’s settings and policies. Application deletion does not automatically erase provider recovery history.
Application retention
Waitlist records and abuse counters have expiration deadlines. A scheduled daily cleanup removes expired records from the active database. A failed or delayed cleanup job can delay that physical removal.
- Waitlist request
- Expires 24 calendar months after the first request. It may be removed earlier following a verified removal request.
- Abuse-control counters
- Expire at the next UTC midnight and are scheduled for deletion at that boundary. Delayed cleanup can extend their physical retention.
Provider recovery history
The configured Cloudflare plan retains D1 recovery history for 7 days.
Cloudflare D1 keeps recoverable database history for 7 days on its Free plan or 30 days on its Paid plan. This history is always enabled. Deleting a live row does not immediately erase it from past database history; those recovery copies age out under Cloudflare’s lifecycle. Read Cloudflare’s Time Travel documentation.
Request removal or changes
To leave the waitlist or request access, correction, or deletion, email prontera@ramonoliveira.xyz from the address involved. Requests are handled manually. We’ll verify that you control the address before changing its details or removing the record. Sending an email does not itself delete the record.
Removal from the active waitlist is separate from the provider recovery history described above.
Analytics and cookies
This implementation includes no analytics tracker, advertising pixel, tracking cookie, account creation, or payment collection. Fonts and interface assets are served with the website. Waitlist addresses are not sent to analytics.
This notice will be updated if the website’s collection or processing changes. The security page describes the project’s development stage and reporting contact.