Privacy Policy

Last updated: 5 October 2026

1. Introduction

This policy explains how Ruvix Ltd (Ruvix Labs, "we", "us") uses your information when you use ThreadCam on iPhone, on Android, in your browser at threadcam.com (including the online studio), or as the ThreadCam app in ChatGPT, and when you order a printed garment from us. We are responsible for your information. We don't sell it.

2. Information we collect

2.1 Your account

  • A random account ID. The web studio creates an anonymous account for your browser so your credits and purchases have a home.
  • If you sign in with Google, Apple or email: your email address, and your name if the provider shares it. Passwords are handled by Google Firebase Authentication; we never see them.
  • Your credit balance, purchases and subscription status.
  • If you connect your ThreadCam account to ChatGPT: the link between them (see ThreadCam in ChatGPT below).

2.2 Your designs

  • Images you upload, text you add, garment and colour choices, and the designs you make.
  • What you ask the AI for (your prompts, inspiration images and marked areas) and the images it returns.

2.3 Automatically collected

  • Device and browser information (model, operating system, browser, language) and, in the apps, crash reports.
  • How you use ThreadCam, such as screens opened, the paywall shown and export steps.
  • Advertising measurement data if you arrived from one of our ads (see Measurement and advertising below).

2.4 Printed orders

If you order a printed garment: your name, shipping address and email address, and what you ordered (see Printed orders below).

2.5 Support

Messages, screenshots and files you send us when you ask for help or report a bug.

3. How we use your information

  • To run ThreadCam: show your designs, create AI images, make your exports, and keep your designs saved
  • To manage credits, purchases and subscriptions, and to prevent fraud and abuse (for example, stopping prompts that break our rules)
  • To show your design on a garment in ChatGPT, price it and, if you order, print and ship it
  • To answer support requests and send service messages, such as receipts and order updates
  • To understand how ThreadCam is used and fix problems
  • To measure which of our ads lead to sign-ups and purchases

We do this to provide the service you asked for, to meet legal obligations (such as keeping payment records), and because we have a legitimate interest in keeping ThreadCam secure, improving it and knowing which of our ads work.

4. Where your designs are stored

In the web studio without signing in, your designs and images stay in your browser (browser storage called IndexedDB). They aren't sent to us, except the images and prompts you send to the AI. Clearing your browser data deletes them.

When you sign in, we also save a copy of your designs and the artwork they use to your account in the cloud (Google Firebase: Cloud Firestore and Cloud Storage), so you can open them in another browser. Only you can access them. If you delete a design in the studio, its cloud copy is deleted too.

In the apps, your projects are stored on your device.

AI images are created by our AI provider, OpenAI, which receives your prompt and any images you send with it. OpenAI processes them to return the result and, under its API terms, doesn't use them to train its models. We keep a temporary copy of each AI result on our servers so it can be delivered to you, and delete it automatically after a short period.

5. Payments

On the web, payments are handled by Stripe, and web subscriptions are sold through Onelink, Stripe's merchant of record service, which receives your name, email, billing country and payment details to take the payment, handle tax and send your receipt. Subscriptions are managed by RevenueCat. We never see your full card number. In the apps, purchases go through Apple or Google, and RevenueCat checks them for us.

6. Measurement and advertising

We advertise ThreadCam, for example on Facebook and Instagram, and we measure which ads lead to sign-ups and purchases. Here is exactly what happens.

  • AppRefer, our attribution service, records an ad click on its servers before sending you to ThreadCam (your IP address, browser information, the ad click ID and campaign). We keep that click ID in your browser's storage, with the page you first landed on and campaign tags, and remove it from the address bar.
  • When you sign up, start checkout or buy, we send AppRefer that fact with the click ID, the Meta browser cookie IDs (_fbp, _fbc) and, where we have it, a hashed (SHA-256) copy of your email address. Your plain email is never sent. AppRefer shares these facts with the ad network, such as Meta, from its servers so they can measure and improve our ads.
  • Meta's pixel runs on threadcam.com and records page views, when you start designing and when you create your account. When you create your account during setup, the pixel also receives your email address and your ThreadCam account ID, hashed (SHA-256) in your browser before they are sent, together with your setup answers (for example what you're making and on which garment). Meta uses these to measure and improve our ads. It never receives your designs or anything else you type. Meta may use its own cookies (_fbp, _fbc) under its own privacy policy.
  • In the apps, we use Meta's SDK and AppRefer for the same purpose. On iPhone, we only use your device's advertising identifier if you allow tracking when asked.

