Privacy Policy

1. Who's responsible for what

Bark Scheduler operates the platform and is responsible for the technical/security practices described below. Each School controls its own catalog, pricing, and cancellation policies, and is responsible for how it represents itself to its own Customers — we don't review or edit a School's content.

2. Information we collect

• Account information — name, email, phone (optional), and a hashed password (we never store your password in plain text).
• Pet information (Customers) — a pet's name, breed, age, behavioral notes you add, and whether you've confirmed vaccination status.
• Booking and payment history — which classes, private lessons, or room rentals you've booked, and payment confirmation status. We don't store full card numbers — Stripe handles that directly (see §4).
• Business information (Schools) — your business name, branding (logo, colors), and connected Stripe account details.
• Communications — messages sent through our contact form, and the confirmation/reminder/cancellation emails the platform sends on a School's behalf.
• Basic technical data — a session cookie that keeps you logged in, and error/diagnostic information (see §5) if something goes wrong.

We don't use advertising or analytics tracking cookies today — the only cookie set is the session cookie needed to keep you logged in.

3. How we use this information

• To operate the booking/scheduling/payment features you use.
• To send transactional emails — booking confirmations, reminders, cancellations, and (for trainers) daily schedule digests.
• To process payments and platform subscription billing.
• To maintain the security of accounts and the platform (e.g. rate-limiting abusive login attempts).
• To respond to support requests sent through the contact form.

4. Who we share it with

We share information with the following third-party services, each only for the purpose described:

• Stripe — processes all payments (booking checkout and platform subscription billing). Stripe receives your payment details directly; we don't see or store your full card number.
• Resend — sends transactional emails (confirmations, reminders, cancellations, password reset).
• Supabase — hosts our database (Postgres). Every School's data is isolated from every other School's at the database level.
• Sentry — receives error reports if something breaks, so we can fix it. Error reports are tagged with an internal account ID, not your name/email/pet details.
• Trigger.dev — runs the scheduled jobs that send booking reminders and trainer daily digests.
• A School's own CRM (Nutshell or Zoho CRM), only if that School has connected one — if so, your name, email, and booking history may be synced to that CRM so the School can manage its own customer relationships. This is entirely the School's choice; we don't connect a CRM on a School's behalf.
• Zapier, only if a School has connected it — a School may use Zapier to send booking/customer data to other tools it uses, via an API key it generates itself.

We don't sell your information, and we don't share it with anyone else for their own marketing purposes.

5. Error monitoring

If something goes wrong while you're using the platform, technical details about the error (what happened, which part of the app, an internal account/School ID) may be sent to our error-monitoring service (Sentry) so we can investigate and fix it. We deliberately avoid sending your name, email, or pet details in these reports — just enough to find the right database record if we need to look further.

6. Data security

Passwords are hashed, never stored in plain text. Sensitive credentials a School connects (like CRM API keys) are encrypted at rest. Every School's data is isolated at the database level (row-level security), so one School can't access another's data even in the event of an application-level bug. No system is perfectly secure, and we can't guarantee against every possible breach, but we take reasonable, industry-standard steps to protect your information.

7. Data retention

We keep account, booking, and payment history for as long as your account (or the School you're a Customer of) remains active, and for a reasonable period after in case it's needed for support, legal, or accounting reasons. If a School closes its account, its Customers' data is retained or deleted according to [describe your actual retention/deletion practice here once decided].

8. Your choices and rights

You can review and update most of your account information directly (name, phone, pet details) from your account settings. To request a copy of your data, a correction, or deletion, contact us using the details in §11 — we'll respond as required by applicable law. [If you operate in a jurisdiction with specific rights language required — e.g. GDPR, CCPA — add that language here after legal review; it isn't included in this draft since it depends on where your business and customers are located.]

9. Children's privacy

Bark Scheduler isn't directed at children, and we don't knowingly collect information from anyone under 13. If you believe a child has provided us information, contact us and we'll remove it.

10. Changes to this policy

We may update this policy as the platform changes. We'll update the "Last updated" date above when we do.

11. Contact

Questions about this policy, or a data request? Reach out via the contact form on our homepage, or at [your support email].