KNEXEN

Security

Last updated: August 16, 2026

We take the security of your account and data seriously. Here’s an overview of how KNEXEN is built and how to report a concern.

Infrastructure

KNEXEN runs on Vercel with Supabase for authentication, database and file storage. All traffic between your browser and KNEXEN is encrypted in transit (HTTPS/TLS). Passwords are never stored in plain text; authentication is handled by Supabase Auth, and we never see or store your raw password.

Access control

Every request to view or change data is checked on the server, not just in the browser. Our database uses row-level security policies so that, for example, private profile fields, connection requests, and moderation actions are only readable by the people authorized to see them.

Abuse prevention

Sensitive actions (signup, login, connection requests, posts, comments, and reports) are rate-limited to reduce spam and abuse. Members can report and block other users, and reported content is reviewed through our moderation process.

Reporting a vulnerability

If you believe you’ve found a security vulnerability in KNEXEN, please report it via feedback rather than filing a public issue. Include as much detail as you can (steps to reproduce, affected URL) so we can investigate quickly. We ask that you give us a reasonable opportunity to fix the issue before disclosing it publicly.