Public auth is separate from member access
Google and email/password can create a public account session. Member and admin features still require a server-side portal role.
Privacy
The portal stays minimal.
Last updated May 26, 2026. Public account authentication is available without turning on tracking, payments, uploads, private messages, or member access by default.
Minimal product data
The portal keeps display preferences narrow and does not add analytics, payments, uploads, private messages, or live assistant behavior.
No secrets in git
Provider values, tokens, project identifiers, private account records, raw logs, screenshots, and private contact values stay outside the repository.
Manual account requests
Support, data export, and deletion requests are handled manually through the published account support contact.
Role-gated member data
Member-only surfaces check server-side role visibility before showing preferences or admin summaries.
Provider-owned authentication
Password reset, confirmation, OAuth, session policy, SMTP, and rate limits remain controlled in the auth provider and deployment settings.
Requests
For account support, data export, or deletion, use the official support contact and avoid sending passwords, tokens, provider links, payment details, health details, or private identifiers.