Effective date: October 2026. These terms cover the mobile apps and this site. They are the rules of use, written in the same voice as the privacy note, because the facts underneath are the same. By using an app you accept this page as the current account of those rules. If you do not accept them, do not use the app.
The studio has built mobile apps for years. The work covers behavior, design, build, testing, release, and updates. These terms do not sell you a second, secret version of that work. What the product does is what the build does. What it refuses — a personal profile, a path between users — is refused here as well.
Both platforms
Every product is made for both platforms. iOS and Android are both part of the plan. A build is not finished while one store carries the product and the other is left as an afterthought. Behavior, design, build, testing, release, and updates are carried for both. You may meet the app on either platform. The limits in these terms travel with it. An iOS screen and an Android screen can follow different habits of navigation and type. They do not follow different rules about the assistant, the unique id, or the absence of a profile.
Acceptable use
Use the apps for their ordinary purpose: the tasks the screens actually offer. Do not try to break the software, interfere with the service, or probe for other people’s information. There is no directory of users to harvest, and attempting to invent one is not allowed. Do not use the app to send personal data to other users. The product has no such channel. Do not try to build one out of the assistant, the push path, or the unique id.
Do not misuse the assistant to harm someone, to impersonate the studio, or to pressure another person. Do not treat a reply as permission to do something the rest of these terms forbid. The apps are not a tool for collecting contacts, precise location, or a private dossier. If a use needs those things, it is outside this product.
- Follow the screens that exist. Do not scrape, flood, or disrupt them.
- Leave other people out of your use. There is no social layer to exploit.
- Keep identification where the privacy note puts it: a unique id, and nothing more.
The assistant’s limits
The in-app AI assistant can talk with users. It is not a human. No member of the studio is on the other end of that chat, and you should not write as if one were. It is not professional advice. It is not legal, medical, financial, or any other licensed counsel. A fluent answer is still not a professional opinion. Do not rely on it for a decision that needs a qualified person, and do not present a reply to someone else as if the studio had signed it.
What someone writes is used only to answer that person. It is not passed to other users. You agree not to put another person’s secrets, contact details, or private records into the assistant in the hope that the app will deliver them. It will not. The assistant is a reply to you, not a courier. If you need a person, email the developer. The assistant cannot stand in for that letter, and these terms do not treat a chat transcript as notice to the studio.
Attribution, push, and the unique id
Attribution uses Singular. Push notifications use OneSignal. The only identifying item is a unique id. The apps build no personal profile. They do not take your name, email, phone number, contacts, or precise location in order to describe you. Users do not send personal data to each other. Those sentences are terms, not decoration. They bind the product in the same way the privacy note describes them.
Singular’s role is the route that led to an install. OneSignal’s role is addressing the device for a notification. Neither role is a license to identify you to other users, and you may not use the unique id as if it were a public name. Email you send to the developer is ordinary mail. It is not added to an in-app profile, and it is not shared with other users. The form on the Contacts page opens your email app. It is not a server intake.
Availability
The apps, the assistant, Singular attribution, and OneSignal push are provided as they are available. Service can pause for a release, a repair, or a cause outside the studio. A screen can fail to open. A reply can be slow or absent. A notification can arrive late or not at all. These terms do not promise a particular minute, a particular uptime, or a particular answer.
Features can change as updates ship. An update follows the same plan on both platforms, but it can still alter a screen, remove a path that did not belong, or tighten a limit that was unclear. Availability is not a warranty that today’s layout is permanent. It is a statement that the service can be interrupted and that you should not build a critical plan on the assumption that it cannot.
Changes
These terms can change. When they do, the page shows the new text and a new effective date. October 2026 is the date of this version. The dated page is the version that applies. Check it when you return. Continuing to use the app after the date changes means the new terms are the ones to read. We will not hide a material change inside an untitled edit. The date at the top is the signal.
A change to these terms does not override the privacy note by silence. If the handling of the unique id, Singular, OneSignal, or the assistant changes, both pages have to say so. You should read them together. They are a pair.
Disputes
If you have a dispute about the apps, the assistant, these terms, or the privacy note, raise it by writing to the developer. That letter is how a dispute starts. There is no separate portal and no in-app tribunal. Send the note to the address below, say what happened, and include a way to reply. The studio will read it and answer.
Write to CIRRUS AERO LTD at [email protected]. Please describe the platform you used, what you expected, and what occurred. Do not send the dispute only to the assistant. The assistant is not a human and does not receive legal notice. A dispute is a letter to the developer, and this section is the whole of that path.