Privacy Policy

Sprang — peg solitaire for Android com.brettsprang.sprang · published by Knut Petter Lake, Oslo · in force from 15 October 2026

A privacy notice is usually written by addition: here is a thing we collect, and here is another. This one is written the way the game is played. Everything a notice like this might have to deal with goes on the board first, and then it is jumped off, one piece at a time, with the reason given for each removal. What survives to the end is the whole of what is true.

The board as it starts · fourteen pieces
1Accounts and sign-in
2Device and advertising identifiers
3Advertising and ad networks
4Analytics and usage statistics
5Crash and performance reporting
6Payments and purchase records
7Mailing lists and newsletters
8Cookies and web storage
9Transfers outside the EEA
10Processors and sub-processors
11Retention schedules
12Consent records and withdrawal
13A Data Protection Officer
14Profiling and automated decisions

Run one · everything that needs a wire

The published package declares no internet permission. Four pieces depend on a connection the software cannot open, so all four come off in one run.

PIECE 3Advertising and ad networks

Sprang shows no advertising of any kind. No advertising SDK is compiled into it, no ad slot exists in any screen, and no request for a banner or an interstitial could leave the device even if one did. Nothing is therefore disclosed to an advertising network, because there is no network in the build.

PIECE 2Device and advertising identifiers

The advertising ID, the Android ID, the serial number, the IMEI, the MAC address and the list of installed packages are not read. The permissions that would be needed for several of them are not requested, and the ones readable without a permission are of no use to software that cannot transmit them. No identifier is generated locally to stand in for them either.

PIECE 4Analytics and usage statistics

No analytics library is present — not Firebase Analytics, not Google Analytics, not an in-house counter. Which board shapes are popular, how long a session lasts and where players give up are facts I do not have and have chosen not to acquire. Design decisions here are made by playing the thing, not by measuring you.

PIECE 5Crash and performance reporting

No crash reporter is embedded. If Sprang stops unexpectedly, I learn about it only because somebody writes to me, which is the slower route and the one I accepted on purpose. Android's own platform reporting is a separate matter and belongs to Google; it is dealt with further down.

Ten left. Four jumps, no connection to make them with.

Run two · everything that needs a name or a payment

Three pieces assume a person on the other side of a transaction. Sprang has no such side.

PIECE 1Accounts and sign-in

There is no account, no registration, no profile, no nickname, no e-mail field and no social or Google sign-in. The game opens to a board. Because there is nothing to log in to, there is nothing by which one player could be told apart from another, and no name, address, telephone number or date of birth is ever asked for.

PIECE 6Payments and purchase records

The build carries no billing library, no in-app purchases, no subscriptions and no paid removal of anything. I therefore hold no order history, no billing address and — this part matters — no fragment of a card number, not even the last four digits. Should the store listing itself ever carry a price, that transaction happens inside Google Play and its record stays with Google and your bank.

PIECE 7Mailing lists and newsletters

There is no list to join and no box inviting you to join one. Writing to me puts you on nothing: your message sits in a mailbox until the matter is finished, and when there is no longer a reason to keep it, it is deleted rather than filed for later.

Seven left. Half the board is clear and no personal data has appeared yet.

Run three · everything that belongs to a website

Three pieces are standard furniture in a notice written for a web service. Sprang is an installed application with no server behind it, and they do not apply in the form the words suggest.

PIECE 8Cookies and web storage

The game is native Android, not a page in a browser frame, so no cookie, pixel, tag, beacon, local-storage key or similar web mechanism is set by it. Settings and progress are ordinary application files, described below. This page you are reading now sets no cookie either; the only thing it fetches from elsewhere is its two typefaces from Google Fonts, and when your browser asks for them your IP address necessarily reaches Google, exactly as it does for any image on any site.

PIECE 10Processors and sub-processors

I engage nobody to handle personal data on my behalf: no hosting provider, no backend service, no support desk, no contractor. There is consequently no processor agreement under Article 28 to list, because there is no processing of yours for anyone to carry out. Google Play is not my processor — in respect of your use of the store Google acts as a controller in its own right.

PIECE 9Transfers outside the EEA

I transfer nothing anywhere. Nothing leaves the handset by the software's own doing, so there is no export of personal data to a third country and no standard contractual clauses, adequacy decision or derogation under Chapter V for me to rely on. Where Google moves data it has collected through the store or the operating system, Google answers for those transfers under its own notice and its own safeguards.

Four left. And every one of them only existed because of the ten already gone.

Run four · the paperwork the first ten would have required

These four are consequences. Each is obligatory in a notice where data is collected, and each falls away once it is not.

PIECE 11Retention schedules

A retention table sets out how long each category of personal data is kept and on what trigger it is erased. I hold no category of your personal data, so I have no schedule and would be inventing one to print it. The files the game writes on your own device last exactly as long as you leave the app installed — clearing its data, or uninstalling it, removes them, and nothing survives elsewhere because nothing was ever copied elsewhere.

PIECE 12Consent records and withdrawal

Sprang asks for no consent, which is why there is no consent banner, no preference centre and no record of what you agreed to and when. Consent under Article 6(1)(a) is a lawful basis for processing; where there is no processing there is no basis to establish and nothing for you to withdraw. If you ever see a consent dialogue in this game, the build has changed and so must this page.

