Privacy

This notice covers loop.loop808.nl — the dashboard itself, everything it stores, and every request it makes on your behalf. It does not cover Roblox. Once you follow a link out to Roblox, or once Roblox is asked for a figure, what Roblox does with that request is governed by their privacy policy, not this one.

Loop is an independent tool. It is not affiliated with, endorsed by or operated by Roblox Corporation.

Loop is run by one independent Roblox developer, established in the Netherlands. Under the GDPR that makes them the controller for everything described here: one person, one server, one database, and no company behind it.

Everything in this notice is answered at loop808contact@gmail.com. There is no data protection officer, because a one-person service is not required to appoint one and appointing a fictional one would be worse than saying so.

You sign in with Roblox, through their OAuth 2.0 flow, and Loop asks for two permissions only — openid and profile. What Roblox hands back, and all that is stored from it, is:

• your Roblox user id, which is the account's primary key here;
• your username and display name;
• the URL of your avatar thumbnail;
• when you first signed in, and when you were last seen.

Those permissions cannot read your revenue, cannot see your friends or messages, and cannot act on your account. Nothing is ever posted to Roblox on your behalf.

Signing in is also how an account is created. There is no separate registration, no password and no email address — this site never asks for one and has nowhere to put it. If you write to the address above, that mail is in an inbox, not in this database.

Being signed in is one cookie, loop_session. It holds a random token and nothing else — no name, no id, nothing readable. It is HttpOnly so no script can reach it, SameSite=Lax so another site cannot make your browser send it, and Secure, because loop.loop808.nl is served over HTTPS.

The server does not keep that token. It stores a SHA-256 fingerprint of it, so a stolen copy of the database is not a list of sessions somebody can paste into their own browser. The Roblox tokens attached to the session are encrypted, because unlike the fingerprint those do get replayed to Roblox.

A session lasts 30 days, and that window slides forward while you use it. Signing out deletes the row immediately. During sign-in a second, ten-minute cookie (loop_oauth) carries the handshake and is then thrown away.

Each session also records the IP address and browser user-agent string it is being used from, refreshed while it is in use. Neither decides whether you are allowed in — binding a session to an IP would sign you out every time your phone changed cell tower. They are kept so that one account signed in from two countries in the same hour is something that can be seen, which nothing else in the database could show. They go when the session does.

You can see that list yourself, in Settings → Where you are signed in: every browser currently holding a sign-in to your account, with the address and device each was last used from, and a button to end any of them or all but the one you are reading this on. Ending one signs that browser out immediately and changes nothing else about your account.

The revenue, marketplace and transaction tabs need something the sign-in cannot provide, so they are optional and stay empty until you paste your .ROBLOSECURITY cookie into Settings yourself. Without it everything public still works — players, visits, ratings, and your own notes and plans.

If you do paste one: it is encrypted with AES-256-GCM before it is written, under a key held in the server's environment rather than in the database, and bound to your user id so it cannot be copied into another account's row and decrypted there. It is never sent back to your browser, never included in an export, and never sent anywhere but Roblox over HTTPS. Disconnect in Settings erases it and leaves everything else about your account alone.

It is the most sensitive thing this service will ever hold — a .ROBLOSECURITY is full access to a Roblox account, because Roblox offers no narrower key for these endpoints. Giving it is a deliberate act, and taking it back is one click. Nothing on this site nags you to provide one.

Everything you type is stored as you typed it, kept until you delete it, and scoped to your account — every query in this app is filtered by user id, and no tab has a way to read another account's rows:

• projects, their stages, owners and target dates, and their tasks;
• calendar events, with their dates, times and notes;
• notes;
• your team roster and the revenue split set against each member;
• ledger entries you add by hand, with their labels and amounts;
• the competitor watchlist;
• artwork uploaded to the Thumbnail Tester. Those are files on the server's disk, in a directory named for your user id, and deleting one moves it aside before it is removed.

Your display settings live here too: currency, DevEx rate, tax rate, and which groups and experiences you have chosen to show or hide.

With your account connected, the dashboard reads your groups, your experiences, their player and visit counters, their ratings, your Robux balances and — with a credential — your earnings and sales. Most of that is fetched when you open a tab and cached for about a minute, so that switching tabs does not re-run forty-odd calls to Roblox.

Three kinds of reading are kept rather than cached, because they are history Roblox does not keep for you:

• Daily snapshots — one row a day per experience: visits, players, votes and, if a credential is set, revenue. Roblox publishes running totals only, so a day-over-day trend has to be differenced from readings this service takes itself.
• Hourly concurrency — how many people were playing, averaged and peaked per hour. Counts, not people: nothing here identifies a player of your experiences, and this service never asks Roblox who they are.
• Competitor readings — the same public counters for the rival games on your watchlist, once a day.

Sales records are the one place another Roblox user's name appears: Roblox returns a purchase with the buyer's display name attached, and Revenue Intel shows it as Roblox sent it. Those records are fetched for the request that draws them and are not written to the database.

The team roster stores the names, roles and — if you fill it in — Roblox user ids of people who are not necessarily using this dashboard. So does anything you type about somebody in a note or a project.

This service cannot ask them whether they mind, and does not pretend to: for that data you are the one deciding what is collected and why. Enter what the studio's books need, tell them it is there, and delete it when it stops being relevant. If one of them writes to the address above about data you entered, they will be told to ask you, and — if they insist — that the row can be removed.

No other signed-in user, on any tab. Registration is open — anyone with a Roblox account can sign in, and gets their own empty dashboard — and none of them can see a row of yours.

Administrators can. Today that is the one person who runs loop.loop808.nl. It is stated plainly rather than buried, because it is the honest answer. An admin can:

• see the register of accounts — name, avatar, when each was created and last seen, and the IP and browser each live session is being used from;
• open one account's detail: what it owns, how much of it, and whether its Roblox connection is failing;
• export everything held about an account as a file (the credential is excluded from it);
• suspend an account, which ends its sessions and touches nothing it owns;
• delete an account and everything it owns.

Every one of those writes a row to the audit log naming the admin, the action, the account it was done to and the time. That log cannot be edited from anywhere in the app. Nothing is looked at as a matter of routine: the reasons are answering a request like yours, or a report that something is broken or being abused.

Nobody else is given access. There is no analytics provider, no error-reporting service, no advertising network and no processor holding a copy — the only companies in the picture are Roblox, the currency feed and whoever rents out the server, and only the first two receive anything (see below).

Three sets of rows are about the software rather than about you, and all three can name you:

• Errors — when a request or a Roblox call fails, the service stores what failed, the message, the status, and the user id whose request it was, so one broken account can be told from a broken site.
• Background job runs — what ran, when, how long it took and whether it worked.
• The audit log — the admin actions described above.

Errors and job runs are pruned on a schedule set in the admin panel. Audit rows deliberately are not, and deliberately survive the deletion of the account they name: “who deleted this account, and when” is exactly the record worth keeping, and one that cascaded away with its subject would delete itself first.

Two destinations, and no others.

• Roblox — the users, groups, games, economy, apis and thumbnails hosts on roblox.com, over HTTPS, to read the figures the dashboard shows. Your browser also loads game icons and avatars from Roblox's image CDN, which means Roblox sees those requests as it would on any site showing a Roblox thumbnail.
• An exchange-rate feed — api.frankfurter.app, falling back to open.er-api.com, asked once a day for the rates against the US dollar so a Robux figure can be shown in your currency. The request is the word “USD”. It carries no identifier, no cookie, and nothing about you or your studio.

Transfers outside the EEA. Roblox Corporation is a United States company, so a request made to Roblox on your behalf — and every thumbnail your browser loads from them — reaches the United States. That is inherent in a dashboard that reads Roblox, and it happens under Roblox's own terms and safeguards rather than under any arrangement this service could make. The currency feed is asked for a public exchange rate and is sent nothing about you.

The server and its database sit with one hosting provider, who can reach the disk in the sense that any host can. Which provider and which country can change if the service moves; ask at the contact address and you will be told what it is at the time.

Nothing is sold, rented or shared for anybody's marketing, here or anywhere. There is no business model that would want it.

Two cookies, both described above: the session, and the ten-minute sign-in handshake. Both are strictly necessary — they exist to deliver a service you asked for and to keep it secure, which is why there is no cookie banner. There is nothing to consent to, because there is no analytics or advertising cookie to refuse.

Your browser also keeps two preferences in local storage, purely so the app does not flash the wrong palette while it loads: the theme you chose, and whether you asked for square corners. They never leave your machine.

If you install the dashboard as an app, its service worker stores nothing — it exists only because browsers require one before offering to install.

