Sailia is designed to help you manage customer data responsibly. This page explains what data is collected, how it is stored, and the tools available to help you meet your privacy obligations.Documentation Index
Fetch the complete documentation index at: https://sailia-mintlify-docs-reorg-1776046906.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
What data Sailia collects
Sailia stores customer information needed to process bookings, manage accounts, and communicate with your customers.| Data type | Purpose | Where stored |
|---|---|---|
| Name and email | Booking confirmations, workflow emails, account login | Sailia |
| Booking history | Visible to customers and staff on the customer profile | Sailia |
| Payment details | Card numbers and payment credentials | Stripe (not stored in Sailia) |
| Membership and pass status | Tracks active subscriptions and remaining sessions | Sailia |
| Waiver responses | Signatures, checkboxes, text, and file uploads | Sailia |
| Profile images | Optional photos uploaded by customers | Sailia |
| Staff notes | Internal notes on customer profiles — not visible to customers | Sailia |
| Tracking events | Booking tracking data sent to GTM or PostHog | Third-party analytics provider |
Payment security
All card payments are processed through Stripe, which is PCI DSS Level 1 certified — the highest level of payment security certification. Sailia never stores, processes, or has access to full card numbers. When customers enter payment details:- Card data is sent directly to Stripe’s servers.
- Stripe returns a secure token that Sailia uses for the transaction.
- Recurring payments for memberships and instalment plans use Stripe’s tokenized billing.
Because Sailia never handles raw card data, your PCI compliance scope is minimized. You do not need to complete a full PCI Self-Assessment Questionnaire for using Sailia.
Customer accounts and consent
When customers create an account on your booking page, they provide their information voluntarily. Customers can:- View their data — booking history, memberships, passes, and waivers are visible in their account
- Update their details — customers can edit their name, email, and contact information
- Manage marketing preferences — subscribers can unsubscribe from marketing emails through the link included in every campaign
Guest checkout
Customers who book as guests (without creating an account) provide only the information required to complete the booking. Their details are stored against the booking record but they do not have a login to manage their data.Waivers and document storage
Waivers can collect sensitive information including signatures, health declarations, and uploaded documents. This data is:- Stored securely against the individual booking
- Accessible only to staff with appropriate permissions
- Linked to the specific participant who completed the waiver
Staff access controls
Sailia’s permission system lets you control which staff members can access sensitive data:| Permission | What it controls |
|---|---|
| View other user profiles | Access to customer profiles, booking history, and notes |
| Financial dashboard | Access to payment data, payouts, and financial reports |
| Staff management | Access to other staff members’ profiles and timesheets |
| Communications | Access to send emails and manage marketing campaigns |
Data in integrations
When you connect third-party integrations, data may be shared with external services:| Integration | Data shared |
|---|---|
| Stripe | Payment amounts, customer email, product details |
| Xero | Payout amounts, invoice line items, VAT categories |
| Google Tag Manager / PostHog | Booking events, session IDs, product names |
| Adventuro | Activity details, availability, booking confirmations |
| Automated workflows | Customer name, email, booking details (via merge fields) |
Review the privacy policies of each third-party service you connect. You are responsible for ensuring these integrations comply with your local data protection regulations.
Data exports
Sailia provides several export options for extracting your data:- Booking exports — all booking records with customer details
- Financial exports — payment and payout data
- Customer exports — customer profiles and contact information
- Donation exports — donation records with Gift Aid details
- Timesheet exports — staff timesheet entries
Best practices
- Review staff permissions regularly — remove access for staff who no longer need it
- Use waivers for consent — add a consent checkbox to your waiver templates for activities that require explicit data consent
- Monitor marketing subscribers — respect unsubscribe requests and keep your audience list clean
- Secure your account — use a strong password for your Sailia admin account
- Audit integrations periodically — disconnect integrations you no longer use to minimize data sharing
Related guides
Permissions reference
Control what each staff member can access.
Waivers
Collect consent and signed documents.
Payments and Stripe
How payment data is handled securely.
Customer accounts
How customers manage their own data.