Skip to content

Operational Security

Security & Data Handling

Edgineer is built with SIM-first constraints and minimal data collection. Waitlist data is stored in Cloudflare KV, admin actions require an admin-only token, and bot protection is handled with Turnstile.

No broker keys, no auto-trading access, and constrained data flows with explicit admin controls.

What to expect

  • Waitlist records stored in Cloudflare KV.
  • Admin export and delete actions protected by an admin-only token.
  • Bot protection via Turnstile when enabled.
  • Replay-first educational workflows without broker integration.

Current boundaries

  • No broker API key collection.
  • No live trade execution pipeline.
  • No open admin endpoints without token verification.

Data Flow Overview

Simple, constrained storage architecture for launch operations.

  1. 01User submits waitlist form.
  2. 02Pages Function validates and rate-limits request.
  3. 03Record is written to KV with attribution fields.
  4. 04Authorized admin reads exports via token header.
  5. 05Deletion endpoint removes records on request.

To request data deletion, contact privacy@edgineer.io from the same email used for waitlist signup.