YOUR PRIVACY · OUR RESPONSIBILITY

ARMADA Antivirus Privacy Policy

Document revision 1.13 · November 8, 2026

Applies to ARMADA Antivirus 2.0.0. Describes scanning, account, licensing and optional email data.

Who operates the service

ADVANCED CYBER SECURITY DOO BEOGRAD - VRACAR is responsible for the personal data described here. Our address is RUDNICKA 8, Beograd (Vracar), 11000, Serbia. Contact support@acs.co.rs for privacy questions, support or requests about your data. Our company website is acs.co.rs.

Scanning stays on your device

ARMADA Antivirus scans content that Android permits it to access. You choose files and folders and control the relevant Android permissions. The app does not inspect other apps' private storage.

ARMADA analyzes files and app artifacts on your device. Scanning does not upload scanned files, their contents, original storage paths or Vault contents to ARMADA. If you request a scan summary by email, the email service receives the recipient address, a summary and any TXT report you choose to attach, as explained below. Installed-app scans inspect Android-visible base and split APKs locally. The email does not include a full installed-app inventory. Quarantine and permanent deletion are separate actions.

If you explicitly export a report, it can include item display names, app labels, package identifiers and detection details. The export excludes scanned file contents and original storage paths. Review any report before sharing it. A selected app, its provider and the recipient handle the copy you choose to share under their own policies.

Optional automatic Protection

After separate in-app disclosure and your affirmative consent, automatic Protection checks Android-visible app APK artifacts. Folder monitoring is optional and starts off. Only one folder that you explicitly select and enable is included in automatic file monitoring; no default Downloads or ARMADA app-controlled folder is included automatically. Android package-change, file-system and folder-provider signals can prompt local checks; periodic work can also reconcile the enabled accessible scopes. This is not continuous access to the whole phone or other apps' private data. Granting shared-storage access alone neither enables folder monitoring nor expands it to all shared storage.

You can turn Protection off, select or change the monitored folder, disable folder monitoring while keeping its selection, remove the selection and release its read grant, or revoke Android permissions. The Protection folder and Daily Scan selection are separate controls. Android controls background execution and when work may resume after a phone restart, so checks or notifications can be delayed or incomplete. Automatic checks do not upload scanned content, package inventories or findings.

Local app data

Local app data includes installation keys, access grants, account and session state, your selected account's verified email, preferences, scan history, quarantine metadata and threat-definition information. Protection also keeps consent and enabled-state settings, an authorized folder reference, aggregate work and recovery state, and the last completed-check time. Its recovery store does not keep a persistent package inventory or queue of package findings.

Installed-app scanning can keep a bounded, device-local cache of keyed cryptographic markers to reuse previously verified results. It does not store readable package names, paths, signer values, ordinary content hashes or an app inventory in that cache.

Automatic checks of eligible local files can also keep a bounded, device-local cache of authenticated cryptographic markers, excluded from Android backup and device transfer. It holds at most 4,096 opaque location and proof records, with timestamps, to reuse verified unchanged-file evidence. It does not store readable file names, paths, URIs, file contents, ordinary content hashes or findings, and is not uploaded. Reuse requires fresh identity and access checks and matching definitions. Evidence older than seven days is not reused; outdated records can remain until replaced or cleared, so this limit does not promise physical deletion at the exact expiry time.

The current automatic threat-warning details are held in the running app process and can be lost when it ends; separately recorded History has its own retention limits. A result of NO_THREAT_DETECTED describes the scan evidence; it is not a guarantee of safety.

Google sign-in and your original trial

Google identity tokens can also contain optional profile claims such as a name, profile-picture URL, language or organization domain. When Google includes these claims, they travel within the signed token to our service. We do not build a profile from these optional claims, download the profile picture, or retain the optional fields as account records. The verified account identifier and email are handled as described below.

When you choose Google sign-in, the app sends a Google identity token to our service to verify your account. The token contains an account identifier and verified email. We return the verified email for account display and derive a keyed pseudonymous account identifier for licensing. Pseudonymous records are still personal data.

After the applicable in-app disclosure and action, the app reads and sends ANDROID_ID over HTTPS for protected account operations. These include account verification, original-trial activation and recovery, signed-in status refreshes, account-linked subscription operations and licence authorization when you request a server email. Android scopes this identifier to your device, Android user and app signing key; it is not an IMEI, SIM identifier or advertising ID.

