Krikkit is operated by StoresWiki LLC, Lewes, Delaware, USA. This policy explains what we collect when you generate and publish sites with Krikkit, why we hold it, and how you get it out or removed.
What we collect
- Account data — your name, email address, password hash, and the sign-in and security events on the account.
- Project data — the prompts you write, the pages, copy, layout and assets generated from them, and your edit history.
- Billing data — plan, subscription state, credit balance and invoices. Card details go directly to our payment processor; we never see or store a full card number.
- Connected services — where you link a datastore or deployment target, the credentials needed to reach it, held encrypted.
- Technical data — IP address, user agent, request timestamps and error traces, used for security, abuse prevention and diagnostics.
What we do with it
- Generate, store, preview and export your sites, and keep your revision history usable.
- Meter credits, enforce plan limits and bill the account.
- Keep the platform secure and investigate faults and abuse.
- Send transactional email: verification, password reset, billing and security notices. We do not add you to a marketing list without asking.
We do not sell your data. We do not publish your projects anywhere you did not ask us to.
AI generation
Generating a site means sending your prompt, and the project context needed to answer it, to the AI provider configured for the platform. That is the only purpose it is used for. Your prompts and generated projects are not contributed to third-party model training. Where you supply your own provider key, that traffic runs under your own agreement with that provider instead.
Third parties we necessarily involve
- The AI provider configured for generation, as described above.
- Our payment processor, which handles the payment and holds the card data.
- Our email relay, which delivers transactional mail.
- Our hosting provider, which holds the encrypted database and backups.
- Any service you connect yourself — a datastore, a repository, a deployment target. You choose those and their own terms apply to what you send them.
How long we keep it
Projects and account data stay until you delete them or close the account. Deletion from the live service is immediate. Encrypted backups age out on their own schedule and are never selectively restored to reinstate erased data. Invoices are kept for as long as accounting law requires.
Your rights
You can ask for access, correction, export, restriction, objection or erasure. There is no charge and no form to chase: write to [email protected] or open a support ticket. We acknowledge verified requests within 5 business days and complete them within 30 days. If you are in the EU or UK and unhappy with the outcome, you may complain to your supervisory authority.
Security
Everything is served over HTTPS. Passwords are bcrypt hashes, unrecoverable by anyone including us. Connected-service credentials and provider keys are encrypted at rest with a key that is not in the database, so a database dump alone does not expose them. Two-factor authentication is available on your account and we recommend turning it on.
Cookies
A session cookie keeps you signed in, a CSRF token cookie prevents request forgery, and a preference value remembers your theme. That is all. No advertising cookies, no third-party tracking pixels. Blocking the session cookie prevents sign-in, because the sign-in mechanism is the cookie.
Children
Krikkit is not directed at children and we do not knowingly collect data from anyone under 16.
International transfers
Our infrastructure is in the European Union. Where a processor above is outside your region, the transfer relies on that processor's safeguards, such as standard contractual clauses.
Changes
Material changes are announced in the application before they take effect. The date shown with this policy is always the current version.
Contact
StoresWiki LLC
Lewes, Delaware, USA
[email protected]
storeswiki.com
Support runs on tickets and email rather than a phone line, so every request keeps a written record for both sides.