Privacy

DivineBooking is scheduling software for independent service businesses. The business you book with controls its client list; DivineBooking stores and processes that information to provide the calendar. We do not sell personal information, run a consumer booking marketplace, or use advertising trackers on the product.

The business operating a DivineBooking workspace decides why client information is collected and how it is used for its services. DivineBooking processes that information on the business's behalf. If you are a client, contacting the business first is usually the fastest way to correct a booking or client record. You can also contact us and we will coordinate with the business where appropriate.

• If you book an appointment: your name, email and/or phone number, the service and time selected, and information you deliberately add to the booking. The business may keep notes about later visits inside its workspace.
• If you use a DivineBooking workspace: account identifiers, business details, staff access, services, availability, and client and appointment records that you create or import.
• If you start a paid plan: subscription status, selected billing interval, renewal dates, and Stripe customer and subscription identifiers. Stripe, not DivineBooking, collects and stores the full card details entered at checkout.
• Automatically: request information such as IP address, browser or device details, timestamps, and strictly necessary sign-in cookies. On this public marketing site, Vercel Analytics and Speed Insights also process route, referrer, approximate location, device, and performance information so we can understand visits and improve page performance.

• Creating, changing, displaying, and protecting appointments.
• Sending booking confirmations and email reminders when configured.
• Providing history, exports, support, error investigation, and abuse prevention.
• Running optional integrations only when a workspace or staff member chooses them.

DivineBooking uses managed infrastructure and service providers. Storage and processing locations depend on the provider and deployment, and some processing may occur outside Canada. We do not currently promise that all workspace or client data remains in Canada.

Our dated provider list explains the purpose, information involved, and location statement for each service at Data + privacy.

We limit service-provider access to the work each provider performs:

• Clerk supports staff sign-in and session management.
• Railway runs the application services and database infrastructure.
• Cloudflare supports object storage and edge services where configured.
• Inngest runs scheduled and retryable background work.
• Resend delivers confirmation and reminder email and receives the recipient address, content, and delivery metadata.
• Sentry receives diagnostic information when error reporting is configured.
• Google receives appointment event information only when a staff member connects the optional one-way calendar integration.
• Anthropic may receive CSV column names and up to three sample rows, or batches of iCalendar event fields that the local parser could not identify, only when a workspace user deliberately enables the optional mapping helper. Samples can contain names, email addresses, phone numbers, notes, or appointment details. The helper is off by default, and the manual mapping path does not require this transfer.
• Vercel hosts this public marketing website and provides aggregate website analytics and performance measurement. It does not host the client-booking database.
• Stripe provides the secure checkout, recurring subscription, billing portal, and invoices used to pay for a DivineBooking workspace. Stripe receives the billing contact and payment details entered in its checkout.

SMS delivery through Twilio and taking card payments from a business's clients are not currently offered as live plan features. Stripe subscription billing for the DivineBooking workspace is separate from client payment processing.

We do not sell personal information or share it with data brokers or advertising networks.

Booking responses containing client or appointment information are sent with private, no-store cache instructions. Application and audit records may include IP addresses, user agents, actor identifiers, and change details for security, reliability, and troubleshooting. Our current security-control evidence and its limitations are published on the Security page.

Client and appointment records are generally retained while the related workspace is active because the business relies on its visit and change history. Normal delete actions use recoverable flags or status changes instead of immediately destroying a record. DivineBooking does not currently publish one universal automatic purge period for every record type.

Before closing a workspace, the owner should request an export and confirm the deletion plan with us. Operational and backup copies, where present, may remain until their applicable rotation or recovery period ends. Contact us for the current timing that applies to a specific request.

• Access, correction, export, or deletion: ask the business you booked with or email us. We may need to verify the request and coordinate with the workspace owner before changing business-controlled records.
• Email: contact the business if a booking confirmation or reminder used incorrect contact information. Transactional messages may still be needed for an active booking.
• SMS: SMS reminders are not currently offered as a live plan feature. Consent and opt-out instructions will be presented before any future launch.
• Optional import assistance: use the manual mapping path if you do not want CSV sample rows or unparsed iCalendar event fields sent to the optional AI provider.

If this policy changes in a meaningful way, we will update the date at the top and provide additional notice when appropriate. Questions or requests: privacy@divinebooking.app.