Privacy Policy
Last updated 20 October 2026
1. What we collect
- Account info — your email address and a password. Your password is never stored as plain text; it's hashed with Argon2 before it ever touches our database, so even we can't read it back.
- Your uploaded pattern files — the PDF you upload, the SVG and legend data we generate from it, and the corrections you make in the editor.
- Your designs — if you use the quiet book designer: the shapes you make (including the descriptions you type to create or change them), their colors, materials and notes, and the books and pages you arrange them on.
- Basic usage data — job status, timestamps, credit balance, and a count of the AI requests your account makes (and their estimated cost to us), so the Service works, daily limits can be applied, and we can answer support questions.
- Error reports — when something breaks, technical details of the error (which page or request failed, and your account ID) go to our own error tracker, which runs on our server. We use them only to fix bugs.
We don't run advertising pixels or third-party marketing scripts. We do use Ahrefs Web Analytics to count page visits (which pages are viewed, the referring site, and the rough country and device type). It's cookie-free and doesn't track you across other websites; we use it only to see which pages people find useful.
2. How your pattern file is processed
Converting a hand-drawn or scanned pattern into a color-grouped SVG requires reading the handwritten color notes on the page. That step is handled by Google's Gemini vision model — page images from your PDF are sent to Google's Gemini API for that single purpose, and nothing else. Google processes that request under its own API terms; we don't control what Google does with it beyond our request, so if that matters to you, read Google's Gemini API terms as well. Everything else in the pipeline — rasterizing the PDF, tracing the vector paths, assembling the final SVG — runs on our own server.
To save time and cost, we remember Gemini's reading of each page. If exactly the same page image is converted again (for example, the same bought pattern uploaded by another customer), that stored reading is reused instead of asking Gemini again. Only the AI's reading is stored this way — never your files, your corrections, or who you are — and it is only ever reused for an identical page.
So we can help when something goes wrong and keep improving how patterns are read, our staff can look at a conversion: the uploaded file, the page images and the pieces that were found. We only do this for support and to check and improve the conversion quality, never to reuse or share your patterns.
Pattern Decoder: when you use the Pattern Decoder, the photo of your knitted or crocheted item and any notes you add are sent to Google's Gemini API to write the pattern, and the photo is kept for the same job retention window as your other job data.
2a. The quiet book designer
The designer uses Google's Gemini models too. When you ask it to draw a shape, suggest parts or changes, suggest story ideas, or make a photo preview, the text you typed and (where needed) a picture of your shape or page are sent to Google's Gemini API to produce the result. Before that, what you type is checked — by a word list and a quick Gemini check — to keep content suitable for a children's book.
Shared shapes: generated shapes are kept in a shared library so that the next person who asks for the same thing (say, "a red apple") gets a ready-made shape instantly instead of waiting for a new drawing. Only the shape picture and outline are shared, matched by the words of the description — never your name, your email, your books, or your pages. If you'd rather not share a shape, avoid putting anything personal in a shape description.
3. Payments
If you buy a credit pack, your card details are entered into a secure payment form hosted by our payment processor, Stripe (a PCI-DSS Level 1 certified payment provider), and sent directly to Stripe — your card number never reaches our server. We only ever see a payment reference and the outcome of the charge, which we use to credit your account.
4. Bot protection
Signup and the contact form are protected by Google reCAPTCHA Enterprise, to stop automated account creation and spam. Google processes some technical data (like your browser and IP address) to make that assessment — see Google's Privacy Policy for how reCAPTCHA handles that.
5. The free SVG-resize tool
The free SVG cut-file resize tool doesn't require an account and doesn't save anything — the file you upload is fixed entirely in memory for that one request and discarded the moment the corrected file is sent back to you.
6. Cookies
We set exactly one cookie: a session cookie that keeps you logged in. It's functional
only — HttpOnly so page scripts can't read it, and sent only over HTTPS. We
don't set advertising, tracking, or cross-site cookies. The editors also save a few
small preferences in your own browser's storage (such as custom colors you've added);
those never leave your device. reCAPTCHA (on signup and the contact form) and Stripe (on
the payment form) may set their own cookies on those pages.
7. Who we share data with
| Who | What they get | Why |
|---|---|---|
| Google (Gemini API) | Page images from your uploaded PDF; in the designer, the text you type and pictures of your shapes and pages; in the Pattern Decoder, your photo and any notes | Reading handwritten color notes; drawing shapes, suggesting parts, changes and story ideas, photo previews, and the children's-content check; writing a knit or crochet pattern from your photo |
| Google (reCAPTCHA Enterprise) | Browser/device signals at signup and on the contact form | Blocking automated bot accounts and spam |
| Stripe | Payment details, entered directly into Stripe's secure form | Charging a credit pack purchase |
| Resend | Your email address and the email we send you | Delivering account emails (like the sign-up verification link) and contact-form messages |
| Ahrefs (Web Analytics) | Cookie-free page-visit counts: page, referrer, rough country and device type | Seeing which pages are useful |
That's the complete list. We don't sell data to anyone, we don't share it with data brokers or advertisers, and we don't hand it to any other third party beyond the ones above, each of which exists to make one specific part of the Service work.
8. How long we keep it
Job data (your uploaded PDF and the files generated from it) is kept for a limited retention window described in our Terms of Service — download anything you want to keep long-term rather than relying on it staying in your account indefinitely. Account data is kept for as long as your account exists.
9. Your rights
You can delete your account yourself at any time, in the Android app (Account → Delete account) or on the website's Profile page — see what is deleted and what is kept. You can also ask us to access, correct, or delete your account and job data via Contact support. If you're in the EU/UK, this covers your rights under the GDPR; if you're in Australia, this covers your rights under the Privacy Act 1988 (Cth).
10. Changes to this policy
We may update this policy from time to time; the "Last updated" date above will change accordingly.
11. Contact
Questions about this policy, or about your data: use Contact support.