Privacy Policy

Awaken (“Awaken”, “we”) is a browser-based 3D game editor at awaken3d.dev, operated by Ciarán McCormack. This policy explains what we collect, why, and how it is stored. It covers the website, the hosted editor at editor.awaken3d.dev, and the sign-in service.

Your projects stay on your machine

The Awaken editor runs entirely in your browser. Your projects are saved to your own disk through the browser’s File System Access API. We do not upload, store, or see your projects, scenes, or assets. You can use the editor fully without an account.

Usage statistics

The hosted editor sends usage statistics to Raiblin’s own server, so we can see which parts of the editor people use and fix what breaks. We use them only for statistics: never to build a profile of you, never to find out who you are, never to track you across sites, and we never share or sell them. Each report holds:

• a random install ID, made in your browser the first time the editor opens, not linked to you or your account, and replaced with a new one every 13 months;
• the editor’s version and whether it is the released editor or a development build, and whether the browser is on a phone, a tablet or a desktop, and the browser’s name, main version and operating system (such as Chrome 141 on Windows), never its full identifying text;
• where the visit came from: the domain of the site that sent you (such as google.com), or the campaign tag on the link you followed, never the full address. When you open the editor from awaken3d.dev, this site passes that on in the link; it keeps it only for that browser tab and sends it nowhere itself;
• what happened and when: the editor started (and whether your browser supports WebGPU), a project was opened, or the Open picker was closed without choosing a file, an import ran (the file format, how many files, whether it worked and why not, and for a zip or folder how many files it brought in or skipped and the skipped files’ extensions, such as psd), Play was pressed, a script was edited, an export ran (how it ended: a file written, the save dialog closed, or why it stopped, with the error’s message when there was one), a store package was installed, an item on the Welcome page was used (such as a template, a docs link or a first-steps check, never a project name), an Email us link or button was used and where it was (such as the Help menu or a failed export), never what the email says, and the editor reloading or asking you to save first because it was updated while open, and on a phone, that the screen pointing you to a computer was shown and whether you sent yourself the link (and whether by sharing or by email) or opened the editor anyway;
• how long each session lasted;
• errors the editor hits: the kind of error, its message, where in the editor’s code it happened, and whether your browser was showing the page translated.

They never hold your projects, scenes, assets or scripts, file or asset names, your name, your email address, your account, or your IP address.

The server runs on Vercel. It holds new reports in Vercel Blob, Vercel’s private file storage, until they move into a Neon database, which happens every day, all in the USA. It does not store your IP address. Vercel keeps standard request logs, which do include it. We keep each report for 25 months, then delete it.

To turn this off, switch off Usage stats in the editor, under File, Editor Settings. The editor then deletes the install ID and any reports not yet sent, and sends nothing more.

Emails you send us

An error the editor shows has an Email us this errorbutton. It writes an email in your own mail app, and copies the same text to your clipboard, holding the error, the editor’s version, your browser’s full user agent and version, your operating system and its version, your screen size, CPU thread count and memory, your GPU’s name, and how many objects and assets the open project has (never its name or contents). Nothing is sent until you send that email yourself, and you can read and change it first. We use what you send only to answer you and to fix what went wrong, and we keep it in our mailbox.

What we collect, and only when you sign in

Signing in is optional. It is required only to publish plugins or packages, and to buy or download paid assets from the store; free assets download without an account. Sign-in uses GitHub or Google. We never handle passwords. When you sign in, we receive from your chosen provider:

• your provider account ID (the stable identifier we key your account on);
• your email address, where the provider supplies a verified one;
• your username or handle, used as your display name.

We request the scopes read:user user:email from GitHub andopenid email profile from Google. We do not read your repositories, files, contacts, or any other data.

Why we collect it

The account identifies you so that plugins and packages you publish are attributed to you, and so the store and registry can gate publishing and paid purchases to a signed-in user. If you never sign in, none of this data exists for you.

How it is stored

Account records are stored in MongoDB Atlas. When you sign in we issue a session token, signed with our own key; the database keeps only a hash of that token, never the token itself. Sessions expire automatically.

Cookies

We set one session cookie (awaken_session) on .awaken3d.dev so a single sign-in covers the editor, store, and docs, and a short-lived cookie during the sign-in exchange itself. Both are strictly necessary for sign-in. The editor also sets a cookie, __vdpl, holding the ID of the editor version it opened, so an open editor keeps loading its own files after we release a new version. It is sent only with requests for the editor’s code files, holds nothing about you, expires after 7 days, and is strictly necessary for the editor to work. The usage statistics install ID is kept in your browser’s local storage, not in a cookie. We do not use advertising or third-party tracking cookies.

Who we share it with

We do not sell your data and do not share it for advertising. Data is processed by our infrastructure providers acting on our behalf: MongoDB Atlas (account database), Vercel (hosting and Vercel Blob storage) and Neon (usage statistics database). During sign-in you interact directly with GitHub or Google under their own privacy policies.

Retention and your choices

We keep your account record until you ask us to delete it. Session records are removed automatically when they expire. Usage reports are deleted 25 months after they arrive. To access or delete your data, email awaken3d@raiblin.com and we will action it.

Changes

If this policy changes we will update the date above. Continued use after a change means you accept the updated policy.

Contact

Questions about this policy: awaken3d@raiblin.com.

← Back home