Customer accounts
Profiles, addresses, booking preferences, messages, and payment references.
Privacy
How Reslay uses the data that keeps bookings and support in context.
Reslay uses account, booking, payment, messaging, and business-workflow data so both customer and provider experiences remain functional, traceable, and easier to support.
Provider workspaces
Business details, visibility settings, wallet activity, and payout-related records.
Support continuity
Issue history, replies, and tracking context for booking, payment, and technical problems.
Privacy in Reslay is mostly about keeping service delivery, support, and financial context attached to the right record.
Privacy Summary
The main privacy categories stay practical and product-focused.
These points combine what the customer app, provider app, and website already rely on for the platform to work well.
Account and identity details
Profile information, account details, and related images help identify users and keep customer or provider records tied to the right person.
Addresses and local discovery
Location information supports home-service bookings and helps surface relevant nearby providers.
Bookings and service context
Selected services, scheduling details, timing, and location choices are used to complete appointments accurately.
Messages, notes, and attachments
Consultation messages, booking notes, inspiration context, and related attachments are kept so the right provider, customer, or support thread retains its history.
Payment references
Reslay keeps the references and amounts needed to verify checkout and connect payments to bookings.
Support and issue tracking
Support conversations and issue records are stored so booking, payment, payout, and technical problems can be reviewed with proper context.
Notifications and preference settings
Notification choices help shape how reminders, provider replies, offers, and support updates reach the account.
Provider business and payout data
For provider accounts, business profile details, wallet activity, billing visibility, and payout records are used to run the professional side of the platform.
Readable Summary
This page is the plain-language overview, not the long-form legal document.
The website summary is meant to stay aligned with the product experience across customer and provider accounts while keeping the main promises readable.