Privacy Policy
LivingHits (“we”, “us”) operates the JONIVIEW app and the website joniview.com (the “Service”). This policy explains what personal information we process and why, how long we keep it and how we protect it.
1. The short version
- Your phone screen and sound, what you tap on the car screen, and what you type with the car keyboard are never sent to or stored on our servers. They travel only between your phone and your car within your phone’s hotspot.
- The app does not access your location, microphone, camera, contacts, phone number, advertising ID, or hardware IDs such as IMEI. To tell devices apart it uses only a hash of the device ID that Android gives the app. The app uses the Nearby devices permission only to show the Bluetooth devices paired with your phone so you can choose one for Auto start, and to check whether a device you chose is connected.
- The website has no sign-up or payments and uses no advertising or tracking tools.
2. Information that stays on your phone
The app uses the following only on your phone and never sends it to us. We cannot see it.
- Your phone screen and app sound, what you tap on the car screen, and text you type with the car keyboard (including showing text already in a phone text field on the car screen)
- The list of apps installed on your phone (to show them on the car screen)
- Car connection history and Wireless debugging pairing details (the 6-digit connection code is stored briefly on our server while the connection signal is exchanged, as shown in section 3)
- Diagnostic logs for troubleshooting (stored in the app’s private storage on your phone)
- The addresses of the Bluetooth devices you choose for Auto start, and your Auto start settings (so that you can choose, the app reads the list of Bluetooth devices paired with your phone; these are kept only on this phone and are not backed up)
- Your quality settings (kept only on this phone and not backed up)
3. Personal information we process
| Category | Data | Purpose | Legal basis |
|---|---|---|---|
| Account (when you sign in with Google in the app) | Sign-in ID (Firebase UID), your Google account email address and name, sign-in method | Confirming who owns a license, managing registered devices, handling requests such as account deletion | Contract |
| Anonymous sign-in (all users, including those who do not sign in) | Anonymous sign-in ID (Firebase UID) — created automatically by the app the first time you use the free trial or the car screen. It contains no email or name | Checking requests that write trial and car-connection data, and letting only the creator of a connection room or code change or delete it | Contract |
| Sign-in security (including anonymous sign-in) | IP address and device, OS and SDK version information — processed by Google (Firebase Authentication) during sign-in | Security and fraud prevention | Legitimate interests |
| Purchase | Google Play order ID and purchase token, product, purchase/refund status and time (verified through RevenueCat) | Verifying your license, refunds, fraud prevention | Contract; legal obligation (keeping purchase records) |
| Device registration | A hash of the device ID (the original is not stored), device model, device name, registration time | Enforcing the number of devices per account (2), fraud prevention | Contract |
| Free trial | Trial time used (seconds) and time recorded, per device-ID hash — not linked to your account | Preventing repeat trials by reinstalling | Legitimate interests |
| Car screen connection | 6-digit connection code (stored in Cloud Firestore for the connection signal, valid for up to 10 minutes), connection room identifier, the sign-in ID (Firebase UID) of whoever created the room, and temporary connection details the phone and the car browser need to reach each other (including network addresses inside the phone’s hotspot) | Connecting the phone to the car browser to show the phone screen | Contract |
| Support | Email address, name (if given), message content | Answering you, handling disputes | Contract; legitimate interests |
| Website logs | IP address, browser information, time and page — recorded automatically by our host (Cloudflare) | Providing and securing the website (blocking attacks) | Legitimate interests |
Payment methods and card details are handled by Google; we never receive them.
4. How long we keep it
- Account and device list: deleted immediately when you delete your account in the app; within 10 days if you ask by email. As Google states, it is removed from Google (Firebase) live and backup systems within 180 days after deletion.
- Anonymous sign-in ID: kept in Firebase Authentication for as long as we provide the Service. If you later sign in with Google, the same ID usually becomes your account’s sign-in ID and is deleted when you delete your account. However, if you sign in with a Google account that already has a JONIVIEW account, the app switches to that account and the previous anonymous ID remains, unlinked to any account. An anonymous ID that is not linked to an account is not removed from Firebase Authentication when you uninstall the app or clear its data (the phone gets a new ID next time).
- Purchase and refund records (including the sign-in ID and purchase data kept at RevenueCat): 5 years; complaint and dispute records: 3 years, as required by Korean e-commerce law. These are kept separately for that period even after account deletion, then destroyed.
- Support messages: 3 years after we answer.
- Free-trial records: 1 year after last use. Website logs: per Cloudflare’s retention policy. Sign-in security data: as Google states, Firebase Authentication keeps IP addresses for a few weeks.
- Car connection data: the connection code is deleted as soon as you close the code screen. Otherwise it expires after 10 minutes and can no longer be used, and expired codes are deleted automatically. Connection room data (including the sign-in ID of its creator) expires 30 days after last use and is then deleted automatically.
When a retention period ends or the purpose is fulfilled, we destroy the data without delay. Electronic files are deleted so they cannot be recovered; we do not keep personal information on paper.
5. Sharing
We do not sell your personal information or provide it to third parties, except where the law specifically requires it or authorities request it through legal procedures.
6. Service providers
| Provider | Role |
|---|---|
| Google LLC — Firebase (Authentication, Cloud Firestore Seoul region), Google Play | Sign-in (including anonymous sign-in) and sign-in security, storing account/device-list/trial/car-connection data, payment processing |
| RevenueCat, Inc. | Verifying Google Play purchases and managing license status |
| Google LLC — Gmail | Receiving and answering support email |
| Cloudflare, Inc. | Website hosting and security |
7. International transfers
| Recipient (contact) | Country | Data | When and how | Purpose / retention |
|---|---|---|---|---|
| Google LLC (support.google.com/cloud/contact/dpo) | USA. Cloud Firestore data is located in Korea (Seoul region), but Google may access it from abroad for operations and support, and sign-in (Firebase Authentication, including anonymous sign-in) and sign-in security data are processed in US data centres, so we disclose this as a transfer. | Account, anonymous sign-in, sign-in security, device, trial and car-connection data in section 3; support email | Over the network when you sign in or use the free trial or car screen in the app (including anonymous sign-in), or email us | Tasks in section 6 / periods in section 4 |
| RevenueCat, Inc. (www.revenuecat.com/privacy) | USA | Sign-in ID (Firebase UID); purchase data in section 3 | Over the network after you sign in with Google, when you open the app (automatic license check) and when you open the purchase screen, buy or restore | Tasks in section 6 / purchase records 5 years |
| Cloudflare, Inc. ([email protected]) | USA and other countries with Cloudflare data centres | Website logs | Over the network when you visit the website | Hosting and security / Cloudflare’s retention policy |
If you do not sign in or purchase in the app, your account and purchase data are not transferred. However, the free trial and car connection also need the anonymous sign-in ID, sign-in security data, device-ID hash and time used, and car-connection data, so if you do not want those transferred either, you cannot use the app. Website logs are necessary to provide the website, so to avoid them you would need not to use the website.
8. Cookies and local storage
- We do not use cookies. Cloudflare may set strictly necessary cookies for security (blocking automated attacks).
- Your language choice on the website is stored only in your own browser (localStorage) and is not sent to us. Clearing site data in your browser removes it.
- The car-screen page remembers your phone's language in the car browser's storage (localStorage) so it opens in the same language next time, and keeps a marker in that tab's temporary storage (sessionStorage) so that, if the page is older than the app, it reloads only once. Neither is sent to us. Clearing site data in the car browser removes them.
9. Automated checks
When verifying your license and registering devices, the app automatically checks purchase records, the number of registered devices (2) and the 30-day interval for new devices. If such a check has refused you, you can ask us for an explanation or a review by a person using the contact below.
10. Pseudonymised data
We do not process pseudonymised data without consent for statistics, scientific research or public-interest archiving under Article 28-2 of Korea’s Personal Information Protection Act.
11. Your rights
- You can ask at any time to access, correct or delete your personal information, to restrict or object to its processing, to receive it in a portable format, or to withdraw consent.
- Email us at the contact below, preferably from the email address you signed in with so we can confirm it is you. A legal representative or someone you authorise can also make a request.
- We act within the period required by law (10 days for access, correction and deletion under Korean law) and tell you the outcome. If the law requires us to refuse or limit a request, we tell you why.
- You may also lodge a complaint with the data protection authority where you live.
12. Deleting your JONIVIEW account and data
You can delete your JONIVIEW account and associated data in either of these ways. Uninstalling the app alone does not delete your account.
- In the app: Settings → Account → Delete account
- By email: send an email with the subject “Delete JONIVIEW account” to [email protected] from the email address you signed in with. You can do this without the app installed.
- Deleted: your account (sign-in ID, email and name), the device list, and the license record on this phone.
- Kept: purchase and refund records for 5 years and dispute records for 3 years, as required by law, stored separately and then destroyed. The purchase record at RevenueCat (sign-in ID with order ID, purchase token, product and purchase/refund status) is not deleted with your account; it is kept for 5 years for payment and refund handling and the purchase-record retention duty under Korean e-commerce law, then destroyed. The sign-in ID left in car connection codes and rooms is deleted automatically once it expires after the periods in section 4 (10 minutes and 30 days). Per-device trial records are not linked to your account and are destroyed 1 year after last use. To enforce the device-swap limit, hashes of your Google account identifier and device IDs, together with the last swap time, are kept for up to 33 days after account deletion and then destroyed. If you sign up again with the same Google account within that period, they are used to continue applying the swap limit.
- Timing: Settings → Delete account in the app takes effect immediately. If you ask by email, we delete within 10 days of confirming your request and let you know.
- Deleting your account also removes the lifetime license on that account, and it cannot be restored. Google Play payment history is managed by Google.
13. Security
- Access to personal information is limited to our representative.
- Encryption in transit (HTTPS), database security rules that let only you read and write your account document, least-privilege access, device IDs stored only as hashes, and car-screen content that travels only between your phone and car and is never sent elsewhere.
- Data is stored in the secure data centres of Google (Firebase), RevenueCat and Cloudflare.
14. Children
The Service is not directed to children under 14 (or the minimum age in your country, if higher), and they cannot create an account. If we learn that we have collected such a child’s information, we delete it promptly.
15. Controller and contact
The controller of your personal information is LivingHits. Privacy officer: 김민겸 (representative) · [email protected]
16. Remedies in Korea
You can also seek mediation or advice from: Personal Information Dispute Mediation Committee (1833-6972, www.kopico.go.kr), Personal Information Infringement Report Center (118, privacy.kisa.or.kr), Supreme Prosecutors’ Office (1301, www.spo.go.kr), Korean National Police Agency cyber crime reporting (182, ecrm.police.go.kr).
17. Users outside Korea
- Legal bases: contract (account, anonymous sign-in, purchase, device, car connection), legal obligation (keeping purchase records under Korean law; for users in the EU and UK, keeping purchase records relies on our legitimate interest in handling disputes and legal claims), legitimate interests (sign-in security, fraud prevention, trial records, answering support requests).
- The European Union and the United Kingdom have adopted adequacy decisions for the Republic of Korea. Data transferred to US providers (Google, RevenueCat, Cloudflare) is protected under each provider’s data protection terms (such as standard contractual clauses).
- We do not sell personal information or share it for targeted advertising.
18. Changes
We will announce changes on the website and in the app at least 7 days before they take effect, and at least 30 days before for significant changes to your rights, such as collecting new kinds of data.
This policy takes effect on 2026-10-21.
Revision history: established 2026-09-30 → revised 2026-10-10 (corrected the server storage of the 6-digit connection code, the anonymous sign-in ID and its retention, IP address processing during sign-in, the RevenueCat purchase record kept after account deletion, and how car-screen sound and keyboard input are handled) → revised 2026-10-21 (added that the addresses of the Bluetooth devices you choose for Auto start, your Auto start settings and your quality settings stay only on your phone and are not backed up, when the Nearby devices permission is used, and that the car-screen page remembers your language in the car browser).