Privacy Policy

Last updated October 20, 2026

Draft template. Set LEGAL_ENTITY_NAME, LEGAL_CONTACT_EMAIL, LEGAL_ADDRESS and LEGAL_JURISDICTION and have a lawyer review this text before launch. It is not legal advice.

BookingPortal, a lemonade.lifestyle product, is booking software run by [Your company name] (“we”). Businesses use it to take bookings from their customers. This policy explains what data is handled, why, and what rights you have. Contact: privacy@example.com, [Your company address].

Cookies and tracking: short version

No analytics, no advertising, no tracking pixels, no third-party trackers. We do not profile visitors.
Customers who book do not receive any cookie from us. No cookie banner is needed because we set none for them.
Business owners and staff who sign in receive one strictly necessary session cookie (bp_session, HTTP-only, used only to keep you signed in). It is removed when you sign out or it expires after 14 days.
If a customer pays a deposit, the payment form is provided by Stripe, which may set its own cookies or use similar technology for fraud prevention and payment processing, under Stripe's own policy.

Who is responsible for which data

Customer data (the name, contact details, vehicle and booking details a customer gives when booking): the business you book with is the controller; [Your company name] processes it on that business's behalf. To use your rights, contact the business, or use the links on your booking confirmation (see below).
Account data (owner and staff names, email addresses, password hashes, sign-in sessions, terms acceptance): [Your company name] is the controller.

What we collect and why

Bookings: name, email, phone, address (for mobile services), vehicle details, answers to the business's questions, appointment time and status. Purpose: to make and manage your booking, send confirmations and reminders.
Accounts: name, email, hashed password, role, sign-in sessions. Purpose: to run the service securely.
Technical: IP address, used briefly for abuse prevention (rate limiting) and security logging. We do not use it for tracking.
Payments: card details are entered with Stripe and never reach our servers; we store only payment identifiers and status.

Who receives data (sub-processors)

We use these providers to deliver the service: hosting and database (e.g. Vercel and a managed PostgreSQL provider), Stripe (payments), Resend (email) and Twilio (SMS). They process data only to provide those services. Some are located outside your country; where required we rely on appropriate safeguards.

How long we keep it

Booking and customer records are kept while the business keeps its account, unless erased earlier on request. When a business deletes its account, its data is permanently deleted. Sign-in sessions expire after 14 days, password-reset and invitation links after 1 hour and 7 days. Rate-limit counters are purged within hours.

Your rights

Depending on where you live (for example under GDPR, UK GDPR, PIPEDA or CCPA) you may have the right to access, correct, export and delete your data, and to object to or restrict processing.

Customers: your booking confirmation links to a page where you can download your data and erase your personal data yourself (you must cancel any upcoming booking first). You can also ask the business directly.
Businesses: the owner can export all business data, export or erase any customer's data, and permanently delete the account from the admin area.
Anything else: email privacy@example.com. You may also complain to your data protection authority.

Erasing a customer removes their name, contact details, vehicles, address and answers, and redacts audit entries about them. Bookings remain only as anonymous records so the business's schedule and accounts stay accurate. Payment records held by Stripe are governed by Stripe's retention rules and the business's legal obligations.

Security

Data is encrypted in transit; passwords are stored as salted hashes; each business's data is isolated at the database level; access is limited by role; sign-in and public endpoints are rate limited. No system is perfectly secure; we will notify affected parties of a breach as the law requires.

Changes

We will post updates here and, for material changes, ask account holders to accept them again.