Data collected
Optional
Only crash reports, and only when you tap Send.
Data shared
None
Nothing goes to any third party.
In transit
Encrypted
TLS between your two devices. HTTPS for crash reports.
Where your data goes
Your phone
Reads only the folders you chose. Keeps the pairing, the folder list and a file index in private storage.
Files, names, sizes, dates, checksums, phone name and model
TLS 1.3, both sides pinned, same Wi‑Fi
Your computer
Saves the files in the download folder you chose. Your own device, not a third party.
No cloud, no tracking. No usage analytics, ads, advertising ID, account, location, contacts or purchases. The only thing the developer can receive is a crash report you approve.
Crash reports you approve
After a crash, if you say yes
The next start asks: Send or Don’t send, with an optional comment. Nothing is sent without a tap, for each report.
What a report holds
The error’s technical details (which may rarely name a file or folder), the app, Android and phone model, the crash time, your comment, the end of the app’s log, and two random IDs: one for this installation and one for the report.
Where it goes, and how long
Over HTTPS to the developer’s own server. Not shared. Deleted after at most 90 days, plus up to one day.
Your address
Used in the server’s memory only, to accept one report an hour from one address and 60 an hour in total. Not stored with the report, not logged.
Answers in Google Play’s Data safety form
| Question | Answer |
|---|---|
| Does the app collect or share any of the required user data types? | Collects, optionally. Shares nothing. |
| Data types collected | Crash logs, Diagnostics, Device or other IDs, Other user-generated content. All optional. |
| Why it is collected | Analytics: finding and fixing crashes |
| Data types shared | None |
| Is data encrypted in transit? | Yes |
| Can you ask for your data to be deleted? | Yes, by writing to the contact address. See “Deleting your data” below. |
| Independent security review | Not done |
Google Play counts data as collected when it leaves your device, unless only the sender and the recipient can read it. JstSync’s files travel encrypted between your own phone and your own computer, so they fall under that exception. Crash reports go to the developer’s own server, so they count as collected; each one is optional and is sent only when you tap Send.
Permissions the app asks for
Camera
Only while the scanner is open, to read the QR code. Pictures are never stored or sent.
Local network and Wi‑Fi multicast
To find your paired computer on your Wi‑Fi. Answers count only from that computer.
Network access and state
To connect to your computer, to wait for an unmetered Wi‑Fi, and to send a crash report you approve.
Notifications
Shows a transfer in progress, with its Stop button. The app works without it.
Background sync
Foreground service for data sync, run at boot and keep awake: to finish a transfer and check for new files after a restart.
Folders
No storage permission: you pick each folder in Android’s own folder picker.
Deleting your data
- On the phone: uninstall JstSync, or clear its storage in Android’s settings.
- On the computer: remove the phone in the desktop app. Files already copied stay there; they are yours to delete.
- At the developer: crash reports you sent are deleted after at most 90 days. To have one deleted sooner, write to the contact address with the date of the crash and your phone model.