Privacy
What we collect, and what we do with it.
Last updated 30 September 2026
The short version
We collect what an account needs to exist, what a licence needs to work, and what a message needs to be answered. No card payments are taken through this site at present. We do not sell any of it and we do not share it for advertising. We count page views only if you say yes, and even then without cookies and without anything that identifies you. You can delete your account yourself, at any time, from your account page.
Who is responsible for it
Object Forge AI is run by Andrew Kassatly, a sole trader based in Lebanon. That is who decides what happens to your data and who answers for it: in the language of data protection law, the controller. Write to sales@objectforge-ai.com about anything on this page. The business details page has the rest.
What we store
| Data | Why |
|---|---|
| Name and email | To identify your account and send you confirmation and password-reset mail. |
| Password hash | To sign you in. Hashed with a modern algorithm and salted; we never hold the password itself and cannot recover it for you. |
| Session records | A token and an expiry, so you stay signed in. We do not record the network address or the browser you signed in from. |
| Google account id | Only if you choose Google sign-in. We receive your email and name, nothing more. |
| Licence and activations | Which machines have activated the application, shown by a name you can recognise, so you can revoke one, and how much model time the licence has used this month, so the allowance can be enforced. |
| Subscription state | Whether your licence is active, how many seats it covers and when its period ends. It is what decides whether the download and the application work. No card details are collected, because no card payments are taken yet. |
| Messages | What you type into the contact form, so we can answer it, and the page you sent it from (the page only, never anything after it in the address). Kept as a record because email delivery is not guaranteed. |
| Release-notice address | Only if you ask to be told when the build ships, or if you have a licence and are waiting for it. Just the address and which page it came from. It buys exactly one email. If you unsubscribe, the address is kept marked do-not-email until that email has gone out, so it cannot be sent to you by mistake, and then deleted with the rest of the list. |
| Abuse-prevention counters | How many times one network address has recently tried to sign in, reset a password or send a form, so that repeated attempts can be slowed down. The address is never stored: only a one-way scrambled code made from it, which cannot be turned back into the address. Counters are deleted once they are a day old. |
Why we are allowed to
- To provide what you signed up for: your account, your licence, its machines and its model time. Without these there is no service to give you.
- Because you said yes: counting visits, and the release email if you asked for it. Take either back whenever you like, from cookie settings or the unsubscribe page.
- Because we have a reasonable need to, weighed against yours: answering a message you sent, telling a licence holder their download is ready, and slowing down repeated sign-in attempts.
- Because the law requires it: keeping billing records, once there are any.
What the desktop application sends
The Windows application talks to us to activate, to re-check that your licence is still valid, and to report how many model tokens a run consumed. Your game project is never uploaded. The application reads it on your machine and sends only what a request needs.
Where a generation request goes depends on whose key pays for it, and this is the one part of this page worth reading twice.
- On your own provider API key. The request goes from your machine straight to the model provider. It does not pass through us and we never see it.
- On the model time in your plan. The request comes through our service, because the account paying for it is ours. That means your prompt, your field names and the handful of your objects the request needs do pass through our servers on the way to the model provider. We use them to answer that request and to count its tokens, and for nothing else: not to train anything, not to build a collection of our own, and not to look at unless you ask us to help with a specific run. We keep the token counts, which are numbers. We do not keep the content.
Image renders work the same way. A render is a short description of one object, built from its fields, sent to Google’s image model to draw. On your own Gemini API key it goes from your machine straight to Google. On the model time in your plan it comes through our service to Google, and we treat it exactly as above: used to draw that picture and count its tokens, the counts kept, the description and the picture not.
If you would rather no request of yours ever reached us, use your own provider key, and your own Gemini key for renders. That option is not going away, and choosing it does not cost you anything beyond the provider’s own bill.
Who else processes it
- Neon hosts the database, in the region chosen for the project.
- Vercel hosts this website and runs its server code. If you say yes to counting visits, it also counts page views and measures load times: no cookie, no device identifier, and nothing that follows you to another site.
- Resend sends confirmation, password-reset and receipt email.
- The model provider answers generation requests made on the model time in a plan, as described above.
- Google confirms who you are if you use Google sign-in, and draws image renders made on the model time in a plan, from the render description alone, as described above.
These providers act on our instructions and are given your data only to do the job named above. They run their services mainly in the United States and the European Union, and the business is run from Lebanon, so your data may be handled in any of those places.
How long we keep it
Account data lasts as long as the account. Delete the account and it all goes at once: the account, its sessions, its licence, its machines, its usage, and any message or release-list entry under the same address. Messages from people without an account are kept while they are useful to answer and reviewed periodically. The release list is deleted once the email it exists for has been sent.
Billing records are the exception. Invoices and payment records are kept by us for as long as tax law requires, which is several years, and they survive an account deletion. That is not a choice we get to make: a business has to be able to show what it was paid and by whom.
Children
Object Forge AI is a tool for making games, not a game, and nothing here is aimed at children. You must be 16 or older to create an account, and sign-up asks you to confirm it. If we learn that we hold data about somebody younger, we delete it.
Your rights
Delete your account yourself, at the bottom of your account page. Without an account, ask on the delete your data page. You can also ask for a copy of what we hold, or ask us to correct it, and you can take back any yes you have given at any time.
If you are in the UK or the European Economic Area you have these rights under the GDPR, and you may also complain to your national data protection authority. Californian residents have equivalent rights under the CCPA; we do not sell or share personal information as it defines those words. Write to sales@objectforge-ai.com and we will answer within 30 days.
Cookies
None, unless you sign in; then one, to keep you signed in. The cookie policy lists each one by name.
Changes
If this policy changes in a way that matters, account holders are told by email before it takes effect, and the date at the top of this page changes.