Privacy Policy for Globemark
Globemark Privacy Policy
Sanghun Jeong ("the Developer") operates the Globemark app ("the App"). This policy explains what information the App handles, how it is processed, and the rights you have.
Effective date: 31 October 2026
1. What the App collects
The App has no accounts and no developer server. Everything you record — the countries and cities you have visited, the places you want to go, your trips, what you wrote in them and what you spent on them — is stored on your device. The Developer never receives what you wrote. The one exception is statistical: the App reports which countries you have marked as visited or as places you want to go, and which cities from its built-in city list you have marked that way (by that list's English name and id — never a city you typed in yourself), and how many places and trips you have, to Firebase Analytics (2-1 below).
Apart from those statistics, there are exactly two ways your records leave your device, and both of them go only to your own cloud account:
- The Google Drive backup you run yourself (2-5 below). It uploads everything you wrote — trip titles, journal entries, companion names, your trips' expenses — into a hidden folder in your own Drive that only this App can open. It is not shared with anyone, it does not appear among your Drive files, and the Developer cannot read it.
- Your device's own operating-system backup (Android Auto Backup / iCloud), if you have it switched on. See section 4.
What you share yourself is separate from both: a share card, or a route video or route image, goes wherever you send it from the share sheet, and a ledger template goes wherever you save it (Trip expenses, below). The App itself uploads none of them. A route video or image shows the places on that route and anything else you chose to put in it: a photo of yours as its marker or as pop-ups, your home city when the route starts or ends there, and the places you have marked as visited when it is drawn over your map.
A Google Timeline file you choose. A route video can follow the path recorded in a Google Maps Timeline export. When you pick such a file, the App reads it only on your device, and only to draw that route video. The system file picker hands the App a copy of the file, and the App deletes that copy as soon as it has read it. If the App is closed before then, it deletes the copy the next time you open the route video maker. Around the home and work places found in the file, the line is cut out of the drawing — within about 3 km by default, which you can change to anywhere from 1 to 10 km — with the centre of each cut and the ends of the line moved by a random amount, so the gap does not point at the place itself. The cities they are in are hidden from the video too, unless you choose to show them; the cut stays either way. If Google grouped trips in the file, the App offers their dates to pick from; choosing one only sets the dates. The App sends nothing from the file anywhere (the route video events in 2-1 carry the kind of route, the number of stops, the file's format, whether it could be read and why not, how many trips Google grouped in it and how many you ticked, and whether you picked days or grouped trips — never places, dates, times or coordinates) and adds nothing from it to your visited places or your trips; a route drawn from such a file can never be saved as a trip. All that stays on the device is the route as drawn, with those stretches already cut out, among your recent routes (section 4).
Saving a route as a trip. A route you built yourself, place by place, can be saved to your journal as a trip once every place on it has a date. That writes the trip to trips.json and marks its places as visited in visits.json — your home city too, when the route starts or ends there — just as writing the same trip in the journal would, so those countries, and those cities from the App's built-in city list, also join the visited lists in 2-1. Only a route you built yourself can be saved this way: a route made from your trips is already in your journal, and one drawn from photos or a Google Timeline file is never saved as a trip.
Trip expenses. A trip's Expenses tab keeps what you spent on it: for each cost its amount and currency, its date, its category, cash or card, an item name and a memo if you add them, its exchange rate, and who paid it and who shares it, by the names of the trip's people. The trip also keeps the currency its totals are in and the last rate used for each currency. All of it is stored with the trip in trips.json on your device. Exchange rates are the ones you enter or bring in from a file you import; the App never looks them up online. None of it is sent to analytics or to an ad network: all the App itself reports to analytics from the tab is the fixed name of a page you open from it, such as expense_editor (2-1). It is included in the Google Drive backup when you run one (2-5) and in your device's own backup (section 4). What you change after tapping the pencil at the top of the tab is kept only when you press Save: until then it is not written to the file or to a backup, and it is discarded if you leave and choose Cancel when asked, or if the App is closed first. Get template makes an Excel or CSV file from the trip — its days, the names of its people, the currencies to pick from and the trip's current rates, with the trip's name in the file name, and none of its expenses — and saves it only where you choose in the system's save dialog; on iOS, the copy made inside the App for that dialog is deleted once the dialog closes. A file you pick with Import (CSV, Excel) — a filled-in template, or expenses exported from Triple — is read only on your device: the copy the system file picker hands the App is deleted as soon as it has been read, and the App sends nothing from it anywhere.
The App shows ads (Google AdMob) to fund itself, collects usage statistics (Firebase Analytics) and crash reports (Firebase Crashlytics) to improve, and sells Globemark Pro. Everything handled that way is listed in section 2, and nothing you typed — city names you entered, trip titles, journal text, companion names, anything in your trips' expenses — is ever sent to an ad network or to analytics.
2. Third-party services
2-1. Firebase Analytics (Google)
Usage statistics, to see which parts of the App are used and how people use their map. They are tied to a random app-instance id that Firebase creates, not to your name, email address or any account.
- Handled: device model, OS and app version, coarse country/region, an app-instance id, in-app action events, which of the App's screens you open, and, on Android, the advertising ID.
- Events collected: marking a country, marking a city (for a city from the App's built-in city list, its English name and its id in that list; for a city you typed in, only its country and the fact that it was typed in), saving a trip (with its length in days) or deleting one, finishing an import from photos (how many photos, cities and countries), sharing your map (how many countries), finishing the first-run flow, changing the app language, finishing a backup or restore, opening the ad privacy settings form, opening and closing the Pro page (which feature prompted it, whether it offered a rewarded ad, whether it closed with Pro turned on, an ad watched or neither, and how many times its ad button was pressed), starting, completing, cancelling, failing or restoring a purchase, the steps before a route video is made (choosing what its route is made from, opening the editor and the style screen, watching the preview to its end, and a video not starting when it was asked for — Make video, Try again, Continue, or the App carrying one on when you come back to it — with the reason; each step carries where you started, the kind of route, whether it is a recent route and its number of stops or the preview's length, and a video not starting also its format, length, trips, Pro options and which attempt it was — never places, titles, coordinates or distance), setting or clearing the home city (where it was done, and only whether one was set, the prompt closed or the city cleared — never which city), reading a Google Timeline file (its format, whether it could be read and why not, how many trips Google grouped in it and how many you ticked, whether you picked days or grouped trips, and the number of stops — never its places, dates or times), and starting, finishing, cancelling or failing a route video (where you started it and which kind of route it follows, whether it is a recent route made again, its format, length, number of stops and trips, the Pro options used, whether an ad or Pro unlocked it and whether Pro was bought for it, whether it was a first try, a retry or a resumption, how long it took to make, how far a cancelled one got, and why one stopped or failed — never places, titles, coordinates or distance), a rewarded ad for it not loading or not being watched to the end, saving or sharing it, and saving a route you built yourself as a trip.
- Screens: the App names the screen you are on in a
screen_viewevent, using a fixed name it defines — one of its five tabs (globe,journal,route_video,stats,settings) or a page such aspro,photo_import,trip_detail,expense_editor,ledger_settleor a step of the route video maker — never a title or anything you typed. - Your current totals: how many countries and cities you have marked as visited, how many you have marked as places you want to go, how many trips you have logged, and which marker style you chose for visited places. These are set as user properties whenever they change, and sent as one
mark_totalsevent each time the App starts. - Which places you have marked: once a day while you use the App, and again each time Import from photos adds marks or a Drive restore finishes that day, one
visited_countryevent for every country you have marked as visited, carrying that country's ISO code (for exampleKOR); onewant_countryevent for every country you have marked as a place you want to go, with its code and whether you have also marked it as visited; and onevisited_cityorwant_cityevent for every city from the App's built-in city list (GeoNames) that you have marked as visited or as a place you want to go, carrying its country code, its English name in that list (for exampleLisbon) and its id there. Each send carries at most 150 cities from each of those two lists; the rest follow on later days in turn. Places marked by Import from photos are included. A city you typed in yourself is never in these events, and the photos themselves and their coordinates are never sent. - Your home city: the home city you set for route videos (section 4) is never sent as a setting, and the route video and home city events never name it. But a city marked on your map is reported like any other marked city, so if your home city is also marked as visited or as a place you want to go, it is in the lists above too. Saving as a trip a route that starts or ends there marks it as visited (section 1).
- Separately from that list, Firebase automatically collects standard events such as app open, session start, screen view, app update and completed in-app purchase.
- A completed purchase carries the product id (
globemark_pro/globemark_pro_monthly), the plan, where the Pro page was opened from, and the price and currency code the store reported; the other purchase events carry only the plan (monthly/lifetime), where the Pro page was opened from and an error category, and a restore only whether a purchase was found. No payment details ever reach the App — Google Play and the App Store handle payment entirely. - Events carry counts, country codes, the English names and ids of cities from the App's built-in city list, and a fixed set of labels the App defines (mark state, where the action started, which screen, which plan, a route video's format and options, which error category). City names you typed, trip titles, journal text, companion names and anything in your trips' expenses are never sent in any event.
- The App's own events and totals wait inside the app until the consent step in 2-3 has finished. They are then sent if that step allows ads to be requested — which is the case once the consent form has been answered, whichever options were chosen, and wherever no form is required — and are discarded unsent if it does not, for example when the consent state cannot be read. Firebase's own automatic events, such as first open, can be recorded on the very first launch before that step finishes.
2-1-1. Firebase Crashlytics (Google)
Crash reports, to find and fix what makes the App crash.
- Handled: when the App crashes or hits an unexpected error, a report with the error and its stack trace, device model, OS and app version, a random installation id, and, when usage statistics are on, the App's most recent statistics events (2-1).
- Crash reports are sent whatever the ad-consent choice, because they are needed to keep the App working.
2-2. Google AdMob (ads)
The App shows three ad formats.
| Format | When it appears |
|---|---|
| Banner | Always, at the bottom of the screen above the tab bar; and, while a route video is being made, a 300×250 one on that screen |
| Interstitial | Immediately after you save a trip, save a city's marks, or press Save to finish editing a trip's expenses (also when you leave that edit with changes and choose Save when asked) |
| Rewarded video | Only when you choose to watch one, in exchange for a single run of 'Import from photos', or for making one route video |
Marking a country or a city on the globe never triggers an ad.
- Handled: advertising ID (Android Advertising ID), coarse location, device information, ad interaction data.
- On iOS the App does not ask for App Tracking Transparency permission, so no IDFA is collected.
- Personalised ads use those identifiers. Without consent you get non-personalised ads, or no ads at all. If the consent state cannot be read — a network failure or a timeout — the App treats that as no consent and requests no ads.
- For Globemark Pro users the ad SDK is never initialised. AdMob reads no advertising ID, and none of the three formats is shown (on Android, Firebase Analytics may still read it — see 2-1).
- On Android you can reset the advertising ID or turn personalisation off at any time (Settings → Google → Ads). On iOS the App requests no tracking permission, so it does not appear under that setting; ad personalisation is changed in Settings → Ad privacy settings inside the App.
2-3. Ad consent (Google UMP)
In the EEA, the UK and other GDPR regions, Google's User Messaging Platform consent form appears on first launch. You can change that choice at any time in Settings → Ad privacy settings.
2-4. International transfer
Firebase Analytics, Firebase Crashlytics and AdMob are operated by Google LLC, and the data above may be processed on Google servers outside your country.
- Recipient: Google LLC (United States and other countries where Google operates data centres)
- Data and purpose: the items in 2-1, 2-1-1 and 2-2 / statistical analysis, crash diagnosis and ad delivery
- Retention: per each service's policy (Firebase Analytics defaults to 14 months; Crashlytics keeps crash reports for 90 days)
2-5. Google Drive backup (optional, user-initiated)
Only when you start it from Settings, the App signs in to your Google account and backs up or restores your records to your own Google Drive. This is a Globemark Pro feature.
- What the backup contains: your country and city marks, city names you typed in, your trips with their titles, everything you wrote for each day, moods, companion notes, the names of any companions you entered, and each trip's expenses (amounts, currencies, exchange rates, cash or card, item names, memos, and who paid and who shares each one) — all your records in the App, as written. Expense changes you have not yet kept with Save are not in it. It goes only into the hidden app folder described below, which nothing but this App can open.
- Data handled: your Google account's email address, name and profile picture (shown in the app so you can see which account is connected), and an OAuth token.
- Scopes requested: basic profile (email, name, picture) and
drive.appdata— Drive access is limited to files this App created. It cannot list or read any of your other Drive files. - Where it is stored: a hidden, app-specific folder (
appDataFolder) in your own Google Drive. - Backup data is never sent to a developer server, and the Developer cannot access its contents.
- Data in transit is encrypted with HTTPS.
- You can disconnect the account at any time from the backup screen's Disconnect action, or delete the backup file directly in Google Drive.
Google's Privacy Policy: https://policies.google.com/privacy
2-6. In-app purchases (Google Play / App Store)
Globemark Pro comes as a monthly subscription (globemark_pro_monthly) or a one-time lifetime unlock (globemark_pro); both grant exactly the same thing.
What Pro gives you
- No ads at all — banner, interstitial and rewarded.
- Google Drive backup and restore (2-5 above).
- No limit on photo import. Without Pro you can read the locations of 5 photos at a time; going beyond that means buying Pro or watching one rewarded ad (2-2 above). Making a route video from photos has no such limit.
- Route videos with no ad and no watermark, and the Pro video options, such as 4K and 60 fps on devices that support them, custom markers (transport, emoji or your own photo) and extra map styles. Without Pro, making a route video takes one rewarded ad (2-2 above) and the video carries a small Globemark mark.
How payment is handled
- Payment is handled entirely by Google Play or the Apple App Store. The App never receives, and cannot see, a card number or any other payment detail.
- There is no developer server, so there is no server-side receipt validation either. The App asks the store directly whether the purchase is active and stores only the answer — true or false — on the device.
- Your purchase is re-checked with the store every time you reopen the App. If the store reports no active purchase, the flag on the device is cleared (an expired subscription, a refund). If the store cannot be reached at all, a subscription is kept for at most 35 days after the store last confirmed it, and is then cleared until the store confirms it again (a lifetime purchase is not affected).
- The App reads the store's price string and currency code in order to display the products.
- Stored on the device: whether Pro is active, whether it is the subscription, whether it is the lifetime purchase, when the store last confirmed it, and a file-format version (
pro.json). The file holds no account details and no receipt, and is not included in the Google Drive backup. - What is sent to the store, and how it is handled, is governed by each store's own policy.
- Google Play: https://policies.google.com/privacy
- Apple: https://www.apple.com/legal/privacy/
- A subscription can be cancelled from [Manage subscription] in the App's settings, or from the store's own subscription screen. Refunds follow each store's refund policy.
2-7. Google API Services User Data Policy (Limited Use)
The App's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, data obtained from Google Drive is:
- used only to provide the backup and restore feature you asked for,
- never transferred to or sold to third parties,
- never used for advertising,
- never read by humans.
3. Permissions
| Type | Permission | Why |
|---|---|---|
| Optional | Photos / media | For "Import from photos", to read the capture location (GPS) of your photos read-only and mark the places you have been; the countries and cities marked this way become part of the visited lists in 2-1. For a route video made from photos, to read the capture location and date of the photos you pick, also read-only, and draw the route in the order they were taken; this marks nothing. Any route video can also show one photo you choose as its marker, and a route made from photos can show its own photos as pop-ups; those photos are read, also read-only, and drawn into that video. Beyond that the photos never leave the device and their coordinates are never sent anywhere; a route video shows only the line, the places and any photo you chose for it, and goes only where you share it. |
| Optional | Add to Photos (iOS, NSPhotoLibraryAddUsageDescription) | Only to save the share card when you choose Save Image, the route videos you make (each is saved automatically once it is finished, and Download again saves another copy), and the route map image when you choose Download route map. Nothing else is ever written there. No location is written into a saved video or image. |
| Optional | Storage (Android 9 and earlier, WRITE_EXTERNAL_STORAGE) | Asked only on Android 9 and earlier, at the moment a route video or route map is saved, to write it to the public Movies or Pictures folder. On Android 10 and later these are saved to Movies/Globemark and Pictures/Globemark without any permission, and this one is never asked for. |
| Optional | Notifications (Android 13 and later, POST_NOTIFICATIONS) | Shows the progress and the end of a route video being made, so the work can go on from the home screen or with the phone locked. Asked once, the first time a video is made; the video is made whether or not you allow it. The notification holds only the progress and the state of the render. |
| Optional | Photo location (ACCESS_MEDIA_LOCATION) | Required on Android 10+ to read a photo's coordinates. Without it every location reads as empty, and neither the import nor a route video made from photos finds anything. |
| Required | Internet | Ad requests, usage statistics and crash reports, Google Drive backup and restore, and looking up in-app products and checking your purchase with the store. |
| Automatic | Advertising ID (com.google.android.gms.permission.AD_ID) | Used by AdMob for ad delivery and frequency capping. Resettable in device settings. |
Choosing a Google Timeline file for a route video, or a file to import into a trip's expenses, needs no permission: the system file picker gives the App only the one file you pick (section 1). Saving a ledger template needs none either: it goes through the system's own save dialog.
4. Retention and deletion
The App collects no identifying or account information on any server, so there is nothing on the Developer's side to delete.
- Local data: what you record lives on your device (
visits.json,trips.json,settings.json,pro.json). Deleting the App erases the copy on your device. - Route videos:
settings.jsonalso keeps the style of the last route video you made, including the @handle and the emoji if you set them, and the home city you set for route videos (Settings → Home city), which is used only in a video that starts from it or returns to it, and then appears in that video (and in the trip, if you save that route as one — section 1).routes.jsonkeeps your 30 most recent routes so that one can be made into a video again: the stops, the line as it was drawn and the style of each, plus your photo library's own reference to each photo it used: the photos of a route made from photos, and a photo you chose as its marker (never the photo itself). A route is saved after the cut around home, work and any city you hid (section 1), so the stretches inside those zones are not in it.route_privacy.jsonholds one random value, made on the device the first time it is needed, that sets how far each of those zones is shifted and trimmed; because it stays the same, a place is cut the same way in every video made at the same radius. Videos of the same place made at different radii can, compared together, narrow down where it is. That file holds no places.route_credits.jsonholds short fingerprints (hashes) of the route videos a rewarded ad unlocked, so one that stopped or failed can be made again without another ad; each is kept for 24 hours, and the file holds no places, titles or coordinates. A video is made in the App's temporary folder, and the App deletes its own copies more than a day old each time you open the route video maker. A long video is made in parts, so that one that stops can be continued: the parts stay in that temporary folder until the video is finished, or for about a day if it is not, and are then deleted the same way; a video you saved to your photo library or shared stays wherever you put it. None of the files in this item goes into the Google Drive backup. - Operating-system backups: if Android Auto Backup or iCloud backup is switched on for your device, those files are also copied to your own cloud account and restored when you reinstall. That is your operating system's own feature and follows its policy; turn it off for this app in your device settings if you would rather it did not.
- Copies of damaged files: when a data file cannot be read, the App keeps the original under a
.corruptname rather than deleting it, so nothing is lost by accident. It goes when the App does. - Google Drive backup: you can delete it yourself in your Google Drive, or disconnect the account in the App. Each new backup replaces the previous one and the App keeps only the newest, clearing any leftover earlier file on the next backup.
- Auth tokens: discarded from the device when you disconnect. The Developer never stores them. If that fails — a network error, say — you can revoke the grant yourself at https://myaccount.google.com/permissions.
- Third-party data: whatever Firebase Analytics, Firebase Crashlytics and AdMob collect is deleted on Google's own retention schedule (Firebase Analytics defaults to 14 months; Crashlytics keeps crash reports for 90 days).
5. Security measures
- Encrypted transport: everything that leaves the device — ad requests, statistics, crash reports, Google Drive backup and restore — travels over HTTPS.
- Records kept apart from ads: what you write is never used for advertising and is never passed to an ad network. Analytics receives only what 2-1 describes — counts, country codes, the English names and ids of cities from the App's built-in city list, screen names and fixed labels — never your text or your expenses.
- Least privilege: Drive access is limited to the app-specific folder, so the App is technically unable to reach your other files.
- Minimal collection: statistics carry counts, country codes, the public English names and ids of cities from the App's built-in city list, fixed labels and, for a completed purchase, the price and currency the store reported only — never names, titles, amounts or text you entered.
- No developer access: backup files live in your Google Drive; the Developer cannot access them.
6. Your rights
You may at any time request notification of how your data is handled, access to it, correction or deletion of it, or that its processing be stopped. Requests sent to the address below will be acted on without delay.
- Email: studio.novalabs@gmail.com
You can also manage your data directly:
- Disconnect in the App: Settings → Back up to Google Drive → Disconnect
- Delete the App: erases the copy on your device (see section 4 on operating-system backups)
- Revoke the App's access in your Google account: https://myaccount.google.com/permissions
- Change ad consent: Settings → Ad privacy settings (shown where it applies)
- Reset the advertising ID / turn off personalisation: Android Settings → Google → Ads (not applicable on iOS, where the App requests no tracking permission)
7. Children
The App does not knowingly collect personal information from children under 14. If a child under 14 uses the App, a legal guardian's consent is required. If information from a child under 14 is found to have been collected without that consent, it will be deleted immediately.
8. Contact
- Name: Sanghun Jeong
- Role: Developer (solo)
- Email: studio.novalabs@gmail.com
9. Changes to this policy
If this policy changes, the change will be posted on this page and the effective date updated.