Glent — one rule, countless solutions
Glent collects nothing, sends nothing, and has no way of doing either.
There is no account, no cloud save, no advertising and no measurement. Which levels you have finished, your best move counts and your settings are written into the app's own private folder on the phone, and that is the end of the matter.
Below is the full account: what is stored, what the app is barred from touching, why the shuffled board needs no network to be fresh, what Google sees because the game is on Google Play, and what you can ask for under UK law.
Glent is published by SO-Recruit Ltd, registered in England at 12 Greenhead Road, Huddersfield HD1 4EN, with Nicholas Arthur Ledgard responsible for it. Under the UK GDPR the company is the data controller for the app.
The name says recruitment, so here is the thing worth stating plainly rather than leaving to inference: this game touches no recruitment data whatsoever. No candidate record, no CV, no contact list, no client database. The game holds no such data, has no permission to read anything of the kind from your phone, and — as the next section but one explains — no means of sending or receiving anything at all. The two halves of the company do not share a byte.
For anything on this page, write to glow@so-recruit.online.
Three things, none of which describe a person:
There is no name in that, no email address, no account, no device identifier and no advertising ID, because the app never asks for or generates one. Android keeps each app's private folder out of reach of every other app installed, and that folder is the whole of this game's memory.
Glent declares no internet permission. Android enforces that at the level of the operating system rather than trusting the app to behave: without the permission, a connection simply cannot be opened. It also means the promise is checkable — the permission list is visible on the store page and on the handset, before and after installing, and a future version that wanted to talk to anything would have to add a line there in full view.
No camera, no microphone, no location, no contacts, no photos, no wider file access either. A grid of squares that flip when tapped has no use for any of them.
The shuffle hands you a new board on demand, and it does so without asking anybody for one. A board is produced on your own handset by starting from a finished grid and applying a run of random taps — which guarantees, by construction, that the taps can be undone and the board can be solved. Scattering tiles at random would not: on some board sizes most random arrangements cannot be lit at all, whatever anyone does.
So there is no puzzle server, no request going out when you ask for another board, and no record anywhere of how many you asked for or when.
No ad network, no analytics library, no crash reporter, no attribution kit, no social sign-in. Nothing in this game is funded by watching whoever is holding the phone, which is the reason the list of stored items runs to three.
That is worth saying explicitly for a bright, simple puzzle, because bright, simple puzzles are handed to children constantly. With nothing advertised and nothing gathered from anybody, there is no profile to assemble out of a child's play, no attention to resell, and no purpose in asking anyone's age — the answer would change nothing the app does.
One thing happens above the app's head. Where backup to Google Drive is switched on, Android may copy the small progress-and-settings file into your own Google account, alongside the backups of everything else on the phone. That copy is yours, governed by Google's terms rather than ours, and invisible here — we hold no account there and have nothing to look at.
It is also the only way a set of finished levels survives a new handset. The switch is in Android's own settings, for the whole device or for this app alone.
Installing is an arrangement between you and Google, logged against your Google account. What a developer sees afterwards is a console of aggregates: installs by country, the spread of Android versions, the drift of a rating. No individual row lies beneath those totals for anyone here to open, and nothing in them concerns a level or a move count.
Google's own part is covered by Google's privacy policy at policies.google.com/privacy.
Everything is in one folder, so there is one action and nobody to write to. Uninstalling takes the progress, the records and the settings with it. To keep the game but return every level to unplayed, Android's app settings will clear its storage.
Both happen at once, neither can be undone, and neither needs anything from us — there was never a second copy to delete.
Everything above is about data that never arrives. This is the exception. An email leaves us holding an address and a message, kept while the matter is open and for a reasonable period afterwards in case it comes back, then deleted.
It is used to answer you and for nothing else: not a list, not a sale, not passed along, and — given the company's other line of work, which deserves saying — never added to any recruitment system, database or mailing of any kind. The lawful basis is legitimate interests in replying to correspondence. Ask for an exchange to be deleted and it goes.
The UK GDPR and the Data Protection Act 2018 give you rights over personal data held about you: access to it, a copy of it, correction, erasure, restriction, objection, and portability. Aimed at the game those requests find nothing, because the game hands us nothing. Aimed at the mailbox above they work in full, free of charge, and within one month.
Send them to glow@so-recruit.online. If the reply falls short, the Information Commissioner's Office supervises this in the United Kingdom and will take a complaint directly, without you having to come to us first: ico.org.uk.
One date sits under the title, and that is the version in force. For a change that genuinely moves data — anything collected, any third-party component, anything crossing a border — the sequence does not vary: this page is rewritten, the Play Console's Data safety declaration is corrected in the same sitting, and the release responsible goes out after both.
A tidier sentence is not such a change, and brings nothing with it but a later date.
SO-Recruit Ltd
12 Greenhead Road, Huddersfield HD1 4EN, United Kingdom
Responsible: Nicholas Arthur Ledgard
© 2026 · Registered in England & Wales