The raw Android ID is a transient request input. We derive a versioned keyed phone marker (HMAC), rather than retaining the raw value as a licensing database field, and associate the marker with your verified account and a separate installation public key. That association enforces the original first-phone trial and prevents repeated trial claims. It remains pseudonymous personal data, not anonymous data. We do not use it for advertising or tracking across ARMADA products, and it is not included in scan reports or email contents.

The first qualifying phone receives one original trial. Reinstalling on that phone can restore only the remaining time; a second phone does not receive that trial. A factory reset, another Android profile or a changed app signing context can affect recognition. Play Integrity helps protect eligible requests; it does not independently verify the raw ANDROID_ID supplied by the app.

You can decline Google sign-in. Access then depends on any independently available license or review access. If the available offer requires account verification, declining sign-in leaves its protected scanning and protection features unavailable; the app does not promise a separate no-sign-in offer to every user. Signing out stops use of the selected account session; it does not cancel a Google Play subscription.

Purchases and licensing

Google Play processes payments. We receive purchase tokens, product and offer identifiers, purchase relationships, timestamps and subscription status to verify access and reconcile renewals, expiry, refunds and revocations. We store purchase tokens encrypted, together with keyed lookup values and licensing records. We do not receive payment-card details or learn the payer's Gmail address from a purchase.

Protected requests also use installation public keys, signed proofs, one-use challenges, session credentials, request identifiers and, where required, transient Play Integrity tokens. Google Play rights and current private REVIEW access are handled separately from account trial eligibility. Manual/Promo activation and legacy Review access are retired in version code 86; historical licensing and revocation records remain subject to the retention rules below.

New annual subscriptions use a verified ARMADA Google account for ownership and later recovery. That selected account can differ from the Google account used by Play for billing. We send a pseudonymous account reference to Google Play with checkout and verify the returned purchase relationship on our service. We retain the minimum account-to-purchase and subscription-lineage records needed to restore that paid subscription after a reinstall or loss of the old installation key. Restoration does not create a new charge or trial.

Linking an older installation-owned purchase requires your explicit request, a verified account session, proof from the surviving original installation key and provider verification. Possession of a purchase token or email alone cannot assign ownership. If the original key is lost and no ownership link exists, automatic account recovery is unavailable. Changing the selected account does not transfer purchases between accounts.

Why we process this information

We process account and licensing information to provide the access and account functions you request and to perform the associated service contract. Our legitimate interests in securing the service and preventing repeated trials, fraud and replay attacks support the minimum account/device bindings and security records used for those purposes. We process privacy requests to respect your rights and meet applicable legal obligations. You may contact us to object to processing based on legitimate interests.

Eligibility and licensing decisions are automated using account, phone, provider and security evidence. If you believe a decision is wrong, contact support for review. An unsuccessful or unverifiable request does not establish eligibility.

Providers and locations

Our licensing service and database backups are hosted at Hetzner in Germany. Authorized administration and support are provided by our company in Serbia. Backups currently remain on the same server.

For email delivery, including optional scan-summary emails and internal account-deletion notifications, we use DreamWeb Hosting, operated by Dream Technologies Group d.o.o., Belgrade, Serbia. The ACS-owned mail.acs.co.rs domain and support@acs.co.rs address use that hosted mail service. DreamWeb describes its role for hosted email accounts in its Data Processing Agreement; see also its Privacy Policy.

DreamWeb publicly describes a main infrastructure location in Germany and geographically distributed DNS and backup infrastructure in the United Kingdom, the Netherlands and Finland. This provider-wide description does not mean every email is stored in every listed country. Its processing agreement permits subcontractors inside or outside the EU subject to the stated safeguards. Contact us for account-specific processing and transfer information.

Google provides sign-in, Play Billing, purchase verification, Play Integrity and subscription notifications. Google's own handling of account, device and payment information is described in its Privacy Policy and the applicable Play terms. Its service provider depends on your region, generally Google Ireland Limited for the EEA and Switzerland and Google LLC elsewhere. Google may process information in countries outside Germany, including the United States; see its data-transfer information. Contact us for information about arrangements applicable to your data.

The external account-deletion page loads Google's sign-in library only after you choose to verify your account. Reading this privacy page does not load that library or use analytics or advertising cookies. The deletion flow uses a short-lived security cookie to protect your request.

