dGost Privacy Policy

Who is responsible

This policy covers dGost 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 dGost. You can also write to our postal address above. This app policy is separate from the pzb.si website privacy policy.

Property records and responsibility

dGost processes the account/session information needed for authorised staff access and the selected tenant's reservations, calendar, guests, check-ins, invoices, messages, housekeeping/service tasks, breakfast-pass counts and wallet actions. Guest details can include name, birth date, nationality, identification-document fields, stay dates and contact information. The phone uses the property's dGost.si records rather than creating a second independent PMS database.

The accommodation provider is normally the controller of its guest, staff and booking records. PZB operates the platform on that provider's behalf under the applicable service arrangements and is responsible for its own account, commercial and support processing. A guest should contact the accommodation provider about a stay record; PZB can help identify the relevant service contact.

Camera scans and the AI-photo distinction

Camera permission is optional. In standard guest check-in, passport/ID machine-readable fields are parsed on the device; camera frames and raw MRZ lines are not uploaded or retained. Editable identity fields are shown for review before the operator creates the canonical guest-book entry. Breakfast-pass scanning discards camera frames on the device and records reservation references and admission counts.

The separately selected AI fallback sends a metadata-free one-shot document JPEG through the authenticated encrypted channel for server-side AI-assisted extraction. The image can contain highly sensitive identity information. Processing returns an unverified editable prefill; the documented flow deletes the photo after processing and does not itself create a guest or submit a report. Use this only after the required disclosure/consent and review the returned fields. Local-scanning privacy claims do not apply to this upload.

Reporting, communication and feedback

Submitting a reviewed guest entry sends identity/stay fields to the property's server records. Guest reporting to AJPES and Slovenian invoice fiscalization use the property's configured server integrations and legal obligations. Certificates and integration credentials are not copied into the app.

Choosing a WhatsApp action opens a pre-addressed conversation with the available guest phone number. The operator reviews and sends in WhatsApp; its provider processes the information under its own policy. Feedback actions can send the current app screen and optional comment to the authenticated support service and may be mirrored to the dedicated development/support channel. A screenshot may contain guest details; review the screen before sending.

Service requests, legal bases and recipients

Internet access is used for authorised property operations and pinned HTTPS update checks. Installation enrollment uses a per-device Android Keystore key and an encrypted application channel in addition to HTTPS. Server requests also expose IP address, request time and normal diagnostic information. Install-package permission supports a verified direct APK update followed by Android's installation confirmation.

For PZB's own processing, the bases are providing the requested service or contract, legitimate interests in support/reliability/security, and applicable legal obligations. The property's controller determines the bases for guest reporting, staff tasks and guest communication. Recipients depend on the action: authorised property staff, infrastructure/support providers, reporting authorities, communication providers, and the configured AI extraction service for an explicitly selected fallback. PZB does not sell personal data. Applicable safeguards are required for restricted international transfers by PZB.

Retention and deletion

Android automatic backup is disabled. Wallet records and payout IBANs are not cached on the phone by the documented native wallet workflow. Removing the app does not remove reservations, submitted guest-book entries, invoices or support records from the server.

Guest-book, fiscal, accounting and audit records may require statutory retention; the accommodation provider is responsible for its schedule and processing instructions. Contact the property for guest-record requests and info@pzb.si for app/account or support requests. We do not promise that legally required records can be immediately erased, or invent a single automatic expiry period for all data. Document-photo processing and final guest-record retention are separate stages.

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.