PremioGuard ("we", "us") operates a cloud-hosted endpoint protection and USB port-control service for Windows fleets. This notice explains what personal data the service processes, and it applies to every account: the account holder, the sub-accounts an administrator creates under it, and — where you have deployed the desktop agent — the individual computers enrolled under a licence.
For enquiries about this notice or to exercise any right described in section 11, contact us at contact@premioguard.com. Data subject requests are handled by the account administrator named on the account, and we will assist them directly where the request concerns an organisation's fleet.
We collect three distinct categories. They are separated here because they are governed differently: account data is processed to deliver the service you asked for, telemetry is processed to perform the protection function, and billing data is processed to meet a legal obligation. Section 6 sets out the basis for each.
| Category | Specific fields | Source |
|---|---|---|
| Account identity | Full name, email address, company name, job title, telephone number, country and billing address, account role. | Provided directly by you at sign-up or by your administrator. |
| Authentication | Password hash (bcrypt, never the password itself), two-factor enrolment state, second-factor method, hashed recovery codes, last sign-in timestamp, sign-in IP address. | Generated by us when you set your credentials. |
| Sub-accounts | The same identity fields, plus a permission set chosen by the account holder, and a "must change password" flag on first issue. | Created by your account administrator. |
| Licensing | Licence key, plan, seat allocation, activations, issue and expiry dates, and whether the licence was purchased or granted. | Generated by us; plan and seat count derive from your subscription. |
| Billing | Transaction reference, amount, currency, payment method type, processor reference, and the outcome of each review. We do not store full card numbers — those are held by the payment processor. | Our payment processors and, for manual or crypto methods, your administrator. |
| Support correspondence | Enquiry name, email address, subject, message body, and internal notes added while resolving it. | Provided by you via the contact or enquiry forms. |
| Server and security logs | Request metadata including IP address, timestamp, user agent, and endpoint; plus authentication outcomes and administrative actions. | Generated automatically by the application infrastructure. |
This is the most important section of this notice, because it describes data collected automatically from hardware you operate, rather than from a person who filled in a form. Every item below is transmitted by the PremioGuard desktop agent. The agent collects nothing that is not listed here, and the list is generated by the software rather than assembled by an operator.
Each enrolled computer is identified by a hardware identifier: a one-way SHA-256 digest computed on the device. The raw machine identifiers are never transmitted, and a digest cannot be reversed to recover them. This is what binds a licence to a machine without the service holding the underlying serial numbers.
When a USB device is connected, the agent reports the device's characteristics and what action was taken in respect of it. Specifically:
File contents on removable media are not transmitted. PremioGuard records that a device was connected and what was done about it. It does not read, copy, or upload the files stored on that device. The one exception is a file you have explicitly configured for transfer under a transfer policy, described in section 4.
Where your administrator has configured a transfer policy, the agent may copy a file from a permitted source to a managed destination. Copies are written to a local mirror, which serves two purposes: the destination stays available if the network drops, and a file is stored once and served to every machine that needs it, rather than being transferred repeatedly.
Mirrored content is retained for the same period as other operational data set out in section 7. Where a transfer policy is removed, content no longer referenced by an active policy is deleted on the next retention sweep.
To authenticate you, maintain your session and second-factor state, apply the permissions attached to your role, enforce your licence and seat allocation, and display the fleet information on your dashboard.
To block or permit USB devices, to detect and quarantine threats, to enforce application and file-transfer restrictions, and to keep each enrolled computer within the number of activations its licence permits.
These functions require processing the telemetry in section 3. If the agent stopped reporting that telemetry, the service would stop protecting the fleet — which is why this processing is necessary rather than discretionary.
To take payment, issue a licence, credit a wallet, and administer subscriptions including renewals and refunds. Payment card data is handled by our payment processors and never stored on our systems.
To enforce section 8 of the Terms, to rate-limit and block automated sign-in attempts, and to investigate activity suggesting an account has been compromised.
To answer enquiries, diagnose faults reported by your agents, and understand aggregate reliability. Aggregate statistics are computed across the population and are not intended to identify an individual or an individual account.
To keep accounting records, comply with lawful requests from public authorities, and enforce our own legal rights.
We do not sell personal data, and we do not use fleet telemetry for advertising. We do not use your data to build behavioural profiles for targeted marketing.
| Processing | Lawful basis |
|---|---|
| Account identity, authentication, and sub-accounts | Performance of a contract (Art. 6(1)(b)) — required to give you the service you purchased. |
| Fleet telemetry, device inventory, and enforcement records | Performance of a contract (Art. 6(1)(b)), and where the account is a business, legitimate interests (Art. 6(1)(f)) in securing the fleet. The protection function cannot be performed without this data. |
| Billing, licensing, and transaction records | Performance of a contract (Art. 6(1)(b)) and legal obligation (Art. 6(1)(c)) for accounting records. |
| Server, authentication, and security logs | Legitimate interests (Art. 6(1)(f)) in operating and defending the service. |
| Abuse detection and enforcement of the Terms | Legitimate interests (Art. 6(1)(f)) in protecting the service and other customers from misuse. |
| Support correspondence | Performance of a contract (Art. 6(1)(b)) and legitimate interests (Art. 6(1)(f)) in improving the product. |
| Direct marketing by email | Consent (Art. 6(1)(a)), which you may withdraw at any time. Service messages about your account, licence, and billing are not marketing and are sent on the basis of the contract. |
Where we rely on legitimate interests, we have considered your rights and concluded the processing is necessary and proportionate. You may object at any time (see section 11), and we will stop unless we can identify another lawful basis.
We keep personal data for as long as the account is active and for a defined period afterwards, so that billing disputes can be resolved and a reinstated account behaves as though it had never been closed. The periods below are the published retention schedule.
| Data | Retained for |
|---|---|
| Account and sub-account identity data | Life of the account, then 90 days after closure. |
| Authentication and session records | 90 days. Historical sign-in records are kept only while an investigation could still need them. |
| USB connection and block/unblock events | 90 days from the event. |
| Device connection/disconnection session records | 90 days from disconnection. |
| Security events, threats, and quarantine records | 90 days, or longer where a threat is under active investigation. |
| Application inventory and activity records | 90 days from the record. |
| File transfer records and mirrored content | 90 days from the transfer, or until the policy is removed and the next retention sweep completes. |
| Billing, payments, and wallet transactions | Seven years from the transaction, to meet statutory accounting requirements. Set by tax law, not by us. |
| Administrative audit records | 90 days, and longer where the record relates to a disputed transaction or an investigation. |
| Support enquiries and correspondence | 24 months from the last reply, so a returning customer has the history of their issue. |
| Licence and activation records | Life of the licence, then 90 days, so a reactivation can be validated after a reinstall. |
When a period ends, the data is deleted or irreversibly anonymised. Where a limited record must be kept — a transaction reference required by tax law, for instance — we restrict it to what that obligation requires and no more.
We share personal data only with the following categories of recipient:
We do not disclose fleet telemetry to advertisers, data brokers, or analytics providers. There is no advertising or cross-contextual-behavioural tracking in this product.
Our servers are located in the United Kingdom and the European Economic Area. Some recipients identified in section 8, notably email delivery and payment processing providers, may process data outside those regions. Where that happens, transfers are made under an adequacy decision where one exists, or under standard contractual clauses together with a transfer risk assessment, and with supplementary measures where those are considered necessary. A copy of the safeguards applied to a specific transfer is available on request.
No system is perfectly secure. If a breach affects your personal data and is likely to result in a risk to your rights and freedoms, we will notify the supervisory authority within 72 hours of becoming aware, and notify you without undue delay where the risk to you is high.
Subject to the conditions in the applicable law, you have the right to:
Obtain confirmation of whether we process your data, and a copy of it. Most of your data is visible to you in the dashboard already.
Have inaccurate data corrected. Account and contact fields are editable directly.
Have your data deleted, where we are not required to retain it. We cannot delete billing records we must keep for tax purposes, and will tell you which records those are.
Have processing limited while a dispute about accuracy or legitimate interests is resolved.
Receive the data you gave us in a structured, commonly used, machine-readable format.
Object to processing based on legitimate interests, and to direct marketing at any time. We will stop unless we identify another lawful basis.
Where processing relies on consent, withdraw it at any time without affecting prior processing.
Lodge a complaint with your supervisory authority. In the United Kingdom that is the Information Commissioner's Office. We would rather you raised it with us first, but that is your choice and not a precondition.
Requests are actioned within one month. We may need to verify your identity before disclosing data; where an account's fleet data is concerned, the request is normally handled by the account administrator, and we will assist them in confirming what must be released.
PremioGuard is not directed at children and is not intended for use by anyone under 16. We do not knowingly collect data from children. Fleet telemetry describes computers, not people, and a deployment that includes a personal device used by a minor should be operated in accordance with the data protection law applicable to the person operating it.
We update this policy when our processing changes. The "Last updated" date at the top of this page is the authoritative version date, and the version number identifies the specific revision. Where a change materially affects how we use your data, we will notify account administrators by email before the change takes effect. Continuing to use the service after the effective date constitutes acceptance of the revised policy.
The Terms & Conditions and the User Agreement form the contract for the service and are updated in step with this notice.