Network and server infrastructure may process connection information such as IP address, request time, requested address, browser information, response status and error details for delivery, troubleshooting and security. Do not put passwords or authentication tokens in support messages or web addresses.

We do not sell personal data or use account/phone bindings for advertising. The app does not include a general advertising or analytics SDK.

Google SDK diagnostics

The Google Play Billing library includes technical event reporting to Google. This can include billing operation outcomes, application and library versions, event timing, Android version and build, device model/manufacturer, network type, language, configured country, time-zone offset and SIM operator code. These technical records support operation and diagnosis of the billing integration; they are not scanned file contents or ARMADA scan results.

The library can queue diagnostic events in app-local storage for later transmission. These events are not limited to in-memory processing of a single request. Google handles the received diagnostic information under its applicable terms and privacy policy; our account-deletion process does not promise to erase every record independently held by Google.

When optional environment checks are enabled for this application in Google Play, Google also processes app activity information about apps that can capture the screen or control the device, and device information about Play Protect status. This processing belongs to the Google integrity service; it does not mean ARMADA uploads its local scan results or package inventory.

Google Play Integrity processes request and application metadata, Play licensing information and device attestation information to protect licensing requests. ARMADA receives integrity decisions and retains minimum associated security records. The application has no general advertising or audience-tracking integration; this does not mean its Google components send no technical data.

If you installed ARMADA Antivirus through Google Play, the app may check for an update when you open it. Google Play processes device metadata, the installed version of ARMADA Antivirus, and information about any installed modules and asset packs for this app to determine whether an update is available and estimate its download size. Google handles this information under its own terms and privacy policy. ARMADA does not send scanned files, scan results, or Vault contents as part of this update check.

Optional scan summary email

If you enter one recipient and tap Send for an available scan result, ARMADA sends the recipient address and a scan summary over HTTPS to its email service for delivery. The summary includes the scan type, timestamps, counts, coverage limits and definition release information. It does not list individual files or apps. A summary can report a complete, limited, cancelled, interrupted or failed scan. Reports are never sent automatically.

Attach detailed scan report is off by default. If you select it and tap Send, ARMADA also sends a TXT report. It lists recorded details for items classified as malicious, such as file display names, app labels and package identifiers for detected installed apps, available SHA-256 file hashes, detection details and recorded Vault actions. Other results appear as counts. The attachment does not contain the scanned files or their contents, original storage paths, Vault contents, a full installed-app inventory, account details or licence credentials.

ARMADA uses the recipient address, summary and any selected attachment to deliver the message you requested. We send it from support@acs.co.rs through DreamWeb's mail service at mail.acs.co.rs using authenticated TLS. DreamWeb processes the message, including any selected attachment, for delivery to your chosen recipient.

The provider may retain delivery queues, technical or security logs and any email stored in hosted mailboxes or backups under the applicable service arrangements. Its published shared-hosting backup description includes daily and weekly copies, some stored off-site; those are provider arrangements, separate from ARMADA's email-service ledger. The published processing agreement provides for deletion of processed data within at most 90 days after the hosting service ends, subject to legal retention exceptions. This is not a 90-day lifetime for each email during an active service. The recipient and their email provider may retain a delivered message independently. Contact support for the arrangements and retention periods applicable to this mail account.

Sending also verifies your existing licence. Account-linked licences use your selected existing account session, an installation-key proof, Play Integrity and the signing-scoped ANDROID_ID already described above. These authorization fields are not included in the email. Sending does not start a trial, buy or renew access.

ARMADA's email service processes the recipient address, summary and any selected attachment in memory for delivery. Its separate delivery ledger retains a random request ID, installation-key digest, a digest of the recipient and report, delivery status, time and a generic failure code for up to 24 hours. The ledger does not store the recipient address, readable report or attachment, account session or licence proof. The ledger does not control how long a mail provider or recipient keeps a copy. A digest is pseudonymous data. Restarted or uncertain requests are never automatically sent again.

On the phone, a local retry record holds a random request ID, a digest of the recipient and report, and a timestamp. It does not save the recipient or report in readable form. The retry record is valid for 24 hours and is cleared on a confirmed terminal outcome; an expired record can remain in app-private preferences until cleared or replaced. This local record is separate from the server delivery ledger and is not a promise of timed physical deletion on the phone.

