Terms of Service

LABEL CREATOR AND CHROME PLUGIN — FIRST-PARTY STATISTICS PRIVACY NOTICE

Version 2026-11-01.3 — 1 November 2026

1. Scope and controller

This notice covers only SiltaTek's Label Creator for Windows and Label Creator Chrome Plugin, not SiltaFlow. The programs are free and proprietary. Controller: Martone Fabio, private individual, Via del Carrara 43, 55010 Capannori (LU), Italy; Italian tax code MRTFBA93P01G491B. Privacy and rights contact: info@siltatek.com. Licence and terms are available in the program and at https://www.siltatek.com/terms.html; the website notice is at https://www.siltatek.com/privacy.html.

2. Licence, information and lawful basis

Accepting the licence governs software use. The acknowledgement box records presentation of this notice: it is not consent to processing, does not certify reading or understanding and does not waive your rights.

These statistics form part of the program's standard model and start after the notice is presented and acknowledged. They are not offered through optional consent or an ordinary opt-out switch. The GDPR basis is the legitimate interest in understanding adoption and use to maintain and improve the product for everyone (Article 6(1)(f)), balanced against your rights and limited by the safeguards below. Free use is not an exemption from data protection. We do not claim a legal obligation to provide statistics or that they are indispensable to perform the contract.

For storage and access on the device, the controller adopts the Italian classification of exclusively first-party analytics for aggregate statistical processing, within Section 122 of the Italian Privacy Code and the Garante's guidance. This is not specific authorisation of these programs by the Garante. Acknowledgement does not replace any consent required by applicable law. Your right to object remains available as explained in section 7.

3. Purpose and data

We measure observed profiles over 1, 7 and 30 days and individual months, version adoption and feature use to allocate time to maintenance, compatibility and general development. We collect UTC day, product, observed version and a technical sequence to order late submissions; interactive or automatic presence and features used that day; interface language and broad OS/browser categories, including browser major version. We do not record the precise sequence of actions.

Counters cover launches/openings, saves, PDFs, print requests and jobs, outcomes and quantities submitted to the printing system, sources/modes, connector families, APIs, scheduled tasks/imports and manual or automatic PLU operations. Plugin counts cover openings, requested searches and outcomes, PDF/printing and communications. Where available, we count active or idle foreground duration without recording keys, contents or other applications. Environment categories support distinct-profile distributions and compatibility/language priorities. Profiles and submitted jobs do not equal people, unique PCs or certified physical prints; offline use, pauses, resets and missed submissions limit coverage.

4. Code, separation and excluded data

After acknowledgement, a random UUID is created for the individual product's Windows or Chrome profile; it is not derived from hardware. It recognises the same profile for distinct counts. The server transforms it using HMAC-SHA256 with a dedicated key and separation by product; the original UUID is not retained. These are pseudonymous data, not an anonymous flow.

Counters are stored without a profile identifier. Daily presence, version, modes, feature mask and environment categories remain linked to the pseudonym within the intermediate window to calculate statistics of distinct profiles; this is not an annual individual history. Dashboards and CSV files show aggregates without ordinary browsing of individual profiles. Authorised technical personnel may access intermediate data when necessary for operation, security and rights requests.

We do not collect geolocation, hardware fingerprints, accounts, user/PC/printer/file/project names, visited URLs or Odoo addresses, credentials, queries, business records, labels, barcodes, PLU values, typed text, keystrokes or full errors. We do not use the data for advertising, sales, links between products or with customer records, individual worker assessment, personalisation, individual prices/offers or automated decisions with legal or similarly significant effects.

5. Sending and retention

Local summaries are sent over HTTPS normally every 60 minutes with a short random delay; pending submissions may resume on restart. Offline use and sending failures do not interrupt work or repeat printing. Queue: at most 7 days and 1 MB, with excess deleted. We do not retain original POST bodies or put identifiers in application logs, URLs or exports.

