On this page
This note describes how mobile apps from the studio handle information. It is written for the person holding the phone. The apps run on iOS and Android. They are built to do their work without assembling a portrait of you.
Hold onto the short version. There is no personal profile. Users do not send personal data to each other. Attribution uses Singular. Push notifications use OneSignal. The only identifying item those two services receive from the app is a unique id. The sections below say what each of those sentences means in practice.
Attribution with Singular
When an app is installed, the studio wants to know which listing or campaign the install came from. That measurement is attribution, and the service used for it is Singular. The app can send Singular a unique id created for that install, together with the fact that the install happened and the campaign context Singular already tracks.
Singular is not given your name, your email address, your phone number, your contacts, or your precise location. Attribution is read to see whether a release reached the people it was built for. It is not used to follow you across the rest of your life, and that id is not handed to another user of the app. If a campaign number is useful, it is useful as a count, not as a biography.
Push with OneSignal
Some builds ask the operating system for permission to show a notification. If you allow that, delivery is handled by OneSignal. OneSignal receives a unique id and the push token the phone’s system creates so a message can reach that device. A push token addresses a device. It is not your telephone number, and it is not a request to read your contacts.
OneSignal is used to send product notices, such as a finished update or a change inside the app. A name or an email is not attached to that registration, because the app did not collect them. If you decline notifications, the app should keep working without them. A notice is a tap on the glass, not a condition of using the product.
The assistant inside the app
Some of our apps include an assistant you can write to. The assistant is software. It is not a human, even when the sentences sound calm and careful. It does not give professional advice. A reply is not legal advice, medical advice, financial advice, or counsel from any other specialist. Treat it as a response inside the product. Decisions stay with you.
The words you type are used to produce that reply. They are not shown to other users, they are not posted where another person can read them, and they are not added to a profile of you. The apps do not keep such a profile. When the reply is done, the exchange has served its purpose. If you need a person at the studio, write to the developer. The assistant cannot turn into that person, and it should not be given documents or secrets it has no reason to hold.
No exchange between users
These apps are not a channel from one person to another. There is no directory of users, no shared inbox, and no control that delivers one person’s writing to someone else. The assistant answers the person who wrote. It does not introduce you to anyone. Users do not send personal data to each other, because the product has no path for that delivery and we do not add one in the background.
That boundary is part of the design, not a slogan we hope to grow out of. A feature that needed people to find each other would be a different product, and it would need a different note. This note is for apps that keep each person’s use on its own path.
No personal profile
We do not build a personal profile. The apps do not collect your name, your email address, your phone number, your contacts, or your precise location in order to describe you. There is no account screen whose job is to store those facts, and no hidden record that stitches them together later. Please do not type them into the assistant. It has nowhere proper to put them, and a reply does not become more careful because a phone number was included.
The absence of a profile is a choice we keep when a feature is added. If a future build truly needed one of those facts, this note would change first, with a new effective date, and the app would have to ask in the open. Until that date exists, assume the list above is still refused.
The unique id
The identifying item the apps rely on is a unique id. It gives Singular something stable to count for an install, and it gives OneSignal something stable to address when a notification is allowed. It is not your name. It is not a password you chose. It is not an account you sign into on a website. It does not travel from you to another user.
Remove the app, and that id stops being useful for that installation. A later install can receive its own id. The id exists so attribution and push have an address. It does not exist so the studio can sketch a life around it, and it is not combined with the text you send the assistant to invent a profile the rest of this note says we do not keep.
Emails you send the developer
If you write to the studio, you choose the words. A message to the address below, including one opened from the contact form on this site, arrives as ordinary email. We read it so we can answer. We do not pour it back into the app, we do not build a profile from it, and we do not share it with other users of the app.
The contact form has no server behind it. It opens your email application, encodes the subject and body, and leaves the sending to you. Avoid attaching sensitive documents we did not ask for. An email is correspondence with the developer. It is not a field in the app’s data model, because that model has no personal profile to drop it into.
Changes to this note
We revise this note when the way the apps handle information changes. The date at the top is the effective date of the words you are reading. The current version lives on this page. We do not keep a silent older meaning behind a rewritten paragraph. If you want to know what applies, read the note that carries the latest date. A change to terms of use, when there is one, is dated on its own page and does not quietly rewrite this one.
Contact
Questions about this note go to the developer. Say which app you mean and what you want clarified. We read the letter and reply to it.
KEPLER & VALE LTD