How Krikkit is built and operated. Operated by StoresWiki LLC, Lewes, Delaware, USA.
In transit and at rest
Every connection is HTTPS with a current TLS configuration; plain HTTP is redirected. Provider keys and connected-service credentials are encrypted at rest with an application key held outside the database, so a database dump alone does not yield them.
Accounts
Passwords are stored as bcrypt hashes and cannot be recovered by anyone, us included. Sign-in is rate limited. Two-factor authentication is available and you should enable it — it is the single largest improvement you can make to your own account's security.
Tenancy
Projects, prompts and credentials belong to an account and every read is scoped to the authenticated session rather than to an identifier taken from the request. That is the property that stops one customer reaching another's work by editing a URL.
AI providers
Prompts and the project context required to answer them are sent to the configured provider for generation only. Your work is not contributed to third-party model training. Supplying your own provider key keeps that traffic under your own agreement.
Backups
The database is backed up automatically with encrypted off-site copies. Backups exist to recover from failure, not to resurrect deleted work: an erasure request is applied to the live service immediately, and backups holding the old copy age out on their own schedule.
Reporting a vulnerability
Email [email protected] with enough detail to reproduce. We confirm receipt, keep you posted, and credit you if you want. Test against your own account only, and give us a reasonable window before publishing.
What we do not claim
There is no SOC 2 report and no ISO certificate on this installation, and we are not going to display a badge we have not earned. What is described above is what is actually implemented, and you are welcome to ask how any of it works.