Pseudonymous details: at most 45 UTC calendar days measured from the observed day, without renewal for late arrival. The operational limit covers windows up to 30 days, queue delays up to 7 and monthly closing from day 8 of the following month; it is a limited-margin ceiling subject to review. Inactive profile and minimal notice receipt: 45 days from last receipt. The receipt includes version, client-declared acknowledgement date, language and first server receipt; it does not prove understanding. Aggregates without ID: 13 months for monthly and seasonal comparisons. Deduplication: 14 days. After erasure, a minimal resend-blocking reference: 14 days; rights-related suspension lasts as necessary to handle that request and does not automatically end after those 14 days.

Separate temporary application security data: logical expiry after 1 hour and removal by the cycle scheduled every 10 minutes, normally about 60–70 minutes. Aruba MySQL backups: daily, retained 7 days, not used for analysis. Restoration must reapply erasures, suspensions and expiry rules. Website storage backup is separate and excludes MySQL. The local receipt and code remain while you retain the relevant state, including during a pause, for reference and rights requests.

Remote blocks for objection or restriction are kept separately with the HMAC reference, request category and technical dates. They remain until the case is closed, subject to review, solely to respect your rights. They do not contain the correspondence text.

6. Recipients, network and transfers

The controller and authorised persons have access; Aruba S.p.A. hosts the service in Italy as processor within its assigned remit, and authorities may receive data as required by law. The provider may carry out separate infrastructure processing under the applicable roles. We do not disclose metrics to advertising services or third parties for their own analytical purposes.

IP addresses are not retained in analytical tables. They are visible on connection; provider network, access, error and protection logs are separate from our one-hour expiry. The plan's actual HTTP/IP log duration is unverified: criteria are time necessary for operation, security, incidents and relevant obligations. We claim neither zero IP processing nor an invented duration. Separate application security relies on the legitimate interest in protecting the service. The absence of all access or processing outside the EEA has not been verified; ask the controller about recipients and any applicable safeguards.

7. Objection and pausing during a request

You may object at any time, on grounds relating to your particular situation, to processing based on legitimate interests (Article 21(1) GDPR). Write to info@siltatek.com with the product, privacy code if available and reasons for your request. View and copy the code in settings; do not publish it. You may contact us without it; we do not require hardware identifiers for statistical convenience and will explain any limits in locating your profile.

To make a request, you can pause local collection and sending in the privacy area: the pause stops new data, empties the queue and cancels submissions in progress where possible. It persists across restarts; no feature is automatically removed because you pause or exercise rights. Pausing does not itself send email or a request to the server, nor recall submissions already received. Contact the controller to address remote data. Your code remains available.

Once we receive a request that can be linked to the profile, we suspend linked analysis while reviewing it and handle any applicable restriction. We stop unless we demonstrate compelling legitimate grounds overriding your interests, rights and freedoms, or grounds for establishing, exercising or defending legal claims; accepting the licence alone does not demonstrate this. We give a reasoned outcome and carry out any required erasure. Neither restart nor a new acknowledgement automatically resumes a pause. Aggregates already genuinely no longer attributable may remain until expiry.

Uninstalling the app or plugin does not guarantee an automatic erasure instruction to the server, especially while offline. Remote details follow the stated expiry rules or an earlier request for erasure where required; aggregates already no longer attributable remain until expiry. If you want to request erasure after removal, retain the code beforehand if available. You may also contact us without a code.

Resuming cancels only the local pause you set. It does not automatically withdraw an objection or other request sent to the controller, waive rights or override a remote block. If a request is pending, await its outcome or contact the controller. Resuming requires explicit confirmation and acknowledgement of the current notice.

8. Other rights and response

You may request access, rectification, erasure and restriction where provided by law; portability applies only when its conditions are met, which do not follow from legitimate interest alone for these statistics. You may complain to the Italian Garante or the competent supervisory authority and seek a judicial remedy. We respond without undue delay, normally within one month; a permitted extension of two further months is explained within the first month. Information you provide for rights requests is handled in a separate case for the request and as strictly necessary for obligations and legal rights, reviewed on closure; it is not used in statistics.

9. Access and changes

The notice, version, language, acknowledgement date, state and code are available offline. Restarting or changing language does not renew a legal choice or cancel a suspension. Before material changes to purposes, data or recipients, we reassess the lawful basis and conditions for device access and update the notice; where consent is necessary, we obtain it before new collection. Previous consents remain separate and are not retrospectively converted to another basis.