Version 0.1 · 19 September 2026 · applies to the Noah mobile app and web application
Noah is software licensed to an organization — a school, a tour operator or a similar group organizer. That organization decides which people are entered into Noah and why, and is the data controller for the information about them.
Noah is operated by AKD Systems, which acts as a processor on that organization's instructions. Each organization's data is held in its own tenant and is not visible to any other organization.
You cannot create a Noah account yourself. Accounts are issued by your organizer: staff accounts for administrators and guides, and separate accounts for adult travellers and for verified guardians. A child usually has no account at all — guides can run a trip entirely without child logins.
| Information | Why | Who entered it |
|---|---|---|
| Name, username, chosen language | Signing in and addressing you correctly | Your organizer |
| Email, phone, date of birth, nationality, staff notes on a client profile | Organizing the trip | Organizer staff |
| Emergency contacts | Reaching someone if there is a problem on a trip | Organizer staff |
| Identity documents (passports, ID cards, visas, consent forms) | Travel and border requirements, where the organizer needs them | Organizer staff, on the web app only |
| Seat, group and itinerary | Running the trip | Organizer staff |
| Attendance (“unknown”, self-reported, guide-verified, absent, excused) with its time and source | Headcounts | Guides, travellers, guardians |
| Answers to polls and forms | What the organizer asked | You, or a guardian for a linked child |
| Updates sent to you and your acknowledgements | Communication during a trip | Guides and staff |
| Game nicknames and scores | The on-board games | Players |
| Sign-in records and an audit log of sensitive staff actions | Security and accountability | Created automatically |
| Your phone's model, Android or iOS version, the app version, its time zone, and an identifier the app generates for that installation | Knowing which phone runs which version when something goes wrong, and — during testing — how much the app is actually used. It is not an advertising identifier and is not shared with anyone. | Created automatically by the app |
| A notification token from Google (Firebase Cloud Messaging) | Delivering a notification when the app is closed. The notification itself says only which kind of update arrived — never the message, a name or a place. | Created automatically by the app |
A child and a guardian are two separate identities in Noah; they never share a login. A guardian sees a child's information only after the organizer has verified the link between them, and only for that child — never another family's. Verification can be withdrawn by the organizer, which ends the access at the guardian's next request.
A guardian acknowledging an update means only that the guardian saw it. Noah never treats it as proof that a child was present anywhere.
Access is decided by the organizer through roles and permissions, and enforced by the server on every request. In particular: a traveller sees their own seat, plan and updates, never the roster or other people's details; a guide sees the trips they are assigned to; identity documents sit behind a separate permission that guides do not normally have, and every time one is opened it is written to an access log.
No system is perfectly secure, and Noah does not promise that a message will always arrive on a phone. Device settings, silent mode and network coverage are outside its control.
Trip information is kept while the organization needs it. Identity documents carry an expiry and are deleted automatically by a scheduled job — currently 180 days after they are filed, unless the organizer sets a shorter period. Records of published events used to synchronize the apps are pruned after 24 hours.
Because your organizer decides what is held about you, ask them first — they can correct or remove information directly in Noah, including deleting an account. If you cannot reach them, write to us at the address below and we will pass the request to the organization responsible and support them in answering it.
If this policy changes materially, the new version is published here with a new date, and organizers are told.
AKD Systems — akdsystemslb@gmail.com