Product analytics

On threadcam.com we also keep our own simple usage statistics, so we can see which pages and steps work and where people get stuck: for example that a page was viewed, which setup option was picked from our list, that the paywall was shown, that checkout started or that a design was exported. Each event is stored with a random ID kept in your browser, a random per-visit ID, your ThreadCam account ID if you have one (checked on our server), the campaign name or ad type you arrived from, and whether you're on a phone, tablet or computer. We don't store your IP address, browser details, email, what you type or your designs. Paid orders and subscriptions are recorded by our server from the payment, with the amount and currency only. This data stays with us (Google Cloud), is kept for 400 days, and is never sold or shared with advertisers. If your browser sends Global Privacy Control or Do Not Track, none of it is collected.

Your choice: we honour Global Privacy Control. If your browser sends it, we don't load Meta's pixel, don't store the ad click ID and don't send any measurement or analytics events for that browser. You can also email us to stop using measurement data linked to your account. Opting out doesn't change anything in the studio.

7. ThreadCam in ChatGPT

The ThreadCam app in ChatGPT shows a design on a 3D garment, lets you change it, prices a printed garment and gives you a checkout link. You don't need a ThreadCam account to use it.

7.1 What ChatGPT sends us

  • The artwork image ChatGPT passes to ThreadCam (for example an image it created or one you shared), which we download from the link ChatGPT gives us.
  • If ChatGPT can't attach an image, a written description of the design and an optional style, which we use to draw it.
  • Your choices: garment, colour, placement, side, size and position of the design, and for prices and orders the size, quantity, country and (for the US, Canada and Australia) state.
  • The changes you make in the ThreadCam panel inside ChatGPT.

We don't receive your ChatGPT name, email or chat history. A mockup isn't linked to who you are unless you connect a ThreadCam account. ChatGPT may attach general context to its requests, such as your language; we don't use or store it.

7.2 What we send back to ChatGPT

A description of the mockup (garment, colour, design size and position), links to the design images, prices, the checkout link and, while the panel is open, a small picture of the current mockup so ChatGPT can talk about it. ChatGPT handles this under OpenAI's own privacy policy.

7.3 Designs ThreadCam draws

When ThreadCam draws a design from a description, the description (and the garment colour) is sent to OpenAI's image model, which returns the image. Under its API terms OpenAI doesn't use it to train its models. We limit how many designs ThreadCam draws per day for everyone together; that count isn't linked to you.

7.4 Storage and how long

Design images, mockups, mockup previews and exports are stored on Cloudflare R2, our storage provider. They can be opened for 24 hours (a mockup for 24 hours after its last change) and are then deleted automatically, at the latest within three days. Anyone with a link to one of these images can open it during that time, so the links use long random IDs. Files that belong to an order are kept with the order (see Printed orders).

7.5 Connecting your ThreadCam account

  • You can connect a ThreadCam account to ChatGPT. You sign in on threadcam.com with Google or email and password (through Google Firebase Authentication; we never see your password) and approve the connection.
  • We then give ChatGPT an access token that identifies your ThreadCam account ID and email address. Access tokens last 30 days; ChatGPT can renew them with a refresh token that lasts up to 180 days. We store only a hashed copy of each refresh token, with your account ID and email, and the details ChatGPT registers to connect (its name and return address).
  • With a connected account, ThreadCam checks with RevenueCat, our subscription service, whether your account includes exports. ChatGPT is told whether you're signed in, your email and whether exports are available. Exports you make from the panel are stored as described in 7.4.
  • To disconnect, remove ThreadCam from your connected apps in ChatGPT's settings. ChatGPT then stops using the tokens; the stored refresh record expires 180 days after it was issued and is then deleted automatically, or email us and we'll delete it straight away.

