This policy explains how SaliMek Manager, its native messaging host, and SaliMek Download Manager handle information needed to discover file and media links and manage downloads on your device. The responsible publisher is Ahmed Abu Mecca.
Information processed
- Page, file, media, and network-resource URLs needed for download detection, page titles, and filenames. Source URLs may include query parameters or temporary access tokens supplied by the source website.
- Tab and frame identifiers, media-detection timestamps, and response information such as content type and download disposition, to associate resources with their page and identify final download URLs after redirects.
- Selected request headers:
Referer,Origin, andUser-Agent, to allow media requests with the necessary page context. - Extension preferences, including automatic download capture, and the result of the latest connection or handoff. The desktop application also retains download information such as URL, filename, destination, size, progress, and status.
The extension does not require a personal account or query Chrome's browsing-history database. It does not intentionally collect passwords, form contents, messages, or payment information, and does not copy complete browser Cookie or Authorization headers; the limited GoFile exception is described below. The extension contains no advertising, usage-analytics, or marketing-tracking tools.
Purposes
Information is used to detect downloadable resources, display media links and download buttons, hand download requests to the application installed on your device, show available download choices, and check the connection. When automatic capture is enabled, a browser download may be paused and then cancelled after the local application accepts its URL, to avoid duplicate downloads. If handoff fails, the extension attempts to resume the browser download.
Storage, processing, and recipients
Extension preferences and cached information are stored locally in your browser profile. Download requests are passed to the native messaging host and SaliMek desktop application on the same device through Native Messaging. The application's local database retains pending requests, download records, and necessary request context.
The extension does not transmit your browsing data or download links to a publisher-operated server or VPS. When checking a link or downloading a file, the desktop application contacts the source website and its media or redirect servers. Those destinations receive your IP address and the information needed to fulfil the request, including the selected page-context headers where needed. Their handling of information is governed by their own policies. Source connections use HTTPS when the URL and source support it.
Data is not sold, used for advertising or marketing profiles, or used to determine creditworthiness. Its use is limited to the download-management functions and optional statistics described here.
Retention, controls, and deletion
The extension keeps a limited local list of discovered media per tab. A tab's list is removed when the tab closes or starts loading another page; stale entries are evicted during subsequent cache updates, rather than by a guaranteed background timer. Preferences and the latest handoff result remain until extension data is cleared. The desktop application's download records remain until the user removes them through the application or clears its local data.
You may disable automatic capture in the extension popup, restrict site access through Chrome settings, or disable or uninstall the extension. Disabling automatic capture alone does not stop media detection on permitted pages. Disable or uninstall the extension to stop all extension activity. Uninstalling the extension does not automatically remove downloaded files or the desktop application's database.
Permissions
Site access enables media detection and download buttons; webRequest identifies resources and request context; tabs associates them with tabs; downloads supports browser-to-application handoff; contextMenus adds right-click actions; storage keeps local preferences and caches; and nativeMessaging communicates with the local application.
This page, contact, and updates
This page has no data-collection forms, tracking tools, or third-party fonts or scripts. A locally hosted script provides navigation and website interface behavior. Its hosting provider may process normal access logs such as IP address, request time, and browser type for website operation and security. No analytics tools are embedded in this page.
For privacy questions, contact Ahmed Abu Mecca at [email protected]. Do not send private download URLs, access tokens, or sensitive details in public reviews. We update the date of this policy when our functionality or data practices change.
Limited Use
SaliMek Manager uses information only to provide the download-management features described in this policy, in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements. Information is not sold or used for personalized advertising, marketing profiles, or unrelated purposes. The publisher has no server receiving your download history and does not have remote access to read it. If you voluntarily contact support, the publisher receives only the information you choose to include in your message.
The product page includes optional developer support. When its PayPal section becomes visible, the official button loads from PayPal, which may process your IP address and browser information under its privacy policy. InstaPay links open the InstaPay service. SaliMek does not receive card details or payment passwords; payment does not take place inside the application.
GoFile download session
When you start an HTTPS download from file-*.gofile.io, the extension may pass the observed accountToken for that exact URL/tab to the local Windows app. It never copies unrelated-site cookies or complete Cookie headers, and never stores the token in extension storage. The app encrypts authorization for the Windows account outside download history and statistics, with a 30-minute lifetime. Expired entries are cleaned on access/insertion and the entry is deleted after successful saving. A host-only secure cookie is sent only to the same HTTPS host and /download/web/ path, never to SaliMek or a different redirect host. Without a suitable session the browser download is preserved.
Telegram account
The optional Telegram feature connects directly to Telegram using your API ID, API Hash and account. Application credentials and the session are encrypted locally for your Windows account and are never sent to the SaliMek website. Login codes and two-step passwords are not saved. Message links and filenames remain in local download history. Sign out revokes the session and removes the local account file; you can also revoke it in Telegram device settings. Content-saving restrictions are respected.
Optional desktop usage statistics
From 2.28.17, only after explicit revocable consent in Settings, the desktop app may send a random installation identifier and app version daily over HTTPS to mecasoft.xyz to count active installations. Reports contain no device names, filenames, download URLs or browsing history. The service stores an identifier hash, UTC activity dates and version; records expire 90 days after last activity. Hosting may keep separate connection logs. Opting out stops new reports and clears the local identifier; an already in-flight request may finish. Downloads and updates never require participation. The extension itself sends no usage analytics. The product-page counter records requests when its download button is clicked, without using the installation ID. It does not count unique people or completed transfers, and excludes direct links and app updates.
Optional WE allowance account
When linked, SaliMek opens the official my.te.eg site over HTTPS in a separate WebView profile. Passwords and sign-in codes are entered directly to WE; SaliMek does not read them or send them to MecaSoft. The app reads only the fixed home Internet allowance fields from the account page response, then stores total, used and remaining GB encrypted for the local Windows account. Account identifiers and session tokens are not saved in SaliMek settings. Disconnect removes the local WE session and cached allowance; it does not affect the customer's WE account.