No source code access.
BuniOD tests your application through the browser. It does not connect to your repository and does not modify your source code.
What BuniOD can access, what it stores, and what to keep in mind before you run scenarios against your application.
BuniOD tests your application through the browser. It does not connect to your repository and does not modify your source code.
Browser scenarios interact with the connected application as a user and may create or update test data. Use dedicated test accounts and non-production environments where possible.
HTTP basic-auth credentials for your application are encrypted at rest with AES-256-GCM. Account passwords are stored as bcrypt hashes.
Customer data is logically isolated: each project is visible only to its owner and the members they invite.
The details behind the points above.
The BuniOD app is served over HTTPS.
Your prompts, expected results and the structure of tested pages are processed by Google (Gemini) and OpenAI models to generate and run scenarios.
Test identity details, such as test inbox addresses and custom fields, are stored as you provide them. Don’t put real customer data in them.
Console and network logs are stored with each run, with sensitive values redacted where they are detected.
A deleted account can be restored for 30 days. After that it is permanently removed together with its projects and files.
BuniOD does not currently hold SOC 2 or ISO 27001 certification. Contact us if you need details for a security review.
Create a free account, add your application and describe the first flow you want to verify.
Start free