Privacy Policy

Privacy Policy · Terms of Service · support@k2vsoftware.com

Last updated: 5 October 2026. This policy covers the current Browter desktop application, its website at https://browter.k2vsoftware.com, and communications with its publisher. Website hosting and analytics retention details are displayed alongside this policy.

1. Publisher and scope

Browter is developed and published by an independent software developer based in Sri Lanka, operating under the trading name K2V Software Solutions ("we", "us", or "our"). K2V Software Solutions is a publishing/trading name, not a separately registered company. Privacy questions and requests can be sent to support@k2vsoftware.com.

This policy distinguishes information processed locally by the app from information that we or website providers may receive. Microsoft, browser vendors, destination websites, and your email provider have their own data practices and policies.

2. Our approach to desktop privacy

Browter is a local browser/profile chooser, not a hosted browsing service. It does not require a Browter account and has no publisher-operated backend for link routing. The app does not upload your links, recent-link history, settings, delivery records, or diagnostic files to us. It does not include Google Analytics, advertising trackers, or automatic crash-report uploads.

Local processing can still involve personal or confidential information. URLs, profile labels, executable paths, and website hosts can reveal information about you. Other parties receive information when, for example, the selected browser opens a destination, Windows performs Store operations, you copy a link to the clipboard, or you choose to share a file.

3. Information processed by the desktop app

Links and browser launches

Browter receives the address or local HTML-file path that Windows or another application asks it to open. It validates the request and passes the original address to the selected or fallback browser. That browser and the destination may then process the address, network information, and their own cookies/accounts. Browter does not fetch or render the destination webpage itself.

Browser discovery and settings

The app reads local Windows browser-registration information and supported browsers' profile metadata to identify installed browsers and profiles. It uses names, profile-directory identifiers, executable locations, and launch arguments to build your choices. It does not read browser passwords, cookie databases, or browsing-history databases for this purpose.

Saved settings can include browser/profile entries and labels, executable/profile paths, launch arguments, fallback choices, shortcuts, appearance, startup and gaming-mode preferences, and recent-link/logging preferences. Settings exports and recovery copies can contain those details. Exports are saved where you choose and are not automatically sent to us.

Input and foreground context

Windows services detect the configured shortcut, handle selection keys/pointer interactions, and determine foreground/full-screen state for relevant features. A link handoff can include the source process name and foreground window title in memory. Window titles are not written to Browter's delivery records, ordinary logs, verbose logs, or crash reports. Source process names can appear in opted-in verbose routing records. Browter does not create a stored record of ordinary typed text or send keyboard/pointer events to us.

Optional recent links

Recent links contain the full address, selected browser entry, and time opened. You can retain the last 10, 20, or 50 entries, or turn the feature Off; the default is 20. Retention is count-limited rather than a fixed number of days. Reopening sends the address to your selected browser. Copying makes it available on the Windows clipboard.

Delivery and crash recovery

The local delivery directory stores the original address while opening is unfinished or its outcome is uncertain. This recovery storage operates even when Recent links is Off. It enables recovery after interruption. Source process names and window titles are not stored in these records.

Completed requests remove the original address and retain a request identity, address hash, and delivery state to suppress duplicate retries. If a launch outcome is uncertain, Browter may preserve the address, copy it to the clipboard, and ask you to check the browser before retrying; it does not automatically retry an ambiguous launch. These records are not uploaded. Local hashes/identifiers are not a claim that records are anonymous.

Diagnostics and crash files

Ordinary diagnostics can contain event types, reasons, browser-entry labels, timings, request identifiers, exception types/method names, and an address's scheme and host. They omit address credentials, paths, queries, and fragments; local-file addresses are represented as file:. Hosts and entry labels can themselves be sensitive.

Opting into verbose logging allows full addresses and source process names in local Debug records. Settings enables verbose logging for 15 minutes; diagnostic writes reject an expiry more than 24 hours ahead. Crash files contain app/Windows versions, exception types/method names, and up to 50 redacted diagnostic records. They omit exception messages, source paths, foreground titles, and full addresses from verbose records. No diagnostic or crash file is sent automatically.

