Privacy Policy

1. About this policy

This policy explains how ShareX, the Android file-sharing app developed by Akansh Sirohi, handles information when you use the app and its browser-based local web interface. ShareX lets you browse, send, receive, and manage files over a local network. This policy also explains the hosting of this privacy-policy page.

2. Information the app accesses and stores

• Files and folders: ShareX accesses files and folders available through the storage access you grant. This may include photos, videos, audio, documents, and other files. File contents and metadata, such as names, paths, types, and sizes, are processed to display, preview, upload, download, and manage files. File contents are transmitted to connected devices when you use sharing features.
• Installed applications: ShareX reads information about installed apps, including app names, package names, icons, and APK locations, to provide its app-listing and APK-sharing features. This information may be displayed to connected browsers with file-manager access. It is not sent to the developer for profiling or advertising.
• Connection information: Local network addresses, browser or device information, connection identifiers, and access decisions are used to establish connections, show access requests, and control access. If you remember a device, ShareX stores its identifier, name, approval information, and last connection time on your Android device.
• Transfer history: ShareX stores transfer records locally, including file names, paths, types, sizes, transfer direction, and dates or times. These records support the transfer-history interface.
• Settings and security information: ShareX stores your preferences, sharing configuration, plugin information and permissions, and security settings locally. If you configure a web password, the app stores a password hash and information needed to validate access sessions.
• Camera input: Camera access is used for QR-code scanning when you use that feature. ShareX does not upload camera frames to the developer.
• Diagnostic information: Operational messages and errors may appear in local app or Android logs. ShareX does not include an automatic developer-operated analytics or crash-reporting service. If you choose to submit logs or screenshots for support, the information you provide may be received by the developer and the service you use to send it.

Core file sharing does not require a ShareX account. The current app does not include advertising or analytics SDKs and does not sell personal information.

3. Android permissions

• Storage and all-files access: Allow browsing, reading, receiving, and managing files on your device. On supported Android versions, all-files access gives the app broad access to shared storage; connected devices with file-manager access may be able to browse and manage accessible files.
• Installed-app visibility: Allows ShareX to list installed applications and support APK sharing.
• Camera: Allows QR-code scanning.
• Network and Wi-Fi access: Allows the local server and connected browsers to communicate, checks network availability, and supports downloads such as the plugin catalog.
• Notifications and foreground service: Allow ShareX to show sharing status and keep the local server running while sharing is active.
• Battery-optimization exemption: Helps keep sharing available in the background if you choose to allow it.

You can manage permissions and special access in Android Settings. Withholding or revoking a permission may prevent the related feature from working.

4. How information is used and shared

ShareX uses information to provide the features you use: local file access and transfers, application sharing, connection approval, remembered devices, security controls, history, and plugins. Local transfers go between your Android device and connected devices rather than through a ShareX cloud relay.

Devices with access to your file manager may receive file listings, previews, downloads, installed-app information, and other information exposed by the sharing interface. Depending on your settings and permissions, those devices may also upload or manage files. Stop sharing and revoke remembered access when you no longer want a device to connect. A recipient may keep copies of files already received.

The developer does not automatically receive your file contents, installed-app inventory, transfer history, or local device database through ordinary use of the core sharing features.

5. Plugins and third-party services

ShareX connects to GitHub to retrieve the plugin catalog and download plugin archives. These requests disclose standard network information to GitHub, such as your public IP address and request details, including the requested plugin. They do not require uploading your shared files or full installed-app inventory to the developer.

Plugins can provide additional browser-based functionality. Their handling of data depends on the plugin's code and features; a plugin may contact external services or process information you provide to it. Review a plugin's source, permissions, and privacy information before using it. Approval for a plugin is separate from file-manager approval.

If you open an external link, download from an external service, or submit a support request, that service's privacy policy applies to its processing. GitHub describes its practices in the GitHub General Privacy Statement.

6. Browser storage and this website

The local web interface uses browser storage and cookies for functionality such as interface preferences, device recognition, and access sessions. These mechanisms support the local service rather than advertising tracking. You can remove them using your browser's site-data controls; doing so may reset preferences or require access approval again.

This privacy-policy page contains no analytics scripts, advertising, embedded trackers, or third-party fonts. When hosted on GitHub Pages, requests are handled by GitHub, which may process visitor information such as IP addresses and request details under its own privacy statement. Visiting this page does not send your local ShareX files to GitHub.

7. Security

ShareX provides connection controls and optional password protection. Use a trusted network, approve only devices you trust, and stop the server when you finish. Access controls do not prevent a recipient from retaining files you have shared.

Transport encryption depends on your server settings. Plain HTTP connections are not encrypted. HTTPS support does not mean every connection is encrypted or that the bundled certificate provides the same assurance as a certificate uniquely issued to your device. Do not expose the local server directly to the public internet or assume that a password alone encrypts transfers.

No device, storage system, or network can be guaranteed completely secure.

8. Retention and deletion

Locally stored settings, transfer history, remembered devices, and persistent plugin permissions generally remain until you remove them using available app controls, clear ShareX's app storage, or uninstall the app. Temporary sessions and access grants have lifetimes determined by their settings and the running sharing session.

• Clear transfer history in the app to remove transfer records. Clearing history does not delete the transferred files.
• Remove remembered devices using the app's device controls to revoke remembered file-manager access. To remove all persistent local app data, including plugin permissions, clear app storage in Android Settings.
• Delete received or shared files separately using the app or a file manager. Clearing app storage or uninstalling ShareX does not necessarily delete files saved in shared storage or copies on recipient devices.
• Clear site data in your browser to remove locally stored web-interface data.

Android backup is enabled in the app. Depending on your Android version, device provider, and backup settings, app data may be included in system-managed backups or device-to-device transfers. Backup copies and restored data are governed by your backup provider and settings. The developer does not operate that backup service.

If you contact the developer, the support service may retain your messages and attachments. Contact the developer to request deletion of information you supplied; information may need to be retained to resolve an ongoing request or meet an applicable legal obligation. Third-party services control their own retention, and the developer cannot delete copies retained independently by file recipients.

9. Your choices and privacy requests

You control whether to start sharing, approve connections, remember devices, use plugins, and grant Android permissions. You can stop sharing at any time and use the deletion controls described above.

Depending on applicable law, you may have rights to access, correct, delete, restrict, or object to processing of personal information, and to complain to your local data-protection authority. Contact the developer about information you have provided directly. Information that stays only on your device can generally be managed there; the developer cannot remotely retrieve or erase it.

10. Children

ShareX's core features do not ask users to submit their age or create an account. The developer does not knowingly collect children's personal information through the core sharing features. If you believe a child has provided personal information directly to the developer, contact the developer to request its review and deletion. Parents and guardians should supervise children's file sharing and access to third-party plugins or services.

11. Changes to this policy

This policy may be updated when ShareX's features or data practices change. The latest version will be published on this page with an updated date. Where required, material changes will also be communicated through the app or another appropriate channel.

12. Contact

ShareX is developed by Akansh Sirohi. For privacy questions or requests, email akanshsirohi18@gmail.com.

Source code: github.com/akanshSirohi/ShareX. Do not post private files, passwords, or sensitive personal information in public GitHub issues.