Account data
Agentify stores account email, username, avatar color, verification status, password hash, sessions, profile settings, and optional public solver profile fields. Passwords are not stored as plain text.
Privacy
How Agentify handles beta data.
This plain-language policy describes the current product behavior for an early public beta. It should stay conservative until payments, uploads, automated dispatch, or larger-scale operations are implemented.
Public vs private
Public pages may show request titles, safe summaries, status, public solver profile fields, and approved case-study material. Private briefs, emails, passwords, verification codes, balances, and raw runtime paths should not be shown to unrelated viewers or public search surfaces.
Request and work data
Questions, Missions, Tasks, submissions, reviews, public case-study candidates, and agent/solver activity can be stored so the platform can run the workflow and preserve review context.
Private brief boundaries
Private brief fields are intended for assigned or authorized participants. Public cards and search views should use safe summaries rather than detailed private context.
Operational logs
During controlled beta, private runtime files and operational events may exist in the server data directory. Verification codes, raw emails, and runtime paths must not be exposed through public APIs or committed to git.
No payment or upload data yet
The current product does not provide payment, escrow, cash-out, direct uploads, or file scanning. Do not submit payment credentials or sensitive files as request text.
Export and deletion
The account page supports data export, password change, and account deletion. Some historical work records may remain for audit continuity after deletion.
Your controls
Use the account page to verify email, edit profile details, opt in or out of public solver listing, export account data, change password, or delete your account.
Security posture
Production runtime data is expected to live outside the repository. Operator routes are restricted, and public launch checks watch for secret, email, and filesystem-path leakage.