1. Data controller and contact

This policy covers www.rosrunner.com and its pages, the RosRunner application and its update service. Jason Chang, an individual publishing under the RosRunner name ("we", "us"), is responsible for personal data we process as described here. Data processed only on your computer or managed devices, and not provided to us, remains under your or your organisation’s control.

For questions or to exercise your rights, contact [email protected]. This is our current primary contact channel; it does not restrict other methods available to you by law.

2. What this website collects

We have not added forms to this site. We do not use website connection data for advertising, behavioural profiling or automated decisions producing legal or similarly significant effects on you, and we do not sell personal data.

Traffic statistics (no cookies). The site uses Cloudflare Web Analytics to count visits and referring pages. It stores no cookies on your device, uses no device fingerprinting and builds no cross-site profile of you; the statistics are aggregated. Because it does not access information on your device, this processing is not based on consent. See Cloudflare’s privacy policy.

Google Analytics. The site uses Google Analytics 4 to learn which pages actually help. When it loads depends on where you are: in the EU, the EEA, the United Kingdom and Switzerland it loads only after you agree in the cookie notice, and before that no related request is made and no _ga or similar cookie is stored; elsewhere it loads when you open a page, and you can decline at any time through “Cookie settings” in the footer. The region is determined by the hosting provider from the connection; when it cannot be determined, you are asked first. It collects page views, referring pages, browser and device type, and an approximate location derived from your IP address.

Your choice. You can change your decision at any time through “Cookie settings” in the footer. Once you decline, Google Analytics is no longer loaded and the _ga cookies set for this site are cleared; the withdrawal does not affect the lawfulness of processing carried out before it. In regions where consent is required, the legal basis is your consent; elsewhere it is our legitimate interest in understanding how the site is used, safeguarded by the ability to decline at any time. Declining does not affect any part of this site.

International transfers. Google Analytics is provided by Google Ireland Limited, and data may be processed by Google LLC in the United States or other third countries. For the safeguards involved, see Google’s privacy policy and how Google Analytics uses data.

Necessary connection processing. The site is hosted on Cloudflare Pages. To deliver pages, maintain security and prevent abuse, the provider processes technical data such as IP addresses, request paths and times, and user agent information sent by your browser. Retention and deletion depend on the services used, applicable settings and provider policies; not all data stays on your computer.

Hosting security features. Depending on the protection enabled and the request, Cloudflare may use necessary security cookies or verification mechanisms. The fact that we set no cookies of our own does not mean every connection will be cookie-free. See Cloudflare’s privacy policy and cookie documentation.

3. When you contact us

When you contact us about the product, licensing, support or security, we process the email address, name or form of address, message and attachments you provide to answer your request, troubleshoot and conduct necessary follow-up. Depending on the request, we rely on consent, a contractual or similar relationship, or another applicable basis permitted by Taiwan’s Personal Data Protection Act. Contacting us does not constitute consent to unrelated uses.

Providing information is your choice. Without a reply address or information needed to investigate an issue, we may be unable to respond or complete support. Provide only necessary data; before sharing someone else’s data, ensure you are authorised and remove unnecessary identifiers.

We retain correspondence and attachments only as needed to handle the request and the resulting licensing or support relationship. Where retention is necessary to meet a legal obligation or address a specific dispute, it is limited in scope and duration. Once the purpose ends and no other lawful basis for retention exists, we delete the data or cease processing and use; copies in provider backups may be removed separately through their backup rotation processes.

We do not use your correspondence address to send marketing emails without consent. Necessary notices relating to your request, service security or legal obligations are not marketing emails.

Do not send unnecessary confidential material. Support will not ask for a device password. Review and redact diagnostic material before sending it, following the support page. Diagnostic attachments you choose to send are handled under this section.

4. How the RosRunner application handles data

The following are product facts about the current build, verifiable from the software itself.

The application contains no telemetry. It does not send device lists, command text or output to us for product usage analytics. Management operations you request exchange the data needed to perform them with the target RouterOS devices. What you choose to send with the AI assistant goes to the AI service you configure, as described in section 5.

Credentials. Login passwords you do not choose to save are held by the application in memory during execution; saved passwords are stored in the operating system’s credential store (Credential Manager on Windows). Profile metadata, such as profile names and usernames, is stored separately in local JSON files without passwords. This is not an unconditional confidentiality guarantee for the operating system, memory dumps or content you export.

Local data. Device lists, Stash, preferences, credential profile metadata and diagnostic records are stored under your local user data folder, %LocalAppData%/RosRunner/, separately from the installation directory. Stash contains device entries, not command text or output. Uninstalling does not automatically delete this data folder.

