Terms of Service

Otinerary is a trip planning, collaboration, booking records, expense calculation and public itinerary service operated by David Kim. The initial audience is in the United States. These Terms apply to accounts and use of the service.

Otinerary does not provide booking purchases, banking, payment or money transfer services. Bookings, expenses, cost sharing and settlements are user-entered records and calculations and do not replace actual booking fulfillment or payment. The external Ko-fi support link opens a separate service; it is not a feature for Otinerary to collect card information directly or execute payments. Support is not guaranteed to be a tax-deductible donation.

Users must be at least 18. Initial account setup requires confirming this age requirement and explicitly accepting the Terms. This does not involve collecting birth dates or verifying everyone's actual age.

Accounts use verification codes received by email. Keep your email and account access secure, and do not use another person's account without permission. Notify the operator if you suspect unauthorized account access.

Information processing is described in the Privacy Policy. The Privacy Policy is a notice about information processing; the current account flow does not require a separate policy-consent checkbox. Terms acceptance, policy notice and photo publication confirmation have different scopes. Where applicable law requires separate consent for specific processing, that procedure must be followed.

Trip members view or change information according to membership and assigned permissions. The trip manager and shared-expense treasurer have different roles, and the payer, cost sharer and fund holder may also differ.

Check whom you invite and what you publish, and obtain authority to enter or share others' personal information, booking and expense records. Users and companions must check shared-record accuracy and whether payments and settlements actually occurred. Linking an itinerary item or booking to an expense connects records; it does not automatically create spending or change a booking. A suggested settlement is not a completed payment, and saving a payment record does not transfer money.

Users retain their content rights. To upload or enter photos, text or manually created place information, you must have the necessary copyrights, usage rights and authority to process other people's personal information.

You grant Otinerary a non-exclusive license to store, process and display content and perform necessary transformations, such as photo cropping, resizing and reencoding, to provide the service. This license is limited to the trip collaboration, publication and copying features you choose and operations needed for them. Content ownership is not transferred to Otinerary. Photo publication confirmation does not include permission to copy photos into other users' trips.

Do not enter or publish content that infringes others' privacy, copyright or other rights. Sourced place and map data are also subject to their providers' rights and terms.

A public trip is a public version separate from the original. Reviewing the preview and completing publication authorizes display of its public title, author display name, description, trip tags, destinations and included itinerary and place information to internet users. Places may include addresses and saved coordinates.

Trip photos are managed in Edit trip details. A saved private photo or previous public cover does not create new publication permission. Initial publication and republication require reviewing the current text and saved trip photo, or the no-photo state. If there is a photo, you must review its rights, personal information and public effect. Confirming no photo does not approve future photos.

Replacement, removal or first addition of a trip photo while published applies to both private and public photo states after reviewing the state and public effect again. Approving only the photo does not publish unreviewed title, description or itinerary changes. Text changes need a separate reviewed publication update. Changing private text or photos while unpublished does not republish automatically.

Canceling before confirmation does not change the previous confirmed state. If confirmation fails before reaching the server, the previous state remains. Responses can be lost after server application, so a network error alone does not prove a change was not saved. Check the current state or the result of retrying the same request. Cleanup of remaining upload candidates and files is separate from display changes.

Ordinary sign-out or normal session termination does not withdraw confirmed public photo approval. New changes and reuse of unused confirmation proofs from ended sessions are blocked. Explicit unpublishing or withdrawal and account, permission, trip, photo and publication restrictions continue to apply.

Uploading or publishing STOP photos and choosing standalone public covers are currently unavailable. Historical files or references remaining physically do not mean the feature is offered or new permission exists. Current trip photo processing does not store the original file unchanged and excludes additional metadata such as EXIF and GPS during reencoding. It does not automatically remove all faces, addresses, documents or free-text personal information, nor guarantee the same treatment retroactively for every historical file.

Actual original trip dates, companions, bookings, expenses, private notes and authentication identifiers are excluded from public fields. Personal information in free-text public descriptions or photos is not all removed automatically. Original text edits do not automatically change published text.

Publishing permits other users to copy the published itinerary, place information and sources into their own private trips and use them there. Each copy is a separate, independent trip.

Photos, previous public covers, photo publication permissions, private notes, bookings, expenses and unpublished data are not copied. Confirming public photo display does not grant others the right to copy the photo.

Unpublishing or deleting the original trip or account does not recall independent copies already made by others or screens and photo files saved externally. Sources and usage terms of copied provider data must be preserved. Excluding photos from app copying is separate from the limits on recalling bytes already delivered externally.

