1. About Outpost and this policy
OrbiterAgent provides Outpost, an iPhone app for nearby communication, navigation, and preparedness. This policy describes the current iOS app, these Outpost information pages, and Outpost-related support. Other OrbiterAgent products and outside websites have their own policies.
Outpost does not require an Outpost account, email address, or phone number. Your nickname and a cryptographic device identity are created on your phone. Outpost does not operate a central message-history or cloud-AI service for the app.
2. Information kept on your phone
Outpost stores your settings, contacts, group information, chats, beacons, saved places and routes, supplies, item photos, storage locations, checklist progress, and cached conditions locally. Personal records are stored in an encrypted app database. Device identity and storage keys use the iOS Keychain. Public map downloads, reference documents, model files, and the public Shop cache use separate local files; they are not all stored in that encrypted database.
Installed Advisor inference runs on your phone. Questions and AI answers are held for the current app session rather than uploaded to a cloud AI provider. Reference guides and PDFs may be bundled or downloaded; bookmarks and installation preferences can remain on the device. Eligibility for an App Store review request is also recorded locally.
3. Sharing with nearby phones
- Private and group message content is encrypted for its intended participants. Participating relay phones can handle encrypted packets and see public sender and routing information. Encryption does not make a nickname anonymous or verify a person's identity; compare contact fingerprints in person.
- Nearby chat and beacons are public to participating Outpost phones that receive them. They can expose your nickname, public device identity, message, timestamp, and any beacon coordinates you choose to include. GPS is not automatically attached to chat messages.
- Optional relaying forwards eligible packets through other Outpost phones. A recipient may save, copy, or share received information. Blocking someone or deleting your own copy cannot remove copies already held by another phone.
- Contact cards and QR codes contain a nickname and signed public identity information, not your private keys. Exporting or sharing other information sends the selected content to the app or recipient you choose.
4. Device permissions
- Location, when allowed while using the app, supports your map, coordinates and altitude, city/county lookup, forecasts, route starting points, and star-map alignment. Online lookups send relevant coordinates or searches to the providers described below. Sharing a location in a beacon is a separate choice.
- Bluetooth supports nearby discovery and packet exchanges. Your public Outpost identity and the content or encrypted packets you choose to send may reach participating phones.
- Camera access supports QR scanning and the sky-camera view. Outpost does not upload or record sky-camera frames as part of those features. Motion and barometer readings support orientation and pressure tools on compatible devices.
- Photos selected for routes or supplies are stored locally. Notification permission enables activity alerts generated on your phone; previews may display message content when enabled in your preferences.
You can decline optional access or change it in iPhone Settings. Features depending on that access may be unavailable or use manual input instead. Hardware and iOS background restrictions also apply.
5. Online services and their requests
Outpost uses online services for the features below. The service receiving a request can receive the request contents, your IP address, and ordinary network or device metadata. Those services have their own privacy practices; local storage does not mean that every app feature operates without an internet request.
- Apple services process address searches, route endpoints, and reverse geocoding of coordinates. Apple also handles App Store distribution, native review requests, and Apple-hosted asset downloads. See Apple's privacy information.
- The National Weather Service receives coordinates to supply forecasts for supported U.S. areas. See the National Weather Service privacy notice.
- OpenFreeMap supplies online and downloaded map data. Map requests identify the requested map area or tiles. See OpenFreeMap for service information.
- Supabase serves the public Shop catalog and hosted product artwork. Catalog requests do not include your chat history, contacts, GPS, supplies, or Advisor questions. Product image hosts also receive the image requests needed to display their artwork. See Supabase's privacy policy.
- Shop links open outside retailer websites. A configured link may contain affiliate parameters, and marked affiliate links may earn OrbiterAgent a commission. Retailers handle their own cookies, accounts, orders, payments, and privacy choices. Outpost does not process the retailer's checkout or receive your payment-card details.
Satellite Check-in prepares text for you to review, copy, and send using Apple Messages. Outpost itself does not send satellite messages. If you choose to send the prepared text, Apple, your messaging provider, and the recipient handle it under their respective services and terms.
6. Analytics, support, and this website
Outpost builds with usage analytics use PostHog US Cloud to understand onboarding and feature use. Events can include introduction steps and reading time, permission choices, tabs and feature actions, download or operation outcomes, app and iOS versions, device model, timestamps, and anonymous installation/session identifiers. The analytics identifier is separate from your public Outpost identity; no Outpost account is needed.
Analytics do not include chat or beacon text, nicknames, contact keys, Advisor questions or answers, GPS coordinates, addresses, photos, supply names or storage locations. Screen recording, automatic capture of text and taps, advertising identifiers, and behavioral advertising are not enabled. IP-based location enrichment is disabled; PostHog still receives ordinary network requests and their IP addresses. See PostHog's privacy policy.
Usage analytics are enabled by default and can be turned off under Settings → Anonymous usage analytics. Turning this off stops collection of new events. A bounded queue of events collected while enabled can be stored on your phone while offline and sent later; information already collected can remain subject to our analytics retention settings. Turning analytics off does not disable the app's field tools.
We do not sell your local chats, contacts, supplies, or Advisor questions. Apple may provide installation, crash, testing, and App Store information under its own settings and terms, including TestFlight feedback you choose to submit. Older app builds without this analytics integration do not send these PostHog usage events.
If you contact us, we receive the contact details, messages, and attachments you choose to send. We use them to respond, troubleshoot, and meet applicable obligations. Visiting these pages also involves ordinary requests to our website host and content-delivery providers. Do not send private message histories or precise locations to support unless they are needed for your request.
7. Retention, deletion, and your choices
Personal app records generally remain on your phone until you remove them or clear local app data. Packet lifetimes limit transfer attempts; beacon expiration does not erase your history or copies on other phones. Nearby posts have a limited local history, but recipients can retain their own copies. Cached files may also be removed by iOS.
Settings → Delete local app data clears the app's personal records, downloaded route maps, saved Shop cache, and removable Advisor data and packs. Bundled references remain part of the installed app. Device identity keys remain in the Keychain after this in-app deletion; the app does not promise that uninstalling deletes every Keychain record.
You can manage permissions and notification previews in app or iPhone settings and use the app's available export and deletion controls. We cannot retrieve your local-only database from our servers or remotely erase data another recipient has retained. For information we actually hold, such as support correspondence, you may request access, correction, or deletion by contacting us. Applicable law may provide additional rights or require some information to be retained.
8. Security and processing locations
Outpost uses cryptographic protections for personal storage and private message content, but no device, software, or communication method is completely secure. Public messages, public identity metadata, shared locations, unlocked devices, and information you export require your own care. We do not promise anonymity, perfect confidentiality, or guaranteed delivery.
Data you send to online providers or to support may be processed in the United States or other countries where those providers operate. Local app processing and direct phone-to-phone sharing follow the location of the participating devices.
9. Children and policy changes
Outpost is not directed to children under 13. If you believe a child has provided personal information to us, contact us so we can address the information we hold. Nearby public chat is not a private space.
We will update this page and its effective date when these practices change. Material changes may also be communicated in the app or through another appropriate notice.
10. Contact
Privacy questions and requests: privacy@orbiteragent.com. Product support: support@orbiteragent.com. Legal questions: legal@orbiteragent.com.