Privacy policy

Who runs this site

• Legal name: February Solutions, MB
• Company code: 308104153
• Country: Lithuania
• Contact: hello@realenginesimulator.com

That company is the data controller for everything described below.

1. What we collect

• What you send us. The feedback and partnership forms ask for a name, an email address and a message; the partnership form also asks for your site and a rough audience size.
• Usage. Pages viewed, which engine was opened, and events like starting an engine or running a dyno sweep, with the device and browser details your browser reports and an approximate location from your IP address. Our host keeps short-lived request logs; a form submission is stored with its IP address and user-agent as an anti-abuse measure. Opening or running an engine on the community pages is counted once a day per account; its builder sees how many, never who. On some visits the simulator also measures how smoothly it draws: frame times and draw counts, with the graphics chip reduced to its maker’s family (Intel, Apple and the like) and the processor and memory to coarse ranges.
• Your account, if you make one. The email address you sign in with, or, if you choose Google, the email address and name Google shares with us; when you last signed in; and whether you have opted out of our emails. We keep the engines you save, with the names you give them.
• Engines you share, if you do. Submitting an engine to the community stores it with the name and notes you give it, the builder handle you pick, and the figures we measure from it. We review every submission. Once we approve one, the engine, its name, your notes and your handle are shown to signed-in subscribers; it is listed only while your account is on a paid plan. Everyone else sees only how many engines and builders are listed, by engine family. Your email address and account stay private.
• Your subscription, if you buy one. Polar, the merchant of record, holds your card, your billing address and your invoices; we never see your card. We keep your Polar customer id and whether the subscription is active and until when, so the site knows you are on Pro. If you type an email before paying without an account, we pass it to Polar to fill in the checkout, and afterwards read back from Polar the email you paid with so the sign-in form can offer it; we store neither.
• Your browser. Your browser stores the engine you built, the email you typed before checkout (for a week at most, with an unpaid build), your survey progress and, once you sign in, your session token. None of it reaches us on its own. Clearing site data removes all of it.

Analytics never receives the simulator’s own URL parameters. A shared engine link carries your whole build in the query string; we send the page path and standard UTM tags, nothing else. There is no session recording and no heatmap on this site.

2. Cookies

There are no adverts on this site and no advertising cookies. Nothing here follows you to another site or builds a profile for anyone to sell. What is left is analytics, and your browser’s memory of what you were doing.

Analytics

Google Analytics and PostHog each store an identifier to tell a returning visit from a new one. We switch off Google Signals and ad-personalisation signals, so Google cannot use analytics from this site to build advertising audiences. Block every cookie and you lose the saved build and nothing else. The simulator needs none of them to run. When you sign in, this browser’s analytics history is linked to your account id so we can see what signed-in people use; it is never linked to your email address.

3. Why we use it

• Running the site and defending the forms against abuse. Legitimate interests.
• Replying to you when you write in. Legitimate interests, and your own request.
• Understanding usage so we know what to build. Consent where local law requires it for the storage involved, legitimate interests otherwise.
• Running your subscription: knowing you are on Pro, and keeping the builder open to you. Performance of the contract.
• Showing the engines you share to subscribers, and telling you how often they are opened and run. Performance of the contract, and legitimate interests.
• Telling you about the simulator, if you have an account. Legitimate interests, as somebody who already uses it; consent where the law asks for it. See the next section.

Emails we send

We send two kinds. Service emails keep your account working: the sign-in link or code, replies to what you write to us, and a personal request for your feedback, for example after you cancel a subscription. You get these for as long as you have an account and use the site; there is no opting out of them.

Marketing emails. If you have signed in, we may email you about the simulator: new releases, discounts and the like. Every one carries an unsubscribe link, and one click ends them; you can also opt out by writing to us. Opting out never affects the service emails or your account. To choose who gets which, our mailing list holds your plan, whether a subscription is active or set to end, its length and renewal date, and when you last visited.

4. Who else handles it

These providers process data on our instructions, under contract. None may sell it, and we do not sell it either.

• Google. Analytics measures traffic; and, only if you choose it, sign-in.
• PostHog. Product analytics: which engines people run, which features they use; our server also reports purchases and engines shared to the community, keyed to the account.
• Vercel. Hosting and content delivery, including request logs.
• Supabase. Sign-in (it sends the sign-in email and holds the account) and the database holding form submissions, saved engines, and shared engines with their handles and visit counts.
• Resend. Emails a copy of each submission to us, and carries the emails we send you.
• Plunk, Railway and Amazon Web Services. Plunk keeps our mailing list: your email address, account id, plan, subscription standing, length and renewal date, and when you last visited. We run it ourselves on Railway’s servers, and Amazon SES delivers the emails it sends.
• Polar. Takes the payment for Pro, issues the invoice and handles the tax, as the merchant of record under its own privacy policy. It tells us your customer id and whether the subscription is active.

Submitting the feedback form attaches the email address you gave to that browser’s analytics history, so we can match your report to the session it describes. Write to us by email instead if you would rather we did not. We also disclose data where the law requires it.

5. Where it goes, and for how long

Those providers process data in the European Union and the United States. Where personal data leaves the EEA it moves under the European Commission’s Standard Contractual Clauses or an adequacy decision.

• Form submissions. While the request is still useful. We review them at least once a year, and delete yours sooner if you ask.
• Account and saved engines. Until you delete them, or ask us to. We may close an account nobody has signed into for two years; we email first, and we never close a paid-up Pro subscription this way.
• Shared engines and their counts. Until you withdraw the engine or delete your account; withdrawing deletes its counts with it.
• Your opt-out. After you unsubscribe we keep the fact that you did, so we do not email you again by mistake.
• Subscription record. While the account exists; Polar keeps invoices for as long as tax law makes it.
• Analytics. Our providers’ standard schedules, up to 14 months for Google Analytics event data.
• Server logs. Short-lived, operational use only.
• Browser storage. Until you clear it. It never reaches us, so we cannot clear it for you.

6. Your rights

You can ask for a copy of the personal data we hold about you, ask us to correct or delete it, restrict or object to how we use it, or ask for it in a portable form. Where we rely on consent you can withdraw it at any time, and you can object to our emails at any time: the link in each one does it. Email hello@realenginesimulator.com and say what you want, including deleting your account and every engine in it. We answer within a month, and a person reads it. If you think we have got it wrong you can complain to your data protection authority; ours is the State Data Protection Inspectorate of Lithuania (vdai.lrv.lt).

7. Children and security

Plenty of the people reading this site are students. We do not knowingly collect personal data from children under 16, and nothing on the site asks for any. If you think a child has sent us personal data through a form, write to us and we will delete it.

The site is served over HTTPS, and submissions and saved engines are written to a database reachable only from our server-side code, with no public read access. Accounts have no password to leak: you sign in with a one-time link or through Google, and the session lives as a token in your own browser. Card details go to Polar over its own checkout page and never touch our servers.

8. Changes and contact

The date at the top says when this page last changed. We announce a change that matters to what we collect or why on the site, and, if you have an account, by email before it takes effect. Questions about any of it: hello@realenginesimulator.com, or the contact page.