Privacy policy

Effective November 2, 2026.

The free workshop is open for personal projects. There are no purchases or subscriptions available today.

Moopky is an independently operated online design service. Contact: info@moopky.com.

Your model inputs stay in your browser

Images, SVG artwork, entered model text and CSV orders are processed in your browser and its workers. These inputs are not uploaded by the modelling tools. Exported STL and 3MF files download to your device. If you voluntarily attach material to a support email, that copy is shared with support; avoid sending customer orders or personal photos unless needed.

Licence and payment records

Payments are currently disabled. The following describes records retained if a licence or payment flow was previously used; the free workshop does not request payment details.

When a licence is issued, the server stores a hash of its key, its tier, creation and expiry times, status and whether the key was revealed. It also stores Stripe customer, checkout-session, subscription, payment-intent and processed-event identifiers, plus refund/dispute markers needed to prevent access being restored after revocation. The raw delivery key is held briefly in server memory before its one-time reveal; it is not stored as plaintext in the licence database.

If payment services are enabled in a future release, Stripe will handle checkout and billing and receive the payment and contact information you provide there. Moopky does not store card numbers in its application database. Stripe processes payment data under its own policies. Support correspondence may include information you send us to identify a purchase.

Cookie and local storage

If you previously used licence access, the ts_license cookie is an HttpOnly, signed licence-session cookie. It uses SameSite=Lax and is Secure in production, with a maximum lifetime of one year. It lets the server look up current access; it does not contain your raw licence key. Signing out deletes this browser cookie. Free single-model STL and 3MF downloads do not use a local quota counter. When you choose Save make, local storage also keeps the model settings, text, SVG artwork and preview palette for up to 24 designs. Uploaded images are not saved. My makes lets you reopen or remove these designs; they are not synced to other devices. Clearing browser data can remove that local state and your signed-in session.

Anonymous counts and infrastructure

Application analytics store daily counts by event name, page path and tool, including page views, tool opens, builds, downloads, upgrade prompts, checkout starts and purchases. Page views can also include a validated, lowercased external referrer hostname and a validated utm_source label, never a full referrer URL. Same-site and direct visits have an empty referrer. Interest buttons count only the feature (3mf, batch or commercial), page path and day; they collect no contact details. Analytics requests omit cookies and the HTTP Referer header. These are event counts, not unique visitor counts. They do not store IP addresses, cookies, uploaded content, query strings or persistent visitor identifiers. In-memory rate limiting derives short-lived buckets from network addresses. Hosting and reverse-proxy infrastructure can process network addresses and request metadata to deliver the service and investigate errors. These details are not included in application analytics.

Requests and retention

Contact the operator to ask about access, correction or deletion of information associated with a purchase. Include a receipt reference, not card details or your secret key. Payment and transaction records may need to be retained for accounting, dispute handling and legal obligations. We retain these records while needed for those purposes and to provide your purchased access. Deletion requests may not remove information from every backup immediately.