Who this note is for
This note describes how the mobile applications covered by it treat information. It is written for the person holding the phone, in ordinary language, and it matches the way the apps are actually built. The effective date is October 2026. If a later note replaces this one, the new date is printed in the same place at the top of the page.
The applications are made by DROMMEX LTD. The same company is the developer you can write to. The note applies to the iOS build and the Android build of a product. Both platforms follow this note. A difference in the shell — navigation, type, or store rules — is not a difference in what is collected.
Singular, for attribution
Attribution uses Singular. When an app is installed, or opened through a campaign, Singular can receive the unique id together with the fact of that install or open. That is how the studio can tell which campaign led to the install. The report is about the install, not about a biography of the person who installed it.
Singular does not receive, from these apps, a name, an email address, a phone number, a contact list, or a precise location. The studio does not attach a second identifier beside the unique id in order to make the report richer. If a campaign needs to be measured, the unique id and the install event are the measurement. Nothing in the attribution path is a message from one user to another.
OneSignal, for push
Push notifications use OneSignal. The unique id is what OneSignal uses to address the install. A notification is a short text chosen for that install: a release note, a reminder the app itself is allowed to send, or a similar studio notice. It is not a letter from another person using the app.
OneSignal is not a channel between users. One person cannot push a message into another person’s notification tray through this setup. The iOS build and the Android build both use OneSignal, with the platform details each system requires, and both of them address the install by the unique id alone. Turning notifications off is a system setting. The app does not replace that setting with a private switch that keeps sending anyway.
The assistant
The in-app assistant can talk with the person using the app. It produces written replies. It is not a human. It is not professional advice of any kind: not medical, not legal, not financial, and not safety advice. A confident tone in a reply does not change that. If a question needs a qualified person, the assistant is the wrong place to ask it, and the reply should not be treated as that person’s judgment.
What someone writes is used only to produce the reply they see. Those messages are not passed to other users. They are not shown in anyone else’s session, and they are not used to build a personal profile. Do not send another person’s secrets to the assistant expecting them to be forwarded, stored as identity, or kept for later. The assistant has no job that involves introducing users to each other.
No exchange between users
The apps are not a messenger. There is no inbox shared between accounts, because there are no accounts of that kind. There is no profile to find, no handle to search, and no path that carries personal data from one person to another. What you type into the assistant stays in the service of your own reply. What arrives as a push was not typed by another user as a way of reaching you.
If two people use the same app, the product still does not connect them. Their unique ids are separate. Their assistant conversations are not pooled. A feature that would let one user address another is outside this note because it is outside the apps.
No personal profile
The apps build no personal profile. They do not ask you for your name. They do not ask you for an email address, a phone number, your contacts, or a precise location. They are not designed with a field whose job is to store those facts, and they do not assemble them quietly in the background from the unique id.
Please do not type a name, an email, a phone number, a contact, or a precise location into the assistant as if it were a form. The assistant is not an identity form. If those words appear in a message, they are still only part of the text used to answer you. They do not open a profile, and they do not get attached to the unique id as a name would be attached to an account.
The unique id
The only identifying item is a unique id. It exists so Singular can attribute an install and so OneSignal can deliver a push to the correct install. It is an identifier for the install, not a portrait of a person. It is not your name. In these apps it is not tied to an email address or a phone number that you typed, because the apps do not ask you to type either one.
The same rule holds on iOS and on Android. The studio does not mint a second id for the other store, and it does not join the unique id to a contact book, a precise map point, or an account password. When this note says “the only identifying item,” it means there is not a hidden second one reserved for advertising or for support.
Mail sent to the developer
If you write to the developer, you use your own mail client. The message is ordinary correspondence: your address, your words, and any return mail. It is not mixed into the app’s unique id. It is not sent to Singular or OneSignal as a profile. It is not shared with other users of the app. The studio reads it in order to answer you, and that is the purpose of the address published on this site.
The address is [email protected]. Writing that email is optional. Nothing inside the apps requires you to send one in order to keep using them. A mail about this note, about the assistant, or about a build is welcome. A mail that asks the studio to forward your words to another user is a request the apps are not built to fulfill.
When this note changes
The studio may update this note when the apps change, or when the role of a provider changes. Singular and OneSignal are named here because they are the providers in use. If that stopped being true, this page would have to say so, and it would show a new effective date. The page you are reading always shows the current note. Continued use of an app after a new date is your signal to read the note that carries that date.
A change of wording in the assistant, or a change in a store listing, does not by itself rewrite this note. A change that alters what is collected, what is sent to Singular, what is sent to OneSignal, or how the unique id is used does rewrite it, and the date at the top moves with that rewrite.
How to reach the developer
Questions about this note go to the developer, DROMMEX LTD. Use the email on this site, or the form on the contacts page, which only opens your mail client. You can also read the terms, which state the assistant’s limits, acceptable use, and how a dispute is raised: by writing to the developer. The studio answers in writing. This note does not ask you to create an account in order to ask a question about it.