Your site.
Your permission.
Use StackSnack only on a website you own or have explicit permission from its owner to test. A public URL, exposed key, or discoverable database is not permission.
Confirm authorization before each scan
By starting, verifying, or repeating a scan, you confirm that you have that permission and that the requested checks are within its scope. Follow the website owner’s conditions and your hosting provider’s testing rules. The checkbox records your confirmation; it does not independently prove ownership.
Keep the scope clear
Surface scans inspect public web files and security headers. Website verification enables deeper file checks. Database, authentication, and storage probes require separate backend approval. Supabase offers self-service verification through an owner-created function; Firebase requires independent project approval. A verification tag on a website does not establish control of every connected service.
No disruption or abuse
Do not use StackSnack to test unrelated sites, collect other people’s information, bypass access controls, or overwhelm a service. Do not evade request limits or submit repeated scans to create load. Database reads still consume resources and can trigger logs, alerts, or incidental application behavior. Optional cross-user checks sign your disposable test accounts in and out; no target records are created, changed or deleted. Stop if the owner withdraws permission.
Reports stay private to the creating browser
A report URL alone does not grant access. Keep the creating browser’s cookies to retain access; clearing them or changing browsers means you need a new authorized scan. Reports may contain sensitive security information, so take care with screenshots and copied findings.
A useful check has limits
Results cover only the checks that completed. Skipped or failed checks reduce coverage. A clean report is not a guarantee of security, a certification, or a substitute for a broader assessment. Review evidence and confirm changes before deploying fixes.
Questions or a security concern?
Email support@stacksnack.io or use the feedback form. Keep credentials, private report links, and sensitive evidence out of public posts.