Lorepage — Access Terminal
--:--:--
LOCAL
// LOREPAGE — ACCESS TERMINAL
USER IDENTIFICATION
AUTHENTICATE TO ENABLE CROSS-DEVICE SYNC  |  LOCAL MODE AVAILABLE WITHOUT ACCOUNT
// SESSION : ACTIVE
USER IDENTIFIED
// JUMP TO WIDGET
// SESSION CONTROL
// Use "Clear Local Data" on shared or public devices to leave no trace.
// RETURNING USER
LOGIN
// AUTHENTICATE WITH EXISTING IDENTIFIER
! CAPS LOCK ACTIVE
// Session persists until manually terminated. No re-authentication required across devices.
// RECOVERY PROTOCOL
RESET KEY
// REQUEST A RECOVERY LINK BY EMAIL
// Check your inbox. The link expires after 60 minutes. If it does not arrive within a few minutes, check spam.
// NEW USER
REGISTER
// CREATE A NEW IDENTIFIER TO ENABLE SYNC
! CAPS LOCK ACTIVE
—
// Account creation activates cloud sync. All data remains private and inaccessible to anyone else.
DATA POSITION
// DATA POSITION : ACTIVE
ON DATA HANDLING

This platform handles data the way I would want my own handled. Not because a policy requires it. Because I use this system myself. The rules I built are the rules I live under. There is no separate standard.

The login option requires data to be stored. That is the technical reality of cross-device sync. But stored does not mean accessible. I do not see it. I do not interact with it. It exists in the database the same way a key exists in a lock nobody is turning.

This page exists instead of a cookie banner.

OPTIONS
// OPTION 01
LOCAL ONLY
No account. No server. Everything you log stays in your browser and nowhere else. Clear your browser or switch devices and the data does not follow. What you have is yours — completely, literally. Export it as JSON or PDF at any time. Nothing leaves your machine unless you take it.
NO ACCOUNT REQUIRED JSON EXPORT PDF EXPORT BROWSER ONLY
// LOREPAGE — ACCESS TERMINAL — V1