dIR Privacy Policy

Who is responsible

This policy covers dIR and its PZB-operated download, support and connected services. PZB, Prestolnica Zdravja Bled, d.o.o. (PZB d.o.o.), Ljubljanska cesta 8, 4260 Bled, Slovenia, is responsible for its own app-operation, support and commercial records. Registration number: 6305733000. VAT ID: SI74779931. For business apps, the organisation using the service can be the controller of its customer, staff or guest records; the relevant distinction is explained below.

For privacy questions, access or deletion requests, email info@pzb.si and mention dIR. You can also write to our postal address above. This app policy is separate from the pzb.si website privacy policy.

Standalone and connected records

Standalone mode stores seller settings, customers, catalogue, invoice records and output preferences on the device. Connected mode reads and writes the selected company's authoritative records through the dIR portal: account and role information, company details, customers, invoices, payments, banking, stock, production and enabled specialist workspaces. Selecting a country does not require GPS; the current connected Android data region is Slovenia.

The company using dIR normally determines why its customer, employee and financial records are processed and is their controller. PZB operates the service on its behalf under the applicable service arrangements, while remaining responsible for its own account administration, billing and support. If you are an invoiced customer, contact the invoice issuer for requests about the underlying transaction; PZB can help route a service-related request.

Permissions and optional workspaces

Internet access supports connected records and update checks. Camera access supports QR/pass scanning. Bluetooth connects an already-paired thermal printer. Notification and foreground-service permissions support active Taxi metering or the optional floating app button. Display-over-other-apps permission is requested only for that floating button; it is a device preference, not permission to read other apps' content.

Location is used by the native Taxi meter while a drive is active, including when the screen is off. Connected drives submit distance, elapsed/waiting measurements and job status to the portal; the server-confirmed fare is authoritative. The current Taxi implementation does not retain exact route coordinates after a drive. Event/parking workspaces can process pass references, admission events, parking times and number plates when the operator uses those features.

Documents, printing and support

Sharing an invoice or export gives its contents to the recipient or app you choose, such as email, a print service or a file destination. Customer PDF and payment QR links contain document-specific information. Anyone you give a usable document link to may obtain the associated document while sharing remains enabled. A payment QR is not proof that payment has occurred.

Support screenshots are off by default. When enabled and explicitly sent, the app captures its own window and submits the screenshot and diagnostic context through the authenticated support service. A screenshot may include customer, invoice or financial information visible on that screen. Standalone mode has no direct screenshot-upload route.

Connections, purposes and recipients

Downloads and update checks expose ordinary server-request information such as IP address, requested URL, app version and request time. Connected sessions use authentication data to provide authorised company access. PZB uses account and service data to fulfil the requested service, connection/support information for its legitimate interests in reliability and abuse prevention, and required commercial records to comply with law.

Data recipients depend on the company's configuration and your actions: its authorised users and accountant, infrastructure providers, document recipients, print services and the relevant fiscal or banking integration. Slovenian fiscal submissions use the company's configured FURS process. The organisation is responsible for the legal basis of its customer and staff records. PZB does not sell personal data; restricted international transfers undertaken by PZB require applicable GDPR safeguards.

Retention, security and deletion

The app disables Android automatic app backup. Local records remain until removed, app-owned storage is cleared or the app is uninstalled. Exported documents, printer output and connected portal records are separate copies. Clearing a phone is not a request to delete the company's accounting records.

Issued invoices, audit and fiscal records can be subject to mandatory retention and cannot necessarily be erased on request. The company's applicable accounting and service requirements determine those periods. Ask the company about its records or email info@pzb.si about your PZB account/support records. We identify any legal retention exception rather than promise a universal automatic purge date. Connected traffic uses HTTPS, the app rejects cleartext traffic, and server access is company/role scoped; device security and care with shared documents remain important.

Your rights and how to contact us

Under the GDPR, where applicable, you may request access, correction, deletion, restriction or portability of your personal data, and object to processing based on legitimate interests. You may withdraw consent at any time; this does not undo processing that was lawful before withdrawal.

Contact info@pzb.si with the app name and enough information to locate your records, such as the email used for a purchase, order reference or installation identifier. Do not send passwords, payment-card details or unnecessary activity files. We may ask for proportionate verification and normally respond within one month, subject to lawful extensions. We explain any records we must retain.

You can complain to Slovenia's Information Commissioner or your local data-protection authority.

Changes to this policy

The date above identifies the current policy. We will update it when app features or data handling change. A policy update alone does not authorize a new use of sensitive data: where required, the app must explain the change and request permission or consent before that processing begins.