Mail-server acceptance does not confirm inbox delivery. If ARMADA offers Use email app and you choose it, ARMADA passes the recipient address, summary and any selected TXT attachment to the email app you choose. You can review or cancel the message there before sending from your account. The email app, its provider and the recipient handle the message under their own policies. You can use local results and exports without sending email.

Retention and account deletion

Use the app's account-deletion control, the account-deletion page, or email support@acs.co.rs. The web flow verifies your Google account without requiring the app, its old installation key or ANDROID_ID. We may need to verify an email request before acting on it.

A submitted request is pending until an operator completes it. Our handling target is to remove eligible active account associations and sessions within 30 days of a verified request. We will explain any applicable exception or additional verification needed. You can check the request status through the authenticated flow.

  • Active account associations and sessions are kept to provide the account service, until fulfilled deletion removes them. Signing out revokes access but is not account-data deletion.
  • A minimum pseudonymous consumed-trial record remains while the one-trial offer operates, with an annual review of whether it is still needed. Deletion does not grant a new trial.
  • Purchase, minimum pseudonymous purchase-ownership and independent-license records remain where needed to service those rights, prevent reassignment to another claimant, reconcile provider events and resolve related disputes. Fulfilled account deletion deactivates active account-to-purchase associations and removes eligible sessions; provider renewals alone do not reactivate them. A later explicit, verified recovery by the same owner may re-establish the account association. Deleting the account does not cancel Google Play billing or grant a new trial.
  • Deletion decisions and completion records are retained to demonstrate fulfillment and prevent a database recovery from undoing it. They must remain available for as long as a retained backup or relevant dispute can require them.
  • Technical and security records are retained according to their troubleshooting, incident or abuse-prevention purpose and reviewed when that purpose ends. We do not promise that all such records are automatically erased at a fixed interval.
  • Database backups are retained for one year from creation with administrator-restricted access. They are compressed tar.gz archives on the same server. Compression is not encryption. Deleted data may remain in an archive until it expires; later deletion decisions must be reconciled before a restored database serves users. Backup creation and expiry are currently handled manually.

Where a specific legal obligation or dispute requires limited retention, we restrict the retained information to that purpose and explain the applicable reason when responding to your request. We do not treat every account record as subject to a blanket legal hold.

Internal account-deletion notifications

To help our staff handle privacy requests, a separate internal monitor sends new-account-deletion notifications and reminders about pending requests to our support@acs.co.rs mailbox through the DreamWeb-hosted mail service described above. These emails contain only the request reference, submission channel and time, current status and, for reminders, the time spent pending. They do not include your name, email address, Google token, phone identifier, scanned content or scan reports.

The monitor can read only this limited request metadata and cannot complete, reject or delete a request. Its separate private ledger stores request references, first-observation and baseline information, notification job identifiers, delivery states, attempt counts, generic failure reasons and timestamps. It stores no email bodies or authentication credentials. We retain this minimum operational and deduplication metadata while the notification function operates and review it when that purpose ends; this is not a promise of deletion at a fixed interval. Mailbox and provider retention remain separate, as described above. Notifications do not change the account-deletion scope, retained-record policy or Google Play billing, and an email is not proof that a deletion request has been completed.

Retention on your phone

Local History uses a 365-day age limit and caps of 100,000 scan sessions and 100,000 remediation events, with separate finding-detail and display limits. Older or excess records are removed when History maintenance runs; this is not a continuously scheduled erasure at the exact expiry time. Installed-app and automatic-check History can retain aggregate sessions without reconstructing process-only package details.

Local settings, access grants, folder references, caches and retry metadata remain under app and Android storage controls until cleared, replaced or removed as their respective functions require. Clearing app data can remove local records and access keys; uninstalling or clearing data does not delete source files outside the app, cancel billing or fulfill a server account-deletion request.

Account deletion does not delete local files, scan history or quarantine content on your phone. Manage local data in the app and Android settings. Manage subscription cancellation separately in Google Play.

Your choices and rights

You control Android permissions and selected scan locations and can sign out of the selected account. Depending on applicable law, you may request access, correction, deletion, restriction or portability of your personal data and object to processing. Contact support using the address above; we may request proportionate verification to protect your account.

You may complain to the Serbian Commissioner for Information of Public Importance and Personal Data Protection, or another data protection authority competent for your location. Exercising these rights does not require purchasing a subscription.

Material policy changes will be dated and published at this address.