Secure Sign-In
Authentication and session management are handled through Clerk. Only approved users can access private areas of ClayHQ.
ClayHQ is built to protect club, association, and competitor information with secure access controls, trusted infrastructure, and privacy-conscious data handling.
Authentication and session management are handled through Clerk. Only approved users can access private areas of ClayHQ.
ClayHQ applies role-based access controls for system admins, association admins, club admins, and competitors. People only see the areas and information relevant to their role.
ClayHQ is delivered over encrypted HTTPS/TLS connections. Information is protected while travelling between your device and ClayHQ.
ClayHQ is built using established cloud providers including Vercel, Supabase, Clerk, Stripe, and Resend, rather than running on unmanaged local infrastructure.
Payments are processed through Stripe. ClayHQ does not store full card numbers or card security codes on its own servers.
ClayHQ uses data required to operate memberships, registrations, events, results, and communications. We do not sell competitor, club, or association information.
Access controls are designed so one club cannot access another club's private admin data without explicit authorization.
Security is ongoing. We continuously review access patterns, dependency updates, operational logs, and security issues, and apply improvements over time.
If you discover a potential security issue, please contact support@clayhq.app so we can investigate promptly.
Contact our team at support@clayhq.app and we will respond as quickly as possible.