PIECE 13A Data Protection Officer

No DPO has been appointed, and none is required: Article 37 compels an appointment for public authorities, for large-scale systematic monitoring and for large-scale processing of special-category data, and a single person publishing an offline puzzle is none of the three. The address at the foot of this page reaches the only human involved.

PIECE 14Profiling and automated decisions

Nothing about you is scored, segmented, predicted or ranked, and no decision affecting you is taken by machine. The game does make choices — which board to offer next, whether a jump is legal — but those run on the rules of peg solitaire and the position in front of you, not on a model of the person holding the phone. Article 22 has nothing to bite on.

Board clear. Fourteen jumped, in four runs, with a reason for each.

What is left on the board

In the game, a clean board with one marble standing is the win. Here the honest answer is not one but three, and I would rather set them down plainly than round the number to something prettier. None of the three involves me holding information about you; two of them exist whether I like it or not.

Remains · in your hand

What the game writes on your device

Sprang keeps a small save file so a board survives being interrupted: which shapes you have solved, your best result on each, the half-played position you walked away from, and your settings — sound, haptics, the marble finish, left- or right-handed layout.

It lives in the application's private storage area, which Android keeps apart from other apps, and it is never read by me. There is no cloud save and no backup I operate. It is not personal data in my hands for the straightforward reason that it is not in my hands at all. If you want it gone: Android Settings → Apps → Sprang → Storage → Clear data, or uninstall, and it goes with no trace left behind on my side.

Remains · in Google's hands

What the store and the operating system know

Installing anything from Google Play means Google processes the installation against your Play account, and Android may send Google diagnostic and crash information depending on your device settings. That processing is Google's, under Google's own privacy notice and Google's own legal responsibility as controller. I am not a party to it and cannot see into it.

What does reach me from Google, through the Play Console, is aggregate and anonymous — install and uninstall counts, countries, Android versions, device models, ratings — plus one exception that is not anonymous at all: a public review. If you write a review, I see the display name you chose, the stars, the text and the date, and I may reply to it in public. That is Google's review system working as designed, and the only way to withdraw it is to edit or delete your review in the Play Store. Please do not put anything private in one.

Remains · on my side of the table

Who is responsible, and what you may do about it

The controller for Sprang is a private individual, not a company: Knut Petter Lake, of Herslebsgate 17B, 0561 Oslo, Norway. The name Knut Lake on the store listing is a publishing name with no legal form behind it — no AS, no other registration — so the person legally answerable is the one named here. Reach me at brett@knutlake.space. Skriv gjerne på norsk — norsk eller engelsk går like bra.

The General Data Protection Regulation applies in Norway through the EEA Agreement and personopplysningsloven (LOV-2018-06-15-38), and it gives you eight moves against a controller. I list them because they are yours, and I tell you at once what they will fetch from me, which is almost nothing — the honest result of fourteen jumps:

Access · Art. 15Ask what I hold about you. The answer will be that I hold nothing, and I will say so in writing.
Rectification · Art. 16Correct what is wrong. There is no record of yours here to correct.
Erasure · Art. 17Have it deleted. Already the position — and your own save file is yours to clear.
Restriction · Art. 18Freeze processing. Nothing of yours is being processed to freeze.
Portability · Art. 20Receive your data in a usable format. I have no file to hand over.
Objection · Art. 21Object to processing on legitimate-interest or direct-marketing grounds. I rely on neither.
No automated decision · Art. 22Not be subject to solely automated decisions. None are taken.
Withdraw consent · Art. 7(3)Take back a consent. None was ever asked of you.

Against Google those same moves have real weight, and should be exercised there — through your Google account settings or Google's own privacy contact — since Google holds what Google holds. A request to me is free, needs no particular form, and I answer within one month; write from any address you like, though if I genuinely cannot tell who is asking I may have to ask you something back, and if a request is plainly unfounded or endlessly repeated the Regulation lets me say so.

Children. Sprang is suitable for any age and is not directed at children specifically. Norway sets the age for a child's own consent to information society services at 13, under personopplysningsloven § 5 — but nothing in this game rests on anyone's consent, at any age, because nothing is collected to consent to. A child can play it on an aeroplane with the handset in flight mode and the game is unchanged.

If you think I have this wrong. Tell me first if you are willing — brett@knutlake.space — but you are under no obligation to, and you may go straight to the supervisory authority. In Norway that is Datatilsynet, Postboks 458 Sentrum, 0105 Oslo, datatilsynet.no. If you live elsewhere in the EEA you may instead complain to your own national authority, or go to the courts where you live. You may also ask Datatilsynet to look at a claim made on this page and check it against the published package; the package is the evidence and I would rather it were inspected than taken on trust.

Knut Petter Lake

Private individual · controller for Sprang
Herslebsgate 17B, 0561 Oslo, Norway
brett@knutlake.space · knutlake.space

No organisation number is given here because there is no registered organisation to give one for. If you need to be certain who you are dealing with, the name and address above are the whole of it, and the developer name shown on the Google Play listing is the same person.

That is the end of the run. Fourteen pieces on, fourteen jumped, three left standing — a file on your phone that I never see, a store account that belongs to Google, and one man in Oslo who can be written to. If any of that stops being true, this page is rewritten before the build that changes it is published, and the date at the top moves. There is no earlier version: this is the first.