Security and Access Boundaries

Passwords are handled by the authentication service and are never stored here in plain text. Authentication cookies are refreshed on the server, and admin access is checked against a separate membership table.

The browser uses only the publishable key. Favorites and submissions are isolated by user ID, administrative writes are protected by RLS policies, and the service-role key is never shipped to clients.

Payments are completed in Stripe Hosted Checkout. Amount, currency, Price, and quantity are fixed on the server. A success redirect cannot mark an order paid; only a signed webhook may fulfill it after checking the amount, environment, and order. Before entering Stripe, the user must actively accept the no-refund terms; the terms version and acceptance time are stored with the order audit record.

Official tool websites are third-party services. After leaving the directory, verify the domain, HTTPS connection, and payment details. Never enter credentials on a page you do not trust.

Report broken links, impersonation, or security issues through the contact page with the affected URL, reproduction steps, and necessary screenshots. Never include real passwords or keys.