• What you typed — until you delete it, or the account is deleted.
• Your account row — while the account exists.
• History and snapshots — indefinitely, because a year-old trend line is the point of recording them. They can be pruned on request.
• Sessions, with their IP and user-agent — 30 days from last use; expired rows are cleared as the app runs.
• Sign-in handshakes — ten minutes.
• Cached Roblox reads — overwritten by the next one, and droppable at any time.
• Errors and job runs — until pruned; they are diagnostic and there is no reason to keep them long.
• Audit rows — kept, as explained above.

Deleting an account removes every row it owns and the files it uploaded. What survives is the audit record that it existed and was deleted, plus error and job rows that may carry its user id — a number, with nothing left in this database to resolve it to.

• Credentials and Roblox tokens are encrypted at rest, under a key held outside the database.
• Session cookies are stored as fingerprints, never as the value the browser holds.
• Every write is checked to have come from this site, and the session cookie is SameSite so a browser will not attach it to another site's request.
• API responses are marked never to be stored by a proxy or a disk cache.
• The site is served over HTTPS only, refuses to be framed by another site, and asks browsers for no access to camera, microphone or location.

None of that is a guarantee, and a notice claiming otherwise would be worth nothing. If there is a breach affecting your data you will be told what happened and what to do about it, and where the law requires it the Autoriteit Persoonsgegevens will be notified within 72 hours.

If you think your Roblox credential has been exposed, disconnect it in Settings and log out of all other sessions on Roblox, which invalidates it everywhere at once. If you find a hole in this site, the contact address is also where to report it — it will be welcomed, not argued with.

The GDPR asks for a reason per purpose rather than one for the site, so here they are:

• Performing the service you asked for — your account row, your session, everything you type, and the Roblox figures fetched for your dashboard. You asked for a dashboard; this is what a dashboard is (Art. 6(1)(b)).
• Your Roblox credential — processed only because you chose to provide it, for the one purpose of reading your own figures. Withdraw it with Disconnect and the processing stops with it (Art. 6(1)(a)/(b)).
• Keeping the site working and unabused — error records, job runs, session IP and user-agent, and the audit log. A legitimate interest in security and in being able to diagnose a fault, which is why these are minimal, diagnostic and short-lived rather than a profile (Art. 6(1)(f)).
• The history it accumulates — daily snapshots and hourly readings, because a trend cannot be produced retrospectively and having it is the feature you signed in for (Art. 6(1)(b)).

No special-category data is asked for, and none of it is used for advertising, profiling or any automated decision that has an effect on you — there is no such mechanism in the code.

If the GDPR applies to you, you have the right to access what is held, to have it corrected, to have it deleted, to restrict or object to processing based on legitimate interests, to receive your data in a portable form, and to withdraw consent where consent is what allowed it.

Three of those you can exercise yourself, without asking anyone: edit or delete anything you typed, disconnect your credential in Settings, and sign out to end a session. For the rest, write to loop808contact@gmail.com naming the Roblox account — an export is a file containing everything held about it, and a deletion is the whole account and its files. Either is answered within one month, and neither costs anything.

You are also entitled to complain to a data-protection authority. In the Netherlands that is the Autoriteit Persoonsgegevens; if you live elsewhere in the EEA, your own national authority will do. Raising it here first is faster, but it is not a condition.

This is a tool for people running a studio, and it is not directed at children. Reaching it requires a Roblox account, whose age rules are Roblox's and are applied by Roblox.

If you are under 16, ask a parent or guardian before signing in — in the Netherlands that is the age from which you can agree to a service like this yourself. If it becomes clear that an account belongs to a child below that age without a parent behind it, it will be deleted rather than kept, and a parent can ask for exactly that at the address above.

This page ships with the software, so it changes when the software does — which is the point of writing it here rather than pasting a template. The date at the top is when the wording last changed, and it is set by hand rather than by the build, so it means what it says. If a change materially affects what is held about you or why, the notice will say so plainly rather than quietly moving a date.

Loop is run by one independent Roblox developer, established in the Netherlands, and reached at loop808contact@gmail.com. For anything about the data held on you — a copy of it, a correction, or deleting the lot — that address is the whole procedure. Say which Roblox account you mean, and expect an answer within one month.

There is no form to fill in and no ticket system, because there is no support department: it is one person reading that inbox. An admin can act on all three requests directly — the export writes out everything held about one account as a file, and the delete removes every row it owns.