Use of Google Maps is subject to the Google Maps Terms of Service and Google's Privacy Policy. Geoapify and original place data may be subject to the Geoapify Terms and Conditions and OpenStreetMap copyright and ODbL notice and other applicable source terms.

Do not remove place or map attributions or bypass provider usage restrictions. Place and route information does not guarantee completeness, currency or safe passage. Check trip conditions and actual routes before departure. Features such as public transit routing may be paused or unsupported. Opening external map links is subject to that service's terms.

Place information confirmed with Wikidata is under CC0, and place photos from Wikimedia Commons are under the license and attribution terms shown with each photo. Search-term suggestions use Anthropic's AI service; the Privacy Policy describes what is sent.

Ko-fi support links open an external service. Its terms and its payment providers' terms apply to payments, support, refunds and personal information processing. Using Otinerary's trip records is separate from supporting it externally.

Unauthorized account or trip access, infringement of others' privacy or copyright, illegal content, forged consent, malicious use and bypassing request limits, security or permission protections are prohibited.

To report infringement or misuse, send the relevant public link and a description to davidkim9299@gmail.com. After necessary review, the operator may take appropriate steps, such as restricting public access, under applicable law and to protect the service.

Unpublishing blocks public access within the service without immediately physically deleting the original and publication history. Trips can be restored for 30 days after deletion. After the restoration deadline, necessary exceptions, valid references, uncertain success and retry states are checked, and cleanup follows normal operational retention targets and actual scope. Expiry alone is not shown as completed cleanup. The trip's 30-day restoration period is not every photo's retention deadline. Restoration or account state changes do not republish trips automatically.

Final account deletion confirmation first blocks app and public access and changes display information. This is separate from actual completed cleanup of personal information, authentication accounts, photos and backups. The trip's 30-day restoration period does not apply. Request receipt and blocking, review and waiting or holds, actual processing and retries, and confirmed service cleanup are explained separately. Required shared-trip roles, such as manager, must be resolved before deletion. Privacy rights requests under applicable law can be submitted to the operator separately from that process.

Shared itinerary, expense and settlement records needed by other members may be retained with a “Former user” label and minimal information as needed for the trip and settlement. Unnecessary private notes, booking references and authentication links are subject to follow-up cleanup. Changing a display name alone does not make all shared records irreversibly anonymous.

Follow-up cleanup is limited to explicitly confirmed requests and targets with reviewed references and processing state. New account deletion requests and trip photo changes confirmed after the Privacy Policy takes effect are handled within their reviewed scope. Existing material is not cleaned up in bulk; material directly included in a new deletion request is reviewed individually for valid references and scope. Bulk automatic cleanup of retired STOP photos, previous standalone public covers and existing unprocessed files is not enabled. Follow-up work needing separate review is shown as waiting or on hold, not as completed cleanup. Privacy rights inquiries and deletion requests remain available.

Cleanup targets, target periods, exceptions, backup scope, expiry and delays follow the Privacy Policy's retention and deletion guidance. Blocking access or receiving a request is not described as completed deletion. Failures, external dependencies or legitimate retention exceptions are explained with remaining scope and reasons and handled according to applicable law. Operational targets alone do not guarantee providers' actual retention or automatic deletion settings for logs, email delivery records or backups.

App-managed deletion does not automatically delete others' independent copies or logs and backups external providers retain under their own policies. The service offers no function to recall image bytes already delivered externally or files saved separately.

Necessary minimal processing records and remaining backups follow separate retention standards after service cleanup. Before restoring older backups, verified current deletion and withdrawal states and necessary minimal identifier links are checked. Service access is not automatically resumed if necessary evidence or keys are missing or the permitted restoration deadline has passed. Details of retention purposes, standards and processing status are available in the Privacy Policy and through contact channels.

The service may continue to improve, but uninterrupted or error-free availability is not guaranteed. Some features may be temporarily restricted for outages, maintenance or misuse response. Material service or Terms changes are announced appropriately, such as within the service. Where a material Terms change requires new acceptance by existing users, that procedure is followed. Confirming publication of an individual photo does not replace acceptance of Terms changes.

These Terms do not exclude consumer rights protected by applicable law or liability that cannot be limited by law. Delayed follow-up cleanup or protective measures do not waive statutory privacy rights or processing deadlines.

To the extent permitted by applicable law, California law is the default governing law for these Terms. Mandatory laws and consumer protections applicable to the user may take priority. This wording alone does not determine applicability of or exemption from all privacy laws.

Operator David Kim · davidkim9299@gmail.com

Account and privacy contact options and deletion features are available in Privacy and account.