PhoneInSight Privacy Policy
In short
- PhoneInSight has no server of its own. Everything the app processes is stored only on the PC where it runs.
- Erasure records, device information, stock and certificates are not sent to the developer (S. Park) or to anyone else.
- No ads, no analytics tools, no usage statistics or diagnostics (telemetry).
- Credit purchases, balances and usage reports are handled by the Microsoft Store.
1. Scope
This policy applies to the Windows app PhoneInSight (the "app"). The app opens the factory reset screen on Android phones connected by USB; when the operator runs the reset on the phone, the app detects the reset execution and the reboot, creates an erasure record and a PDF erasure certificate, and manages inbound, stock and outbound. The shop (business) using the app enters and manages this information itself; the developer does not receive or have access to it.
2. Information the app processes
| Category | Details | Source |
|---|---|---|
| Device information | Model name and model code, manufacturer, OS version, storage, IMEI 1 and 2, serial number, battery health, storage encryption status, and whether a Google or Samsung account and Find My are still present (account names or addresses are not recorded) | Read from the phone over USB via adb, or typed/scanned at inbound |
| Erasure records | Times the erasure started, the reset ran and the reboot was detected; result (executed, canceled, failed); task log; operator name; station name | Created by the app; operator and station names entered in Settings |
| Certificates | Certificate and summary numbers, verification code, the device information and erasure record above, issuer details (shop name, business registration number, address, phone, shop logo image), digital signature | Created by the app; issuer details entered in Settings |
| Stock | Inbound and outbound slips, supplier and buyer names, purchase and sale prices, grade, notes and other entries | Entered by the user |
| Credits | Free-credit usage, purchase and usage history (time, pack, quantity, status), and a tracking ID (a random value) for each usage report | Created by the app |
| Settings | Display language and theme, folder locations, backup schedule, alert and sound settings, contact email and similar | Chosen by the user |
| Signing key | Key for digitally signing certificate PDFs, created on this PC and stored encrypted with Windows user-account protection (DPAPI) | Created by the app |
| Error logs | If an unexpected error occurs, the app may write the error details (time, error message, program location) to a log file | Created by the app |
The app does not read or copy photos, contacts, messages or file contents from the phone.
3. Where information is stored
Everything is stored on this PC. The actual locations are shown in the app under Settings → About.
- Data folder: the database (erasure records, stock, certificate records, credit history), settings, the signing key and error logs (
logsfolder). For the Microsoft Store version this is%LOCALAPPDATA%\Packages\<package name>\LocalCache\Local\PhoneInSight. - Certificate folder: issued PDF certificates and summaries. The default is
Documents\PhoneInSight\증명서and can be changed in Settings. Files you "Save as" go where you choose. - Backup folder: automatic backup files (zip — including the database, the signing key and settings). By default, daily in
Documents\PhoneInSight\백업; the app keeps the latest 14 and deletes older ones. You can change the folder and schedule, or turn backups off, in Settings.
Cloud sync: if the backup or certificate folder is inside a synced folder such as OneDrive (including when Windows is set to back up the Documents folder to OneDrive), that service uploads those files to your cloud storage. The upload is done by that service, not by the app, and that service's terms and privacy policy apply. Backup files contain erasure records and the signing key, so choose a folder that is not synced if you do not want this.
Device tool (adb): to talk to phones, the app runs Android Debug Bridge (adb) on this PC. adb uses a local connection that stays within this PC, and it creates the authentication key that phones use to allow this PC in the .android folder of your Windows user profile.
4. Information sent to the developer
None. The app has no server of its own and does not send the information in section 2 to the developer or to third parties. Error logs are not sent automatically. The developer only receives logs or files if you choose to attach them when contacting support, and uses them only to handle your request.
5. Microsoft Store (payments)
Credits are sold as in-app add-ons through the Microsoft Store. Purchases, payment methods, receipts and credit balances are processed and kept by Microsoft with the Microsoft account signed in to Windows. The app only asks the Store for, or reports to it:
- the list and prices of credit packs, and opening the purchase window;
- the credit balance;
- used credits (the add-on, a quantity of 1 and a random tracking ID). No device information or erasure records are included.
The developer can see the sales reports Microsoft provides to publishers (such as aggregated sales and revenue). Microsoft's processing is covered by the Microsoft Privacy Statement.
6. Ads, analytics and telemetry
The app has no ads, does not use an advertising ID, includes no analytics or tracking tools, and does not collect usage statistics or diagnostics (telemetry). Windows notifications (toasts) are shown only on this PC.
7. Retention and deletion
- The app keeps information on this PC until you delete it.
- Uninstalling: when you uninstall the app in Windows, the data folder (database, settings, signing key, error logs) is removed with it.
- Files in Documents: certificate PDFs and backup files remain after uninstalling. Delete them yourself if you no longer need them. Copies uploaded by a sync service must be deleted in that service.
- The adb authentication key (
.androidfolder) also remains after uninstalling and can be deleted by you. - Purchase history and credit balances on your Microsoft account are kept by Microsoft.
A shop that records information about its customers or business partners in the app (for example, a device's IMEI or a supplier's name) is responsible for handling that information under the privacy laws that apply to it.
8. Security
Information is stored in folders protected by this PC's user-account permissions, and the certificate signing key is encrypted with Windows Data Protection (DPAPI) so it opens only for the same Windows user. Locking the PC, account passwords and where backups are kept are up to you.
9. Children
The app is a business tool and is not directed at children. It does not specifically collect information from children.
10. Changes to this policy
If the app's behavior changes and this policy is updated, the new version will be posted on this page with a new effective date. Significant changes to how information is handled will also be mentioned in the app's update notes.
11. Contact
Publisher: S. Park
Email: psy@4leafglobal.co.kr