Store entitlement

The app reads entitlement through Windows' Microsoft Store APIs and caches status, such as purchased/trial/inactive and a trial expiry where supplied. Purchases use Microsoft's interface. Browter does not collect your payment-card details or Microsoft account password. Microsoft separately handles account, device, licensing, purchase, and update information under the Microsoft Privacy Statement. Publisher-accessible Store reports are separate from local app link records.

4. Local retention and deletion

• Settings/license cache: remain until changed, replaced, or removed with local app data. Resetting settings is not complete privacy-data deletion and is designed to preserve the license. Exports, recovery copies, and your own backups can remain separately.
• Recent links: older entries are replaced when the chosen count is exceeded. Clear recent links deletes the stored list; switching Off deletes it and stops recording history. Neither action deletes delivery records, diagnostics, browser history, or clipboard contents.
• Completed delivery receipts: become eligible for deletion after 15 minutes. Cleanup runs at startup and during link activity, so eligible records can remain while the app is idle or closed.
• Pending/uncertain deliveries: remain until recovery is resolved or you delete the delivery directory. Failed-write temporary copies are removed when possible, with cleanup retried. Deleting unresolved records prevents recovery of those requests.
• Dated app/handler logs: retained for seven UTC calendar days, capped at 5 MiB per dated file. Cleanup runs when diagnostics are next written, rather than while the app is closed. Crash files remain until you delete them.

Use Settings → Open logs to locate diagnostics. Disable verbose logging and exit Browter before deleting log/crash files. To remove all local Browter data, exit the app and delete its local data directory, or use Windows reset/uninstall controls where available. Packaged installations use %LOCALAPPDATA%\Packages\25659K2VSoftwareSolutions.Browter_5epabrm758az8\LocalState; unpackaged installations use %LOCALAPPDATA%\Browter.

Deleting local data removes settings, recent links, recovery records, diagnostics, and the local license cache. Windows may restore Store entitlement on the next run. Deletion does not cancel a purchase or remove Microsoft records, browser/destination history, clipboard history/synchronization, exports, or backups. Normal file deletion is not a guarantee of forensic erasure.

5. Website hosting

Visiting the website sends requests to its hosting/CDN provider. That provider can process IP addresses, requested addresses/request metadata, browser/user-agent information, response status, timestamps, and security/access logs to deliver the site, prevent abuse, and troubleshoot faults. Hosting data is separate from local desktop information.

The website displays its hosting provider, provider privacy information, and hosting-log retention alongside this policy. The site currently has no support-upload form, account-registration system, embedded third-party video, or fingerprinting feature. Its demonstration uses synthetic addresses and does not submit your choices to a server. Avoid putting private information in website URL parameters; a host can receive a requested URL even where analytics strips its parameters.

6. Optional website Google Analytics

When configured, the website offers Google Analytics 4 to understand public-page visits and clicks on the configured Microsoft Store link. It is separate from the desktop app. No Google analytics tag loads before you choose Allow analytics. Rejection keeps it off; reading the site or using Browter does not require approval. Without JavaScript, this integration does not run.

After approval, Google can process public-page and Store-link click events, cookie/client identifiers, browser/device information, and network information. Page addresses sent by our integration exclude queries/fragments; referrers are blank, and only known public routes are measured. No demo selections, desktop app links, browser/profile names, diagnostics, or user-account IDs are included. Advertising storage, ad personalization, and Google signals are disabled. Automatic Enhanced Measurement is disabled for this integration.

Google states that GA4 uses IP addresses at collection time for location information and does not log or store those IP addresses in Analytics. This does not mean a request reaches Google without an IP address. See Google's Analytics data safeguards and Privacy Policy.

The browser preference is saved in local storage as browter.analytics-consent.v1 for up to 180 days. If storage is unavailable, the choice is kept for the current tab. After approval, host-only _ga and measurement-specific _ga_… cookies have a fixed 180-day expiry, rather than intentionally extending on each visit. Cookie lifetimes are distinct from retention of collected data.

