Verify network traffic yourself

Follow these steps to confirm that LINE Data Master only connects to the expected servers.

Method 1: Windows Resource Monitor

Use the built-in Windows tool to inspect the app's network connections.

1

Open Resource Monitor

Press Win+R, type resmon, and press Enter.

Run✕Type the name of a program to open:resmonOKCancel
2

Go to the Network tab

Click the "Network" tab at the top.

CPUMemoryDiskNetwork← Click here
3

Find LINE Data Master

In the "Network Activity" section, look for the process named "LINE Data Master".

ProcessPIDAddressPortchrome.exe12340142.250.80.46443LINE Data Master8842linebkp.com443LINE Data Master8842obs.line-apps.com443LINE Data Master8842127.0.0.1*svchost.exe102420.190.159.4443

* The MCP Server port is randomly assigned on each launch. The actual number will differ from the illustration. You can check it in the app settings page.

4

Verify the connections

You should only see connections to these destinations:

  • ✓linebkp.com — Subscription verification
  • ✓*.line-apps.com — LINE media download
  • ✓127.0.0.1 — MCP Server (localhost only)
DestinationPurposeStatuslinebkp.comSubscription verification✓*.line-apps.comLINE media download✓127.0.0.1MCP Server (localhost only)✓

If you see connections to any other server, please report to us immediately.

Method 2: PowerShell command

Check all connections with a single command.

1

Open PowerShell

Search for "PowerShell" in the Start menu and open it.

2

Run the command and check the output

Copy and paste the following command into PowerShell:

PS C:\> Get-NetTCPConnection -OwningProcess (Get-Process "LINE Data Master" -ErrorAction SilentlyContinue).Id 2>$null | Select-Object RemoteAddress,RemotePort,State | Format-Table

Expected output example:

RemoteAddress      RemotePort  State
-------------      ----------  -----
104.18.12.33              443  Established
  ↑ linebkp.com
203.104.128.34            443  Established
  ↑ obs.line-apps.com
127.0.0.1                 *    Established
  ↑ MCP Server (localhost, *port is randomly assigned)

Method 3: Inspect Actual Data with Fiddler

The first two methods only show connection targets. This method lets you see the actual data being sent, confirming only email and token are transmitted — no LINE data.

1

Download and install Fiddler Classic (free)

Fiddler is an HTTP debugging tool that intercepts and displays all network requests from applications.

https://www.telerik.com/fiddler/fiddler-classic

2

Enable HTTPS decryption

After opening Fiddler, enable HTTPS decryption to see the content of encrypted requests.

Settings path:

Tools → Options → HTTPS → Decrypt HTTPS traffic ✓
3

Open LINE Data Master and inspect intercepted requests

In Fiddler's left panel, find requests to linebkp.com. Click one and check the Request Body on the right:

Fiddler — Web Debugger# Host URL1linebkp.com/api/auth/check2linebkp.com/api/session/heartbeatHeadersRequest BodyResponsePOST /api/auth/checkContent-Type: application/json{"email":"user@gmail.com","token":"a1b2c3d4e5..."}✓ Only email + token, nothing else✓ Your LINE messages, contacts, images are not here at all✕ No messages, contacts, images — zero LINE data uploaded
4

Verify the transmitted data

The Request Body you see should only contain:

✓ Only email (your login account) and token (for subscription verification)

✓ No message content, contacts, images, or file data

✓ No LINE chat, group, or personal information

Learn more about our privacy and security design.

Back to Privacy & Security
Verify Network Traffic Yourself — LINE Data Master