Privacy Policy
Effective date: November 12, 2026
Visit statistics
Visits from this browser are counted in visit statisticsVisits from this browser are not counted in visit statisticsThis browser can't use storage, so this setting can't be remembered
Fillus (필어스) (“we”) runs this collection of web tools (“this site”) and the mobile apps “건축물대장” (Building Register; “the Building Register app”), “정부 지원금 찾기” (Government Benefits Finder; “the Government Benefits app”), and “물때표” (Tide Table; “the Tide Table app”; together, “the three apps”). We publish this Privacy Policy under Article 30 of the Personal Information Protection Act of the Republic of Korea. The Building Register app has an Android version (Google Play, developer FILLUS, package name com.gofillus.landinfo) and an iPhone version (“건축물대장 조회” (Building Register Lookup) on the App Store, bundle ID com.gofillus.landinfo). The Government Benefits app also has an Android version (Google Play, developer FILLUS, package name com.gofillus.govbenefit) and an iPhone version (“정부 지원금 찾기” (Government Benefits Finder) on the App Store, bundle ID com.gofillus.govbenefit). The Tide Table app also has an Android version (Google Play, developer FILLUS, package name com.gofillus.tidetable) and an iPhone version (“물때표 - 바다 날씨 · 갯벌” (Tide Table - Sea Weather and Tidal Flats) on the App Store, bundle ID com.gofillus.tidetable).
We receive personal information in five ways: emails you send us, visit statistics, access logs, the building register lookup, and comments on housing notices. You can use this site and the three apps without signing up. To comment on subscription and rental housing notices (on this site’s notice pages or in the Building Register app’s comment screen), you must log in with a Kakao account (or, in the Building Register app on iPhone, an Apple account); a comment account is created the first time you log in. Visit statistics are collected by Google Analytics on our behalf (section 7). New-benefit notifications in the Government Benefits app are delivered by Google on our behalf, and we do not receive the values used for them (section 7). To find nearby sea stations, the Tide Table app and the tide table pages on this site use the approximate location of your phone or browser only on that device, and we do not receive your location (section 2). The refresh signal used for tide notifications in the Tide Table app is delivered by Google on our behalf, and we do not receive the values used for it (section 7). This policy covers the whole site, including its Korean pages, and the three apps.
1. Why we process personal information
- Emails: to answer your questions and bug reports, and to fix the bugs you report.
- Visit statistics: to count how much each tool is used, so that we can improve the site and the three apps. We also use them to compare ad revenue by tool and screen (totals only).
- Access logs: to run the site securely and to detect outages and attacks.
- Building register lookup: to find and show the building register information for the building you choose. This also applies when you search in the Building Register app.
- Housing-notice comments: to show comments left on subscription and rental housing notices, to confirm who is logged in, to review and handle reported comments, and to stop use that breaks the community rules. We also use this information to disconnect your Kakao or Apple login when you delete your account.
- New-benefit notifications: to deliver a notification signal, on days when new benefits appear, to phones that have turned on new-benefit notifications in the Government Benefits app (section 7).
- Tide notifications: to deliver a signal, twice a day, to phones that have turned on tide notifications in the Tide Table app, telling the app to download fresh tide and sea weather data and reschedule its notifications (section 7).
- Ads in the apps: to show ads in the three apps. The information used for these ads is sent directly to Google by Google’s ad tool built into the app, and we do not receive it (section 8).
We do not use personal information for any other purpose. If a purpose changes, we will update this policy first.
2. Personal information we process
| Type | Items | How we receive it |
|---|---|---|
| Emails | Your email address, your name (if you include it), the message and any attachments, and the time it was sent | Emails you send to our contact address |
| Visit statistics | The page you viewed (address without the part after the question mark, and title; on a government benefit page, this shows which benefit the page is about, and on a tide table station page, which sea station the page is about), whether you saw a tool’s result, whether you pressed the button for the original text or the application site, or the share button, on a government benefit page, a random number that identifies this browser (kept in the _ga cookie), a visit (session) number, time spent, and the date of your first visit, the referring page (the address of the previous page and the channel, such as search or ads), screen size, browser language, browser, operating system, device type, country, region, and city (estimated by Google from your IP address; Google states that Google Analytics does not store IP addresses), and your ad consent status (EEA, UK, and Switzerland) | When you open a page, the Google Analytics tool on this site (gtag.js) sends it directly to Google |
| Visit statistics (Building Register app) | That you opened the app, whether you saw a result and where you opened it from (address search, recent lookups, or favorites), whether you saw the update notice, a random number that identifies this app installation (Firebase app instance ID), the date you first opened the app, how often and how long you use it, screens viewed, app installs, updates, removal (Android) and operating system updates, ads viewed and their revenue (received by linking Google AdMob), and your ad consent status, app version, phone model, operating system and version, language, screen size, country, region, and city (estimated by Google from your IP address; Google states that Google Analytics does not store IP addresses) | While you open and use the app, the Google Analytics tool in the app (Firebase SDK) sends it directly to Google |
| Visit statistics (Government Benefits app) | That you opened the app, whether you saw a matched list or search results and whether that was the matched list opened with your saved conditions, whether you pressed the button for the original text or the application site, or the share button, whether you opened the app by tapping a notification and the kind of notification (new benefits or a deadline), whether notifications are turned on (once a day), a random number that identifies this app installation (Firebase app instance ID), the date you first opened the app, how often and how long you use it, screens viewed, app installs, updates, removal (Android) and operating system updates, ads viewed and their revenue (received by linking Google AdMob), notifications received and opened, and your ad consent status, app version, phone model, operating system and version, language, screen size, country, region, and city (estimated by Google from your IP address; Google states that Google Analytics does not store IP addresses) | While you open and use the app, the Google Analytics tool in the app (Firebase SDK) sends it directly to Google |
| Visit statistics (Tide Table app) | That you opened the app, the screen viewed (Today, Find, Calendar, or Settings), whether you opened a data source (Korea Hydrographic and Oceanographic Agency, Korea Meteorological Administration, or the Public Data Portal) or the privacy policy from the information screen, whether you opened the app by tapping a notification and the kind of notification (tide or daily summary), whether you added a home screen widget, a random number that identifies this app installation (Firebase app instance ID), the date you first opened the app, how often and how long you use it, app installs, updates, removal (Android) and operating system updates, and your ad consent status, app version, phone model, operating system and version, language, screen size, country, region, and city (estimated by Google from your IP address; Google states that Google Analytics does not store IP addresses) | While you open and use the app, the Google Analytics tool in the app (Firebase SDK) sends it directly to Google |
| Access logs | IP address, time of access, the requested address, browser or app information, and the referring page (the address of the previous page) | Automatically by our server when you open a page or when any of the three apps sends a request to our server |
| Building register lookup | The address you search for, and the building, dong (building number in a complex) and ho (unit number) you choose | When you search in the building register lookup tool or in the Building Register app |
| Comment account | Your Kakao member number or the user number Apple gives us, the nickname we assign you, the login method (Kakao or Apple), when the account was created, and a value used to disconnect Apple login (issued by Apple; we keep it encrypted) | From Kakao or Apple when you finish logging in |
| Housing-notice comments | A pseudonymous value pointing to your logged-in account, nickname, when you agreed to the community rules, when you first and last used comments, comment text, when you posted, edited, or deleted it, likes and users you blocked, the report reason and optional note (up to 300 characters) and when you reported, and records of comments we hid or accounts we suspended with the reason | On this site’s notice pages or in the Building Register app’s comment screen, when you log in and post, like, block, or report |
| New-benefit notifications (Government Benefits app) | Values that identify the phone to notify (the Firebase installation ID and the notification token), the notification topic subscribed to (one topic, the same for every user), and the app version and phone information (such as the operating system version and model) | Sent directly to Google by Google’s notification tool built into the app (Firebase Cloud Messaging) when you turn on new-benefit notifications and while they stay on. We do not receive them |
| Tide notifications (Tide Table app) | Values that identify the phone to notify (the Firebase installation ID and the notification token), the notification topic subscribed to (one topic, the same for every user), and the app version and phone information (such as the operating system version and model) | Sent directly to Google by Google’s notification tool built into the app (Firebase Cloud Messaging) when you turn on tide notifications and while they stay on. We do not receive them |
Visit statistics do not include information that directly identifies you, such as your name or contact details. The numbers that identify a browser or an app installation are generated randomly by Google Analytics, and we do not download or store records by those numbers; we only look at totals. What you enter into a tool, and its results, are not sent in visit statistics.
From Kakao and Apple we receive only your member (user) number. We do not receive your email address, name, phone number, or profile photo, and we do not collect your email address, real name, or phone number for comments either. Requests to the comment server are recorded in access logs like any other request.
What you enter into the building register lookup is used only to find the register information, and it is not kept in access logs or server logs.
The conditions and the benefit name search you enter in the government benefits finder (the finder page on this site and the Government Benefits app) are not included in visit statistics, access logs, or notification signals (section 5).
When you press “내 위치로 찾기” (Find by my location) or “내 주변” (Near me), or allow location access, the Tide Table app and the tide table pages on this site use the approximate location of your phone or browser to choose nearby sea stations. This location is used only on your phone or in your browser and is not stored, and it is not sent to our server, to advertisers, or in visit statistics or notification requests. We do not ask for your precise location or for your location while you are not using the app.
Visit statistics from the Tide Table app do not include station names, favorite stations, your location, your “나는 주로” (I mostly go for) choice, or the fish species you chose.
Tide and sea weather data are requested from our server with a station number and a date, so those requests are kept in access logs. The same applies when the app gets data for your favorite stations.
The information Google collects to show ads in the three apps is described in section 8.
3. How long we keep it and how we delete it
| Type | How long we keep it |
|---|---|
| Emails | 1 year from the day we finish replying |
| Visit statistics | Event data (pages and screens viewed, taps) is kept for 2 months from collection, and information tied to the random number for your browser or app install is kept for 14 months (the Google Analytics retention settings). Google deletes it after that. The daily totals we keep cannot identify anyone and are kept separately |
| Earlier visit statistics (collected on our own servers before the move to Google Analytics) | Deleted after the move; backup copies are deleted after 90 days |
| Access logs | 2 years from the day they are recorded |
| Building register lookup | Not kept. Used only while we look it up |
| Comment account | Until you close (delete) your account. We delete it as soon as you do (for the pseudonymous value kept on the comment side, see the two rows below) |
| Housing-notice comments | Until the writer or we delete them. When the writer deletes a comment, its text is deleted at once and only a placeholder (time and pseudonymous value) remains. If you close your account, your comments and records are deleted at once, and only the pseudonymous value is kept for 1 year before deletion |
| Reports and handling records | Reports are deleted as soon as the reporter or the reported user closes their account. Records of comments we hid or accounts we suspended are kept for 1 year after the account is closed, then deleted |
| New-benefit notifications | We do not keep them. How long Google keeps them is described in section 7 |
| Tide notifications | We do not keep them. How long Google keeps them is described in section 7 |
When the period ends, we delete the information without delay. We delete emails from the mailbox, and we delete access logs and housing-notice comments from storage so that they cannot be restored. Google deletes visit statistics when the retention period ends. Records that a law requires us to keep longer are kept separately for that period. To show results faster the next time someone searches for the same address or building, we keep the address candidates and register information we found on our server for a while. It does not include who looked it up or the address text you entered.
4. Sharing with third parties
We do not provide personal information to third parties, except where a law requires us to.
For the building register lookup, our server sends the address you searched for and values that identify the building to the Ministry of the Interior and Safety’s road name address search API and the Ministry of Land, Infrastructure and Transport’s building register API. We do not send information that could identify you, such as your IP address or browser information.
When you delete your comment account, we ask Kakao to disconnect that member number, or, for an Apple account, ask Apple to revoke the login authorization. The only values we send to Kakao or Apple are the member number and login values they issued.
5. Browser and app storage
This site sets Google Analytics cookies for visit statistics and a comment login cookie for housing-notice comments (the first three rows below). The other values are kept in your browser’s storage (localStorage and sessionStorage) to make the tools easier to use; they stay in your browser and are not sent to us, except that the comment login value is sent to our server when you comment.
| Value stored | What it is used for | How to delete it |
|---|---|---|
_ga cookie | A random number that identifies this browser and the time of your first visit; Google Analytics uses it to count visitors and return visits. Kept for 2 years | The “Opt out of visit statistics” button, or deleting this site’s cookies in your browser settings |
Cookies starting with _ga_ | The number and sequence of the current visit (session). 2 years | Same |
tb_session cookie (a token that confirms your login) | Housing-notice comments. While you are logged in, our server uses it to confirm your login. Kept for 30 days | “Log out”, “Delete account”, or delete this site’s cookies in your browser settings |
| The values you last entered in a calculator | The calculators on the Korean pages: VAT, loan interest, date, D-day, savings, pyeong (floor area), percentage, severance pay, and home buying cost | The calculator’s button for deleting saved values, or deleting this site’s data in your browser settings |
| The values you last entered in the ovulation calculator (the start date of your last period and your cycle length) | The ovulation calculator on the Korean pages, only if you turn on saving | The calculator’s button for deleting saved values, or deleting this site’s data in your browser settings |
| A D-day list (names and dates) | The D-day calculator on the Korean pages | Removing items from the D-day list, or deleting this site’s data in your browser settings |
| The participant names and result slots you entered in the ladder game | The ladder game, on both the Korean and English pages | The ladder game’s button for deleting saved values, or deleting this site’s data in your browser settings |
| The card, station, and sea area tab you last chose in the tide table | The tide table pages on the Korean site. Your location is not stored | Deleting this site’s data in your browser settings |
| Filter choices on the housing-notice list (region, notice type, application status, sort order) | The housing-notice list. Saved only when you turn on “Remember filters”. Search text is not saved | Turn off “Remember filters”, or delete this site’s data in your browser settings |
| Visit statistics opt-out marker | One marker that keeps visits from this browser out of visit statistics | The “Opt back in to visit statistics” button, or deleting this site’s data in your browser settings |
| Comment login value (a token that confirms your login, nickname, and expiry time) | Housing-notice comments. Sent to our server when you comment. Kept for 30 days | “Log out”, “Delete account”, or delete this site’s data in your browser settings |
| Kakao login check value (random characters) | Only while you log in with Kakao. Deleted when you close the tab | Automatically |
The number in the _ga cookie is sent to Google with visit statistics. In the EEA, the UK, and Switzerland, this cookie is set only after you agree in the consent message (section 8).
To opt out of visit statistics, press the “Opt out of visit statistics” button on this page. This deletes this site’s Google Analytics cookies, and from then on this browser does not load the Google Analytics tool. To remember your choice, we keep one marker in your browser’s storage. If you delete this site’s data in your browser settings, this marker is deleted too, and your visits are counted again. To block Google Analytics on all websites, you can use the Google Analytics Opt-out Browser Add-on. You can still use every tool after opting out.
The Google Analytics tool in all three apps keeps an app instance ID and the date you first opened the app in the app’s storage. Clearing the app’s data or deleting the app creates a new number.
The Building Register app keeps the values below in the app’s storage on your phone. These values stay on your phone and are not sent to us. On Android they are excluded from your phone’s automatic backup and from transfers to a new phone, and on iPhone they are excluded from iCloud and computer backups. So they usually do not move with you when you change phones. They are deleted when you delete the app.
| Value stored | What it is used for | How to delete it |
|---|---|---|
| Recent lookups (values used to find the building and unit again, the road name address, building name, dong and ho shown in the list, and the date you viewed it; up to 20) | The recent lookups list in the app | The delete button on each row, “전체 지우기” (Delete all) in recent lookups, “저장한 기록 지우기” (Delete saved records) on the help screen, or deleting the app |
| Favorites (the same values as recent lookups and the date you added it; up to 50) | The favorites list in the app | “즐겨찾기에서 빼기” (Remove from favorites), “저장한 기록 지우기” (Delete saved records) on the help screen, or deleting the app |
| Addresses you searched for in the old app (up to 4) | On a phone updated from the old version, the app moves the recent searches that the old version kept on the phone and shows them on the first screen. The old version’s copy is deleted after the move | The delete button on each row, “저장한 기록 지우기” (Delete saved records) on the help screen, or deleting the app |
| App state values (whether old values were moved, whether you saw the update notice, the version whose update alert you closed, whether we asked for a review, the number of results you saw, when and how often a full-screen ad was shown, and the height of the ad space) | Showing the app’s notices only once, and not showing full-screen ads too often | Deleting the app. “저장한 기록 지우기” (Delete saved records) does not delete these values |
When you log in to comment, the Building Register app keeps your login value (a token that confirms your login, the login method, and your nickname) in the phone’s secure storage (iPhone Keychain, Android Keystore) under the name com.gofillus.landinfo.auth.session. Unlike the values in the table above, it is sent to our server when you comment, and it is used for 30 days. It is deleted when you tap “Log out” or “Delete account”. On iPhone this value may remain after you delete the app, so the app deletes it the first time you open it after reinstalling. If you log in with Kakao, Kakao’s login tool also keeps the login value Kakao issued on your phone. This value is deleted when you delete your account or delete the app.
The Government Benefits app keeps the values below in the app’s storage on your phone. These values stay on your phone and are not sent to us. On Android they are excluded from your phone’s automatic backup and from transfers to a new phone, and on iPhone they are excluded from iCloud and computer backups, so they usually do not move with you when you change phones. They are deleted when you delete the app.
| Value stored | What it is used for | How to delete it |
|---|---|---|
| The conditions you entered (birth year, where you live, individual or household, or small business or business owner, sex, income, household situation, study and work, business stage, industry, and health conditions: preparing for pregnancy or infertility, pregnancy, childbirth or adoption, disability, national merit (veteran) status, and illness or disease) | The matched list and matching for new-benefit notifications. Matching happens only on your phone | Editing them in “내 조건” (My conditions), “건강 조건 지우기” (Delete health conditions; health conditions only), “저장한 정보 지우기” (Delete saved information) on the help screen, or deleting the app |
| Starred benefits | The starred list and deadline notifications | Tapping the star again, “저장한 정보 지우기” (Delete saved information), or deleting the app |
| Notification settings and status (whether new-benefit and deadline notifications are on, whether the notification topic is subscribed, the names of new benefits not yet shown, and scheduled deadline notifications) | Notifications | Turning them off in the notification settings, “저장한 정보 지우기” (Delete saved information), or deleting the app |
| The downloaded benefit list and benefit details (starred benefits and the 100 most recently opened) | Viewing the list and details even without a connection | “저장한 정보 지우기” (Delete saved information), or deleting the app |
| App state values (whether you saw the first-launch guide, whether you refused notification permission, the day visit statistics were last sent, how many details you opened, and when and how often a full-screen ad was shown) | Showing the guide only once, and not showing full-screen ads too often | “저장한 정보 지우기” (Delete saved information), or deleting the app. The full-screen ad record is created again as you keep using the app |
Your list of starred benefits stays on your phone. However, when the app gets a benefit’s details (when you open a detail, when you star a benefit, and when the benefit list changes and the app gets your starred benefits’ details again), it requests them from our server with that benefit’s number, so those requests are kept in access logs (section 2).
The Tide Table app keeps the values below in the app’s storage on your phone. These values stay on your phone and are not sent to us. On Android they are excluded from your phone’s automatic backup and from transfers to a new phone, and on iPhone they are excluded from iCloud and computer backups, so they usually do not move with you when you change phones. However, on iPhone the widget data (the fourth row below) is included in iCloud and computer backups, so it may move with you if you restore a new iPhone from a backup. They are deleted when you delete the app.
| Value stored | What it is used for | How to delete it |
|---|---|---|
| Favorite stations (up to 5), your “나는 주로” (I mostly go for) choice, the station you last chose, and the fish species you chose | The cards on the Today screen, tide notifications, and the home screen widget | Removing a station from favorites (that station only), “저장한 것 지우기” (Delete saved data) in Settings, or deleting the app |
| Notification settings and status (whether tide notifications are on, which kinds are on and how early to notify, whether the notification topic is subscribed, the times and text of scheduled notifications, and when notifications were last rescheduled) | Tide notifications | Turning them off in the notification settings, “저장한 것 지우기” (Delete saved data), or deleting the app |
| Downloaded data (the station list, app settings, current tide and sea weather, and 42 days of tides for your favorite stations) | Viewing them even without a connection | “저장한 것 지우기” (Delete saved data), or deleting the app |
| Widget data (the name of your first favorite station and its tide times and heights for 7 days) | The home screen widget. The widget reads only these values and does not connect to the internet | “저장한 것 지우기” (Delete saved data), or deleting the app |
| App state values (whether you saw the first-launch guide, whether we asked for location, the number of widgets placed, the notification channel name, and when to download data next) | Showing the guide and asking for location only once | “저장한 것 지우기” (Delete saved data), or deleting the app |
“저장한 것 지우기” (Delete saved data) in Settings deletes all the values in the table above, cancels scheduled tide notifications, unsubscribes from the notification topic, and deletes the notification token. It does not delete your choice in the ad consent message (kept on your phone by Google’s ad consent tool), the app instance ID for visit statistics, or the location permission in your phone’s settings. You can change your ad consent with “광고 동의 다시 고르기” (Choose ad consent again) (section 8), and the location permission in your phone’s settings. The Tide Table app uses your approximate location briefly on your phone and does not keep it in the app’s storage (section 2).
Except for the building register lookup, what you enter into a tool is processed only in your browser. It is not sent to our server, to advertisers, or in visit statistics requests. What you enter into the building register lookup is sent to our server to find the register information (sections 2 and 4), but it is not sent to advertisers or in visit statistics requests. The same applies to what you enter in the Building Register app. The conditions (including health conditions) and the benefit name search you enter in the government benefits finder are used only in your browser or on your phone, and are not sent to our server, to advertisers, or in visit statistics or notification requests. The finder page on this site does not store your conditions in your browser either. The approximate location used by the Tide Table app and the tide table pages on this site is used only on your phone or in your browser, and is not sent to our server, to advertisers, or in visit statistics or notification requests.
6. Share links
A share link for a tool’s result contains the values you entered (including D-day names, participant names in the ladder game, and the building, dong and ho chosen in the building register lookup). Anyone who receives the link can see all of those values. If you entered information such as another person’s name, please check before you send the link.
The values in a share link come after the “#” in the address, so they are not sent to the server, and they are removed from the address as soon as the page opens. However, when you open a share link for the building register lookup, the building, dong and ho in the link are sent to our server to find the register information.
The share button in the Building Register app sends a message through your phone’s share sheet. The message contains a web share link with the building, dong and ho you chose, and it does not contain the address you typed into the app. When someone opens that link, it is handled as described above.
On government benefit pages and in the Government Benefits app, sharing sends only the address of that benefit’s page, without the conditions you entered.
7. Outsourcing and international transfer
We entrust the work below to other providers.
| Provider | What we entrust to it |
|---|---|
| Amazon Web Services Korea LLC | Sending replies to your emails (Amazon SES) |
| Google LLC | Delivering new-benefit notifications in the Government Benefits app and tide notifications in the Tide Table app (Firebase Cloud Messaging) |
| Google LLC | Collecting, storing, and totaling visit statistics for this site and all three apps (Google Analytics, Firebase) |
To learn how Google uses this information, see How Google uses information from sites or apps that use our services.
Replies to your emails are sent from servers in Seoul, Republic of Korea, and no personal information is transferred outside Korea for this.
To deliver new-benefit notifications in the Government Benefits app and tide notifications in the Tide Table app, and to process visit statistics, we transfer personal information outside Korea as described below. Because this is outsourcing needed to provide these services, we disclose the items below in this policy and transfer on that basis (Article 28-8(1)3 of the Personal Information Protection Act).
New-benefit notifications
| Item | Details |
|---|---|
| Recipient and contact | Google LLC (Firebase). Privacy contact: https://firebase.google.com/support/privacy/dpo |
| Personal information transferred | Values that identify the phone to notify (the Firebase installation ID and the notification token; on iPhone, this includes the value Apple’s notification service assigned to the phone), the notification topic subscribed to (one topic, the same for every user), and the app version and phone information (such as the operating system version and model) |
| Countries | The United States and other countries where Google has data centers |
| When and how | When you turn on new-benefit notifications and while they stay on, the app sends them over an encrypted connection |
| Purpose | To deliver a notification signal to the phone on days when new benefits appear |
| Retention | Until you turn notifications off or press “저장한 정보 지우기” (Delete saved information). At that point the app unsubscribes from the notification topic and deletes the notification token. Google deletes the Firebase installation ID if the app does not connect to Google for more than 270 days |
| How to refuse, and what happens | Do not turn on “새 혜택 알림” (New-benefit notifications), or turn it off later in the app’s notification settings. If you refuse, you only stop receiving new-benefit notifications. You can still use deadline notifications for starred benefits and every other feature of the app |
Tide notifications
| Item | Details |
|---|---|
| Recipient and contact | Google LLC (Firebase). Privacy contact: https://firebase.google.com/support/privacy/dpo |
| Personal information transferred | Values that identify the phone to notify (the Firebase installation ID and the notification token; on iPhone, this includes the value Apple’s notification service assigned to the phone), the notification topic subscribed to (one topic, the same for every user), and the app version and phone information (such as the operating system version and model) |
| Countries | The United States and other countries where Google has data centers |
| When and how | When you turn on tide notifications and while they stay on, the app sends them over an encrypted connection |
| Purpose | To deliver a signal to the phone twice a day (6:30 a.m. and 6:30 p.m. Korea time), telling the app to download fresh data and reschedule its notifications |
| Retention | Until you turn notifications off, press “저장한 것 지우기” (Delete saved data), or turn off this app’s notifications in your phone’s settings and then open the app. At that point the app unsubscribes from the notification topic and deletes the notification token. Google deletes the Firebase installation ID if the app does not connect to Google for more than 270 days |
| How to refuse, and what happens | Do not turn on tide notifications, or turn them off later in the app’s notification settings. If you refuse, you only stop receiving tide notifications, and you can still use every other feature of the app |
Visit statistics
| Item | Details |
|---|---|
| Recipient and contact | Google LLC (Google Analytics, Firebase). Privacy contact: https://support.google.com/policies/contact/general_privacy_form |
| Personal information transferred | The items in the four “Visit statistics” rows of section 2 (this site, the Building Register app, the Government Benefits app, and the Tide Table app) |
| Countries | The United States and other countries where Google has data centers |
| When and how | When you open a page (web) and while you open and use the app (apps), sent by your browser or app over an encrypted connection |
| Purpose | To total visits, usage, and ad revenue |
| Retention | Event data 2 months from collection; information tied to the browser or app-install number 14 months (section 3) |
| How to refuse, and what happens | Website: the “Opt out of visit statistics” button (section 5), deleting this site’s cookies in your browser, or the Google Analytics Opt-out Browser Add-on. You can still use every tool. Apps: if you delete the app, it no longer sends visit statistics. In that case, you cannot use the app |
Notification signals do not contain benefit names, counts, or the conditions you entered. We do not receive notification tokens, and we do not send notifications to individual phones. On iPhone, Google delivers the signal through Apple’s notification service (APNs). Deadline notifications for starred benefits are scheduled on your phone, so nothing is transferred outside Korea for them.
Tide notification signals carry no text and do not contain station names, favorite stations, or tide times. We do not receive notification tokens, and we do not send signals to individual phones. When the app receives the signal, it downloads fresh data and creates the notification text (station name and time) on your phone. On iPhone, Google delivers the signal through Apple’s notification service (APNs) as a signal that is not shown on screen.
This site, housing-notice comments (including comment accounts), and incoming emails are handled on servers we run ourselves in Korea. Visit statistics are processed by Google as described above; we receive only daily totals and keep them on our servers in Korea. With Apple login in the iPhone app, you log in directly with Apple (Apple Inc., United States), and we receive the user number and login values Apple issues as a result. Our server sends these values back to Apple to verify them when you log in and to revoke them when you delete your account; we do not outsource any processing of personal information to Apple or send Apple personal information it does not already have.
8. Advertising and third-party cookies
This site shows ads through Google AdSense. There are no ads on the About, Contact, and Privacy Policy pages.
Third party vendors, including Google, use cookies to serve ads based on a user’s prior visits to this website or other websites. Google’s use of advertising cookies enables it and its partners to serve ads to users based on their visit to this site and/or other sites on the Internet. Some of these cookies are stored under this site’s address.
| Item | Details |
|---|---|
| Collection technologies | Cookies, web beacons, device identifiers, and other ad technologies |
| Type | Third-party cookies |
| Who collects | Google LLC and third-party ad vendors certified by Google |
| What is collected | Visits to this site and to other websites, ads viewed or clicked, IP address, and browser and device information |
| Purpose | To serve ads and measure their performance, and to choose ads that match your interests |
| How to opt out | The three ways below |
There are three ways to opt out of personalized ads.
- Users may opt out of personalized advertising by visiting Ads Settings.
- Users may also opt out of a third-party vendor’s use of cookies for personalized advertising by visiting www.aboutads.info.
- You can block or delete cookies in your browser settings.
In the EEA, the UK, and Switzerland, the same consent message also asks whether you agree to visit statistics cookies (section 5).
If you turn off personalized ads or block cookies, you will still see ads, but they will not be based on your interests. To learn how Google uses information from sites that use its services, see Google’s explanation.
Google and other third-party ad vendors may collect information about your online activities over time and across different websites, including this site, when you use this site. Ad cookies go directly from your browser to Google and other ad vendors, and we do not receive that information.
Do Not Track. We do not change how this site collects information in response to “Do Not Track” signals from your browser. Instead, you can opt out of our visit statistics (Google Analytics) with the button on this page or the opt-out add-on (section 5), and opt out of personalized ads in the ways above.
US state privacy laws. When this site shows ads to visitors in US states that have consumer privacy laws, it also shows a Google message with a link to opt out of the sale or sharing of your personal information for targeted advertising. If you opt out, Google shows you only non-personalized ads on this site. In those states, Google also treats a Global Privacy Control signal from your browser as the same request.
Ads in the three apps. The Building Register app, the Government Benefits app, and the Tide Table app show ads through Google AdMob. Google’s ad tool built into each app sends the information below directly to Google, and we do not receive it. For the Building Register app and the Government Benefits app, we link Google AdMob with Google Analytics and receive the number of ads viewed and ad revenue as totals in visit statistics; we do not link them for the Tide Table app. What you choose in the ad consent message also applies to visit statistics. The address you search for and the building, dong and ho you choose in the Building Register app, the conditions, the benefit name search and the starred benefits in the Government Benefits app, and your location, favorite stations, and the station and species you choose in the Tide Table app, are not included in ad requests.
| Item | Details |
|---|---|
| Collection technologies | Google’s ad tool built into the app (Google Mobile Ads SDK), Google’s tool that asks for your consent to ads (User Messaging Platform), and your phone’s advertising identifier (the advertising ID on Android, the advertising identifier on iPhone) |
| Type | A third-party ad tool built into the app |
| Who collects | Google LLC |
| What is collected | IP address and the approximate location estimated from it, records of opening and tapping in the app and of ads viewed or tapped, performance information about the app and the ad tool (such as launch time and freezes), and device identifiers (on Android, the advertising ID and app set ID; on iPhone, the advertising identifier if you allow tracking, and a device identifier shared only among apps from the same developer) |
| Purpose | To serve ads and measure their performance, to choose personalized ads, and to prevent fraudulent use of ads |
| How to opt out | The ways below |
You can opt out of personalized ads in the app as follows.
- Android: You can delete or reset your advertising ID in the ads menu of your phone’s settings. If you delete it, the app receives a value of zeros instead of an advertising ID.
- iPhone: Before the app first shows an ad, a window asks once whether you allow the app to track your activity across other companies’ apps and websites. If you choose “Ask App Not to Track”, the app receives a value of zeros instead of an advertising identifier, and you see non-personalized ads. You can change your choice at any time in Settings > Privacy & Security > Tracking on your phone.
- If you open the app in the European Economic Area, the United Kingdom, or Switzerland, Google shows a window asking whether you consent to personalized ads. You can change your choice with “광고 동의 다시 고르기” (Choose ad consent again) on the help screen (Building Register and Government Benefits apps) or the settings screen (Tide Table app). This row appears only in the regions where consent is asked.
You will still see ads, and you can use every feature of the app, even if you delete your advertising ID or do not allow tracking.
9. Your rights and how to use them
You can ask us to let you see your personal information, or to correct it, delete it, or stop processing it. Send your request to the email address below, and we will respond within the period required by law. You can also make a request through a representative. You can use these rights wherever you live.
- Email: toolbox@gofillus.com
Visit statistics and access logs are not linked to names or email addresses, so we may not be able to find the records that belong to you. In that case, we will tell you why. You can stop this site’s visit statistics at any time in the ways described in section 5 and still use every tool. The three apps stop sending visit statistics when you delete the app; in that case, you cannot use the app (section 7).
You can edit or delete your own comments at any time. We review reported comments within 24 hours.
You can delete your comment account at any time with “Delete account” in the comment area on this site’s notice pages, or in the “Account” box at the top of the Building Register app’s comment screen. Deleting it also deletes your comment text, likes, blocks, and reports, and only a “deleted comment” placeholder remains where your comments were. Your Kakao or Apple login connection is also disconnected.
We do not hold the values used for new-benefit notifications in the Government Benefits app. If you turn notifications off in the app or press “저장한 정보 지우기” (Delete saved information), the app unsubscribes from the notification topic and deletes the notification token (section 7).
We do not hold the values used for tide notifications in the Tide Table app either. If you turn notifications off in the app or press “저장한 것 지우기” (Delete saved data), the app unsubscribes from the notification topic and deletes the notification token (section 7).
10. Security measures
- Only the people who run the site can see the email inbox, access logs, the comment admin screen, and the Google Analytics admin screen, and the Google Analytics admin accounts use two-step verification. The value used to disconnect Apple login is stored encrypted.
- The visit statistics totals we keep contain only values that cannot identify anyone, and their screen is not open to the internet.
- Records whose period has ended are deleted as described in section 3.
11. Privacy officer
| Item | Details |
|---|---|
| Name | Park Kiwan (박기완) |
| Position | Representative |
| Contact | toolbox@gofillus.com |
Please send questions, complaints, and requests for remedies about personal information to the contact above.
12. Remedies for privacy violations
If you need a remedy or advice about damage from a privacy violation, you can contact the Korean agencies below.
- Personal Information Dispute Mediation Committee: www.kopico.go.kr, phone 1833-6972
- Personal Information Infringement Report Center (Korea Internet & Security Agency): privacy.kisa.or.kr, phone 118
13. Changes to this policy
This policy applies from the effective date above. When it changes, we post the new policy on this page and record the effective date and the changes in the table below.
| Effective date | Changes |
|---|---|
| September 29, 2026 | First version |
| September 30, 2026 | Added how to opt out of visit statistics to section 5 |
| September 30, 2026 | Added the 13-month lifetime of the first-visit marker to section 5, and published this policy in English |
| October 1, 2026 | Added the home buying cost calculator and the ovulation calculator to the browser storage table in section 5 |
| October 2, 2026 | Added the ladder game to the browser storage table in section 5 and to share links in section 6 |
| October 7, 2026 | Described in the introduction and sections 1 to 6 how values entered into the building register lookup are sent to our server and handled |
| October 12, 2026 | Added the Android app “건축물대장” (Building Register) to this policy in the introduction and sections 1, 2, 5, 6 and 8, and added to section 3 the address candidates we keep on our server |
| October 18, 2026 | Added the iPhone version of the Building Register app to this policy in the introduction and sections 2, 5 and 8 |
| October 20, 2026 | Added “정부 지원금 찾기” (Government Benefits Finder) — the government benefits pages on this site and the Government Benefits app — to this policy in the introduction and sections 1, 2, 3 and 5 to 9 (section 7: outsourcing and international transfer for new-benefit notifications), and described the page viewed in section 2’s visit statistics as the page’s address and title |
| November 4, 2026 | Moved visit statistics to Google Analytics and described this in the introduction and sections 1, 2, 3, 5, and 7 to 10 (section 7: outsourcing and international transfer of visit statistics; section 5: Google Analytics cookies), and described filter memory and comments for subscription and rental housing notices in the introduction and sections 1, 2, 3, 5, 7, 9, and 10 |
| November 12, 2026 | Described Kakao and Apple login for housing-notice comments (comment accounts, the login cookie and the app’s login value, and account deletion) in the introduction and sections 1, 2, 3, 4, 5, 7, 9, and 10, and corrected the retention of reports and handling records (announced on November 5, 2026 to take effect on December 1, 2026, and brought forward to November 12, 2026) |
| November 12, 2026 | Added the mobile app “물때표” (Tide Table) and the tide table pages on this site to this policy in the introduction and sections 1, 2, 3, 5, and 7 to 9 (section 7: outsourcing and international transfer for tide notifications) |