7.6 Logs

Our servers keep standard request logs (such as IP addresses and times) for security, and record errors so we can fix them. We don't log the contents of your designs or descriptions in production.

8. Printed orders

  • Checkout: you pay on a Stripe Checkout page. Stripe collects your name, email, shipping address and payment details and tells us your name, email and shipping address. We never see your full card number. We don't ask for a phone number. Stripe Tax uses your address to work out any sales tax or VAT.
  • Printing and shipping: Printful prints and ships your order. We send Printful your name, shipping address, email address, the garment, size and quantity, and the print files of your design.
  • Emails: we email you about your order (confirmation and shipping updates) through Resend, our email provider, which receives your email address and the message.
  • What we keep: the order record (what you ordered, the price, tax, your name, shipping address and email, and the payment and order references) and the print files. We keep them to fulfil the order, handle returns and support, and for our tax and accounting records, for as long as the law requires. Checkout links stop working after 24 hours.

9. Other services we use

  • Google Firebase (Authentication, Cloud Functions, Firestore, Storage, App Check with reCAPTCHA, and in the apps Analytics and Crashlytics) to run accounts, AI requests and cloud save, and to protect them from abuse
  • OpenAI to create AI images, including designs ThreadCam draws in ChatGPT
  • OpenAI's ChatGPT, when you use the ThreadCam app there (under OpenAI's own privacy policy)
  • Cloudflare (R2 storage) to store designs, mockups, exports, print files and order records for the ThreadCam app in ChatGPT
  • RevenueCat, Stripe (including Onelink and Stripe Tax), Apple and Google for payments and subscription status
  • Printful to print and ship garments you order
  • Resend to send order emails
  • AppRefer and Meta for ad measurement, as described above
  • Gleap, in the apps, for bug reports and support messages
  • Our website host, which processes request information such as IP addresses for security

These providers only use your information to provide their service to us, except Meta, Apple, Google and OpenAI's ChatGPT, which also act under their own privacy policies. We may also share information to comply with the law, to protect our rights or users, or as part of a sale or merger of our business.

10. Browser storage and cookies

The website uses your browser's storage to remember your designs (IndexedDB), your sign-in, your studio settings, the ad click details described above and the random product analytics IDs (see 6). Meta's pixel uses the _fbp cookie, and we set the _fbc cookie when you arrive from a Meta ad link. We don't use other advertising cookies.

11. How long we keep information

We keep your account, cloud designs and purchase records while your account exists. Temporary AI results are deleted automatically. Designs, mockups and exports from ThreadCam in ChatGPT are deleted within three days (see 7.4), and stored ChatGPT sign-in (refresh token) records expire after 180 days and are then deleted automatically. Order records and print files, and payment records, are kept as long as the law requires. Measurement data sent to AppRefer and Meta follows their own retention rules. When you ask us to delete your account, we delete your cloud designs and account data, except records we must keep by law.

12. Your rights and choices

Depending on where you live, you can ask to access, correct, delete or get a copy of your information, and to object to or restrict how we use it. You can also opt out of ad measurement (see above). To do any of this, email support@ruvixlabs.com from the email on your account. In the UK you can also complain to the Information Commissioner's Office.

California: you have the right to know what we collect, to delete it and to opt out of its "sale" or "sharing". We don't sell personal information. Sending hashed identifiers to Meta for ad measurement may count as "sharing"; Global Privacy Control or an email to us opts you out.

13. Children

ThreadCam isn't meant for children under 13, and we don't knowingly collect their information. If you think a child has given us information, contact us and we'll delete it.

14. International transfers

Our providers may process your information outside your country, including in the United States. Where the law requires it, we rely on safeguards such as the standard contractual clauses.

15. Security

We use encryption in transit, access rules that let only you read your cloud designs, and App Check to block abuse. No system is perfectly secure, so we can't guarantee absolute security.

16. Changes to this policy

We may update this policy. We'll post the new version here and change the "Last updated" date. See also our Terms of Service.

17. Contact us

Questions about this policy or your data? Contact Ruvix Labs at:

support@ruvixlabs.com