Privacy Policy

Re:Form is operated by Frame Sixty Labs, LLC ("Frame Sixty", "we", "us"), a company based in Florida, United States, and the controller of the personal data described here. This policy explains what personal data we collect when you use reformsculpt.com and the Re:Form application, why we collect it, and what you can do about it. We have tried to write it in plain language, and it describes what the software actually does today.

1. Where your sculpts are stored

The mesh you sculpt lives on your computer's graphics card while you work. Autosaves stay in your browser's own storage on your machine, and the model files you export are downloads on your machine. Nothing you sculpt is transmitted to us until you save a project or publish a share link.

Saved projects. When you use File ▸ Save, the project file and a small thumbnail image are uploaded to Firebase Cloud Storage (a Google service) under your account, so that you can open them from File ▸ Open or the start screen wherever you sign in. They are stored under your user identifier, readable only by your signed-in account, and are not used for anything else. An open saved project is also autosaved back to your account every few minutes. You can delete any saved project at any time, and deleting your account removes them.

Share links. When you publish a share link, the model (as a .glb file), a thumbnail image and the title you give it are stored in Firebase Cloud Storage and Cloud Firestore. They are publicly readable by anyone who has the link, and by the link-preview services of the apps where you post it. Which account a share belongs to is kept in a separate record that only you and our servers can read. A share stays published until you delete it, and deleting your account deletes your shares.

Remix and the gallery. If you switch on Allow Remix for a share, the credit name you enter is shown on work other people share from it. If you submit a share to the gallery, the display name you enter is stored with the submission and, once the submission is approved, shown beside it on the gallery page with its title and preview picture. Neither names your account, and neither happens unless you choose it. Withdrawing the submission, or deleting the share or your account, removes it.

2. What we collect

Account data. When you create an account, Firebase Authentication (a Google service) stores your email address, a unique user identifier, and your sign-in method. If you use a password, Firebase stores it in hashed form — we never see or hold your password. If you sign in with Google, we receive your email address and identifier from that account.

Consent records. When you accept the Terms of Use at signup, we store a record containing your user identifier, the version of the terms you accepted, the time you accepted it, and whether you opted in to product-update emails. We keep this because we are required to be able to show that consent was given.

Billing data. If you subscribe to a paid plan, Stripe processes the payment and holds the payment details. Your full card number never reaches our servers — checkout happens on Stripe's own hosted page. We give Stripe your account identifier and email address so your subscription is linked to your account, and we keep a cached record of your plan, your subscription status and when it last changed, so the app can unlock your plan quickly.

Messages you send us. If you use the contact form or email us, we keep your name, email address, the content of your message and the country it was sent from, so we can reply. A report sent from Help ▸ Report a problem also includes the diagnostics shown to you before you send it: the app version, your browser, your graphics adapter, the model's size, the active brush and recent error messages. The contact form also keeps a short-lived counter tied to your network address for a minute at a time, purely to slow down automated spam.

Analytics on our public pages. Our marketing pages — the home page, pricing, docs, blog and so on — include Google Analytics, which sets cookies and collects usage information such as pages viewed, approximate location derived from your network address, and browser and device type. The sculpting application itself does not include Google Analytics or any other third-party analytics script.

Usage numbers in the studio. If you choose to share them, then while you are signed in the studio counts how it is used and sends those counts to us: which tools, menu commands and keyboard shortcuts were used and how many times, how many strokes each brush made, which starting shape a sculpt began from, how long the studio was actively in use, the largest size a sculpt reached as a broad band (for example "1 to 5 million triangles"), and how many errors happened. With them we record your plan (Free or Pro), the Re:Form version, your browser and operating system family, your graphics card maker, a broad screen-size band, and how many sessions this browser has had. These are counts and durations only. They never include your sculpts, meshes, images, file or project names, or anything you type. A session is stored against a one-way scrambled form of your account identifier rather than the identifier itself, so that sessions by the same person can be counted together without the record naming the account. This is off unless you choose to share: you are asked, in an optional box, when you create your account, and you can switch it on or off at any time in Edit > Preferences > General > "Share usage numbers"; when it is off, nothing is counted or sent.

