Legal

Privacy policy

Horizon is a game engine that runs in your browser, an editor for building games, and a launcher for playing them. All three need an account, and an account means personal data. This document says exactly which data, why we hold it, who else sees it, how long it stays, and what you can demand from us.

It is written to be read, not to be survived. Where a section describes something technical, it describes what the software actually does.

Last updated In force since

1.The short version

The detail matters and the rest of this page provides it, but if you read only one section, read this one.

  • We sell nothing and we track nothing. Your data is not sold, rented, or shared with advertisers or data brokers. We run no advertising network, no analytics product, and no cross-site tracking.
  • There is no cookie banner because there are no tracking cookies. We set exactly one cookie, and it is the one that keeps you signed in.
  • We never see your card details. Payments go through Stripe, on Stripe pages. Card numbers never reach a Horizon server.
  • Your password is never stored. Only a bcrypt hash of it is, which cannot be reversed back into your password.
  • Your session token is unreadable by JavaScript. It lives in an httpOnly cookie, so even a cross-site-scripting bug on our own site cannot walk off with your session.
  • You can get your data out, or have it deleted. Email us and we act within one month. Section 15 lists every right you have and section 16 is honest about the limits of deletion.

2.Who is responsible for your data

Horizon is an end-of-studies innovation project (EIP) built by a student team at Epitech Paris. The team acts as the data controller for the personal data described here, within the meaning of Article 4(7) of the General Data Protection Regulation (Regulation (EU) 2016/679, the GDPR).

Our full identification details, including the publication director, appear in the legal notice.

Contact for anything in this document, including to exercise your rights: contact@play-horizon.games.

3.What this policy covers

This policy applies to the services we operate at the following addresses:

  • play-horizon.games — this website and its documentation.
  • editor.play-horizon.games — the Horizon Editor.
  • api.play-horizon.games — the API gateway all of the above talk to.
  • The Horizon launcher and the games published through it.

It does not apply to services we do not control. Games published by other users are their content, and Stripe, Google and the other recipients named in section 9 run their own policies for the parts they handle.

4.What we collect and why

Every category below is data the software genuinely stores. There is no catch-all “and any other information we may collect” clause, because a list you cannot verify is worthless.

Data you give us

CategoryWhat it containsWhy we hold itLegal basis
Account identityUsername (public), email address, account creation date, email-verification status, avatar image URL.Create and run your account, identify you to other users, contact you about the service.Performance of a contract — art. 6(1)(b)
Authentication dataA bcrypt hash of your password — never the password itself. If you sign in with Google, your Google account identifier instead. A hashed six-digit email verification code and its expiry, cleared once used.Sign you in, and confirm your email address is real so accounts cannot be opened in someone else's name.Contract — art. 6(1)(b); security obligation — art. 32
Wallet and entitlementsYour coin balance, the games you have purchased, the games you have favourited.Give you access to what you bought and keep it available across sessions.Contract — art. 6(1)(b)
Payment recordsStripe checkout session identifier, amount, currency, status and date. No card number, and no CVC, ever.Take payment, credit your coins, keep accounts, and handle disputes and chargebacks.Contract — art. 6(1)(b); accounting obligation — art. 6(1)(c)
FriendsLinks between your account and the accounts you are friends with, and the friend invitations you sent or received that are still waiting for an answer.Run the social features you chose to use.Contract — art. 6(1)(b)
Documentation comments and ratingsComment text, star rating, the username shown as author, upvotes you cast.Run the community documentation and show which answers are useful.Contract — art. 6(1)(b)

Data created by using the editor

