Privacy Policy

Effective 2026.11.20 · Edition 9 · Operator MOYO Studio · Contact moyoofficial.help@gmail.com

MOYO Studio (Onbit) processes personal information lawfully and keeps it safe, in accordance with Korea's Personal Information Protection Act and related laws. Under Article 30 of that Act, we establish and publish this policy so that you know the procedures and standards by which your personal information is handled, and so that any related complaint can be resolved quickly.

In one paragraph

Onbit's Globe, Passport, stamps and calendar work from start to finish without an account. Photos are read on your device for their capture location and time only; originals never leave it, except a booking screenshot you choose to have read. Your Trips tab records (trip summaries, packing lists, spending, exchange rates and so on) are kept on our server under an anonymous ID even without an account, and you can delete them in the Me tab at any time. The only photos and videos uploaded are one cover photo per city once you link an account (a new copy with no location data), any receipt photo you attach to a shared trip, and any two-second clip you add to a shared vlog, and you can see and delete all of them under Me > Your data on our server. We do not open the photos and videos on our server. Booking screenshots are sent, with their capture location removed, to Google's AI (Vertex AI) to read their text, and are not stored. Your device's location and your photos' capture coordinates are never uploaded under any circumstance. We do, however, store the coordinates of places you pick on the map (a shop, a sight) so we can show them on the map. Before you connect a friend, we ask for your consent to share location information; once connected, only that friend sees your name and city records, and we let you know each time they are shared. People you invite to plan a trip together see only that trip, and the two-second clips added to it for the vlog are seen only by its members. If you open a past trip to "Friends" or "Everyone", only its route goes out (cities, place names, which day, month, number of days, nickname) — never photos, notes, spending, companions or exact dates. The default is "Only me". Place search, maps, travel times and weather are fetched from Google on your behalf, and trip info (typical weather for the month, weather alerts, public holidays, festivals and travel advisories) comes from public agencies and weather providers; neither gets your name or email. On a laptop, you can use the same account in the web version (app.getonbit.app). When you sign in there by scanning a QR code with your phone, we keep only that browser's name (such as Chrome · macOS) for a few minutes, and signing out of the web version clears what Onbit left in that browser. The payment details you add to a payment request stay on your device and are never sent to our server. There are no ads, we do not track you outside the app, and we never sell personal information.

Summary · key processing at a glance

