A plain-language breakdown of how login works, what's stored today, and exactly what access GigStackSocial would need from each platform to go fully live.
You create an account with an email + password. The password is one-way hashed and a signed session cookie keeps you logged in. This is a functional demo-grade implementation — before handling real customer accounts at scale, it should be swapped for an audited auth provider with rate limiting, breach monitoring, and 2FA support.
GigStackSocial runs on a real Neon Postgres database — your data persists across sessions and server restarts.
users — email + hashed passwordbrands — brand names and venue labels you createaccounts — connected-account placeholders (demo status; no real OAuth tokens exist yet)posts — captions, chosen images, selected platforms, and schedule timesNothing in this build posts to real social accounts yet. Going live requires the platform approvals above, production hosting, and a security review.