This note describes how mobile apps from RAK DOKY LTD treat information. It is written for the person holding the phone. The short version is deliberate: these apps do not build a personal profile, people using them do not send personal data to each other, and the only identifying item kept for attribution and push is a unique id.
The studio has made mobile apps for years, for iOS and Android together. The same facts apply on both shores, because every product is built for both. Screens may differ where the platform already taught the thumb a habit. The rules in this note do not differ. If a later version changes what is collected, this page changes with it. The date above is the date of this text.
Singular
Attribution uses Singular. After an install or a first open, Singular can receive the unique id and signals about the install itself, such as which store listing or campaign the installation came from. The studio reads that to understand acquisition: which knock on which door led to this phone, not who the person is.
Singular is not a mailbox between people. These apps do not send Singular a name, an email address, a phone number, a contact list, or a precise location. A campaign measurement is not a portrait. It does not introduce one user to another, and it is not a place where something you typed to the assistant is handed onward as a message.
OneSignal
Push notifications use OneSignal. The unique id is registered there so a notice can be addressed to that installation rather than to a human name. The text of a notification is the notice the app needs to show. It is not a copy of what someone wrote to the assistant, and it is not a message from another user.
OneSignal is not a channel between people who use the app. Two installations can both receive notices without those notices carrying one person's words to the other. Whether a notice appears is also a matter for the phone's own settings. If those settings refuse notifications, the app has nothing to override them with. Turning notices off is done on the device, and the studio treats that refusal as final for that installation.
The assistant
The in-app assistant can talk with the person using the app. It is not a human. It is not professional advice, and it is not a stand-in for a lawyer, a physician, an accountant, or anyone else whose judgment you would hire. A reply can help you continue the task on the screen. It cannot take on a duty that belongs to a person.
What someone writes is used only to answer that person. The words are not passed to other users, and they are not saved into a personal profile. The assistant does not build a memory of who you are in order to describe you later. If a question needs a human decision, the assistant should say so. A person who wants a human at the studio can write to the address at the bottom of this note.
Nothing between users
These apps are not a social product. There is no directory of people, no shared thread, and no control whose job is to carry one person's information to another person. Two installations can exist side by side without the product introducing them.
What you type stays in the reply that comes back to you. Another user does not receive your words, your unique id, or a card of facts about you, because the app does not have that card. There is no hidden pier between berths where personal data is walked across.
No personal profile
The apps do not ask you to build an account out of a name, an email address, a phone number, a contact list, or a precise location. They do not keep a file whose purpose is to describe who you are or to follow you across other services. The studio is not assembling a likeness of the person holding the phone.
A setting can be remembered on the device so the app can open in the state you left it. That is ordinary function, kept on the phone, and it is not a profile held by the studio to identify you. If a screen offers a choice, that choice is about the app working, not about filling in a biography.
The unique id
The only identifying item is a unique id. It exists so two practical jobs can tell one installation from another: attribution, which Singular handles, and push, which OneSignal handles. The id is not your name. In these apps it is not paired with an email address or a phone number. It does not let another user find you.
When the installation is gone, the id no longer points at a phone the studio can reach with a notice. The id is a mark on one installation, like a number painted on a single timber, not a name in a book of people. It is not sold as a description of you, because it is not a description of you.
Email to the developer
If you write to RAK DOKY LTD at [email protected], you are sending ordinary email. The message contains what you chose to write, including your address, because that is how email works. The studio reads it in order to answer. It is not joined to the unique id inside the app, and it is not shown to other users.
Do not send passwords, payment numbers, or anything else you would not put on a postcard. The mailbox is for questions about an app, about this note, or about the terms. It is a letter to the developer, not a field inside the product, and it does not become part of a profile.
Changes
This note can be replaced when the apps change. The effective date at the top moves with the text. The current version is the one published on this page. If a change is large enough that a notice inside an app is warranted, the studio can say so there as well. This page remains the full account. An older copy you saved is a record of an older date, not the note that describes the current version.
Contact
Questions about this note go to the developer, RAK DOKY LTD, at [email protected]. Privacy questions, corrections, and requests to understand a specific app all use that same address. There is no separate data desk. The terms and the contact page use the same name and the same mailbox.