Use Analytics preferences at the bottom of a page to change your choice when analytics is configured. Withdrawal disables collection and removes this integration's cookies; it cannot undo data already received by Google. Clearing site storage removes the saved choice. When analytics is enabled, the configured user/event data-retention period is displayed alongside this policy. Google's retention controls apply to relevant user/event data; standard aggregate reports are handled separately.

7. Support information

If you email us, we receive your address, message, and information/attachments you choose to provide, such as an app version, problem description, or reviewed logs. We use them to respond, investigate, and maintain necessary support records. Our email provider also processes the communication. A support request does not automatically retrieve your local files.

Review attachments before sending them. Do not send passwords, access tokens, payment-card details, or confidential client links. Correspondence is retained while handling the request and afterwards only as reasonably necessary for follow-up, documenting resolution, or applicable legal obligations. A justified legal retention requirement can prevent immediate deletion. You may request deletion at the contact address above.

8. Purposes and legal grounds

Local data enables routing, configuration, recovery, diagnostics, recent-link features, and entitlement checks. Website requests enable delivery, security, and troubleshooting; approved analytics helps improve the website; support information enables us to help you.

Where applicable law requires a legal basis for information we receive, we rely on consent for optional analytics; steps needed to answer your request or provide an agreed service for support; legitimate interests in secure operation/resolving faults where permitted and not overridden by your rights; and legal obligations where retention/disclosure is required. Analytics consent is voluntary and withdrawal does not affect prior lawful processing. Running the app does not make its local files available to the publisher.

9. Sharing and international processing

We do not sell personal information or use local app browsing records for advertising. App records are not shared with us or advertisers through telemetry. Google receives website analytics only after approval. Hosting/email providers receive information needed to provide their services. Microsoft, browsers, and destination sites process information independently when you use them.

Support information and website-provider data may be processed in Sri Lanka or other countries where providers operate. Where law requires a transfer safeguard, the relevant arrangements must be in place before activating that processing. Provider data is not necessarily stored in Sri Lanka. Consult the linked provider policies for their processing locations and safeguards.

Information actually in our possession may be disclosed where required by law, to address lawful requests, or as necessary and permitted to protect rights/security. This does not grant remote access to local app files. A change of publisher/product ownership may transfer information in our possession subject to law and appropriate notice; it does not create desktop telemetry.

10. Security

Local app files are not an encrypted vault. People or software with sufficient access to your Windows account, device, backups, or clipboard may access them. Protect your device and use appropriate account, disk-encryption, and backup controls. Keep Windows/browsers updated. No storage or transmission method is guaranteed completely secure.

11. Your choices and rights

You can inspect/delete local data using the controls and locations above, disable recent links or verbose logging, withdraw analytics consent, and choose what to send in support. We cannot remotely retrieve, correct, or delete files that remain only on your computer.

Depending on applicable law and information actually held, you may have rights to access, correction, deletion, restriction, portability, objection, and withdrawal of consent, and to complain to the relevant data-protection authority. Contact support@k2vsoftware.com. We will respond within the time required by law and may request proportionate information to verify a request. Do not send identity documents unless necessary and requested. For Sri Lankan authority information, see the Data Protection Authority; rights/procedures depend on provisions applicable at the relevant time.

Use the relevant provider's controls for records independently controlled by Microsoft, browsers, destinations, or other services. We may be unable to associate an analytics record with you without its identifier and do not collect additional desktop information just to identify it.

12. Children

Browter is a general-purpose utility and is not directed at children. We do not knowingly solicit children's personal information through the website/support. A parent/guardian who believes a child provided personal information can contact us. Local app files are not automatically available to the publisher; Store age/account requirements are separately governed by Microsoft and applicable law.

13. Changes and contact

We will update this policy and its date when practices change. Material changes receive website notice and, where required, appropriate additional notice or renewed consent before the relevant processing begins. A policy update does not itself enable app telemetry or override your analytics choice.

Publisher: independent developer trading as K2V Software Solutions, Sri Lanka. Contact: support@k2vsoftware.com. Website: browter.k2vsoftware.com. See our Terms of Service.