Privacy policy

Last updated

This policy explains what realenginesimulator.com collects, why, and how to switch the optional parts off. There are no accounts here. You can run every engine on the site without telling us anything about yourself.

Who runs this site

  • Legal name: February Solutions, MB
  • Company code: 308104153
  • Country: Lithuania
  • Contact: grybukasltu@gmail.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.
  • Your browser. Your browser stores the engine you built, and a counter behind the “buy me a coffee” prompt. Neither reaches us. Clearing site data removes both.

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 and advertising

Third-party vendors, including Google, use cookies to serve ads based on a user’s prior visits to this website or other websites. Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the internet.

You may opt out of personalised advertising by visiting Google Ads Settings, or opt out of other vendors’ use of advertising cookies at aboutads.info. Google explains how it uses data from sites that use its services here.

In the EEA, the UK and Switzerland we ask for your consent before setting personalised advertising cookies, and you can change that choice whenever you like. Decline and you get non-personalised ads instead.

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.

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.
  • Advertising, which pays for the hosting. Consent for personalised ads in the EEA, the UK and Switzerland; legitimate interests for non-personalised ads.

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. AdSense serves and measures the adverts; Analytics measures traffic.
  • PostHog. Product analytics: which engines people run, which features they use.
  • Vercel. Hosting and content delivery, including request logs.
  • Supabase. The database holding form submissions.
  • Resend. Emails a copy of each submission to us.

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.
  • 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. Email grybukasltu@gmail.com and say what you want. 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 are written to a database reachable only from our server-side code, with no public read access. There is no account system here, so there is very little to steal.

8. Changes and contact

When what we collect changes, this page changes with it and the date at the top moves. Questions about any of it: grybukasltu@gmail.com, or the contact page.