Built so you can preview any Fishbowl report with confidence — without exposing your live system. Last updated: June 20, 2026.
Every report you build runs against an isolated, disposable demo sandbox seeded with Fishbowl-compatible data. The platform does not connect to, read from, or write to your production Fishbowl database.
You build and validate here, then install the resulting SQL, Jasper, BI Script, or CloudPage on your own system or environment.
Report runs are sandboxed in ephemeral, disposable environments that are torn down when the run finishes.
Reports run against a fixed demo dataset — the same for everyone, containing none of your business data.
We limit lateral access between users, so one session cannot reach another’s.
All data is encrypted in transit using TLS. Stored data is held with appropriate access controls, and we apply the principle of data minimization — collecting only what we need to run the Services.
Sign-in is handled by Microsoft Entra and its multi-identity integrations — email one-time codes and Google today, with more providers soon.
Payments are processed by Stripe. We do not store full card numbers on our systems.
We run only on models that do not train on your data. We primarily use Anthropic and Google models (accessed via OpenRouter), and we evaluate any provider that meets that no-training bar before adding it.
We do use your reports and assistant sessions internally to operate, debug, and improve the Service — see the Privacy Policy for exactly how.
You can request deletion of your account and reports at any time; we delete or de-identify your data except records we must keep to comply with law (such as billing records). See Privacy for details and our subprocessor list.
We welcome reports from security researchers and provide safe harbor for good-faith testing. If you discover a vulnerability, email [email protected] with a description, clear steps to reproduce, any proof-of-concept, and an impact assessment.
We aim to acknowledge reports within one business day, work with you to validate and resolve the issue, and give credit where desired.
Keep your sign-in provider account secure (strong password, two-factor authentication), don’t share access to your authenticated sessions, and report suspicious activity promptly.
We follow industry-standard security practices. We do not currently hold formal certifications (such as SOC 2); we will update this page as our compliance posture evolves.