CategoryWhat it containsWhy we hold itLegal basis
Projects and scenesYour scene documents and their full edit history. Because the scene is a conflict-free replicated document, each change is stored as an operation attributable to its author, and compacted snapshots are signed server-side.Store your work, sync collaborators in real time, and let you step back through the version history.Contract — art. 6(1)(b)
Uploaded assetsMeshes, textures and scripts you import, converted to the engine formats, plus thumbnails rendered from them. Stored content-addressed: identified by a hash of their bytes rather than a filename.Serve your assets to the editor and to players, and avoid storing the same file twice.Contract — art. 6(1)(b)
Published gamesTitle, description, cover image, tags, price, publication state, the pinned version hash, and the current number of players.Publish your game, run it for players, and show it in the launcher.Contract — art. 6(1)(b)
AI assistant requestsThe prompt you type and the script graph you are working on, when you ask the no-code assistant for help.Produce the answer you asked for. See section 10.Contract — art. 6(1)(b)

Data collected automatically

CategoryWhat it containsWhy we hold itLegal basis
Connection and security dataYour IP address, the time of the request, the endpoint called, the response status, and browser-supplied request headers such as the user agent.Enforce rate limits (a sliding window per IP, tightened on login and signup endpoints), detect and stop abuse, investigate incidents, and debug faults.Legitimate interests — art. 6(1)(f); legal obligation — art. 6(1)(c) and art. 6-II LCEN
Server and error logsTechnical records produced by the gateway and the services when handling requests, including error traces.Keep the service running, diagnose bugs, and maintain an audit trail for security.Legitimate interests — art. 6(1)(f)

5.What we deliberately do not collect

It is as useful to know what is absent. We do not collect, and the software has no code path to collect:

  • Payment card numbers, expiry dates or security codes. Those are entered on Stripe's pages and never transit our servers.
  • Advertising or cross-site tracking identifiers, ad-network pixels, or fingerprinting signals.
  • Analytics on your browsing. No analytics or product-telemetry service is active on this site.
  • Precise geolocation. We do not request location permission anywhere.
  • Special-category data under art. 9 GDPR — health, ethnicity, political opinions, religious beliefs, trade-union membership, sex life or sexual orientation. We never ask for any of it; please do not put it in a comment or a game description.
  • Biometric data, and no facial or voice recognition of any kind.
  • Contact lists, calendars, microphone or camera input.
  • Your password in a form anyone, including us, can read.

7.Cookies and browser storage

We set one cookie. It is strictly necessary to keep you signed in, which is why you are not asked to consent to it: art. 82 of the French Data Protection Act exempts storage strictly necessary to provide a service the user requested.

NameSet byPurposeLifetime
access_tokenThe Horizon API gatewayHolds your signed session token. Flagged httpOnly so no JavaScript can read it, Secure so it only travels over HTTPS, and SameSite=Lax so it is not sent on cross-site requests.24 hours, then it expires and you sign in again

Data stored in your browser, not on our servers

The site also keeps a few values in your browser’s local storage. These never leave your device, we cannot read them remotely, and you can erase them at any time by clearing site data.

KeyWhat it holdsWhy
authDataA copy of your display details: your account id, username and email address.So the header can offer your account without a round trip. These are display hints only — they grant no access, and editing them grants nothing. Every authorisation decision is made server-side from the session cookie.
horizon-themeDark, light, or follow the system.So the site does not flash the wrong theme on load.
horizon-cookie-noticeThat you have read the notice about this storage.So the notice is shown once rather than on every visit.

8.What other people can see

Some of what you create is public by design. Be deliberate about it, because we cannot un-publish something from other people’s memories or from search engines that indexed it.

Visible to everyoneVisible to signed-in usersNever public
Your username; games you publish, with their title, description, cover, tags and price; documentation comments and ratings you post, shown next to your username.Your avatar; your friends list to the people concerned; your presence in a shared editing session, including which objects you are moving.Your email address, your password hash, your coin balance, your purchase history, your unpublished projects and scenes, and your AI assistant prompts.

A game you publish is a game other people play. Do not put personal information about yourself or anyone else into a game description, a scene, an asset filename or a comment.

9.Who else receives your data

We use a small number of external providers, each for one clearly bounded job. They receive only what that job needs. Most act as processors under Article 28 GDPR, meaning they may only process the data on our instructions.

