PrimeStay Privacy Policy
This policy describes the strict separation between PrimeStay licensing data and hotel data stored locally in the application. This release text requires legal approval before public publication.
Data Processed by the Licensing Service
- Account data: name, email, login method, password hash, verification and account status.
- Device data: generated installation identifiers, labels, platform, app version, sessions and last activity.
- Purchase and license data: plan layers, entitlement state, purchase-token hash and encrypted token envelope, renewal or expiry and Google Play verification status.
- Security and diagnostics: audit events, privacy-preserving IP hash where enabled, risk signals, failed authentication and integrity results.
Hotel Data Not Sent to Licensing
Rooms, bookings, guests, contacts, phone numbers, payments, expenses, prices, statistics, photos, attachments, local sync events and backup contents remain on user devices. Booking.com calendar import is performed directly by Android over HTTPS and stores occupancy locally.
Purpose
Server data is used only for accounts, authentication, Google Play verification, signed entitlements, device limits, security, refund or revoke processing, support and licensing reliability.
Retention and Deletion
During account deletion, identity data is anonymized after the waiting period. Sessions, installations and temporary account artifacts are removed. Minimal purchase, licensing and audit history may remain attached to the anonymized record where needed for refunds, entitlement revocation, security, legal duties and abuse prevention. Local hotel data is outside the licensing backend and is not deleted by this process.
Terms · Privacy · Refunds · Support · Account deletion