Device identity records. To confirm that a connection reaches the same device as before, the application records in the local file known-hosts.json the public key fingerprints of devices seen over SSH, API-SSL and REST, together with the corresponding address, device name and the time each was last seen. These records exist only on your computer, are not included in exports or diagnostic packages, and can be reviewed and deleted in the application’s settings.

List files and board files. When you choose to save a list file (.rrlist), it contains the device list and credentials and, depending on your choice, is encrypted with a password; a list file without a password is protected only against being read directly in a text editor. You decide where the file is stored, and you are responsible for carrying and keeping it. Dashboard board files and exported .rrboard files contain only the layout and device addresses, never credentials or history.

Connection map. The connection map reads the devices’ connection tracking tables; IP locations, organizations and service names are all looked up locally from offline data, and remote IP addresses are never sent to an online service. The map preference file connection-map.json and downloaded location databases are not included in diagnostic packages. Exported CSV files contain real IP addresses and are yours to keep secure.

Text encoding conversion. Before each conversion, the software keeps a restore record on your computer that contains the original content of the converted fields, which may include password fields. Restore records are stored encrypted on your computer, and the key is kept in the operating system’s credential store. Restore records and exported CSV files are not included in the diagnostics package. The configuration backup made before a conversion is saved in the backup folder you chose and is yours to keep safe.

Crash records and diagnostic packages. The application can save crash records locally when errors occur. The diagnostics window lists package contents, which may include application and operating system versions, error details, activity breadcrumbs and preferences. Records and packages are not uploaded automatically; you decide whether to export and send them. Review them before sending, as redaction cannot guarantee removal of every secret.

Deleting local data. When you no longer need it, close the application and remove the relevant files from that folder; this removes the corresponding settings or records. Remove saved passwords separately through the application’s credential management or Windows Credential Manager, and handle exported, copied or backed-up files separately. We cannot remotely delete this local data for you.

Outbound probing. The external reachability checks in the device audit are disabled by default. If enabled, the device itself makes outbound connections, and the destination receives the network information needed for those connections.

Exported files. Audit reports, network maps and copied output result from your actions and may contain RouterOS configuration, device identifiers or secrets in command output. Identifier replacement on export is string substitution, not a guarantee of anonymity.

5. The AI assistant

The AI assistant is optional. The following applies only when you set it up and send a question.

Data goes only to the AI service you configure. RosRunner has no built-in AI endpoint and no default service: you enter the Base URL of the service yourself in an AI connection profile. When you send, the application transmits the request directly from your computer to that endpoint. We do not receive, relay or store it. The AI service is a separate provider chosen by you, and its own terms and privacy policy govern how it processes what it receives. If the endpoint is a model running on your own computer, the data stays on that computer. This feature contains no telemetry either.

What is sent. Your question, the earlier part of the conversation and, if you choose to attach it, a configuration export snapshot of one device limited to the sections you tick. The snapshot is either fetched read-only from the device with /export or loaded from a .rsc file you choose. As with any network request, the service also receives your IP address and technical request data, together with the API key and any headers you configured.

What is redacted, and what is not. Before sending, the values of password, secret and key-type fields, the serial number and the software id are replaced with ***. IP and MAC addresses, device names (identity), comments and user names are sent as-is, and redaction by field name cannot recognise every secret. The reference material is therefore not anonymised and may contain personal data, such as names in comments or user names; decide what to attach accordingly.

Before sending. The first time you send, a notice explains where the data goes, what is included and what is redacted. The summary line above Send shows the destination host every time, and Preview shows the full text to be sent, without the API key or headers.

API keys. Keys are stored only in the operating system’s credential store (Credential Manager on Windows); if it is unavailable, a key is held in memory for the current session only. Profile metadata is stored in %LocalAppData%/RosRunner/ai-profiles.json without keys; values entered as extra headers or extra request fields (JSON) are stored there in plain text, so neither is a place for keys or other secrets. Deleting a profile also removes its key.

Conversations are not stored. Conversations and reference snapshots are held in memory only while the window is open; the application does not save them to its data folder. Activity breadcrumbs for AI requests record only the kind of request, the HTTP status, duration, byte count and outcome — not host names, URLs, model names, keys or content. A conversation is written to a file only when you choose Export conversation; that file contains the profile name but not its URL or key.

6. Update service data

The installed and portable editions check for versions through update.rosrunner.com; the installed edition also downloads update packages through that service. Requests use release-feed or package file paths. The current implementation adds no statistical query parameters such as a device identifier or installed version, and does not upload device lists, passwords, commands or output through update requests.

