Privacy Policy

Version 1.0 · August 12, 2026

 

This policy applies to No-Show Recovery for Bookings. The publisher is the entity identified in the Wix App Market listing. The Wix merchant remains responsible for customer relationships and the lawful basis for communications.

 

DATA WE PROCESS

 

Site, installation, booking, and service identifiers; Booking and Attendance dates and statuses; a Wix Contact identifier transformed into a tenant-salted hash; rules, templates, hashed consent evidence, suppressions, billing state, audit events, and aggregated outcomes. No customer name, email address, or phone number is stored in plaintext in Neon. The app does not read medical or sensitive data, use AI, or modify bookings.

 

PURPOSES

 

Show booking history and the known no-show rate; apply deterministic rules; report or cancel reminder and recovery events in Wix Automations; enforce consent, opt-out, frequency, and quota controls; measure aggregated uplift; and secure the service.

 

PROVIDERS AND LOCATION

 

Wix provides identity, Bookings, Attendance, hosting, Billing, and Automations. Neon provides PostgreSQL in the AWS Frankfurt region (eu-central-1). No AI, SMS, or external messaging provider is used.

 

RETENTION

 

Booking and Attendance facts are retained until 180 days after the booking ends. Terminal messages, receipts, and runs are retained for up to 180 days; completed outbox items for 30 days; and general audit events for 365 days. Consent and suppression records persist during installation according to their validity. Uninstall stops communications immediately and schedules deletion within 30 days by default.

 

SECURITY AND RIGHTS

 

TLS, separate roles, forced row-level security, minimal Wix permissions, idempotency, and logs without personal data protect the service. Recipients should first exercise their rights with the merchant, who can revoke consent immediately. For app-related access, objection, export, or deletion requests, use the App Market Support link with only a tenant suffix and run ID—never include booking data.

 

CHANGES

 

Any new purpose, subprocessor, or AI use requires a separate policy and release with the necessary reviews.