Trust & security

Security at Selrano

We design Selrano with security appropriate for sensitive academic and personal work. This page summarizes our practices; enterprise customers may request additional documentation.

Infrastructure

Application hosting runs on Vercel. Data, authentication, and file storage use Supabase (PostgreSQL with row-level security). AI inference uses Groq; prompts are not used to train third-party models per provider policy.

Access control

Every workspace route requires authentication. Database policies restrict all tables so users can only access their own rows. API routes validate the session server-side before processing requests.

Encryption

Traffic is encrypted in transit (TLS). Data at rest is encrypted by our cloud providers. Passwords are handled by Supabase Auth (bcrypt); we never store plaintext passwords.

Operational practices

  • Environment secrets stored in Vercel, never committed to source control.
  • Audit logging for sensitive actions (account deletion, support requests).
  • Transactional email via a dedicated provider with domain authentication (SPF/DKIM).
  • Regular dependency updates and production builds on every main-branch deploy.

Report a vulnerability

If you believe you have found a security issue, please email support@selrano.com. Do not disclose publicly until we have had a reasonable time to investigate. We aim to acknowledge reports within 2 business days.

Privacy & compliance

See our Privacy Policy for data collection and your rights. For privacy-specific requests, contact support@selrano.com.

Contact

General support: support@selrano.com. Use our support form for account help.