Short story: we don’t run a “people database” inside LocoWise. The app is not a social network. Your tales do not travel from device to device between strangers — there is no “pass my data to other users” path at all. What exists instead is a small set of technical hooks so the app can work, and a hand-off to outside tools when the story engine or messaging needs a lift.
Who is behind this
LocoWise is developed and published by Sealand Life (Ulrich Baum and team). This notice describes how the app-related processing works in everyday language; it is not legal advice.
What we do not collect on purpose
The developer does not sit on a stockpile of “personal dossiers” — no deliberate harvesting of your name, postal address, or private photo album through LocoWise. If something like a name ever appears, it is because you typed it into a field yourself as part of a story prompt, not because we fished for it in the background.
Identifiers that are almost impossible to avoid
To make analytics tolerable and push messages deliverable, the ecosystem may rely on an app-specific, pseudonymous device or profile identifier (think “label on a box,” not “passport number”). At most, that is the sort of thing we are talking about when we mention a unique id for tracking and notification routing — not a running diary of your life.
When your own words leave the room
The core of LocoWise is text you type so the app can return a textual story or fairy tale. To do that, your message may be sent to third-party services that run the model and related infrastructure. In practice, the payload is: the text you entered (plus whatever minimal parameters the feature needs to stay coherent) with the goal of getting a text answer back. That flow is a service contract between you, us, and those vendors — it is not a broadcast to other LocoWise users.
OpenAI (and similar)
Provider: OpenAI (or an equivalent model host we
may use for the same job).
Role: third-party processor for
AI generation.
What moves: the characters you type into the
request so the system can return a story in words.
What we ask you to assume: their terms and
security practices also apply to that leg of the journey; we
select providers that fit the task, not ones that need your life
story.
Singular
Role: measurement and attribution
— third party.
Typical use: understanding whether an install or
session can be linked to a campaign, without turning the app into
a confessional.
Data in broad strokes: device and campaign
signals as described in Singular’s public documentation, not a
chat log of your fairy tales.
OneSignal
Role: push notifications —
third party.
What passes through: what is needed to show a
message on your lock screen, including a stable token and
preference flags — again, in line with OneSignal’s own docs, not
a parallel social graph.
Users and other users
LocoWise is built so that users are not made to hand each other personal data through the app. If you read something that looks like “sharing,” it refers to the pipeline above (you ↔ services that power the app), not to a hidden mailbox between one parent and another.
Children and bedtime mode
Stories may be for kids, but who taps “generate” is the adult in the room with the device. We don’t use LocoWise to run targeted ads at small children, and we don’t want the app to become a high-school-style gossip network — because that would be the wrong genre entirely.
Where this road can fork
We may update this text when a feature ships or when a law tugs the rope. The “last revised” line at the top is your cue; if the change is more than a typo, we will treat it with care.
Talk to us
Questions go to owner@sealand-life.com — that inbox is the first stop if something in this “mosaic” does not line up with what you see on your phone.