Information used by Aevlo
Aevlo uses your public wallet address, an offchain signature and a signed session cookie to provide your dashboard · it does not ask for recovery phrases or private keys
Joining records your wallet, acceptance of the current terms and the registration time · claims record allocated amounts, request status and completed transfer signatures
Network and storage
Public token balances and finalized transactions are read through the configured Solana RPC service · historical eligibility comes from the operator’s published round snapshot
Private registration and claim records are stored in the configured Supabase database and accessed through server-verified wallet sessions · the service key is never sent to the browser
Session cookies expire after eight hours and are HttpOnly, Secure in production and SameSite Strict
Public records and your controls
Round funding, aggregate amounts, snapshot fingerprints and completed transfer signatures can appear in the public ledger · blockchain transaction details and wallet addresses remain public on the network
You can disconnect your wallet and cancel a pending request before processing · disconnecting clears this browser’s session and does not erase the public blockchain or required accounting records
The initial service does not collect identity documents, private datasets, contact lists or payment-card information