🧬 Session Management

Wallet-Bound Privacy & Security

Every AppDuck session is cryptographically bound to a wallet signature, ensuring secure, private workspaces with clear ownership.

Session Architecture

Wallet Authentication

• Session initialization requires wallet signature

• Private key remains client-side

• Session tokens derived from public key

• Multi-session support per wallet

Data Privacy

• All generated content is private by default

• No centralized storage of user data

• Local processing with encrypted state

• User controls all export and sharing

Session Persistence

• Work can be paused and resumed across browser sessions

• Context maintained for up to 30 days

• Automatic cleanup after expiration

• Manual session termination available

Session Metadata

Each session tracks essential information without storing sensitive content:

{
  "session_id": "0x742d35cc...",
  "wallet_address": "0x1234...abcd",
  "timestamp_created": 1719936000,
  "timestamp_last_active": 1719950400,
  "agent_call_path": ["clara", "vince", "mira"],
  "export_schema_version": "1.2.0",
  "status": "active",
  "outputs_generated": {
    "validation": true,
    "naming": true,
    "business_model": false,
    "product_definition": false,
    "interface_design": false,
    "export_package": false
  }
}

No Custodial Access:

• AppDuck operators cannot access session content

• Encrypted local storage only

• User controls all data export and deletion

• Open source verification of privacy claims

Session Actions

Export Options:

• Download Package: Complete file bundle

• GitHub Repository: Automated repo creation

• Individual Components: Select specific outputs

• Mint NFT: Blockchain ownership record (optional)

Session Management:

• Pause/Resume: Save progress for later

• Fork Session: Create variations from checkpoint

• Share Preview: Generate public preview links

• Delete Session: Complete data removal