See House · 睇樓
Privacy Policy · 私隱政策
See House uses camera, location, search, saved-building, report, and first-party analytics data only to operate the constrained Hong Kong preview and improve reliability. Crash diagnostics are collected separately through Firebase Crashlytics to fix stability bugs. No account is required and none is offered.
English
Summary
- The camera is optional. It gives you a live view while you scan; when scan verification runs, up to a few camera frames are sent securely to identify the building in view. Frames are processed transiently and are not stored by See House.
- Location is used only while the app is open, to rank nearby building candidates. Scan telemetry stores rounded coordinates only; there is no background location.
- No account, no sign-in. We never ask for your name, email address, phone number, or contacts.
- Saved buildings and draft issue reports stay on your device unless you choose to send a report.
- Analytics are first-party operational events without raw IP storage, raw user-agent storage, precise-location storage, raw search-text storage, or third-party ad pixels.
- Crash diagnostics are collected separately through Firebase Crashlytics to fix stability bugs — collected, never shared, and not used to track you.
- Opening a source listing takes you to a third-party site with its own privacy terms.
Camera frames
Camera scan is optional; every flow also works with manual search. While you scan, the camera feed stays on your device as a live view. When scan verification runs, up to three frames from your camera are sent to our servers over HTTPS and processed with an AI vision service acting for See House, solely to identify the building you are pointing at. See House does not store the frames; our telemetry records only the number of frames processed, for reliability metrics.
We do not use camera frames for identity recognition, window-level or unit-level targeting, or any background capture. Scanning only happens while you are on the scan screen with the camera permission granted.
Location
With your permission, your current location is used while the app is open to rank nearby building candidates during scan and search. Scan telemetry stores rounded coordinates, not your precise position, and the app never collects location in the background.
Crash diagnostics
To fix stability bugs, See House uses Firebase Crashlytics, a Google service acting for See House. When the app crashes or hits a fatal error, Firebase Crashlytics collects crash reports (stack traces), device and operating-system state, and a Crashlytics installation identifier. This diagnostic data is separate from the first-party analytics above: it is collected, never shared with third parties for their own use, and never used to track you or for advertising. Crash reporting starts automatically when the app initializes and needs no sign-in.
Other data we process
See House may process building search terms, selected building and listing identifiers, app language, supported-district scope, feature events, report context, and coarse operational status needed to keep the preview honest and reliable. First-party analytics events carry campaign tags and coarse app events only — never raw search text, precise location, camera frames, IP addresses, names, emails, phone numbers, or addresses, and no third-party ad pixels.
Support requests
The in-app and web support forms have no contact fields — a public receipt ID lets you check the status of a report without giving any contact details. The subject and message text you write is stored for moderation and follow-up, so avoid putting personal information in it; any personal data you choose to include in free text is kept with the report. If you email support@see.house, we receive your email address and use it only to reply to you.
Retention and your choices
Local saved buildings and local issue drafts stay on your device until you remove them or send them through the support path; deleting the app removes them. Server-side operational analytics are used for aggregate reliability and launch-readiness checks. Camera and location permissions can be changed at any time in system settings, and the app keeps working with manual search if you decline them.
Your rights (Hong Kong PDPO)
See House aims to comply with the Hong Kong Personal Data (Privacy) Ordinance (Cap. 486). To make a data access or correction request, or to ask any privacy question, contact support@see.house.
Changes
When this policy changes, we update this page and the date stamp below.
繁體中文
摘要
- 相機屬可選功能:掃描時提供即時畫面;當掃描核實運行時,最多會安全傳送數格畫面以辨認眼前的大廈。畫面經即時處理,睇樓不會儲存。
- 位置只在 App 開啟時用於排序附近大廈。掃描遙測只儲存概略化(經四捨五入)的座標;不會在背景收集位置。
- 無需帳戶、無需登入。我們不會要求你提供姓名、電郵地址、電話號碼或通訊錄。
- 收藏的大廈及回報草稿保存在你的裝置,除非你選擇送出回報。
- 分析數據屬第一方營運事件:不儲存原始 IP、原始 user-agent、精確位置或原始搜尋文字,亦無任何第三方廣告像素。
- 當機診斷資料透過 Firebase Crashlytics 另行收集,用於修復穩定性問題——只作收集,不會分享,亦不會用於追蹤你。
- 開啟放盤來源會前往第三方網站,該等網站有其自身的私隱條款。
相機畫面
相機掃描屬可選功能;所有流程亦可改用手動搜尋。掃描期間,相機畫面停留在你的裝置作即時觀看。當掃描核實運行時,最多三格畫面會經 HTTPS 傳送到我們的伺服器,並由代表 睇樓運作的 AI 視覺服務即時處理,僅用於辨認你面前的大廈。睇樓不會儲存畫面;遙測只記錄處理的畫面數目,作可靠性統計。
相機畫面絕不用於身份識別、窗戶或單位層面的定位,亦不會在背景拍攝。只有你停留在掃描畫面並已授予相機權限時才會掃描。
位置
在你授權下,你的目前位置只會在 App 開啟時用於掃描及搜尋期間排序附近大廈候選。掃描遙測只儲存概略化座標,並非你的精確位置;App 不會在背景收集位置。
當機診斷
為修復穩定性問題,睇樓使用 Firebase Crashlytics(代表 睇樓運作的 Google 服務)。當 App 發生當機或嚴重錯誤時,Firebase Crashlytics 會收集當機報告(堆疊追蹤)、裝置及作業系統狀態,以及 Crashlytics 安裝識別碼。此診斷資料與上述第一方分析分開處理:只作收集,不會分享給第三方作其自身用途,亦不會用於追蹤你或作廣告用途。當機回報會在 App 初始化時自動開始,毋須登入。
其他處理的資料
為維持預覽的誠實與可靠,睇樓可能處理大廈搜尋字詞、所選大廈/放盤識別碼、App 語言、支援地區範圍、功能事件、回報內容及概略營運狀態。第一方分析事件只包含推廣標籤及概略 App 事件——絕不包含原始搜尋文字、精確位置、相機畫面、IP 地址、姓名、電郵、電話號碼或地址,亦無任何第三方廣告像素。
支援查詢
App 內及網頁的支援表格不設聯絡資料欄位——公開收據編號讓你毋須提供聯絡資料亦可查詢回報進度。你填寫的主題及訊息文字會被儲存以作審核及跟進,請避免在當中填寫個人資料;你自行填寫的任何個人資料會隨回報一併保存。如你電郵 support@see.house,我們會收到你的電郵地址,並只用於回覆你。
保留與你的選擇
本機收藏的大廈及回報草稿會保存在你的裝置,直至你移除或經支援途徑送出;刪除 App 亦會清除。伺服器端營運分析只用於整體可靠性及推出準備檢查。你可隨時在系統設定更改相機及位置權限;拒絕後仍可使用手動搜尋。
你的權利(香港《個人資料(私隱)條例》)
睇樓致力遵守香港《個人資料(私隱)條例》(第 486 章)。如需提出查閱或改正個人資料的要求,或有任何私隱疑問,請聯絡 support@see.house。
政策更新
本政策如有更改,我們會更新本頁及頁底日期。
Last updated · 最後更新: 2026-09-23 HKT