Privacy policy

SimFabric turns a description of a robot task into a simulated world. It is operated by Voxity Technologies Private Limited (“we”, “us”). This policy explains what we collect when you use SimFabric, why, who else handles it, and the control you have over it.

What we collect

Your account

• Your email address and the name you give us.
• Your password, stored only as a salted hash (Argon2) - we cannot read it. If you sign in with Google, we receive your email, name and Google account identifier from Google.
• Your answers to the optional first-run questions (what brings you here, how you heard about us).
• How you first arrived: the website that linked you here (its name only, such as news.ycombinator.com - never the page or what was in its address), any campaign tags in the link you followed (utm_source, utm_campaign and the like), the SimFabric page you landed on, and the date. Your browser keeps this until you finish or skip the first-run questions, then sends it once with them; it is stored with your account and never updated afterwards.
• Your plan, how many worlds you have generated this month, and your training preference.
• If you join the beta waitlist before you have an account: the email address you type, and when. We use it to decide whom to let in and to write to you when your place is ready.
• If you ask for early access to something that is not open yet (the Loom-1 and Fabric-1 models, or robot training): what you asked for, when, and the note if you write one. You ask by your own click; we use it to decide whom to invite and to write to you about it. Leaving the list deletes it, and so does deleting your account.
• Which version of these terms and policies you agreed to, when, and where (signing up, continuing with Google, or agreeing to an updated version) - so we can show what you agreed to. Deleting your account deletes it.
• If you subscribe to a paid plan: your subscription and the payments made for it - plan, billing period, amounts, dates, status, the kind of payment method (for example card or UPI) and links to your receipts. Your card, UPI or bank details go to Razorpay and never reach our servers.

What you create

• The prompts you send and the worlds generated from them: the scene description, the rendered pictures, and the list of generated files. We keep these as your run history so you can reopen past conversations.
• Generation logs: your prompt, what the AI model was sent and returned, and the checks the world passed or failed. We use these to find and fix problems.
• Things our asset library does not have: when a world asks for an object we hold no model of, we record its name (for example “harp”), how many times it was asked for, the model SimFabric generated for it if one passed our checks, and a link to the run that last asked. We use this to decide what to add to the library. Your prompt is not copied into that record: we read it through the run, so deleting the run or your account removes it. The name and the counts stay.
• Links you share: when you choose Share on a world, anyone who has the link can see that world - the prompt that made it, its pictures, its 3D model and its generated files (with any edits you saved) - and download it, without an account. The shared page does not show your name or email. We count how many times the link is opened. Stop sharing ends the link at once for everyone; deleting that run or your account deletes the link too.
• Files you edit and save in Code: kept with that run, and put in its download in place of the generated file, until you revert them or delete your account.
• Modes you add to a world (its ground or light changed, such as icy or at night): each mode's name, what it changes and the floor friction we measured for it, kept with that run until you remove the mode or delete your account.
• Shots you add to a world (a named camera): its name, where it stands, what it looks at, its lens and frame, what we found when we filmed it (where the camera rendered from, whether something hid what it looks at), and the picture it filmed. Kept with that run until you remove the shot or delete your account.
• A timeline you save for a world: how long it runs, which shot the camera is on when, and the points, joint angles and times you give its robots. Kept with that run until you clear it or delete your account. A film you record in Simulate is made in your browser and saved to your device; the film in a download is made on our servers from the saved timeline and kept with that download until the world changes.
• Presets you save: the name you give it, a world's light and ground, and the colour or finish you gave each kind of object in it. Only you can see or use them; we never use them to build anyone's worlds. Kept until you delete the preset or your account.
• Prefabs you save: the name you give it and, for each object in it, which object it is, where it stood and was turned relative to the others, its colour or finish and whether it moves freely. Only you can see or place them; we never use them to build anyone's worlds. Kept until you delete the prefab or your account.
• Robot files you upload are processed to check them and are not kept after the check finishes.
• 3D models you upload to build a world around: kept with your account, together with the world built from them, until you delete the upload or your account.

Teams

• If you are in a team, its other members see your name, your email address, your role and how many worlds you built this month - and the team's total.
• Worlds you start while in a team are shared with it: every member can open them - the prompts, the pictures, the 3D model, the files - continue them, edit their files, download and share them. You can keep any world of yours to yourself with the Shared with team / Only me switch above it. Worlds you made before joining stay private.
• If a team's owner invites you, we store the address they typed and email it an invitation link. The link works for 7 days and only for that address; the owner sees the invitations still waiting.
• Leaving a team takes your worlds with you and ends your access to the others'. Deleting your account deletes the worlds you started, including teammates' additions to them.

Diagnostic records

• Each request SimFabric's pages make to our servers: which part of the service it was (for example “generate a world” or “open the 3D view”), when, whether it worked, how long it took, and the error if it failed. Never what you typed into a form, your password, or the contents of your files.
• The steps each of your generations went through on our servers, and the error if one failed.
• Errors that happen in SimFabric's pages in your browser, with a random identifier for that tab.
• Help requests you send us: what you wrote and the kind of help you chose, plus - if you are signed in - a copy of your diagnostic records from the two hours before it and anything tied to the error you reported from.
• If you ask for help without signing in: the email you give us to reply to, your message, the page you were on, your browser and screen size, and any errors that browser tab ran into. It is not linked to any account, even one with the same email address.

