Aspis Share Privacy Policy
Last updated: 20 October 2026
TMG LTD develops Aspis Share, an application for transferring selected files between authorized Personal and Work profiles and processing files through an organization's configured security scanner. This Privacy Policy explains how Aspis Share handles personal information and how to contact us.
Privacy contact: dev@tmgltd.co.il
1. Your organization and TMG LTD
Aspis Share normally connects to a server selected and operated by your organization. Your organization determines who can register, which scanner is used, transfer policies, server location, retention settings and administrator access. Its privacy notices and policies also apply to that deployment.
Developing the software does not by itself give TMG LTD access to every customer's server or files. TMG LTD processes deployment data when it operates the relevant service, such as a TMG-hosted demonstration, or receives information through an authorized support arrangement. Your organization can identify the operator and providers for your installation.
Contact your organization's administrator about its processing of your information. You can also contact TMG LTD using the address above, including when TMG LTD operates your service or you need help identifying the appropriate contact. The respective legal responsibilities of TMG LTD and your organization depend on the deployment, applicable law and their agreement.
2. Information processed by Aspis Share
Files you choose to send
Aspis Share accesses files that you select through Android's file picker or explicitly share with the app. These may include documents, photos, videos, audio, archives and exported contact or calendar files. A file may contain personal or sensitive information about you or other people.
The selected file is uploaded to the configured server for scanning, policy enforcement and delivery to the authorized recipient profile. Depending on the scanner and policy, it may be allowed, blocked, sanitized or otherwise processed. File contents are accessible to the server and scanner as needed for this processing.
The app does not automatically upload your entire storage, photo library, address book or calendar. Selecting an exported contact or calendar file can nevertheless transmit the information contained in that file.
File and transfer information
The service processes file names, content types, sizes, cryptographic hashes, transfer identifiers, sender and destination profiles, timestamps, delivery status, scanner policies and results, and related error or audit information. Transfer records may contain snapshots of registration details, including sender email, device model and Android ID. Processed output files have their own associated metadata.
Registration and device information
To authorize and link app instances, Aspis Share processes installation, registration, app-instance and profile identifiers; authentication and enrollment credentials; and configuration information. Registration metadata may include an email address supplied through managed configuration, device model, Android ID, and a device serial number when supplied by the organization.
The app uses the information available to its configuration and profile. It does not require access to your email inbox to use the configured email address. Your organization's administrator can view registration and transfer information in the administration console.
Notifications, connections and diagnostics
When push notifications are configured, Aspis Share uses Google Firebase Cloud Messaging (FCM). Firebase installation identifiers and push registration tokens support message delivery. Aspis sends synchronization or authorization-change signals through FCM; transferred file contents are not included in these push messages. The app retrieves transfer information and files from the configured Aspis server.
Connecting to the server or a service provider exposes network information such as an IP address. Server and infrastructure logs may record connection details, timestamps and errors, depending on the operator's configuration.
Aspis Share maintains local technical diagnostic records for troubleshooting. Its local ACRA crash-capture integration does not automatically send crash reports to TMG LTD. If you explicitly export and provide a diagnostic package to support, the recipient processes the technical information in that package and any other information you choose to provide.
3. Why information is processed
Information is processed to:
register devices and app instances, authenticate requests and maintain authorized profile links;
upload, scan, sanitize where supported, and deliver selected files;
enforce transfer policies, protect the service and maintain security and transfer records;
notify app instances about transfers and authorization changes;
apply storage and retention settings and administer the deployment; and
investigate problems and respond to support or privacy requests.
Aspis Share does not use transferred file contents for advertising, advertising profiles or personalization. The app does not include an advertising feature. TMG LTD does not sell personal information processed through Aspis Share.
4. Who may receive information
Information may be processed by the following parties as needed for the deployment:
Your organization's service operator and authorized administrators. They operate the server and manage registrations, policies and transfer records.
The configured security scanner and its operator. Supported connectors include OPSWAT MetaDefender and Sasa GateScanner. A scanner may be operated within your organization's infrastructure or by a separate provider. The selected files and scanning metadata are sent to that scanner. Its processing, any further analysis or downstream services, and retention depend on the selected product, configuration and applicable provider terms. Ask your administrator which scanner and terms apply.
Google/Firebase. When FCM is enabled, Google processes identifiers and technical information needed to provide its messaging service. See Privacy and Security in Firebase and Google's Privacy Policy.
Configured hosting, infrastructure and email providers. These providers may process data required to operate the deployment. If administrator email notifications are enabled, notifications can contain file names, sender email, device model, file sizes and hashes, transfer direction, timestamps and scan results. The built-in notification does not attach the transferred file or a file download link. Email providers and configured recipients receive the notification metadata.
Authorized support recipients. They receive information that you or your organization provide for support.
A downloaded file can also be opened or shared with another app through an action you initiate. The receiving app's handling of that copy is governed by its own terms and privacy practices.
TMG LTD may disclose information it holds when legally required or as necessary to protect legal rights and the security of the service, subject to applicable law. This statement does not give TMG LTD access to a customer-controlled deployment it cannot otherwise access.
5. Security
Aspis Share uses HTTPS/TLS for communications with its server and supported scanner connections. The Aspis backend encrypts stored file content, and the Android app uses Android Keystore-backed protections for credentials and its protected transfer storage. Registration, metadata, infrastructure and database protection also depend on how the operator configures and secures the deployment.
Aspis Share is not end-to-end encrypted against the server or scanner: those components must be able to process the selected content. Security scanning also does not guarantee that a file is harmless.
Once a file is saved to a destination chosen by the user or opened in another app, that copy is subject to the destination's access controls and retention. No security measure can eliminate every risk.
6. Retention and deletion
Server-side original and processed files are subject to configured retention deadlines and cleanup. They are not processed solely in memory. Downloading a file does not necessarily erase every server-side copy immediately.
Transfer history, registration information and security or administrative records have retention rules separate from file contents. Device revocation invalidates access credentials but does not itself erase retained registration or transfer history. Uninstalling the app or removing a profile does not by itself request deletion of server-side records. Files saved outside the app and diagnostic packages provided to support are separate copies.
Your organization determines the applicable retention periods for its deployment. Ask its administrator for those periods and the treatment of scanner copies, logs, email notifications and backups. These may have separate retention schedules. For a TMG-operated service or information supplied directly to TMG LTD, contact dev@tmgltd.co.il for the applicable retention and deletion arrangements.
To request access, correction or deletion, contact your organization's administrator or email dev@tmgltd.co.il, identifying Aspis Share and the organization or server you use. Do not email passwords, enrollment tokens, private keys or file contents to identify your request. The responsible operator may need to verify your identity and authority before acting. Where TMG LTD does not control the deployment, it will need to direct the request to the relevant organization rather than promise deletion it cannot perform.
Applicable law may permit or require retention of particular records for security, legal obligations or legal claims. Where such records must be retained, the responsible operator should explain the reason and applicable retention criteria. Any privacy rights, including rights to object, restrict processing or complain to a supervisory authority, depend on the law that applies to you and the deployment.
7. Your choices
You choose which files to send. Aspis Share does not upload unrelated files simply because you install or open it. Sending a selected file requires transmission to the configured server and, when enabled, its scanner. Registration information needed for authorization may be required to use the service.
Android permissions and notification settings can be managed through the device settings, subject to your organization's management policies. Disabling a permission or a required service may limit the related feature. Removing a local file, declining notifications or uninstalling the app does not replace a request to delete server-side data.
8. Processing locations
The server and scanner locations depend on the deployment selected by your organization or TMG LTD. Firebase and other configured providers may process information in countries other than your own. Ask the responsible operator about the locations, providers and applicable safeguards for your deployment. We do not claim that all Aspis Share data stays on the phone, within a single country or within TMG LTD's own systems.
9. Intended users
Aspis Share is intended for authorized users of organizational file-transfer services. It is not designed or marketed as a children's service. If you believe a child has provided personal information to a TMG-operated service inappropriately, contact dev@tmgltd.co.il so the matter can be investigated.
10. Changes and contact
TMG LTD may update this Privacy Policy to reflect changes to the service or its data practices. The date above identifies the latest revision. Material changes will be communicated as required by applicable law. Organization-specific notices may be supplied separately by your administrator.
TMG LTD — Aspis Share
Privacy questions and data requests: dev@tmgltd.co.il