Security and trust
What we check before you receive a release, where your data lives, and who can see it.
How every release is checked
Before you receive a release, we check the finished product and its test results against our security and quality requirements.
A release that misses a required standard is sent back to be fixed before you receive it.
We also go through a checklist of what every product like yours has to get right, screen by screen, including keyboard use, phone screens, error messages and security basics. A release that fails an important item on it is sent back too.
| Area | Standard | A sample booking tool (example) |
|---|---|---|
| How the code is organised | C (Acceptable) | B |
| Automatic checks that it works | B (Good) | B |
| Keeping your data correct and safe | A (Excellent) | A |
| Protection against misuse | A (Excellent) | A |
| Other people's code it relies on | C (Acceptable) | B |
| Connections to other services | C (Acceptable) | C |
| How safely it can be changed later | C (Acceptable) | B |
| Speed | C (Acceptable) | B |
| Running it and noticing problems | C (Acceptable) | B |
This card is an invented example to show the shape of a security report. It is not any customer's product.
Where your data lives
Your account, conversations, proposals, builds, and releases are kept in Quokka's database under your organisation. Card details are handled by Stripe.
If you choose Quokka hosting, your product and its data run separately from Quokka's main service, with protected access and encrypted secrets.
Who can see a project
People in your organisation can see its projects. People outside your organisation cannot. Your project information is not shown to another customer.
Nothing about your project is public unless you publish the product you asked us to build.
Your information and privacy
We may use records with personal details removed to improve Quokka. You can turn this off in your account settings, and your projects keep working the same way.
The full wording is in the privacy policy.
What you own
You own the code we build for you, your data, and your designs. General components may be used across products, but your business information and work created specifically for you remain yours.
We do not include your business names, customer data, or private business rules in general components used elsewhere. Your proposal describes what is included in your product.
Report a security problem
Open your project, choose Support, and say it is a security problem. Most questions are answered right away, and anything that needs a person goes to one.
What we keep is described in the privacy policy and the terms of service.
Still have a question?
The conversation is free, and you can ask the project lead how your product and data would be handled.