Kehyh is an iPhone cruise-day planner that turns booking text, itinerary screenshots and notes into a voyage timeline. The official description combines local planning, venue suggestions, checklists and an archive route. Its audience is someone who wants travel references together on the phone rather than repeatedly searching through messages.
This First look uses the App Store listing. We have not imported a booking, identified a ship venue or restored an archive. The useful distinction is between a proposed extraction from source material and a plan whose editable details the traveller has actually verified.
Based on official store information. We have not tested this app hands-on.
What it does
Quick Login creates a local account on the phone without a website or cloud sign-in. Cruise Setup can read pasted booking confirmation text to fill fields such as ship, cabin, dining arrangement, reference and port days, while screenshot import addresses picture-only itineraries. Every field remains editable according to the developer.
Timeline entries can be added, changed, rescheduled or removed, with notes and confirmation information. A practical first evaluation is a short sample itinerary compared line by line with the original booking. A successful import is not evidence that a cabin or port time was interpreted correctly.
Ship-aware venue suggestions include dining rooms, theatres, spa or pool locations and deck information. A manual venue can be added when nothing fits. Check the actual ship information rather than treating a suggestion as an official onboard instruction.
A pre-departure checklist supports due information and overdue markers. A boarding-document index organizes references such as passports and boarding passes, while Trip Notes cover matters including cabin, dining and special requests. The source establishes an index, not a guarantee that every original document is included, valid or sufficient for boarding.
Duck Hunt records found rubber ducks with a photo, location description and tags. This is a separate personal-log feature rather than a navigation or ship-location service. A voyage summary and archive can be created for later viewing, sharing or restoring a full plan.
Before you install
Archive generation uses purchased Cruise Archive Credits. That is a material access boundary, especially if a portable copy or restoration route is the main reason to use the app. The retained source does not provide exact credit prices or every package condition.
The developer describes fully offline operation with plans, photos, notes and archives staying in the app on the device. A local login is not a cloud account or an independently tested backup. We have not verified recovery after a lost phone or the completeness of every archive.
Signing out returns to login without deleting cruise data according to the source. Erase All App Data is a different action that permanently removes it after two confirmations. Keep access control and deletion separate rather than assuming leaving the login view either destroys or backs up the plan.
Imported and suggested travel details should be checked against the operator's current information. The app does not establish an official relationship with every cruise line or a guarantee that a venue, itinerary or boarding requirement is current.
Sensitive notes and document references deserve a deliberate audience when an archive is shared. We have not audited encryption, access protection or file contents. Local storage and the ability to share are different stages of the information path.
Price and access
The linked US App Store download is free. Generating cruise archives uses credits sold through in-app purchases, with current amounts not established by the retained description. Confirm the price and the role of credits before relying on archiving. The local-account workflow is separate from a promise of a free cloud backup or unlimited portable exports.
Our take
The strongest proposition is bringing a cruise's scattered information into an editable, offline plan. The manual fields and venue fallback are important because extraction and suggestions can be wrong. The archive route can support a later handoff, provided its credit requirement and actual contents are understood.
Start with non-sensitive sample material and inspect every imported value. Test the timeline and a representative archive before putting the only useful copy of important information in the app. Keep original booking and boarding references through the appropriate official channels.
We have not assessed extraction accuracy, archive recovery or privacy implementation. Our take is a source-based introduction to a local voyage organiser, with verified source details and the paid archive boundary central to its usefulness.
For a screenshot itinerary, compare numbers and location names closely. An image can be readable to a person while automatic interpretation still needs correction. The editable fields are a review opportunity, not proof the first result is final.
A document index can help you find a reference without becoming the document itself. Check the actual files and official boarding requirements separately before travel.
If a venue suggestion is unavailable or wrong, use the documented manual route and preserve the operator's information. We have not assessed the completeness of the ship database.
An archive intended for sharing should be inspected for personal details. A convenient summary can still reveal a confirmation number or a special request the recipient does not need.
Sources
App icon from the official store listing.