The essentials before the full text. This is a summary; the full text below governs.

  • Permissions requested: photos, location, notifications and the camera (with the microphone), each asked the moment you tap that feature (Article 2-2)
  • What we process: an anonymous identifier; if you link an account, your email, name, city records with the days you were there, and one cover photo per city; if you use the Trips tab, even without an account, trip records and trip summaries; if you plan a trip together, that trip's plan, packing list, spending, receipt photos and members' display names; if you add clips to a shared vlog, two-second clips with the minute they were shot and a caption; if you have a booking screenshot read, the screenshot you chose (not stored once read); if you open a past trip to others, that trip's public copy and your likes and copies; if you report or mute someone, that record; if you sign in to the web version by scanning a QR code, that browser's name and a single-use sign-in slot (deleted within minutes); if you sign in to the web version, a "signed in on the web" record (browser name, when and how); if you make a payment request link, a record of that link; if you choose your passport country, that country; if you bring a quiz result from the website into the app, your traveler type; if you turn on notifications, a device token and your device's time zone
  • Location: your device's coordinates are never sent to our server. The result of turning a photo's capture location into a city on your device (which city you were in and when), and the place names and place coordinates you write or choose in your trip records, are kept on our server
  • Sensitive data, national identifiers, biometrics: not processed
  • What other people can see: a friend connected by code sees your name, city records, (if enabled) cover photos and calendar "Together" trips (Article 4-2); members of a shared trip see that trip's contents, who added what, who picked which places, and the clips members added (Article 4-3); the route of a trip you open to "Friends" is seen by your friends, and the route of a trip you open to "Everyone" by any signed-in Onbit user (Article 4-4); anyone you send a payment request link sees the trip members' display names, the amounts owed and the "sent" marks (Article 4-5)
  • Collected automatically: crash diagnostics and anonymous analytics — analytics can be turned off in Me > Data. The web version loads neither, and the website (getonbit.app) uses only cookieless visit counts (Article 10). Adding to trip statistics (numbers that identify no one) can be turned off under Me > Notifications > "Help other travelers anonymously" and for each trip (Article 2.9)
  • Third-party disclosure: none / Processors: Google LLC (Firebase, Google Maps Platform, Vertex AI) and Vercel Inc. (website hosting and visit counts) / Overseas transfer: United States (diagnostics, analytics, maps and place information, the website); wherever Google processes each request (reading booking screenshots)
  • Retention: destroyed immediately when you delete your account or use "Delete my records from the server" (booking screenshots are never stored; shared trips until the trip is deleted or everyone leaves; clips you added until you withdraw them or leave the trip; a trip's public copy until you set it back to "Only me"; QR sign-in slots at most 15 minutes; "signed in on the web" records until you sign out everywhere else or delete your account; payment request links 30 days; diagnostics 90 days; analytics 14 months; location use and provision records 6 months)
  • Complaints: MOYO Studio Privacy Officer · moyoofficial.help@gmail.com

Article 1 (Scope and where to find this)

This policy applies to the app "Onbit" provided by MOYO Studio ("the Company"), its web version (app.getonbit.app), the Onbit website (getonbit.app, including the pages that open links made in the app and the traveler type quiz), and the quiz's former address (onbit-visa.web.app, which serves the same quiz and its "Continue in the app" link). The same text is available at any time in the app under Me > About > Privacy Policy, and on the web at getonbit.app/en/legal/privacy.
Business information

  • Trade name: MOYO (모두의 요리)
  • Representative: Kyunghwan Im
  • Business registration number: 836-13-02732
  • Address: 18-16 Mabang-ro 10-gil, 4F E223 (Yangjae-dong, Jinwoo Bldg.), Seocho-gu, Seoul, 06776, Korea

Article 2 (What we process and how we collect it)

1. Generated automatically when you use Onbit without an account

  • Anonymous authentication identifier (UID), app installation identifier
  • Usage records: city keys, country codes, day-count buckets, how often trip features are used and in which size bucket (creating a trip, invites, plan items, departure details, expenses, settling up, making videos, opening pre-trip links; never what you wrote, amounts, dates or names) and similar aggregate events
  • Crash diagnostics: where in the code the error occurred (stack trace), device model, OS and app version, IP address

2. When you link an account (optional)

  • The email address provided by Apple or Google, and the name they supply
  • The passport name you choose

Trips tab records are kept under an anonymous ID even without an account (2.3-2). If you link an account, the same records move to it and can be restored on a new device. Planning a trip together (2.3-3) and the web version (2.3-9) require a linked account.

3. Kept automatically once an account is linked (optional)

  • City records (city name, country code, day count, first day lit, photo count)
  • The list of days you were in each city, and how many photos you took on each of those days — used so the server can send the "On this day" notification. Readable only by you; never shown to friends.
  • Light shards, places saved for this year and when you saved them, year stamps and arrival marks, quest progress, interest in printed items
  • One cover photo per city, and the note you wrote on that photo (cover photo backup can be turned off under Me > Your data on our server)
  • On-device identifiers pointing to the photos you chose for covers and stamp backs (not the photos themselves)
  • Home city: the city name you confirmed (not an address), used to leave outings near home out of your trips
  • Your goal for this year (how many new countries)
  • Your passport country: the country you choose under Me > Passport. It decides which government's travel advisories, entry information and emergency contacts we show you. If you don't choose one, we guess from your device's region setting (or, failing that, the app language: Korea for Korean, the United States for English), and the guess is not stored.

3-2. When you use the Trips tab (optional; kept under an anonymous ID even without an account)

  • The trip records you write or choose: legs (mode of transport; flight number, aircraft type, registration, seat, cabin, terminal, gate; scheduled and actual times; lounge, meal, miles and similar), places (name, category, rating; menu, price, wait, room, nightly rate and similar), spending (amount, currency, category), city notes, and your trip rating and one-line summary
  • Travel companions: their names, if you write them. Only you can see these names, and they are left out of "One image" share cards by default.
  • On-device identifiers pointing to the photos attached to a record (the photos themselves are not uploaded)
  • Packing lists and what you checked off, spending (amount, currency, category, number of people splitting it), and exchange rates you set
  • Trip summaries: numbers such as the trip's cities, dates, days stayed, ways of getting around, rating, and photo and video counts (no coordinates)
  • Places you loved: the Google place ID, name, coordinates and Google Maps link of the place you chose, how it was (loved it, it was fine, not great), what was good, a one-line note, and on-device identifiers pointing to attached photos (the photos themselves are not uploaded)

3-3. When you plan a trip together (optional; requires an account)

  • The trip: cities, dates (or number of nights), the creator's identifier, and a city label (Korean and English names and a city key)
  • Members: identifier, the display name used in that trip, role (creator or member), and when they joined
  • The plan: place labels, Google place IDs, place coordinates, Google Maps links, day, time, "been there" marks, and who added each
  • Packing: items (built-in items are stored as item codes and shown in each viewer's language) and checks, and who added each
  • Recent changes: who did what (joined, added a place, set the dates and so on)
  • Picking together: for each place idea that isn't on a day yet, the identifiers of the members who tapped "Want to go"
  • Invite links: the invite code, expiry (7 days), usage count, the inviter's display name and the trip name, and whether it was turned off
  • Notification send marks: kept so the same reminder is never sent twice (which reminder went to whom). For "waiting on your payment" and "help pick places" reminders, we keep who sent it, who received it and the recipient's date (plus the amount, for payments), so each goes out at most once a day. Only the sender and the recipient can read these marks (server security rules).
  • In-app invitations: an invitation kept under the recipient's account (the sender's identifier and display name, the trip's cities and dates, and whether it was accepted)
  • Invites by email: the email address the inviter types in. If an Onbit account uses that address, we send an in-app invitation; we never tell the inviter whether an account exists. The address is used only to send the invitation and is not stored.
  • Finding people by name: you can find only friends you're already connected with and people you've planned a trip with before. There is no way to look up strangers by name.

3-4. Trip ledger and settle-up (optional)

  • Expenses: what it was, amount, currency, the exchange rate used and its date, the KRW amount, the card charge in KRW, category (flights, stay, food, coffee and snacks, getting around, sights and tickets, shopping, other) and detail, how it was paid (card, cash, transit card, app pay — we never take card numbers), place (Google place ID, name, coordinates), time, who paid, who's splitting, receipt items and who had each, each person's share, whether it was tax-free, tip, notes, tags, date, and who added it
  • Receipt photos: a new image, no more than 1600 px on the long side, made from the photo you chose. It is uploaded to our storage so members of the shared trip can check it when settling up.
  • Settle-up: "sent" and "received" marks (who sent, who received, amount)
  • Payment request links: the identifier of the person who made the link, the trip, when it was made and when it expires (30 days), and when we first saw that everything was settled. What people see when they open the link is in Article 4-5.
  • How to pay you (bank and account number, or a payment app username, and your name): if you add it, it is saved only on that device (in the web version, in that browser) and never sent to our server. When you use "Request payment", it goes into the message text and out through the app you choose (KakaoTalk, Messages and so on).

3-5. When you use place search, maps, travel times, weather and trip info

  • What we send to Google (our server makes the request on your behalf): the search text, the coordinates at the center of the map (where you moved the map — not your device's location), place IDs, the coordinates of trip cities and saved places, and the app language. We never send your name, email or account details.
  • Trip info (forecasts, typical weather for the month, weather alerts, public holidays and festivals): our server sends only the trip city's coordinates, the country, the trip dates and the app language. The recipients are Google (Weather API, for forecasts and alerts), the Norwegian Meteorological Institute (MET Norway, for forecasts), NASA (POWER, for typical weather), the Korea Astronomy and Space Science Institute and the Korea Tourism Organization (through Korea's Public Data Portal, for Korean holidays and festivals), the Cabinet Office of Japan (for Japanese holidays), and, for other countries, Nager.Date (public holidays; it receives only the country and the year). None of them receives your name, email or account details.
  • Travel advisories: once a day, our server downloads the advisories published by Korea's Ministry of Foreign Affairs (through the Public Data Portal) and the governments of the United States, the United Kingdom, Canada and Australia, and the app gets the advisories for your destination from our server. Nothing about you is sent anywhere in the process.
  • Showing the map: maps in the app are drawn by the Google Maps SDK, and maps in the web version by the Google Maps JavaScript API; either exchanges the information needed to display the map between your device or browser and Google (the Google Privacy Policy applies).

3-6. When you add clips to a shared vlog (optional; members of a shared trip only)

  • Two-second clips: a video file (with sound) and a small thumbnail, newly rendered on your device from the video you chose (including a Live Photo's motion), cut to two seconds in a landscape frame (1080×692). Originals are never uploaded, and rendering strips the capture location and device metadata, so the file carries no record of where it was shot.
  • Clip record: the identifier and display name of the person who added it, when it was shot (to the minute — used only for ordering and the "18:20" label), its length, where the file is stored, a caption (up to 40 characters), and a fingerprint so the same clip is not added twice.
  • Only clips shot within that trip's dates can be added, and only that trip's members can see them (Article 4-3).

3-7. When you open a past trip to others (optional)

  • Visibility: for each trip, your choice of "Only me", "Friends" or "Everyone", and whether "Plan with this route" is allowed. The default is "Only me".
  • Public copy: a summary made fresh from the trip when you open it — city keys, the names and categories of places you went, which day and in what order, how you traveled, the month you left, the number of days, and your passport name (nickname). Photos, notes, spending, companions, exact dates and times, and coordinates are never part of it. The document name of an "Everyone" copy is a key derived so that neither your account identifier nor the trip's first day can be read from it; the owner and first day are kept in a server-only record.
  • Likes and copies: the likes you leave on other people's public copies and the trips you copy (once each) — the public copy shows only the counts; who pressed them is kept only under your own account and in a server-only record. Copying duplicates that route (cities, place names, order, which day) into your own trips.
  • Reports: the reporter's identifier, the public copy reported, the reason and the time — readable by no user; only the operator reviews them. When three users with linked accounts report a copy, the server takes it down immediately.
  • Mute: the identifiers of travelers you have muted and the trips you have hidden after reporting — readable only by you; the other person is not told.

3-8. When you have a booking or flight-history screenshot read (optional)

  • The screenshots you choose (up to 6 at a time): sent through our server to Google's Vertex AI (a Gemini model) to read the text. Before sending, your device removes the capture location and device information (metadata).
  • What is read (for bookings: flight numbers, dates, times, airports, seats, passenger names, booking references, fares and so on; for flight history: dates, flight numbers, airports and so on) comes back to your device and becomes a record only after you confirm it. The model is told not to read card numbers, passport numbers, dates of birth, phone numbers or email addresses, and anything like them is filtered out again from what comes back.
  • Onbit does not store the screenshots. Under the Google Cloud terms, Google does not use them to train AI models.

3-9. When you use the web version (app.getonbit.app) (optional; requires an account)

  • Sign-in screen: to make the QR code, we create an anonymous identifier in that browser. Once you sign in — by scanning the QR code with your phone, or with Apple or Google — our server deletes that anonymous identifier (it's an empty account with no records).
  • Signing in by scanning the QR code with your phone: a single-use sign-in slot made by the web version, holding that browser's anonymous identifier, the browser and operating system name (such as "Chrome · macOS", which our server builds from the request's browser information using a fixed vocabulary, so your phone can show it on the approval screen), the two-digit number shown on the web screen (your phone must pick it out of three for the sign-in to go through), when the slot was made and when it expires (2 minutes), its status (waiting, opened, "Not me" or wrong number), the identifier of the phone account that tapped "Open", and, once opened, a sign-in token that only that browser can read (the token itself is valid for an hour, but it is used once and deleted at once). We delete the slot as soon as sign-in finishes; any slot left over is deleted by the server within 15 minutes of expiring. Only an account linked with Apple or Google can tap "Open".
  • Signed in on the web: each time you sign in to the web version, we keep under your account the browser and operating system name, when you signed in, how (QR code, Google or Apple) and the last day it was opened. You can see this list on your phone under Me > Open on a laptop, and "Sign out everywhere else" deletes it while signing out every device except that phone (computers, other phones and tablets, as their tokens run out — within an hour at most). Signing out of the web version removes that browser's own row.
  • What stays in the browser: the web version keeps the app's records (settings, data used for trip prep and so on) in that browser's storage (localStorage) and your sign-in state in browser storage (IndexedDB). It marks which account those records belong to, and clears Onbit's records from that browser when you sign out, when the account is deleted, or when a different account signs in. If you sign out or a different account signs in from another tab of the same browser, this tab stops and reloads too, so one account's records never mix into the next.
  • What the web version doesn't use: it neither reads nor asks for your photo library, camera or device notifications, and it loads no crash diagnostics (Crashlytics) or analytics (Google Analytics). The buttons that use your current location (Article 2-2.2) work in the web version too: your browser asks for your location when you tap one, and the coordinates are used only for the check and then discarded, just as in the app.

3-10. The traveler type quiz on the website (getonbit.app/test) (optional)

  • The quiz needs no account. Your answers, your result, the name you type and your friends' names and types are kept only in that browser (localStorage); a friend's answers that arrive through a friend link are kept only in that tab (sessionStorage). When you open a friend link, we read the friend's name and answers from the address and then remove them from it, so they don't linger in your history or bookmarks.
  • To show how people answered each question and how many people got each type, we count answer numbers, result types and whether you came from a friend link, with no name attached. We never keep who picked what.
  • If you share your result, the link carries your type, the name you typed and your answers (so a friend can compare theirs with yours), and goes wherever you send it. Whether to share, and whether to type a name, is up to you.
  • If you bring your result into the app (getonbit.app/t or onbit-visa.web.app/t), your type (your main type and up to two others) and whether to use it for the entry stamp in the Me tab are saved on our server under your account (under your anonymous ID if you haven't linked one). Only you can read it.

4. When you connect a friend (optional)

  • An invite code (8 characters, single use) and the identifier of the person who created it
  • The link record (the identifiers of the two connected people)
  • The passport summary shown to your friend (name, countries lit, city keys with month and day count, whether cover photos are shared)
  • Calendar "Together" requests (sent from "Who were you with on this trip?"): the identifiers of the sender and the recipient, the city, the month, whether it was accepted, and when it was created
  • Your consent to share location information with friends (when you agreed and which edition of the terms applied) and how you want to be notified (each time, or every 30 days)
  • Sharing record: the date, the friend who received it, the purpose and how many times that day — visible only to you and deleted automatically after 6 months

5. When you turn on notifications (optional)

  • Push notification token (per device), the time you chose, your device's time zone (its offset from UTC, refreshed each time you open the app) and language
  • Notification settings: whether "Shared trip updates" and "Trip reminders" (a week before, the day before, the day you leave, and the day after you're back) are on

6. When you fill in "About me" (optional)

  • Birth decade, gender

7. Processed on your device only and never collected

  • The capture coordinates in your photos (EXIF) and the photo originals (for a booking screenshot you choose to have read, see Article 2.3-8)
  • The coordinates used to check that you have arrived somewhere (discarded the moment the check is made; never stored or transmitted)
  • Trip auto-fill calculations: the nearest airport, suggested modes of transport, candidates for where you stayed and ate, and the distance traced by your photos are computed from the airport list built into the app and the photo locations on your device. Only what you confirm with "Yes" becomes a record; a suggestion you pass over with "No" is remembered on your device only, at a resolution of about 300 m, so it is not suggested again.
  • Putting "Taken near here" photos first when you save a place you loved: the distance between each photo's capture location and the chosen place is calculated on your device only.
  • Calendar photos, lock screen images and "One image" share cards: made on your device; they leave it only when you share them or save them to your photo library yourself. The recipient is then the app you chose.
  • Videos in trip credits: videos taken during a trip are read on your device only; the server keeps only how many there were.
  • Trip cover photos (for tickets and credits): used on your device only. Since 1.3.0 they are no longer uploaded, and any uploaded by an earlier version are deleted by the app.
  • Traveler type (the entry stamp in the Me tab): calculated on your device only, from your trip records and the times your photos were taken. If you bring in a quiz result from the website and choose to use it, see Article 2.3-10.
  • The days you completed "Today's one" in the Today tab: remembered on your device only.

8. Records of the use and provision of location information (automatic)

  • Your user ID, the date and time location information was used or shared with a friend, the purpose (which feature), and, where shared, the friend who received it — never coordinates. Under Article 16(2) of the Act on the Protection and Use of Location Information, the server records these automatically in a place neither you nor the app can read or delete, keeps them for 6 months, and then deletes them automatically.

9. Adding to anonymous trip statistics (automatic; can be turned off)

  • To show other travelers what trips tend to look like, parts of a finished trip are turned into numbers that identify no one and added together. No individual record is kept; we only count "one more trip falls into this range".
  • What is added: city, country and month of travel; nights and number of people; how you got there; whether it was a first visit; how it was; a range of photos per day; a range of spending per person per day (converted to US dollars); ranges of spending share by category and card share; the place IDs of places added and places loved, with what was good; packing items checked; the city visited next after that city; place names (shown as "popular places" only after more than 11 different people have written the same name — until then no name is published); a range for the per-person fare read from a booking capture (compared only within the same route, round-trip/one-way and cabin class, converted to US dollars); a time range for the first plan of the day; a range for places per day
  • What is never added: names, photos, receipts, notes, exact dates, exact amounts, companions
  • So that no one is counted twice, we keep a mark of which groups you've already added to, under your own account only (only you can access it; deleted with your account).
  • How to turn it off: Me > Notifications > "Help other travelers anonymously" (for everything), or the last screen of "Write up a past trip" for each trip. Once off, nothing new is added. A shared trip is left out entirely if any one member has turned it off.
  • These numbers are shown only after at least 11 different people and 30 trips are in the same group, and while numbers are small they are shown only roughly, such as "6 in 10".

About location: your device's current coordinates and your photos' capture coordinates are never sent to our server under any circumstance. However, three things are kept on our server. One is the result of turning a photo's capture location into a city on your device — that is, which city you were in and when — which is city-level information (an area of several kilometers or more). The second is the place names you write in your trip records or choose from suggestions (for example, where you stayed or ate), together with the dates of that trip. The third is the coordinates of places you search for or pick on the map (a shop, a sight), stored so we can pin them on the map and calculate travel times; these are the locations of places you chose, not where you were. The first is kept once you link an account; the second and third are kept under an anonymous ID even without one (shared trips under your account).
How we collect: generated automatically as you use the app, the web version and the website; entered or chosen by you; received through Apple or Google sign-in; and when you sign in to the web version by scanning a QR code with your phone.

What we process is the minimum needed for the purposes above. Your device's coordinates and photo originals are not needed for those purposes, so we do not collect them (a booking screenshot you choose is used only to read its text and is not stored).

Article 2-2 (App permissions — photos, location, notifications, camera)

Onbit asks your device for four permissions and no others. None is requested at launch; each is requested the moment you tap the button for that feature. Declining does not stop the app.

1. Photos

  • Asked when: you tap "Open my photos" on the first screen (onboarding), and likewise later under Me > Rescan. On Android, photos and videos are requested together at that point, because vlogs use your trip videos. If you allowed photos only before 1.3.0, videos are requested when you tap "Allow videos" on a trip's vlog card, on the vlog screen or in What's New. If you tap "Shoot 2 seconds" during a trip without photo access, it is requested before the camera opens, so the clip can be saved to your photo library.
  • What is read: the capture location (EXIF) and capture time recorded in your photos. Originals are processed on your device only. Trip auto-fill, places you loved and picking a receipt photo need no new permission and work only within the photos you have already allowed.
  • What leaves the device: never your photo originals (a booking screenshot you choose is handled as described below). If you link an account, only the one cover photo you chose per city is kept on our server (Article 2.3), and capture locations are kept only at the city level. If you attach a receipt photo to a shared trip, a newly made image of that photo is uploaded (Article 2.3-4). If you choose a video (including a Live Photo's motion) with "Add my clips", only the two-second clip rendered on your device is uploaded (Article 2.3-6). A booking screenshot you choose to have read is sent, with its capture location removed, to Google's Vertex AI to read the text, and is not stored (Article 2.3-8). You can see and delete every photo and video of yours on our server under Me > Your data on our server, and turn off city cover photo backup there.
  • Vlogs: the videos from your trip (including the motion of iPhone Live Photos) are read on your device only and strung together two seconds at a time. Saving puts the result in your photo library; nothing goes to the server.
  • Saving to your photo library: when you save a share image or a lock screen image to your photo library, your device may ask for permission to add photos.
  • If you decline: you can continue with "Start without photos" and light cities by hand. Limited access works too, using the photos you allowed.

2. Location

  • Asked when: you first tap one of the three buttons below that use your current location. Requested only while the app is open (WhenInUse); background location is never requested.

① "Right here" in onboarding — lights the nearest city.
② "Stamp me here" on a city screen — checked only when the location is accurate to 100 m or better; gives a visit stamp if you're within 500 m of the landmark.

③ "I'm here" when collecting shards — counts as arrival within 40 km of the city center.

  • What is read: your current coordinates, once, at the moment you tap.
  • What leaves the device: nothing. Coordinates are used only for the check and are discarded immediately. What remains is the city lit, the landmark id, or the city reached, with the date. For ③, the previous coordinates are held in memory only while the app is running, to detect impossible jumps, and are never stored. Place search and maps do not use your current location.
  • If you decline: only lighting by current location, stamps and arrival checks are unavailable; everything else works.

3. Notifications

  • Asked when: you pick a notification time on the last onboarding screen and tap "Start". If you pick no time, you are not asked. The same applies when you later turn a notification switch on under Me.
  • What is read: your device's push notification token.
  • What leaves the device: the token, your chosen time and your device's time zone are sent to the server (Article 5) so notifications can be delivered.
  • If you decline: you simply won't receive notifications; nothing else is blocked. You can turn them off at any time under Me.

4. Camera and microphone

  • Asked when: you first tap "Shoot 2 seconds" during a trip (on the boarding pass in the Trips tab, on the trip's vlog card or on the vlog screen). On iPhone, the camera is requested then, along with the microphone so the two-second clip has sound. On Android, your device's own camera app opens and does the recording, so Onbit does not request camera or microphone access itself.
  • What is read: the two-second video and sound you shoot at that moment.
  • What leaves the device: nothing. The clip goes into your device's photo library and is not uploaded unless you choose it yourself with "Add my clips".
  • If you decline: only "Shoot 2 seconds" is unavailable; a clip shot with your device's own camera app goes into your vlog just the same once it is in your library.

We request no other permissions. We do not request health or step data, contacts, calendar, or iOS App Tracking Transparency (ATT).
The web version (app.getonbit.app) never asks for photos, notifications or the camera. Your browser asks for your location only when you tap a button that uses your current location (used only for the check and then discarded, as in item 2).

On Android there are also normal permissions that are granted at installation and never asked: internet access, vibration, re-scheduling notification times after the device restarts, and setting the lock screen wallpaper. The lock screen wallpaper is changed only when you tap "Set as lock screen".

Article 3 (Purposes of processing)

  • Providing the service: keeping, restoring and carrying your records across devices, restoring cover photos
  • Keeping trip records: storing the trip records you save and carrying them across devices
  • Shared trips: letting you and the people you invite add and see the plan, packing list and spending together, showing who added what
  • Shared vlogs: placing the two-second clips that members of the same trip add into those members' vlogs, and telling members when a clip is added
  • Travelers who've been here: showing the route of a trip you opened to "Friends" or "Everyone" to your friends or to signed-in Onbit users and letting them copy it, counting likes and copies, taking down copies that are reported, and leaving out the trips of people you have muted
  • Settle-up and the trip ledger: working out who owes what, showing ledger views such as categories, day by day and payment methods, and checking receipts
  • Showing place search, maps, travel times, weather and local time
  • Trip info: showing forecasts, typical weather, weather alerts, public holidays and festivals for your trip's city, plus travel advisories, entry information and emergency contacts based on your passport country
  • Picking together: showing who wants to go where among the place ideas, and nudging members who haven't picked yet
  • Payment requests: letting the people who owe you know you're waiting, and showing the settle-up through a link
  • Identifying your account: verifying you through Apple or Google
  • Signing in to the web version: letting you sign in to the same account by scanning a QR code with your linked phone, showing which browser is asking and the three numbers on the approval screen, showing where you're signed in on the web and letting you sign out everywhere else, and clearing that browser's records when you sign out
  • The traveler type quiz: showing how people answered and which types are common, and bringing your result into the app's entry stamp
  • Providing the friend feature: showing passports between people connected by an invite code, finding the cities you've both been to, and showing a trip you both confirmed as "Together" on both of your calendars
  • Sending notifications you turned on — "On this day", new stamp news, a friend's new record, shared trip updates, and trip reminders a week before, the day before, on the day and the day after — timed to your local time
  • Crash diagnostics: finding and fixing the causes of crashes and errors
  • Analytics: aggregate analysis of which cities are lit and saved and of which trip features are used and how much, and improving the service
  • Showing combined statistics: numbers combined so that no one can be identified (how many trips went to a city, how long they usually last, how spending is spread, popular places, fare ranges on the same route and so on), shown as trends among trips to the same city (Article 2.9). No individual record is shown to other users.
  • Meeting our duties under the location information law: notifying you when location information is shared with friends, and recording and keeping the use and provision records
  • Answering inquiries received by email

If the purpose changes, we will obtain your consent in advance.

Article 4 (Disclosure to third parties)

The Company does not provide your personal information to third parties, except where required by law or where an investigative authority requests it through the procedures and methods prescribed by law. What friends and members of shared trips you invite can see is set out in Articles 4-2 and 4-3, and what people who receive a payment request link from you can see is set out in Article 4-5.

Article 4-2 (What other users can see — friends)

Onbit has no public feed, no user search and no recommendations. The following is visible only between two people who exchanged a single-use invite code directly, and we ask for your consent to share location information before you connect (item 7 below).

1. What a friend sees

  • Your passport name
  • How many countries you have lit, and the year you started
  • The cities you lit, with the month and number of days you were there
  • Cities you've both been to
  • Your cover photo for each city — only if you have turned "Show cover photos" on
  • The city and month of any calendar "Together" trip you both confirmed

2. What a friend does not see

  • Exact dates or coordinates
  • The notes you wrote on photos
  • Any other photo in your library
  • Your trip records (legs, places, spending, notes, companions, places you loved). Being friends does not let someone see a shared trip you haven't invited them to.
  • Your email address, or what you wrote in "About me"

3. Calendar "Together"

  • When one person picks the friend who was there under "Who were you with on this trip?" and sends it, and the recipient taps "Yes", that trip is marked "Together" on both people's calendars. Nothing appears unless the recipient confirms.
  • A request carries only the city and the month. It carries no exact dates, coordinates, photos or trip records.
  • If the recipient taps "Not me", or "Remove" is tapped on a "Together" trip, the request is deleted.

4. What you decide

  • Before you connect your first friend, we ask whether to show your cover photos. You can change this at any time under Me > Friends; turning it off stops your friend from receiving the photos immediately.
  • You can mute new-place notifications for each friend separately.

5. Disconnecting

  • Me > Friends > friend's name > ··· > "Remove friend" deletes the link record, and from that moment neither of you can see the other's passport or cover photos. Your friend is not notified.

6. Invite codes

  • A code stops working 24 hours after it is created, and is deleted the moment it is used.

7. Consent and notices for sharing location information

  • Before you connect, we tell you who receives it (friends you connect with by invite code), what they see, why, and for how long, and ask for your consent. Without it, you can't connect, and friends you're already connected with won't see your passport.
  • Each time something is shared, we notify you in the app with who received it, when and why (the default). If you separately agree, we send a summary every 30 days instead.
  • In Me > Friends > Location sharing record, you can see the last 6 months of sharing and change how you're notified at any time.

Article 4-3 (What other users can see — shared trips)

1. Who sees it: only members of that trip (up to 10). There are two ways to become a member: joining through an invite link made with "Plan together" (a link stops working after 7 days, and its creator can turn it off at any time), or accepting an in-app invitation by tapping "Join". Even friends can't see the trip until they accept.
2. What members see: the trip's cities and dates, the plan (places, times, map), who wants to go to which place ideas, the packing list, spending and settle-up, receipt photos, recent changes, members' display names, who added each item, and the two-second clips members added (the display name of whoever shot it, the minute it was shot, and its caption)

3. What members do not see: anything outside that trip (your other trips, city records, cover photos, places you loved, "About me") or your email address

4. Leaving and removing: members can leave at any time, and the creator can remove members. From the moment someone leaves or is removed, they can no longer see the trip. What they added stays with the trip for the other members — except the clips they added, their "Want to go" picks, and the payment and pick reminders they sent or received, which the server deletes.

5. Clips you added: you can withdraw them at any time, and the trip's creator can delete them too. Withdrawing deletes the record and the file together.

Article 4-4 (What other users can see — past trips you open)

1. What you open: for each past trip, you choose "Only me", "Friends" or "Everyone". The default is "Only me", and a past trip assembled from your photos is seen by no one until you open it. A trip still being planned cannot be opened.
2. "Friends": seen by friends connected by code (Article 4-2). Before you open it we obtain your consent to share location information (Article 4-2.7), and we notify you each time it is shown.

3. "Everyone": seen by any signed-in Onbit user. Before you open it, a "This is what others see" screen tells you who receives it, what is shown and why, and asks for your consent.

4. What is shown: cities, the names and categories of places you went, which day and in what order, how you traveled, the month you left, the number of days, your passport name (nickname), and the like and copy counts. An "Everyone" copy carries no account identifier, and its document name reveals no date.

5. What is not shown: photos, notes and one-line summaries, spending, companions, exact dates and times, coordinates, your email, and any of your other trips or city records

6. Copying: only trips where you allowed "Plan with this route" can be copied by others. Copying duplicates the route as it stands (cities, place names, order, which day) into the trips of the person who copied it; later edits to the original, or closing it, do not affect the copy.

7. Reports and takedowns: anyone can report a public copy once. When three users with linked accounts report it, the server takes it down immediately, and it cannot be opened to "Everyone" again until the operator has reviewed it. No user can read the reports.

8. Mute: muting a traveler removes all of that person's public copies from your screens, and they are not told. You can undo it at any time under Me > Muted travelers.

9. Turning it off: setting a trip back to "Only me" deletes the public copy immediately, and from that moment no one can see it. Copies others have already taken remain theirs.

Article 4-5 (What other users can see — payment request links)

1. Who sees it: anyone who receives a link (getonbit.app/s/…) that a member of a shared trip made with "Request payment" can see that settle-up without signing in. You send the link yourself, through the app you choose (KakaoTalk, Messages and so on) — the Company doesn't send it. The link address is 22 random characters and can't be guessed.
2. What is shown: the trip's city name, the total spent, who owes whom how much with "sent" and "received" marks, members' display names in that trip, and when it was last updated

3. What is not shown: account identifiers and email addresses; the details, notes, receipt photos and dates of individual expenses; anything else in the trip, such as the plan or packing list; and how to pay you (that goes only into the message you send)

4. When it closes: the link closes, and shows nothing more, 30 days after it was made, 7 days after the link first saw that everything was settled, when the person who made it leaves or is removed from the trip, or when the trip is deleted. If the person who made it deletes their account, the link is deleted too.

Article 5 (Entrustment of processing)

Processor: Google LLC · Entrusted work: authentication, including issuing the token for QR sign-in to the web version (Firebase Authentication), record storage (Cloud Firestore), storage of cover photos, receipt photos, two-second clips for shared vlogs and stamp artwork (Firebase Storage), hosting the web version and the quiz's former address (Firebase Hosting), notification delivery (Firebase Cloud Messaging), server functions (Cloud Functions — notification generation and aggregation, payment request links, QR sign-in and signing out everywhere else, trip info and quiz counts), crash diagnostics (Firebase Crashlytics), analytics (Google Analytics for Firebase), place search, place details, routes, weather and time zones (Google Maps Platform: Places API, Routes API, Weather API, Time Zone API), showing maps (Maps SDK for iOS and Android in the app, the Maps JavaScript API in the web version), and reading the text of booking and flight-history screenshots (Vertex AI) · Retention: until the processing contract ends or you delete your account
Processor: Vercel Inc. · Entrusted work: hosting the website (getonbit.app) — showing the pages that open links made in the app (trip invites, payment requests, QR sign-in help) and the traveler type quiz, passing quiz counts on to our server, and cookieless visit counts (Vercel Web Analytics) · Retention: until the processing contract ends

The contract sets out in writing the prohibition on processing beyond the stated purpose, technical and administrative safeguards, limits on sub-processing and liability including damages, and the Company supervises the processor. Any change of processor or entrusted work will be published in this policy.

Article 6 (Overseas transfer)

This transfer is made under Article 28-8(1)3(a) of the Personal Information Protection Act as entrusted processing and storage necessary to perform our contract with you, and is effected by publishing the following in this policy.

  • Recipient: Google LLC (1600 Amphitheatre Parkway, Mountain View, CA, USA / privacy contact firebase-support@google.com)
  • Countries and locations: record storage, file storage, authentication and notification generation in the Seoul region of Korea (asia-northeast3); crash diagnostics, analytics, and maps and place information (Google Maps Platform) in the United States; delivering the web version's files (Firebase Hosting) over Google's global network; reading booking screenshots (Vertex AI) wherever in the world Google chooses to process each request (not fixed in advance)
  • Items transferred: those items in Article 2 that are sent to the server. For maps and place information: search text, the coordinates at the center of the map, place IDs, the coordinates of places and trip cities, and the app language — never your name, email or account details. For reading booking screenshots: the screenshots you choose, with their capture location removed.
  • Timing and method: transmitted over encrypted connections as you use the service
  • Purpose: the purposes in Article 3
  • Retention: as in Article 7 (requests for maps and place information, and the processing while a booking screenshot is read, are subject to Google's policies)
  • How to refuse: delete your server records under Me > Account > Delete account or "Delete my records from the server", or delete the app. Token transmission stops when you turn notifications off. Nothing is sent for maps and place information if you don't use place search or maps, and no screenshot is sent if you don't use screenshot reading. Crash diagnostics exist for app stability, and the only way to refuse them is to delete the app.
  • Recipient: Vercel Inc. (440 N Barranca Avenue #4133, Covina, CA 91723, USA / privacy contact privacy@vercel.com)
  • Countries: the United States and the other countries where Vercel operates (its global network)
  • Items transferred: connection information when you open the website (IP address, browser and device type, and the addresses of the page you opened and the page you came from). Visit counts carry only the path of the page you opened; the tokens of payment request, QR and invite links and anything after the address are removed first. The link pages (payment requests, QR sign-in, invites) never pass their address on to other sites.
  • Timing and method: transmitted over encrypted connections when you open the website
  • Purpose: providing the website and counting visits
  • Retention: the value that tells visitors apart in visit counts is discarded after 24 hours, and the Company can see the counts for Vercel's reporting window (1 month on the free plan, 12 months on paid plans; Vercel may keep them longer so that a plan change loses nothing). Connection logs follow Vercel's policies.
  • How to refuse: if your browser sends a do-not-track signal (Global Privacy Control or Do Not Track), no visit counts are sent, and you can turn visit counts off for your browser under "Visit statistics" at the bottom of this policy page. The website keeps working either way. The connection information involved in opening the website is what Vercel needs to deliver the page, so the only way to avoid that is not to open the website — the app and the web version (app.getonbit.app) work without it.

Article 7 (Retention period)

  • Account information and stored records (including trip records): until the account is deleted. Me > Account > Delete account immediately deletes the server document (including trip records), cover photos, invite codes and friend link records, calendar "Together" requests, the passport summary shown to friends, and the authentication account.
  • Shared trips: until the creator deletes the trip or every member leaves. When you delete your account, the server automatically (1) removes you from the trips you belong to, (2) hands any trip you created to the earliest remaining member, (3) deletes trips where you were the only member, including the plan, packing list, spending, settle-up, change log and receipt photos, and (4) turns off the invite links you created. What other members added stays with their trip.
  • Receipt photos: deleted from our storage automatically as soon as the expense is deleted, and all of a trip's receipt photos are deleted when the trip is deleted.
  • Two-second clips in shared vlogs: deleted immediately when the person who added them withdraws them; automatically by the server when that person leaves, is removed or deletes their account; and all of a trip's clips are deleted when the trip is deleted.
  • Booking and flight-history screenshots: never stored (discarded as soon as the text is read).
  • City cover photos: deleted immediately when you delete them under Me > Your data on our server, and not uploaded again until you turn backup back on.
  • Trip public copies: deleted immediately when you set the trip back to "Only me", and automatically by the server when you delete your account. A like you left on someone's copy is removed the moment you tap it again; your likes and copy marks are deleted with your account.
  • Reports: until the reporter's account is deleted (to match them against outcomes). The takedown mark on a hidden copy: until the operator reviews and lifts it.
  • Muted travelers and trips hidden after reporting: until you undo them or delete your account.
  • Invite links (shared trips): stop working 7 days after creation, and are turned off when you delete your account.
  • In-app invitations: deleted as soon as the recipient taps "Later"; otherwise when the recipient's account is deleted.
  • Invite codes (friends): deleted 24 hours after creation, or the moment they are used
  • Calendar "Together" requests: deleted immediately when "Not me" or "Remove" is tapped; otherwise when the account is deleted
  • Anonymous trip statistics: numbers combined so that no one can be identified; they are not personal information and are kept for as long as the service runs. The marks of what you've already added (Article 2.9) are deleted with your account.
  • QR sign-in slots and tokens: deleted as soon as sign-in finishes; any slot left over is deleted automatically by the server within 15 minutes of expiring (2 minutes). The anonymous identifier made by the sign-in screen is deleted by the server once you sign in
  • Signed in on the web: deleted when you tap "Sign out everywhere else" or delete your account (signing out of the web version deletes that browser's row only)
  • Payment request links: deleted automatically by the server 30 days after they are made (they close earlier and show nothing 7 days after the link first saw that everything was settled, or when the person who made them leaves the trip), and deleted immediately when that person deletes their account
  • "Want to go" picks and payment and pick reminder marks: until the trip is deleted. A pick is removed the moment you tap it again, and the server removes a person's picks automatically when they leave, are removed or delete their account.
  • How to pay you: kept only on your device. It's gone when you remove it from the payment request screen or delete the app; in the web version, it is cleared when you sign out.
  • Your passport country: until the account is deleted (on the device, until you change it or delete the app)
  • What the web version leaves in a browser: cleared when you sign out, when the account is deleted, or when a different account signs in. You can also clear it in your browser's site data settings.
  • The traveler type quiz: what's kept in your browser stays until you clear it (a friend's answers from a friend link, until you close that tab). The counts kept with no name attached are not personal information and are kept for as long as the service runs. A result you brought into the app is deleted when you delete your account or use "Delete my records from the server".
  • Crash diagnostics: 90 days from collection
  • Analytics events: up to 14 months from collection
  • Notification token: until you turn notifications off or delete the app
  • Trip records of users without an account: until you use Me > Account > "Delete my records from the server", which deletes them immediately
  • Sharing record (what you see in the app): deleted automatically after 6 months
  • Records of the use and provision of location information: 6 months (Article 16(2) of the Act on the Protection and Use of Location Information). Because the law requires them to be kept, they remain for that period even after you delete your account, and are then deleted automatically.

The Company does not process payments and therefore keeps no transaction records under the Act on Consumer Protection in Electronic Commerce. Settle-up only does the math; no money moves through us.

Article 8 (Destruction)

When the retention period ends or the purpose is fulfilled, information is destroyed without delay. Electronic files are deleted by unrecoverable means, and deletion requests are carried out immediately.

Article 9 (Your rights and how to exercise them)

You may at any time request access to, correction of, deletion of, or suspension of the processing of your personal information.

  • Access and correction: your passport name, "About me" and passport country can be edited directly under Me, your trip records under Trips tab > that trip > "Write about this trip", and spending in a shared trip under Settle up > that entry. For anything else, email us and we will act after verifying your identity.
  • Partial deletion: you can delete parts of your record without deleting your account. One city: Globe tab > that city > "I wasn't here". One photo: open it and tap "Hide from Onbit". Photos and videos on our server (city cover photos, receipt photos, two-second clips): Me > Your data on our server. Trip records: Trips tab > that trip > "Write about this trip", by clearing a field or tapping "Remove" beside a place. A single expense: Settle up > that entry > "Delete". A friend connection: Me > Friends > ··· > "Remove friend". A shared trip: leave the trip. A "Want to go" pick: tap it again. How to pay you: remove it on the payment request screen.
  • Full deletion: you can remove every server record yourself under Me > Account > Delete account. If you never linked an account, use "Delete my records from the server" on the same screen. Either way, the server then deletes everything under your ID, including photos, a second time.
  • Suspension: turning notifications off stops notification processing (Shared trip updates and Trip reminders can each be turned off), "Remove friend" stops sharing with that friend, and leaving a shared trip stops sharing with its members. Opening a past trip to others stops when you set its "Who can see this" back to "Only me"; clips you added can be withdrawn on the vlog screen; and a mute can be undone under Me > Muted travelers. Adding to anonymous trip statistics can be stopped under Me > Notifications > "Help other travelers anonymously" and for each trip. Storing Trips tab records on the server stops with "Delete my records from the server". In the web version, Me > Account > Sign out also clears Onbit's records from that browser, and on your phone, Me > Open on a laptop > "Sign out everywhere else" signs out every device except that phone. You can turn the website's visit counts off for your browser under "Visit statistics" at the bottom of this policy page.

Requests may be made in writing or by email, including through a legal representative or an authorized agent, and will be acted on without delay.

Article 10 (Automatic collection devices and how to refuse them)

The Onbit app and web version use no cookies. The web version keeps the app's records and your sign-in state in that browser's storage (localStorage and IndexedDB); this is what makes the web version work, not advertising or tracking. Signing out clears it, and you can also clear it in your browser's site data settings (you'll then need to sign in again).
The website (getonbit.app) uses a single cookie: onbit_lang, which remembers the language you chose on a link page (1 year). Visit counts (Vercel Web Analytics) use no cookies and count only which pages were opened and how often; the value that tells visitors apart is discarded after 24 hours, and anything after the address and the tokens in payment request, QR and invite links are left out. If your browser sends a do-not-track signal (GPC or DNT), nothing is counted, and you can also turn counting off under "Visit statistics" at the bottom of this policy page (that choice is itself kept in your browser's storage). Beyond that, the only things kept in browser storage (localStorage) are your display settings (light or dark, sound) and the traveler type quiz's answers, result, the name you typed and your friends' names and types; a friend's answers from a friend link are kept only in that tab (sessionStorage). For the short videos on the home page, only the thumbnails load from YouTube (i.ytimg.com) when the page opens (your connection information reaches Google at that point); the videos themselves load from YouTube (youtube-nocookie.com) only when you tap one, and Google's policies apply from then on. The Apple and Google sign-in windows are those companies' own pages, and their cookie policies apply.

We do not collect advertising identifiers (IDFA, ADID) and we do not run personalized advertising. We do not request iOS App Tracking Transparency consent. The app's analytics use anonymous identifiers only, and turning off Me > Data > "Send anonymous statistics" stops collection immediately. The web version loads no analytics.

Article 11 (Safeguards)

  • Access control: server security rules mean only you can reach your own records.
  • Trip record access control: trip records you keep on your own live only inside your own server document, so only you can read them, and they are not part of the passport summary shown to friends.
  • Shared trip access control: only people with a member record for that trip can read or write it; who added an item can't be changed; and spending can be edited or deleted only by the person who added it or the trip's creator. Receipt photos can likewise be read and uploaded only by that trip's members under our storage rules. These checks are made by the server's security rules, not by the app.
  • Friend access control: a friend's passport summary and cover photos, and the public copy of a trip opened to "Friends", can be read only when the link record exists and the owner has sharing turned on. That check is made by the server's security rules, not by the app.
  • Vlog clip access control: clip records and files can be read only by that trip's members; whoever adds a clip can upload only into their own slot; and only the person who added it or the trip's creator can delete it. These checks are also made by the server's security rules.
  • Public copy access control: "Everyone" copies are written only by server functions; the app, as a signed-in user, can only read them. The record holding the owner and first day, the reports and the takedown marks can be read by no user.
  • Protecting outside service keys: the keys used for place search, routes, weather and time zones are kept only on our server; the app sends requests only through our server as a signed-in user, and the number of requests per user is limited.
  • Protecting QR sign-in: a sign-in slot is 22 random characters, lasts 2 minutes and works once, and its token can be read only by the browser that made the slot (server security rules). Before you tap "Open", your phone shows which browser is asking, and you must pick the two-digit number shown on the web screen out of three — a wrong pick closes the slot at once (this stops anyone from approving a QR code someone sent them without looking at the screen). "Not me" closes the slot at once. Only an account linked with Apple or Google can approve, and the number of requests is limited. If you scan a QR code that your account already opened, you can cut it off right there with "Sign out everywhere else".
  • Protecting payment request links: the address is 22 random characters and carries no account identifier. What the link shows is chosen by a server function (names and amounts only), the link closes on its own, and requests are limited per network address.
  • Protecting picks: server security rules let each member turn only their own "Want to go" on or off. Payment and pick reminder marks can be read only by the sender and the recipient.
  • Browser records in the web version: they are marked with the account they belong to; if a different account signs in, they are cleared rather than merged, and the page reloads. If the account changes in another tab of the same browser, this tab stops writing and reloads. If a browser opens with no account but with a previous account's records left behind, the sign-in screen clears them first.
  • Encryption in transit: all communication uses HTTPS/TLS.
  • Minimal collection: your device's coordinates are never sent to the server, and photo originals are never kept there (a booking screenshot you choose passes through only while its text is read).
  • Minimal handling: personal information is handled by a single person, the operator.
  • Limits on viewing photos and videos: the operator does not open the photos and videos stored on our server, except when the law requires it or when you ask us to in a support request.
  • Removing screenshot metadata: before a booking screenshot is sent, your device removes its capture location and device information.
  • Protecting location records: only the server writes the use and provision records; under the security rules, neither you nor the app can read, change or delete them.

Article 12 (Privacy Officer)

  • Privacy Officer: MOYO Studio Privacy Officer (Representative: Kyunghwan Im)
  • Contact: moyoofficial.help@gmail.com

Access requests are received at the same address and handled promptly.

Article 13 (Children under 14)

Onbit is not offered to children under the age of 14. If we learn that a user is under 14, we delete that account and its records.

Article 14 (Remedies)

  • Personal Information Infringement Report Center (privacy.kisa.or.kr / 118)
  • Personal Information Dispute Mediation Committee (privacy.go.kr / 1833-6972)
  • Supreme Prosecutors' Office Cybercrime Division (spo.go.kr / 1301)
  • National Police Agency Cybercrime Bureau (ecrm.police.go.kr / 182)

Article 15 (Items that do not apply)

Of the items set out in the Personal Information Protection Commission's guidance, the following do not apply to Onbit.

  • Additional use or disclosure beyond the collection purpose: none.
  • Processing of pseudonymized information: none. Anonymous trip statistics are combined numbers that identify no one; no individual record is created.
  • Processing or disclosure of sensitive information (health, sex life and the like): none. We do not read health or step data.
  • Bulletin boards open to the general public: none. Disclosure between users happens only within the limits described in Article 4-2 (friends), Article 4-3 (members of a shared trip), Article 4-4 (the route of a past trip you open to "Friends" or to "Everyone") and Article 4-5 (people who receive a payment request link you send). A route opened to "Everyone" is visible to signed-in Onbit users only; trips you have not opened and trip records you keep on your own can be read only by you.
  • Allowing third parties to collect behavioral information: not permitted. There is no advertising SDK in the app.
  • Automated decision-making (profiling): none. Your traveler type (the entry stamp in the Me tab) is calculated on your device only from your own trip records and photo times, and trip auto-fill suggestions and suggested expense categories can be confirmed or changed by you. No decision is made that has legal or similarly significant effects on you.
  • Domestic representative: the Company is a Korean business and is not subject to this requirement.
  • Fixed or mobile video information processing devices: none operated.

Article 16 (Notice of changes)

If this policy changes, we will give notice on the web (the page where this policy is published) at least 7 days before the effective date. In the app, we tell you the first time you open the update that includes the new policy, and by notification where needed. Changes unfavorable to users are announced 30 days in advance.
When we change it, we publish a side-by-side comparison of before and after beneath this policy so you can see exactly what changed, and we keep previous editions available.

Addendum
This policy takes effect on November 20, 2026.

Revision history

  • Edition 9 (effective 2026.11.20, announced 2026.11.13) — Added to the usage records used for analytics how often trip features are used and in which size bucket (Article 2.1, Article 3). What you wrote, amounts, dates and names are never sent, and turning off Me > Data > "Send anonymous statistics" stops this as well. The switch name in Article 10 now matches the app.
  • Edition 8 (effective 2026.10.30, announced 2026.10.23) — Added the web version (app.getonbit.app), signing in by scanning a QR code with your phone, number matching, "signed in on the web" and "Sign out everywhere else" (Article 1, new Article 2.3-9, Article 2-2, Article 3, Article 5, Article 6, Article 7, Article 9, Article 10, Article 11); payment request reminders and links, and keeping how to pay you on your device only (Articles 2.3-3 and 2.3-4, Article 4, new Article 4-5, Article 7, Article 9, Article 11, Article 15); picking together (Article 2.3-3, Article 4-3, Article 7, Article 9, Article 11); your passport country (Article 2.3, Article 3, Article 9); where trip info comes from — typical weather, alerts, holidays, festivals and travel advisories — and maps in the web version (Article 2.3-5, Article 3, Article 5); the traveler type quiz on the website and bringing its result into the app (Article 1, new Article 2.3-10, Article 2.7, Article 7); Vercel Inc., which hosts the website and counts visits, and how to opt out (Article 5, Article 6); and the website's language cookie, browser storage and YouTube thumbnails (Article 10). Added to Article 4-3 that a member's picks and reminder marks are deleted when they leave. Also included changes made after Edition 7 was announced: vlogs and two-second clips now use only videos (including the motion of iPhone Live Photos), not photos (Article 2.3-6, Article 2-2.1); Android asks for photos and videos together (Article 2-2.1); and where "Shoot 2 seconds" can be opened, with Android recording through the device's own camera app (Article 2-2.4).
  • Edition 7 (effective 2026.10.24, announced 2026.10.17) — For 1.3.0, added two-second clips in shared vlogs (Article 2.3-6, Article 4-3, Article 5, Article 7, Article 11), opening past trips to "Friends" or to "Everyone" with public copies, likes, copies, reports and mute (Article 2.3-7, new Article 4-4, Article 7, Article 9, Article 11, Article 15), and the camera and microphone permission (Article 2-2.4). Added to the anonymous statistics the city visited next, popular place names (only once more than 11 people have written the same name) and per-person fare ranges read from booking screenshots (Article 2.9, Article 3). Added to the photo permission explanation that vlogs read videos on your device only. Added that booking and flight-history screenshots are sent to Google's Vertex AI to read their text, with their capture location removed first (Article 2.3-8, Article 2-2, Article 5, Article 6, Article 7, Article 11). Trip cover photos are no longer uploaded (Article 2.3-2 and Article 2.7). Added "Your data on our server" for seeing and deleting the photos and videos on our server and turning off city cover photo backup (Article 2-2, Article 7, Article 9), and that the operator does not open the photos and videos on our server (Article 11).
  • Edition 6 (effective 2026.10.08) — Added shared trips and invitations (in-app invitations, invites by email, and who can be found by name) (Article 2.3-3, Article 4-3), the trip ledger and receipt photos (Article 2.3-4), places you loved (Article 2.3-2), place search, maps, travel times and weather (Article 2.3-5), and adding to anonymous trip statistics with how to turn it off (Article 2.9). Added Shared trip updates, Trip reminders and the device time zone used to send them at local time (Article 2.5, Article 3); Google Maps Platform and receipt photo storage to entrustment (Article 5); maps and place information to overseas transfer (Article 6); retention of shared trips, receipt photos and invite links and what happens on account deletion (Article 7); deleting a single expense, leaving a shared trip and stopping notifications and statistics (Article 9); and access control for shared trips and receipts and protection of outside service keys (Article 11). Added the coordinates of places you choose to the explanation of location. Edition 5, scheduled for 2026.11.03, is replaced by this edition before it takes effect.
  • Edition 5 (scheduled for 2026.11.03, replaced by Edition 6) — Added, in Articles 2, 7 and 9, that Trips tab records (trip summaries, trip cover photos, packing lists, spending, exchange rates) are kept under an anonymous ID even without an account, and "Delete my records from the server"; the home city in Article 2.3; consent before sharing location information with friends, sharing notices and the sharing record in Article 2.4 and Article 4-2.7; records of the use and provision of location information (6 months) in Article 2.8, Article 7 and Article 11; combined statistics and our duties under the location information law in Article 3; and on-device processing of trip credit videos and traveler type in Article 2.7. Updated the automated decision-making note in Article 15 to match current features.
  • Edition 4 (effective 2026.09.30, announced 2026.09.23) — With the new Trips tab, added Article 2.3-2 (trip records), added calendar "Together" requests to the friend items, and added trip auto-fill, the calendar, lock screen images and share images to what is processed on your device only. Added the place names in trip records to the explanation of location. Added the three places that use your current location ("Right here", "Stamp me here", "I'm here") with the check each makes, saving to the photo library, and Android's normal permissions to Article 2-2, keeping trip records and calendar "Together" to the purposes in Article 3, calendar "Together" to Article 4-2, and the retention, deletion and access control of trip records to Articles 7, 9 and 11. Replaced "there is no free-text field stored on the server" in Article 15 with how trip records are actually kept. Revised the notice method in Article 16 to what we can actually do.
  • Edition 3 (effective 2026.09.22, announced 2026.09.14) — Added Article 4-2 (What other users can see) for the friend feature. Added friend-related items (invite codes, link records, passport summary) and the list of days per city to Article 2, together with an explanation of city-level location. Added the friend feature to the purposes in Article 3, invite codes and link records to the destruction list in Article 7, partial deletion to Article 9, and friend access control to Article 11. Added business information to Article 1, and aligned the minimum age with the Terms at 14.
  • Edition 2 (effective 2026.09.11) — Removed the step-count item (the feature was removed before launch) and added Article 2-2 describing app permissions.
  • Edition 1 (effective 2026.09.08) — First issue.