The update service uses Cloudflare delivery and storage services. To deliver updates, prevent abuse and diagnose transfer problems, providers process source IP addresses, request times, file paths and necessary HTTP information. Package filenames can indicate the version or platform being downloaded. This necessary processing is distinct from product usage telemetry; log retention depends on service settings and provider policies.

The portable edition notifies you of updates for you to download. Opening the download page launches your default browser. Blocking connections to the update service may prevent version checks or update downloads.

The Microsoft Store edition is updated through the Store. The edition installed from Microsoft Store does not connect to update.rosrunner.com. Checking for, downloading and installing new versions all go through Microsoft Store — the in-app "Check for updates" and "Download" buttons ask the Store too — and the Store's own automatic updates keep working as usual. Data the Store processes when downloading, installing and updating apps is Microsoft's responsibility under the Microsoft Privacy Statement. Microsoft may also provide publishers with reports on acquisitions, installs and crashes under its own policies; that data is collected by Microsoft according to your Windows and Store settings, and the application itself adds no telemetry. We use these reports only to understand distribution and to troubleshoot problems.

6a. Licensing service and IP location database downloads

Licensing service. When you enter a serial number in the application to activate it, the application connects to license.rosrunner.com and sends the serial number, the public part of a device key generated on this computer (used to bind the licence to this computer), the operating system type, and an optional computer name you provide (up to 64 characters). Later validation, redemption of add-on serial numbers and deactivation send only the activation identifier obtained at activation. The service processes technical data needed to complete the request, such as the IP address and the time of the request.

The licensing service does not receive your device list, RouterOS credentials, commands or command output. The private part of the device key is stored only on your computer (in the operating system’s credential store; on Windows a fallback key is additionally protected with DPAPI), and the licence cache is not included in list exports or diagnostic packages. Without an activated licence, the application runs as the free edition. The legal basis is performance of the licence agreement between you and us.

IP location database. The connection map ships with DB-IP country and organization data. Only when you press Check for updates or download city data in the application does it connect to download.db-ip.com to download the public data files; the request contains no connection records or remote IP addresses. The downloaded data is provided by DB-IP under CC BY 4.0, and that site’s privacy policy governs how it handles technical connection data.

7. Recipients, locations and security

We and providers of website hosting, update delivery and email services process relevant data through network transmission, electronic storage and access as needed to deliver the services described above. Processing may occur in Taiwan and other regions where providers operate or use infrastructure; a domain we own does not mean data is processed only in Taiwan.

We use or disclose data only as necessary to respond to requests, deliver these services, meet legal obligations or lawfully address specific disputes. Disclosures required by supervisory or judicial authorities are limited to what is necessary. Cross-border processing and the use of providers must comply with applicable law; provider policies do not replace our legal responsibilities.

We are responsible for appropriate safeguards proportionate to the nature and risks of the data and for limiting access to what is necessary. We will handle personal data incidents, notifications and regulatory reports as required by applicable law. No transmission or storage method can guarantee absolute security.

8. Your rights

Under Article 3 of Taiwan’s Personal Data Protection Act, you may request access to, review or a copy of personal data we hold about you, supplementation or correction, cessation of collection, processing or use, and deletion. This policy does not restrict rights that cannot lawfully be waived in advance or limited by agreement.

Write to [email protected] describing your request and information that helps identify the relevant correspondence. We may ask for evidence necessary to verify your identity, but not unrelated information. You may also complain to the competent supervisory authority.

Under Article 13 of that Act, we decide access, review or copy requests within 15 days of receipt, extendable by up to 15 days when necessary. Requests for supplementation, correction, cessation of processing or use, or deletion under the applicable provisions of Articles 3 and 11 are decided within 30 days, extendable by up to 30 days when necessary. We will notify you in writing of the reasons for an extension and explain any lawful refusal to comply in full.

If applicable law where you are provides additional rights or different deadlines, we will comply. Where processing relies on consent, you may withdraw it without affecting processing lawfully carried out before withdrawal.

9. Changes and language versions

Revisions will be published here with their effective date. Material changes to processing purposes or scope will be identified, with legally required notice before they apply. Where consent is required, we will obtain it separately; continued browsing will not be treated as consent to new uses of data.

Before introducing analytics or other data-collecting components, we will explain the service, data, purposes and relevant choices and complete any legally required procedures.

This policy is available in Traditional Chinese, English, Japanese, Spanish and Brazilian Portuguese, with the same intended meaning. Please contact us to clarify and correct translation discrepancies. No language version limits your rights under applicable law.

Questions about data handling?

Any question about this policy or about your personal data can be sent by email.