← SwiftCove
Privacy transparency

Subprocessors and service providers

SwiftCove uses the providers below to operate the booking platform. A subprocessor handles personal data on SwiftCove's behalf. Other services may receive limited information under a separate role, which is identified below.

Last updated September 25, 2026

Current subprocessors

Supabase

Database hosting and database API

Ohio, United States

Processes operator accounts, business and tour configuration, availability, bookings, payment-status references, acceptance evidence, and related audit information.

Render

Application hosting and operational infrastructure

Oregon, United States

Hosts the SwiftCove application and scheduled reminder job and processes request, application, operational-log, and rate-limit information needed to run and protect the service.

Google

Operator-owner authentication

Processes the Google subject identifier, verified email, profile information supplied during authentication, and related OAuth and session metadata. Google may process information internationally under its own terms and privacy practices.

Resend

Transactional email

Processes recipient names and email addresses, booking or service-message content, and delivery metadata for confirmations, reminders, onboarding notices, and other operational email.

Other authorized services

O-Pay

Operator-selected hosted payment provider

Each operator separately contracts with O-Pay and uses its own merchant credentials. SwiftCove transmits customer contact details, amount, currency, and booking and business metadata needed for checkout and receives payment and refund status information. O-Pay is an operator-authorized recipient, not a general SwiftCove subprocessor.

Google Fonts, Tailwind CDN, and jsDelivr

Fonts, styling, and public-page assets

A visitor's browser may disclose an IP address and ordinary browser or request metadata when loading these externally hosted resources.

Currently unavailable

Twilio WhatsApp

WhatsApp reminders are not currently available or enabled, and Twilio is not used for current SwiftCove message delivery. If this changes, SwiftCove will update this page before using Twilio for operator or traveler information.

Changes and questions

SwiftCove will update this page when a service provider materially changes. Where required, operators will receive reasonable advance notice and may raise a data-protection objection under the applicable agreement.

Questions may be sent to aumarijoseph@gmail.com.

Read the SwiftCove Operator Privacy Notice