What is Trip Sharing
Create a trip in the app before departure and share its webpage link with a designated contact. While you are on the mountain, your phone reports your location when a time or distance rule you choose is reached (about every 10 minutes by default). If both are enabled, whichever rule is reached first triggers a report. No new point is created without a new valid GPS fix. Your contact can open the link in a browser to see the route, latest reported location, and trip status, without downloading the app or creating an account.
- You must actively enable it: Location is only sent from your phone after you create a trip and consent to the terms; Aki Map will not actively collect your location.
- Anyone who gets the link can view it: Please only share it with trusted people, and you can revoke it anytime.
- No automatic notifications: Your designated contact must open the link to check for updates.
- Automatically deleted after the trip ends: See Data Retention and Privacy for retention periods.
Find the Feature and Agree to the Terms
點圖放大
- On the 'Map' tab, tap 'Info' to open the info panel, scroll down to the 'Trip Sharing' card, and tap it.
- On first use, a message titled 'Before Using Trip Sharing, Please Confirm' will appear, explaining what will be uploaded, who can view it, how long it's retained, and that it cannot replace emergency calls.
- After reading, toggle on 'I have read and understood the above information', then tap 'Agree and Continue'. You can also tap 'Read Full Privacy Policy' to view details.
點圖放大
點圖放大
To disable it later, tap 'Withdraw Consent and Disable Trip Sharing' at the bottom of the 'Create Trip Sharing' screen. This revokes the current link and immediately deletes the entire trip record on the server, including its name, times, route, location points, and link identifiers. If your phone is offline, the revocation is sent when connectivity returns; until then, the server data may still be viewable through the original link. The summary in iOS Trip History remains until you delete it manually.
Create a Trip
| Field | Description |
|---|---|
| Trip Name | Defaults to the currently loaded route name (or 'Mountain Trip Track' if no route is loaded); you can modify it, with a maximum of 60 characters. |
| Display Currently Loaded Route on Webpage | When enabled, your designated contact can see your planned route on the webpage (requires loading a GPX route first). |
| Share Planned Points | Shown only when the loaded route has points you marked beforehand (camps, water sources, summits, retreat points, and so on); expand it to choose point by point. Hut, water, summit, and hazard/retreat points are ticked by default; general points are not. Only the name, position, and type are shared; the note you wrote for a point is never shared. |
| Scheduled Departure / Scheduled End | Return time must be at least 10 minutes after departure time and not exceed 30 days. |
| Allow messages from viewers (from 1.1.9) | On by default. When on, anyone with the link can leave you a message on the page; see Messages. You can turn it off at any time during the trip. |
| Buffer Time | None, 30 minutes, 1, 2, 3, 4, or 6 hours; defaults to 2 hours. If the scheduled return time plus buffer time passes without confirmation, the webpage will display 'Overdue'. |
| Start Location Reporting Immediately After Creation | When enabled, location reporting starts when you create the trip. If disabled, you can tap 'Start Location Reporting' on the trip page later. |
Trip Name
Description:Defaults to the currently loaded route name (or 'Mountain Trip Track' if no route is loaded); you can modify it, with a maximum of 60 characters.
Display Currently Loaded Route on Webpage
Description:When enabled, your designated contact can see your planned route on the webpage (requires loading a GPX route first).
Share Planned Points
Description:Shown only when the loaded route has points you marked beforehand (camps, water sources, summits, retreat points, and so on); expand it to choose point by point. Hut, water, summit, and hazard/retreat points are ticked by default; general points are not. Only the name, position, and type are shared; the note you wrote for a point is never shared.
Scheduled Departure / Scheduled End
Description:Return time must be at least 10 minutes after departure time and not exceed 30 days.
Allow messages from viewers (from 1.1.9)
Description:On by default. When on, anyone with the link can leave you a message on the page; see Messages. You can turn it off at any time during the trip.
Buffer Time
Description:None, 30 minutes, 1, 2, 3, 4, or 6 hours; defaults to 2 hours. If the scheduled return time plus buffer time passes without confirmation, the webpage will display 'Overdue'.
Start Location Reporting Immediately After Creation
Description:When enabled, location reporting starts when you create the trip. If disabled, you can tap 'Start Location Reporting' on the trip page later.
- After filling in the fields, tap 'Create shared trip'.
- Confirm the trip details, departure time, return time, and overdue determination time in the summary, then tap 'Create Trip and Get Link'.
- On first creation, iOS will ask if you allow notifications; it's recommended to allow notifications to receive return reminders.
Share the Link with Your Contact
點圖放大
點圖放大
- Share Link: Opens the system sharing panel with a message containing the trip name, scheduled return time, link, and a reminder to call 119 or 112 if unable to contact after the scheduled time.
- Copy Link: Copy the URL to manually paste into messaging apps.
- Display QR Code: Let the other person scan it in person.
The 'Trip Information' section displays the scheduled return time, overdue determination time, link expiration, and last upload time. The link validity period depends on the trip status; see Data Retention and Privacy.
After Departure: Location Reporting, Reminders, and Completion
點圖放大
點圖放大
- Location Reporting: Your phone sends a location update at the time or distance interval you chose (about every 10 minutes by default). Each update includes coordinates, time, and accuracy, plus altitude and battery level when available. If there is no signal, updates are stored on your phone and sent when the connection returns. The 'Pending Location Points' section on the trip page shows how many are waiting.
- 'Always' Location Permission: Without this permission, the app cannot continuously report your location in the background. The trip page will remind you and provide a shortcut to 'Open Location Settings'.
- Reminder Notifications: 30 minutes before the scheduled return time, you'll be reminded if you need to extend; at the scheduled return time, you'll be asked if you've completed the trip; 15 minutes before the overdue determination time, you'll be reminded of the upcoming overdue status (only if buffer time is set).
- Confirm right from the notification (version 1.1.9 and later): Press and hold (or pull down) a reminder notification to see 'I'm safely down' and 'Extend 2 hours' buttons. After unlocking your phone, one tap is enough, without opening the app, even if the app was closed. The buttons need the phone to be unlocked so a stray touch on the lock screen does nothing.
- Reminders keep coming after the planned time (version 1.1.9 and later): Once the planned return time has passed, you are reminded every 30 minutes, up to 6 times (about 3 hours). They stop as soon as you confirm you are safely down or revoke the link, and move with the new return time if you extend the trip.
- Detecting that you may be down (version 1.1.9 and later): After you have left the start point, if the app sees you back near it, moving at vehicle speed, or standing still for about 20 minutes at about the start's altitude, it notifies you 'You may be safely down'. Driving to the trailhead does not trigger it; you must first have walked for a while. This is only a reminder: the app never confirms for you, you still tap the button. Detection needs location permission ('Always' for the background).
- Extend 2 Hours: If you need more time, tap once to extend your scheduled return time by 2 hours and let your designated contact know the plan has changed.
- Safely Returned: After confirmation, location reporting stops and your designated contact's page will display 'Safely Returned'. The server keeps the entire trip record for 30 days so your contact can review it; the page shows the exact expiry time. While the link is valid, you can download a GPX from the page with reported location points, and the planned route and planned points if you chose to share them.
- Revoke Link and Delete Location Data: Once the server receives the revocation, it immediately deletes the entire trip record, including the trip name, times, route, planned points, location points, and link identifiers; the link and GPX download stop working. If your phone is offline, the revocation is sent when connectivity returns, and the original link may remain viewable until then. Download the GPX first if you need it.
After completion or revocation, tap 'Done, move to trip history' to move the trip out of the current screen and into the iOS Trip History list. A completed link stays available until its original expiry; an early revocation leaves a history summary without location points. History summaries remain until you delete them manually. Shared location points are not saved as a Tracks route; start track recording separately to keep a full track. Only one trip can be in progress at a time.
What Your Contact Sees
Your designated contact can open the link on their phone or computer browser (in the form of akimap.app/g/…). The page automatically updates approximately every 30 seconds, with times displayed in Taiwan Time. On the map, the blue dashed line represents the planned route, the pink solid line represents the reported track, the green dot marks the starting point, and the pink circle marks the most recently reported location. If the climber shared planned points, colored dots also appear on the map: red for hazard/retreat points, orange for huts/camps, blue for water, purple for summits, and gray for others. Tap one to see its name.
Nearby place names: When a reported location is near one of the climber's planned points, or near a hut, trailhead, water source, saddle, or peak built into the offline map, its card shows 'Near ○○ (about N m)'. Your phone matches this from the GPS position. GPS can be off by tens of meters, so the page only says 'near' and does not claim the climber is exactly there.
Trip timeline: Above the list, the 'Trip timeline' groups consecutive reports near the same place into one stop. A place reported only once is 'Arrived' (huts, camps, trailheads, planned points) or 'Passed' (water, peaks); reports at the same place for 15 minutes or more become 'Stayed', with the approximate time. Times are report times, so the real stay may have been longer. If the latest stop also holds the latest report, it is marked 'Latest report is still near here'. Tap a stop to find it on the map.
Slope colors and direction of travel: The 'Slope' button at the top right of the map (off by default) colors the reported track by slope: orange-red is uphill and blue is downhill, and the deeper the color the steeper the climb or descent. Flat stretches and stretches without altitude stay orange, and a legend sits at the bottom left. When you turn it on, the track draws itself from the start to the latest position in about 2.5 seconds, then small white arrows along the line show the direction of travel. The line gets wider as you zoom in, and the arrows only become easy to read once you are zoomed in. Slope comes from the altitude the climber's phone reported by GPS, so treat the colors as a guide when the altitude is off.
點圖放大
點圖放大
| Webpage Display | What It Means |
|---|---|
| Not Yet Departed | The scheduled departure time hasn't arrived yet; location reporting will begin once the climber departs and has signal. |
| No Location Received Yet | The scheduled departure time has passed, but no location has been received yet (possibly due to lack of signal). |
| Trip in Progress | Location has been received; the page displays the last location and scheduled return time. |
| Over 1 Hour Without New Location | Yellow alert. Mountainous areas often lack signal; this doesn't necessarily indicate an emergency. The page only displays the last uploaded location. |
| Past Scheduled Return Time | The overdue determination time has passed without confirmation. The page advises calling 119 or 112 if unable to contact the climber, and to provide the last location and time. |
| Safely Returned | The climber has confirmed completion of the trip. |
| Messages (from 1.1.9) | When the hiker has messages on, a Messages card at the bottom of the page lets you leave a message under a name of your own; see Messages. Trips created with an older app version have none. |
| This Trip Link is No Longer Valid | The link has been revoked or exceeded the retention period. |
Not Yet Departed
What It Means:The scheduled departure time hasn't arrived yet; location reporting will begin once the climber departs and has signal.
No Location Received Yet
What It Means:The scheduled departure time has passed, but no location has been received yet (possibly due to lack of signal).
Trip in Progress
What It Means:Location has been received; the page displays the last location and scheduled return time.
Over 1 Hour Without New Location
What It Means:Yellow alert. Mountainous areas often lack signal; this doesn't necessarily indicate an emergency. The page only displays the last uploaded location.
Past Scheduled Return Time
What It Means:The overdue determination time has passed without confirmation. The page advises calling 119 or 112 if unable to contact the climber, and to provide the last location and time.
Safely Returned
What It Means:The climber has confirmed completion of the trip.
Messages (from 1.1.9)
What It Means:When the hiker has messages on, a Messages card at the bottom of the page lets you leave a message under a name of your own; see Messages. Trips created with an older app version have none.
This Trip Link is No Longer Valid
What It Means:The link has been revoked or exceeded the retention period.
Messages: Leaving Notes Between Your Contacts and You (from 1.1.9)
Besides following your location, your contacts can leave you a message on the share page (to ask about the weather, or remind you about supplies); you reply in the app and they see it on the page. This is not instant messaging: your phone receives a message only the next time it has a connection, which in the mountains can take hours. Messages are also not a way to call for help; in an emergency call 119 or 112 directly.
Turning it on and off
- When you create a trip, "Allow messages from viewers" in the Messages section is on by default; turn it off if you do not want messages.
- During the trip you can switch "Allow messages from viewers" at any time in the Messages section of the trip screen. While off, the page shows no messages and takes no new ones; existing messages are not deleted and come back when you turn it on again. Switching needs a connection.
- On a team trip the leader, the teammates and the viewers share one thread. When the leader turns messages off, teammates' phones hide them the next time they contact the server.
Reading and replying in the app
- Open the trip screen and tap "Chat" in the "Trip | Chat" switch at the top (from 1.2; earlier versions had a Messages section further down the trip screen). Viewers' messages are on the left, yours on the right.
- During a trip you can also tap the chat icon next to the status pill on the map to open the conversation full screen; "Close" at the top returns to the map. The icon only appears for trips with messages turned on.
- Type in "Write a reply…" (up to 200 characters) and tap Send.
- With no signal, a message shows "Not sent yet; it goes out when there is signal" and is sent automatically, once, when you are connected again.
How you notice a new message: while the trip screen is open it refreshes about every 15 seconds; a new message from a viewer makes the phone vibrate once while the app is on screen; the Trip Sharing card shows a red unread count, and so does the chat icon on the map (99+ above 99). With the app in the background, every successful location report also checks for messages and a new one raises a notification. With no signal, you receive it the next time you are connected.
The name viewers see: set it under Settings → Trip Sharing Link, "Name in messages" at the top (optional, up to 20 characters, for example "Sam"). Set it once and it applies to every trip; a change takes effect for new messages at once, and earlier messages keep the name they were sent with. Without one, viewers see "Hiker". On a team trip, teammates' messages use the name they joined with, which they cannot change separately.
Messages on the page: viewers type a name of their own (no sign-in, not verified) and a message in the Messages card on the share page. The page shows each viewer message's state: "Not delivered yet" means your phone has not received it, and "Reached the hiker's phone" means it has.
Team: Share with Friends
When you travel with friends, you can turn on Team: each member reports their own location from their own phone, and your contacts see everyone through the same link. This is lightweight location sharing, not guide-led group management: no rosters, health or insurance records, pre-trip checks or liability records.
Leader
- On the 'Create Trip Share' screen turn on 'Share with teammates', enter your name and the team size (including you, up to 10), then create the trip.
- On the trip page, tap 'Generate invite code' in the Teammates section. The code and a QR code appear; the code is shown only once and is valid for 30 minutes by default.
- Let teammates scan the QR code, or tap 'Copy invite code' and send it with the share sheet. Generating a new code immediately invalidates the old one, so regenerate it if a code leaks.
- The teammate list on the trip page shows each person's name, last signal time and battery. A teammate who has been silent for a while is flagged; you can 'Set as sweep' (only one at a time) or 'Remove' a teammate.
Teammate
- Open Trip Sharing and choose 'Join a friend's team'.
- Scan the leader's QR code, or type the invite code by hand. Then enter the name shown on the team (it need not be your real name).
- Read the notice and turn on the agreement yourself, then tap 'Agree and join'. The leader cannot agree for you.
- After joining, your phone reports your location in the background under the trip's settings; without signal it is stored on the phone and sent when you are back online. To leave, tap 'Leave the team and delete my locations' on the trip page.
Who sees what: anyone with the trip link sees each teammate's name, track, latest position and battery, and the GPX download has one track per teammate. A teammate never receives the share link and cannot do any leader action; a teammate sees only their own status in the app, not other people's positions.
| Situation | What happens |
|---|---|
| Wrong, expired or replaced code, or the trip was revoked | Joining fails and the app always shows 'That invite code is invalid or has expired', without saying which. This prevents code guessing. Ask the leader to check or generate a new code. |
| The team is full | The app shows 'The team is full'. Ask the leader to check the team size or remove someone who is no longer coming. |
| Someone on the team has the same name | Pick another name. |
| You already have a trip in progress | Only one trip at a time; end or leave it before joining. |
| You leave the team or the leader removes you | The server immediately deletes all your location points and identifying data. If you are offline, leaving is sent when connectivity returns. |
| The leader ends the trip | Teammates' phones stop reporting automatically. Teammate data is deleted together with the trip under retention. |
| The leader revokes the trip | The whole team's server data is deleted immediately. |
Wrong, expired or replaced code, or the trip was revoked
What happens:Joining fails and the app always shows 'That invite code is invalid or has expired', without saying which. This prevents code guessing. Ask the leader to check or generate a new code.
The team is full
What happens:The app shows 'The team is full'. Ask the leader to check the team size or remove someone who is no longer coming.
Someone on the team has the same name
What happens:Pick another name.
You already have a trip in progress
What happens:Only one trip at a time; end or leave it before joining.
You leave the team or the leader removes you
What happens:The server immediately deletes all your location points and identifying data. If you are offline, leaving is sent when connectivity returns.
The leader ends the trip
What happens:Teammates' phones stop reporting automatically. Teammate data is deleted together with the trip under retention.
The leader revokes the trip
What happens:The whole team's server data is deleted immediately.
Data Retention and Privacy
Trip Sharing uploads the trip name, scheduled departure and return times, planned route and the planned points you tick (if you enable route display; name, position, and type only, never notes), and location updates at the time or distance interval you choose (about every 10 minutes by default). A location near a planned point or a place built into the offline map also carries that place name and an approximate distance; this matching happens offline on your phone. No account is required, and names or phone numbers are not collected. If Team is on, each teammate also uploads the name they typed and their own location points (see Team). See the Privacy Policy for details.
| Situation | Data Retention Period |
|---|---|
| You tap 'Safely Returned' | The server keeps the entire trip record for 30 days (the link remains accessible and the GPX can be downloaded), then automatically deletes it. |
| Overdue without confirmation, with location points received | The server keeps the entire trip record until 30 days after the overdue determination time (for family and rescue services to review), then automatically deletes it. |
| Overdue without confirmation, no location points ever uploaded | The server keeps the entire trip record until 3 days after the overdue determination time, then automatically deletes it. |
| You revoke the link | The entire server-side trip record is deleted as soon as the server receives the revocation, and the link and GPX stop working. Offline revocations are sent when connectivity returns. iOS Trip History keeps only a summary without location points or secrets until you delete it manually. |
You tap 'Safely Returned'
Data Retention Period:The server keeps the entire trip record for 30 days (the link remains accessible and the GPX can be downloaded), then automatically deletes it.
Overdue without confirmation, with location points received
Data Retention Period:The server keeps the entire trip record until 30 days after the overdue determination time (for family and rescue services to review), then automatically deletes it.
Overdue without confirmation, no location points ever uploaded
Data Retention Period:The server keeps the entire trip record until 3 days after the overdue determination time, then automatically deletes it.
You revoke the link
Data Retention Period:The entire server-side trip record is deleted as soon as the server receives the revocation, and the link and GPX stop working. Offline revocations are sent when connectivity returns. iOS Trip History keeps only a summary without location points or secrets until you delete it manually.
Messages (from 1.1.9): the message text, the name the sender typed and the time are stored on the server, kept with the trip and deleted when the trip expires or you revoke it; a member's messages are deleted when they leave the team. Messages do not appear in the GPX or in the admin trip list.
When a retention period expires, the server deletes the entire trip record (name, times, route, planned points, location points, and link identifiers), and the link becomes invalid. Revocation skips the retention period: once received by the server, it immediately deletes the entire record without keeping a revocation record. iOS Trip History summaries stay on this device, are not backed up to iCloud, and remain until you delete them manually.
Trip Sharing FAQs
What happens if there's no signal on the mountain?
Where do nearby place names come from? What if I have no offline map?
Will my designated contact receive notifications?
How soon do I get a message my contact leaves? (from 1.1.9)
I do not see a Messages section, or the page has no Messages card. (from 1.1.9)
Who can see my messages?
What if I forgot to tap 'Safely Returned'?
What if someone who should not have the link gets it?
What if creating a trip fails or shows 'Currently Unable to Sync'?
Can I share multiple trips simultaneously?
Do teammates have to pay?
Do teammates have to give a name or phone number?
Can I view my trip page outside the app?
Can't find an answer? See Support and FAQ. Screens may vary by app version. Support