RecipientWhat it doesWhat it receivesLocation
Stripe Payments Europe, Ltd. (Ireland), with Stripe, Inc. (United States)Processes coin purchases and handles the payment page.Your email address, the amount and currency, and the card details you enter directly on Stripe's own form. We receive back only the session reference and its status.Ireland / United States
Google Ireland LimitedProvides "Continue with Google" sign-in, when you choose it.Only what you authorise at the Google consent screen: your Google account identifier, email address and profile picture. Google is an independent controller for your Google account itself.Ireland / United States
Google (Gmail SMTP)Delivers the transactional emails we send — principally your verification code.Your email address and the content of that message.Ireland / United States
OpenRouter, Inc.Routes no-code assistant requests to a language-model provider. See section 10.The prompt and the script graph you submit to the assistant. Nothing else, and no account identifier.United States
CloudflareDNS and content delivery in front of the public web domains.Connection metadata for requests it proxies, including your IP address.European Union / United States
Hosting provider — name, address and telephone numberProvides the server, storage and backups on which the whole service runs.Technically, all service data at rest. Contractually, none of it may be accessed except as needed to operate the infrastructure. country

Other disclosures

  • To a court, a regulator or law enforcement, where a valid and binding legal request compels it. We check that requests are lawful and properly scoped, and we disclose the minimum required.
  • To defend a legal claim, where strictly necessary to establish, exercise or defend it.
  • To a successor, if the project is ever transferred to another entity. You would be told before any transfer of your data takes effect, and this policy would continue to apply until replaced.

We do not sell personal data, we do not rent it, and we do not share it for anyone else’s marketing.

10.The AI assistant

The no-code editor has an assistant that can read the script graph you are working on and propose a graph back. It deserves its own section, because unlike the rest of the service it sends your content to a third party.

  • It runs only when you ask it to. Nothing is sent to any model while you are simply editing.
  • What is sent is your prompt and the script graph in question, forwarded by our server to OpenRouter, which routes it to a model provider.
  • We do not attach your username, email or account identifier to the request.
  • Model credentials stay on our server. Your browser never holds an API key.
  • We do not store your prompts to train anything. We have no model of our own and we do not train one.
  • OpenRouter and the model provider it selects apply their own retention to the request in transit. We cannot guarantee what a downstream provider retains.

11.Transfers outside the EEA

Our own servers and storage sit within the European Union. Some of the recipients in section 9 are established in, or transfer data to, the United States.

Where that happens, the transfer is covered by one or more of the safeguards Chapter V of the GDPR requires: the EU–US Data Privacy Framework adequacy decision of 10 July 2023, where the recipient is certified under it, and otherwise the European Commission’s Standard Contractual Clauses.

You may ask us for a copy of the safeguard relied on for a specific recipient, and we will provide it or point you to the provider’s published terms.

12.How long we keep things

We keep data only as long as the purpose requires, then delete it or anonymise it. The periods below are the ones we apply.

DataKept forWhy that long
Account identity and authentication dataThe life of your account, then up to 30 daysThe short tail covers accidental deletion and lets backups roll over.
Email verification code24 hours, or until usedIt is a single-use code; keeping it longer only creates risk.
Projects, scenes, edit history and assetsThe life of the projectIt is your work. History is compacted into signed snapshots over time, so the oldest individual operations stop being individually retrievable.
Published gamesUntil you unpublish or delete themOther people are playing them.
Documentation comments and ratingsUntil you or we delete themThey are part of a shared knowledge base others rely on.
Coin balance and entitlementsThe life of your accountYou paid for them.
Purchase and accounting records10 years from the end of the financial yearRequired by art. L123-22 of the French Code de commerce; survives account deletion as a legal obligation.
Rate-limiting counters60 secondsThe sliding window is one minute long. Nothing persists past it.
Connection and security logs12 months maximumLong enough to investigate an incident, and within the period expected of a hosting provider under art. 6-II LCEN.
AI assistant promptsNot retained by us after the responseWe have no reason to keep them. Downstream provider retention is outside our control.
Support correspondence3 years from our last exchangeSo we have context if you write again, and as evidence if a dispute follows.