Feedback you send. If you rate Re:Form in the studio's feedback card, we store the rating and any comment you choose to send, with your account, to improve Re:Form.

Technical logs. Cloudflare, which hosts the site, processes standard server logs (including network addresses) as part of delivering and protecting it.

3. Why we use it, and our legal basis

We use account and billing data to provide the service you asked for and to manage your subscription — the legal basis is performance of our contract with you. We keep consent records to meet a legal obligation. We use analytics and abuse-prevention data on the basis of our legitimate interest in understanding how the site is used and keeping it working. We send product-update emails only where you have given consent, which you may withdraw at any time.

We do not sell your personal data, and we do not use it for advertising profiles.

4. Who processes data on our behalf

• Google (Firebase Authentication, Cloud Storage, Cloud Firestore and Cloud Functions) — account creation and sign-in, saved projects and their thumbnails, share links, and the studio's usage numbers. Google Fonts supplies the typefaces our pages load.
• Google Analytics — usage measurement on our public marketing pages only.
• Stripe — payment processing and subscription status.
• Cloudflare — website hosting, serverless functions, relaying saved projects between your browser and storage, and storage of consent records, contact messages, and the plan cache.

These providers operate internationally, so your data may be processed outside your own country, including in the United States. They provide contractual safeguards for those transfers, such as the European Commission's standard contractual clauses where relevant.

5. Cookies and local storage

Our public marketing pages set Google Analytics cookies as described above. The application uses your browser's local storage and IndexedDB for things it needs to work — your sign-in session, your saved preferences, your saved brushes, and your autosaved sculpts. That storage is functional, stays on your device, and is not used to track you across other websites. Clearing your browser storage for this site will sign you out and delete your autosaves, so export anything you want to keep first.

6. How long we keep it

Account data is kept while your account exists. Consent records are kept while your account exists and for a reasonable period afterwards, because their purpose is to evidence what you agreed to. Billing records are kept as long as tax and accounting law requires, typically several years. Contact messages are kept while we need them to deal with your enquiry and for a reasonable period after. Saved projects and share links are kept until you delete them or your account. The plan cache is kept while your account exists. Analytics data is retained according to Google Analytics' configured retention period. The studio's usage numbers are kept per session for thirteen months and then deleted, and are deleted sooner if you delete your account; daily totals that describe nobody in particular (for example "how many strokes the Clay brush made today, across everyone") are kept. The spam-prevention counter expires after one minute.

7. Your rights

Depending on where you live, you have rights over your personal data — and we will honour these requests wherever you are. You may ask us to give you a copy of the data we hold about you, correct it if it is wrong, delete it, restrict or object to how we use it, or provide it in a portable form. Where we rely on consent — product-update emails — you can withdraw it at any time, and every such email includes an unsubscribe link.

To exercise any of these, email hello@reformsculpt.com from your account address. We will respond within one month. Deleting your account removes your authentication record, your saved projects and your share links. We keep your consent record for a reasonable period afterwards as evidence of what you agreed to, and billing records that we are legally required to retain until that obligation expires. Autosaves and exports on your own device are deleted by you locally — we hold no copy; the projects you saved with your account are deleted with it, or by you at any time from File ▸ Open or the start screen.

If you are in the European Economic Area or the United Kingdom and you believe we have handled your data improperly, you may complain to your local data-protection authority. We would appreciate the chance to put it right first.

8. Children

Re:Form is not intended for children under 13, and we do not knowingly collect their personal data. If you believe a child has given us personal data, contact us and we will delete it.

9. Security

Sign-in is handled by Firebase Authentication and payments by Stripe, both of which are established providers with their own security programmes. Traffic to the site is encrypted in transit. Consent records, contact messages, and the plan cache are stored in Cloudflare's key storage with no public read endpoint. No system is perfectly secure, and we cannot guarantee absolute security, but we will notify affected users and the relevant authority if a breach occurs that requires it.

10. Changes to this policy

We may update this policy as Re:Form changes. Each version carries the date at the top of this page, and material changes will be brought to your attention in the app rather than made quietly.

11. Contact

Privacy questions, or a request about your data? Email hello@reformsculpt.com.