What leaves the device
Nothing does. Loomcraft opens no connection, holds no account, and has no address to report to. The drafts you chart, the palettes you build and the settings you prefer live in a folder the application keeps for itself on your handset.
That is the entire substance of this document. The pages below take it apart so that each claim can be checked against the app's behaviour rather than believed on the strength of a sentence, which is the only sensible way to read a privacy policy at all.
Nothing here measures you
No advertising framework is linked into the build. Neither is an analytics package, an attribution kit, a crash reporter, a sign-in provider or a billing library. The absence is structural: there is no code to disable, and no server exists that could switch such code back on after the fact.
Set out item by item, Loomcraft never reads, derives or transmits:
- anything that would let a stranger write to you, ring you or find your door;
- the advertising identifier Android keeps for ad networks, the Android ID, the handset serial, or its hardware addresses;
- your position, by whatever means someone might try to establish it;
- contacts, calendar entries, messages, call history, the camera or the microphone;
- a trace of which structures you chose, how long you worked, or which motifs you stamped;
- the drafts themselves, your palettes, or photographs already on the device.
The developer console does show Fox & Døtre some figures, and it is worth saying which: counts of installs grouped by country, rates of crashing, and the star ratings people leave. All of it arrives aggregated, from Google, with nothing in it that points at a person.
What the app puts on disk, and who may reach it
Loomcraft writes, and precision about where it writes matters more than reassurance that it is careful. Its private storage area holds the drafts in your gallery, each bound to the structure and the palette it was made with; the copies you take when trying a second colourway; motif blocks and palettes you assembled yourself; the thread count, the zoom and the state of the symmetry helper; and whether the interface is set to English or to Norwegian.
Android keeps that area to the application that owns it, so other installed software is not shown its contents. Fox & Døtre is not shown them either — nothing in the build accepts an instruction from outside, and a file moves only when you move it.
The exception belongs to the platform. Android runs an automatic backup service bound to a Google account; where a person has it turned on, the system may lift an app's files into that person's own Drive so a replacement handset can restore them. The copy is made directly by the platform under settings the account holder controls. We are not party to it, cannot read it and cannot stop it on anyone's behalf; the control is per application, inside Android's own settings.
Removing the app removes the area and its contents. Clearing the app's data from Android settings empties it and leaves the app installed. Exporting a draft as a picture passes the file to the system picker, and from the moment you choose a destination the file belongs to whatever you chose — a folder, a gallery, a message — and this document no longer reaches it.
Permissions, and what Google's part is
Very little is declared in the manifest. Writing an image out runs through Android's document and media pickers, which hand over a single write to the one destination you indicate and no further view of your pictures. Camera, microphone, position, contacts and telephone permissions are not declared at all, so the dialogue that would ask for them never has cause to appear.
Threads, backdrops and motif sets are part of the download rather than something retrieved afterwards. The app is complete when installation finishes, which is why it behaves identically with every radio switched off.
The store is a separate relationship from the app. Obtaining or updating software through Google Play is an arrangement you make with Google on Google's own terms, and none of the account or device information that changes hands there passes by way of Fox & Døtre.
Who answers for all this
Correspondence about this document, or about anything the app does, goes to the business that lists Loomcraft:
Fox & Døtre
Owner: Isabel Fox
Strandgaten 201, 5004 Bergen
Norway
Mail: skyttel@foxdotre.quest
Fox & Døtre is the controller — behandlingsansvarlig — for whatever Loomcraft might process. Nobody processes anything on our instructions, no second party shares the decision, and no representative has been appointed anywhere, since none of those relationships has anything to attach itself to. A data protection officer is not appointed and not required: that obligation falls on public bodies and on operations whose core business is monitoring people at scale or handling special categories of data at scale, and a single offline drafting tool is neither of those things.
På norsk: skriv gjerne på norsk — du får svar på norsk. Spørsmål om personvern sendes til adressen ovenfor.
Children
Charting a stripe is a reasonable way for a child to spend an afternoon, and there is nothing in Loomcraft unsuited to one: no advertisements, no chat, no link leading out, no contact between users, no screen asking for money. Because nothing is gathered from anybody, nothing is gathered from a child, so Article 8, and the age of thirteen that Norway fixed for parental consent in the Personal Data Act, has nothing here to attach to, consent never being the basis for anything here. A parent who wants that in writing need only ask.
The law this is written under
Norway lies outside the European Union and inside the European Economic Area, and the General Data Protection Regulation reaches it by that route: the 2018 Personal Data Act, personopplysningsloven, carries the Regulation into Norwegian law and fills in the national detail each state is left to settle for itself. The supervisory authority is Datatilsynet, datatilsynet.no.
Some duties survive having no data, and it is more useful to show which than to claim compliance in the abstract:
| Provision | What it asks | Where it lands here |
|---|---|---|
| Article 13 | Name the controller, and say what is collected and why, when data is taken from the person | Section Five names a person and a street. Sections One and Two are the "what" — in this case, nothing |
| Article 5(2) | Be able to demonstrate compliance, rather than assert it | This page, published at a fixed address and dated, is the demonstration we can offer |
| Article 30(5) | Records of processing, with relief for small organisations whose processing is occasional | No records are kept because no processing is carried on; the relief would apply in any case |
| Articles 33–34 | Report a breach to the authority, and to the people affected where the risk is high | Nothing is held that could be breached. Were that ever to change, both notifications would follow |
One thing cannot honestly be claimed here: a long history of handling your data carefully. No such history exists, for the plain reason that nothing is being handled. That is a thinner virtue than it sounds and a sturdier guarantee in practice — an empty shelf spills nothing, and no assurance about our diligence has to be believed on trust.
Loomcraft is listed worldwide, so it is installed inside the European Union and in the United Kingdom as well. A resident of an EU state may raise a matter with the authority of their own country; a resident of the United Kingdom may raise it with the Information Commissioner's Office, ico.org.uk, whose remit rests on the Data Protection Act 2018 together with the retained British version of the Regulation. Approaching us first is quicker, never compulsory.
What you may ask, and what you will be told
Articles 15 through 21 provide for access, correction, erasure, restriction, portability and objection. Article 77 provides for a complaint to a supervisory authority, and that right stands whatever anybody writes on a page like this one.
Write to skyttel@foxdotre.quest. Article 12(3) allows a month; the reply will come sooner and will be brief, since the honest answer runs to a line: no file on you exists here to hand over, alter, wipe, freeze or forward. Nobody will be asked to prove who they are first. No stored material exists for such a check to defend, and requesting a photograph of somebody's identity card so as to confirm an empty drawer would be the one point in the whole exchange where real data was put at risk.
If the reply does not convince you, say so once and we will look again; after that the matter is Datatilsynet's, or your own authority's. Nothing written here asks anyone to give up a right, and nothing written here could.
When this page is redrawn
The value of a document like this lies in the sequence of events around it. Should a later build of Loomcraft acquire anything touching personal data — a gallery that synchronises, a reporter for crashes, motif sets offered for sale, advertising in any form — these words are rewritten and published before that build leaves, never after. The date and edition line beneath the title moves with them, and the substance also goes into the release notes on Google Play, so the change can be seen from the store without anyone coming here for it.
This address does not move while the listing is live. The edition line under the title is the fastest way to see whether anything has altered since you last read it.