13.How we protect your data

Article 32 GDPR requires measures appropriate to the risk. These are the ones actually in place, rather than a list of aspirations.

Credentials and sessions

  • Passwords are hashed with bcrypt, a deliberately slow algorithm with a per-password salt. We cannot recover your password, and neither can anyone who obtains the database.
  • Your session token is held in an httpOnly, Secure, SameSite cookie. JavaScript cannot read it, so a cross-site-scripting flaw cannot steal your session.
  • Sessions expire after 24 hours.
  • Email addresses must be verified with a single-use six-digit code before an account becomes usable, so an account cannot be opened on someone else's address.

Architecture

  • Every frontend talks to a single API gateway, which owns authentication, cross-origin rules and rate limiting. There is one place to get those right rather than four.
  • The gateway strips the internal identity header from every inbound request and sets it itself, so a client cannot claim to be another user by sending that header.
  • Login and signup endpoints carry a tighter rate limit than the rest of the API, which blunts credential-stuffing and brute-force attempts.
  • The database, the object store and the internal services publish no ports to the internet. They are reachable only from inside the private network.
  • All public traffic is served over HTTPS, with certificates issued and renewed automatically.
  • Assets are content-addressed by a cryptographic hash and signed with Ed25519 keys, so a client can verify that the mesh it loaded is the one our pipeline produced and not something substituted in transit.
  • Administrative access to the server is by SSH key only; password authentication is disabled.
  • Configuration secrets are supplied through the environment and are absent from the source repository.

No system is perfectly secure, and we will not claim otherwise. If you believe you have found a vulnerability, please tell us at contact@play-horizon.games before disclosing it publicly. We will not pursue anyone who reports a flaw in good faith, without accessing other users’ data and without degrading the service.

14.If there is a data breach

If a breach of personal data occurs, we will contain it, assess the risk it creates for you, and record it in our breach register.

  • Where the breach is likely to result in a risk to your rights and freedoms, we notify the CNIL within 72 hours of becoming aware of it, as art. 33 GDPR requires.
  • Where it is likely to result in a high risk to you, we will tell you directly and without undue delay, in plain language: what happened, what data was involved, what we have done, and what you should do (art. 34 GDPR).
  • If we cannot identify everyone affected individually, we will publish a notice on this site.

15.Your rights

Under the GDPR and the French Data Protection Act you hold the rights below over your own data. They are free to exercise, and using them will never cost you access to the service.

RightWhat it lets you doWhere it comes from
AccessAsk what we hold about you and get a copy of it, together with the information in this policy.art. 15
RectificationHave inaccurate data corrected and incomplete data completed. You can change most of it yourself from your account page.art. 16
ErasureHave your data deleted where we no longer need it. Read section 16 — some of it cannot go, and we would rather tell you now than after you ask.art. 17
RestrictionHave us pause processing while a dispute about accuracy or lawfulness is resolved.art. 18
PortabilityReceive the data you gave us in a structured, machine-readable format, and have it sent to another provider where technically feasible.art. 20
ObjectionObject to processing based on our legitimate interests. We stop unless we can show compelling grounds that override your interests.art. 21
Withdraw consentTake back a consent you gave, at any time, without having to justify it.art. 7(3)
Not be subject to automated decisionsNot have a decision with legal or similarly significant effects made about you by automated means alone. We make none — see section 17.art. 22
Post-mortem directivesDecide in advance how your data should be handled after your death, and appoint someone to carry that out.art. 85, French Data Protection Act

