On this page
This note says what the mobile apps from this desk do with information, and what they refuse to keep. It is written for a person using the app, not for a filing cabinet. The effective date is October 2026. If a sentence here and a sentence in the app ever seem to disagree, this page is the one to trust until it is replaced.
The apps are made for iOS and Android from one shared plan. The privacy rules are the same on both trays. There is no quieter policy hiding on one platform.
Singular
Attribution uses Singular. When an install needs to be tied to a campaign, a store listing, or another source the studio can measure, Singular receives that signal. The point of the signal is narrow: which source brought this install in. It is not a biography, and it is not a list of what the person did inside the product beyond what attribution itself requires.
Singular does not receive a name, an email address, a phone number, a contact list, or a precise location from these apps. The studio does not use Singular to build a personal profile, and it does not use Singular as a pipe between two people. If Singular’s own company describes broader tools, those broader tools are not the arrangement on this desk. Here, Singular is the attribution door, and the item that identifies the install is a unique id.
OneSignal
Push notifications use OneSignal. A notification has to find a particular install. OneSignal receives the unique id so the message can be delivered to that install and not to a neighboring one. The notification is about the app. It is not a dossier, and it is not a letter from one user to another.
OneSignal is not given a name, an email address, a phone number, a contact list, or a precise location by these apps. Turning notifications on or off, where the system allows it, is a device setting. It does not open a profile on this desk. OneSignal is a delivery door. It is not a room where users meet.
The assistant
The apps include an assistant that can talk with you. Call it a clerk if that makes the limit easier to see. It is not a human. Nobody at the studio is sitting behind the reply in real time, reading it as a person would. It is not professional advice: not legal, medical, financial, or any other licensed kind. A reply can be useful and still be the wrong thing to rely on for a decision that needs a qualified person.
What you write is used only to answer you. The message is the input for that reply. It is not passed to other users. It is not posted, forwarded, or dropped into someone else’s install. It is not used to assemble a personal profile. If you would not want a stranger to have the sentence, do not put the sentence in the box — the clerk is software, and the promise here is about where the words go, not about giving them the care a person would.
No exchange between users
Users do not send personal data to each other. There is no inbox between people, no shared contact book, and no transfer of one person’s details to another person’s device. The route card on the home page is the whole picture: the install, then Singular, the install, then OneSignal, and a closed gap where a second user might have stood.
Nothing in the assistant, the push path, or the attribution path is a back door between users. If two people use the same app, they are two installs. The studio does not introduce them to each other’s information. “No user-to-user data” is a design rule, not a slogan saved for the tally line.
No personal profile
The apps build no personal profile. They do not ask you to register a name. They do not take your email address as an account. They do not take your phone number. They do not read your contacts. They do not collect a precise location and store it as where you are. There is no profile page that adds those fields up into a person the studio can browse.
That limit is easy to miss because many apps start with an account. These do not. If a screen ever looks as if it is asking for a name, an email, a phone number, your contacts, or a precise location in order to identify you, treat that as a defect and write to the developer. The rule on this page is the rule the build is supposed to follow.
The unique id
The only identifying item is a unique id. It exists so two outside services can tell one install from another. Attribution needs that distinction, which is why Singular receives it. Push needs that distinction, which is why OneSignal receives it. The id is not your name. It is not a phone number written in another alphabet. These apps do not attach it to a profile of personal details, because they do not keep one.
The id is per install, not a membership card you carry between products as a public identity. It is not shown to other users. It is not a handle they can search. If the id is rotated or replaced by the system, the privacy shape does not change: whatever the new value is, it is still just an id for attribution and push, not the start of a profile.
Emails sent to the developer
If you write to the studio, you are sending an email. That message leaves your mail app and arrives in the developer’s mailbox. It is not a feature stored inside the mobile app, and it is not shared with other users of the app. The form on the contacts page does not post the note to a server of ours. It opens your mail client with the subject and body filled in.
An email can contain whatever you choose to type, including your name and your email address, because that is how mail works. Sending it is your choice. The studio reads it in order to reply. It is not added to an in-app profile, because there is not one, and it is not fed to other users. Please do not send secrets you would not put in an ordinary email.
Changes
If this note changes, the new text replaces the old text on this page, and the effective date at the top changes with it. October 2026 is the date of this version. The studio does not keep a silent second copy that says something gentler. When you want the current rules, load this page again. The terms page will be updated when the contract language needs to match.
Contact
Questions about this note go to the developer, in writing. The developer is the same desk that ships the apps.
OFFICE CRAP PTY LTD
You can also use the contacts page. The terms repeat these facts in the language of use, limits, and disputes.