Sessions and your browser

• A sign-in token, kept in your browser’s storage and in one cookie (sf_session) that scripts cannot read. It exists to keep you signed in and to load your own pictures.
• Your theme and unsent drafts, kept only in your browser.
• How you first arrived (above), kept in your browser's storage (sf_first_touch) until it is sent with your first-run answers.
• If the “Continue with Google” button loads, Google may set its own cookie.

We do not use advertising or cross-site tracking cookies.

How we use it

• To run SimFabric: sign you in, generate and show your worlds, keep your history, and apply plan limits.
• To send you verification and password-reset codes.
• To tell you a world is done while SimFabric is open in another tab: if you allow browser notifications (Settings → General), this browser shows one. We keep nothing for that, and we do not email you about finished worlds.
• To stop abuse of free accounts: one account per mailbox (an address with a “+tag”, or a Gmail address with dots, counts as the same mailbox), no temporary-email domains, and a limit on how many accounts one network address can create. For that limit we keep a count against your network address for up to a day - the count, not a record of what you did.
• To find and fix failures, using the generation logs and diagnostic records.
• To answer your problem reports. Only the SimFabric team can read them. Our replies, and yours, are kept with the report and shown to you under Your requests; each reply of ours is also emailed to you.
• To understand, in aggregate, who uses SimFabric and how they found it: sign-ups, plans, activity and how people first arrived, seen only by the SimFabric team in an internal dashboard. For this we note the date you first build a world, first download one and first share one, and which days you use SimFabric while signed in (the day only, not what you did). Deleting your account deletes these too.
• To train and improve SimFabric’s models - only if you say yes. We ask once when you join, with “Yes” and “No thanks” side by side and neither chosen for you; skipping the question leaves it off. You can change it at any time in Settings → Privacy, and logs from while it was off are never used for training. Even with it on, we only train on output from models whose licence permits it.

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

Who else handles it

We use a small number of service providers, each only for its job:

• Our AI model providers When our models is under heavy load we at times parse input through (Groq, Cerebras and Anthropic) receive your prompts and the context needed to generate a world. Each request goes to one of them; and redirected to our models if generation of a world is required.
• Resend delivers our emails, so it receives your email address and the code we send, the prompt of a finished world when we tell you it is done - and, when you send a problem report or answer one of our replies, its text on its way to our support inbox, and our replies on their way to you.
• Google, if you choose to sign in with Google.
• Razorpay processes payments if you subscribe to a paid plan: it receives your payment details and the email address you pay with, and sends us the status of your subscription and payments.
• Upstash (through Vercel) may hold the beta waitlist: the email address you leave and when, until we move it to our own servers. To limit abuse it counts requests from your network for an hour, by a one-way code made from your network's address - never the address itself.
• The companies that host our servers.

These providers may process data outside your country. We may also disclose information if the law requires it, or to protect people or the service from harm.

How long we keep it

• Your account stays until you delete it.
• Run history stays until you delete your account. Each account has a storage allowance set by its plan (shown on the Plans page); when yours is full, your own oldest runs are removed to make room. Your most recent run is always kept, and one person's use never removes anyone else's history.
• Verification codes expire after 10 minutes and are deleted within the hour. You stay signed in while you use SimFabric; a session unused for 30 days ends, and an ended session (expired, or signed out) is deleted within a day.
• Records of payments and subscriptions are kept for as long as tax and accounting law requires, including after you delete your account - without being linked to it any more.
• Diagnostic records are deleted after 30 days. A problem report keeps its own copy of them until your account is deleted.

Your choices and rights

• Change your name or your training preference in Settings.
• Delete your account in Settings → Account. This immediately deletes your account, your sessions, your run history and pictures, any worlds held in memory, the generation logs linked to your account, your diagnostic records and your problem reports. It also cancels any paid subscription at once; payment records are kept, unlinked, as described above.
• To get a copy of your data, correct something, or ask a question, email support@simfabric.dev.

Security

Passwords are hashed with a per-account salt, sign-in tokens and API keys are stored only as hashes on our side (an API key is shown to you once, when you make it), and each person can reach only their own history and worlds - apart from a world they choose to share by link. No system is perfectly secure; if you believe your account was accessed without your permission, contact us.

If you add your own key for a model provider, it is stored encrypted, used only to run your own sessions, never shown again, and deleted when you remove it or delete your account. Your prompts and what the session works on then go to that provider under your agreement with them, and what those sessions do is never used for training.

Children

If you are under 18, you may use SimFabric only with the consent of a parent or guardian.

Changes

If we change this policy in a way that matters, we will update the date above and tell you in the product or by email before the change applies to you.

Contact

Questions or requests about your data: support@simfabric.dev.