How to use them

  1. Write to contact@play-horizon.games, saying which right you are exercising and which data it concerns.
  2. We reply within one month. If the request is complex we may extend that by up to two further months, and we will tell you why within the first month (art. 12(3)).
  3. If we have genuine doubt about who is asking, we may request additional information to confirm your identity — never more than necessary, and never a copy of an identity document unless there is no other way (art. 12(6)).
  4. If we refuse, we will say so, explain why, and tell you how to complain. We will not simply go quiet.

16.What deleting your account actually does

Most privacy policies stop at “you may request deletion”. Here is what actually happens, including the parts that are imperfect.

What is removed

  • Your account record, with your email address, password hash, Google identifier, avatar and verification state.
  • Your scenes and your games, which are deleted together with the account by design.
  • Your membership of other people's friends lists, from which you are pulled automatically.

What does not go, and why

  • Purchase and accounting records. Kept for ten years under art. L123-22 of the Code de commerce. This is a legal obligation and art. 17(3)(b) GDPR permits it. They are kept for accounting only, and are not used for anything else.
  • Documentation comments. These are not deleted automatically with the account today. Ask us and we will delete them or detach them from your identity — tell us which you prefer.
  • Shared assets. Assets are stored by a hash of their content, so one set of bytes is stored once however many people uploaded it. If another user independently imported an identical file, the stored blob remains for them. Your link to it is removed.
  • Collaborative edit history. Where you contributed to a project someone else owns, the operations you made remain part of that project’s history, because removing them would corrupt work that is not yours. Ask us and we will detach your name from them.
  • Backups. Data persists in backups for a short period after deletion, and is overwritten as they rotate. We do not restore a backup to recover deleted personal data.
  • Security logs. Retained for their period in section 12, as art. 17(3)(b) and (e) permit.

17.Profiling and automated decisions

We make no decisions about you by automated means alone that would have legal or similarly significant effects. We do not profile you, we do not score you, and we do not build behavioural segments.

Two automated mechanisms do exist, and neither is a decision about you within the meaning of art. 22: rate limiting, which may temporarily refuse requests from an IP address making too many in a minute, and content moderation, which may flag content for review. Where moderation leads to an actual decision about your account or your content, a human takes it, we give you reasons, and you can appeal — see the terms of use.

18.Children and young users

Horizon is not intended for young children. You must be at least 15 years old to create an account on your own, which is the age France sets under art. 8 GDPR and art. 45 of the French Data Protection Act.

  • Between 15 and 18, you may use Horizon yourself, but purchases should be made with your parent's or guardian's agreement.
  • Under 15, an account may only be created with the verifiable consent of a parent or guardian, given jointly with you.
  • Under 13, do not create an account.

If you are a parent or guardian and believe your child holds an account they should not, write to contact@play-horizon.games. We will verify the situation and delete the account and its data promptly. We do the same on our own initiative whenever we learn an account holder is below the age required.

19.Beta status

20.Changes to this policy

We will update this policy when the service changes or the law does. The version in force is always the one on this page, with its date at the top.

  • For a minor change — clearer wording, a corrected address, a renamed field — we update the page and move the date.
  • For a substantive change — a new purpose, a new recipient, a longer retention period, a new legal basis — we will notify you before it takes effect, by email or by a notice in the product, and give you at least 30 days.
  • If a change relies on your consent, it will not apply to you until you give it.

We keep earlier versions and will send you the text that applied on a given date if you ask.

21.Contact and complaints

Any question about this policy, or any request about your data:

Complaining to a regulator

If you are not satisfied with how we handled your request, you can lodge a complaint with a supervisory authority. Ours is the French CNIL, and you may also complain to the authority where you live or work (art. 77 GDPR).

Commission Nationale de l’Informatique et des Libertés — 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France. Telephone +33 1 53 73 22 22. cnil.fr

You also have the right to an effective judicial remedy against us or against a supervisory authority (art. 78 and 79 GDPR). Please do write to us first — most things are faster to fix directly.

The rest of the legal set

These documents are meant to be read together. Where they overlap, the more specific one governs its own subject matter.