Privacy Policy

Reacpaw Trainers is software that helps professional dog trainers manage clients, dogs, schedules, training plans, and communication. This Policy covers personal information we handle through the website at trainers.reacpaw.com, the trainer web application, the trainer features of the Reacpaw mobile app, secure client form and waiver completion pages, and related support (together, the “Service”).

Dog owners who connect with a trainer use the Reacpaw companion app, which has its own privacy policy. This Policy explains what happens to their information inside a trainer’s workspace and what Reacpaw handles as the platform when a Client completes a form or waiver or makes a paid booking.

The Service is operated by Christelle Sissoko, doing business as Reacpaw, Quebec, Canada (“Reacpaw”, “we”, “us”, or “our”).

When we decide how information is used

We are responsible for (the “controller” of) information about trainers and team members, such as their accounts, profiles, subscription billing, booking-payment setup, platform transaction records, legal acceptances, security, and support requests, and about visitors to our website. We also decide how to use payment data needed to operate and secure the platform, comply with law, and manage disputes.

When we act for a trainer

Information about a trainer’s clients and their dogs (“Client Data”) is controlled by the trainer or training business whose workspace it is in. This includes records the trainer enters and the logs, notes, videos, form answers, waiver responses, and related completion records a client shares with that trainer. We process Client Data on the trainer’s behalf, as their processor or service provider. If you are a client and want to access, correct, or delete information your trainer holds about you, contact your trainer first. If you contact us, we will forward your request and help them respond.

Disconnecting from a trainer or deleting your companion-app account stops future sharing but does not automatically delete the trainer’s business records. The trainer-side client and dog records are archived, external account identifiers are removed, and information already stored in the workspace remains under the trainer’s control and retention obligations.

Trainer and Stripe roles for paid bookings

For a paid booking, the trainer is the independent seller and service provider. The trainer decides why it needs information to deliver the service, communicate with the Client, and keep its business records. Stripe independently processes identity, account, payment-method, fraud, payout, and compliance data under its own privacy policy. Reacpaw facilitates the booking and exchanges transaction instructions and status information with Stripe; Reacpaw does not receive full card numbers or card security codes.

Person in charge of privacy

Our person in charge of the protection of personal information is Christelle Sissoko, Founder. You can reach them at [email protected].

Trainer and team member accounts

• Name, email address, and phone number
• Sign-in details. Passwords are handled by our authentication provider, and we do not store them. If you sign in with Google, we receive your Google name, email address, and profile photo.
• Professional profile: photo, years of experience, certifications, training style, short bio, the types of training you offer, and your website and social media links
• Workspace details: business name, description, facility location, logo, team members, and roles
• Settings such as timezone, measurement units, and notification and onboarding progress
• Your trainer code and the invitations you send and receive
• A record of your acceptance of our Terms: the version, date, and how you accepted

Client Data (held for trainers)

• Client details: name, email, phone, address, emergency contact, notes, and archive status
• Dog details: name, photo, birth date, sex, weight, neuter status, adoption date, reactivity level, training goals, and health information such as medical notes, allergies, medications, vaccination, deworming, and microchip status
• Training records: assignments, tracking logs, triggers and encounters, goals, progress analytics, session notes, follow-ups, homework, and pre-session briefs
• Training videos and photos, with any time-stamped feedback on them
• Messages, attachments, and announcements between trainers and clients
• Bookings, reschedule requests, cancellations and their reasons, and session locations

Documents

• Files a trainer uploads or imports, which may include contracts, waivers, vaccination records, photos, videos, and other information selected by the trainer
• Document details such as title, description, original filename, file type and size, category, folder, expiration date, source, and any Client or dog association
• Document and folder permissions, including who granted access, the permission level, and any expiration or revocation date
• Document activity records, including creation, edits, access changes, preview requests, download requests, the trainer responsible, and timestamps

Forms and waivers

• The trainer-created template, its exact published version, title, instructions, questions, choices, required fields, and waiver text
• For an imported waiver, the uploaded PDF or DOCX source file, extracted editable text where selected, original filename, type, size, page count where applicable, and integrity checksum
• The Client or recipient, assigned items, delivery address, assignment status, expiration date, and email-verification and delivery records
• Submitted answers, acknowledgements, agreement or decline, and, for a waiver, the typed legal name
• The verified email address and the dates and times an item was viewed, saved, submitted, signed, completed, or declined
• Technical evidence used to secure and support the completion record, including IP address, IP hash and source, browser or device user agent, event history, and integrity hashes
• The completed PDF stored in the Client’s Documents area and records showing whether the email receipt was delivered

A trainer decides what information a form or waiver requests and why it is needed. Reacpaw uses a secure completion link and one-time code sent to the assigned email address before showing the content. Email verification confirms access to that mailbox; it is not government-identity verification.

Converting an imported waiver into editable Reacpaw content is performed as a document-processing operation and is not sent to an AI model. When a trainer preserves an original PDF, the source is kept in private account storage and its checksum is verified before display and completed-PDF generation.

Scheduling and integrations

• Your availability rules, exceptions, and appointment types
• If you connect Google Calendar: read-only access to your calendar list, events, and busy times, which we show alongside your agenda and use to avoid booking conflicts
• If you connect Google Drive: read-only access to file and folder identifiers, names, types, sizes, and modification times while you browse, and the contents of files or folders you select for import
• Access tokens for connected integrations, which are deleted when you disconnect or delete your account

A Google Drive import creates a separate copy in Reacpaw’s private storage without changing the original. Disconnecting Google Drive stops future access and deletes our integration tokens, but imported copies remain in Documents until you delete them or the workspace is deleted under Section 9.

Reacpaw’s use of information received from Google Workspace APIs adheres to the Google User Data Policy, including the Limited Use requirements. Reacpaw does not use, transfer, or sell Google Workspace user data to create, train, or improve generalized or foundational AI or machine-learning models. Google Calendar and Google Drive data obtained through Google Workspace APIs is not sent to OpenAI or used by Reacpaw’s AI-assisted features.

Billing

Your plan, number of seats, subscription status, billing dates, and Stripe customer and subscription identifiers. Stripe collects and processes your card details. We never see or store full card numbers.

Booking payments

• Trainer seller information entered in Reacpaw, including legal and display names, support email and optional phone, service country, province or state, and business or public address
• Connected-account identifiers and status, requested and active capabilities, onboarding requirements, payout readiness, and Stripe Dashboard access; Stripe collects underlying information such as business type, representative identity, ownership, and bank-account details
• Trainer tax-registration status and attestations, cancellation-policy selections, and records showing who accepted each payments-addendum version and when
• Client-declared and billing country or state, service location or virtual-session jurisdiction, and eligibility results used to enforce supported-region rules
• Booking description, trainer, Client, appointment, currency, subtotal, tax, total, payment status, Stripe transaction identifiers, payment-method type and limited display details, receipt, refund, cancellation, dispute, and chargeback information
• Records of the Client’s final booking confirmation, including the disclosed price, tax, cancellation terms, legal-document versions, timestamp, and technical evidence such as IP address and user agent

Payment methods may include cards, Apple Pay, and Google Pay where Stripe and the Client’s device support them. Stripe collects the payment credentials directly. Reacpaw does not store full card numbers, wallet credentials, or card security codes.

Support and feedback

Messages you send us through email or our contact form, and posts, comments, votes, and media you share on our in-app feedback board. Feedback board posts are visible to other trainers unless you mark them private.

Technical and device information

• IP address, browser and device type, operating system, and server logs
• Login times and security events
• Push notification tokens for the mobile app
• Error reports and performance data. In the trainer web app, this includes session replays that mask all text, inputs, and media and are only recorded with your consent.
• Usage analytics, as described in Section 8

We use personal information to:

• Provide the Service and the features you use
• Create and manage accounts, workspaces, team access, and connections between trainers and clients
• Store and display records, files, and messages to the people they are shared with
• Organise documents, enforce document and folder permissions, track expiration dates, and keep security activity records
• Deliver forms and waivers, verify the recipient’s email address, save progress, record completion or decline, and notify the trainer
• Generate and store completed PDFs, email receipts, and preserve evidence showing the template version and completion process
• Run trials and subscriptions, process payments, and keep billing records
• Check trainer and Client eligibility for supported booking-payment regions
• Set up connected accounts and facilitate authorisations, captures, receipts, refunds, and disputes
• Apply trainer-selected cancellation terms and preserve evidence of each booking confirmation
• Calculate transaction taxes when enabled and keep accounting, compliance, and reconciliation records
• Send service emails, booking reminders, account and billing notices, and push notifications
• Produce AI-assisted summaries, insights, analytics explanations, and tracking-template suggestions (see Section 5)
• Keep the Service secure and prevent fraud, spam, and abuse
• Provide support and respond to your requests
• Understand usage and fix errors, with your consent where required
• Comply with the law and enforce our Terms

We do not sell personal information. We do not use it for targeted advertising, and we do not share it for cross-context behavioural advertising. We do not use Client Data for our own purposes, except in aggregated or de-identified form to maintain and improve the Service.

If you are in the European Economic Area (EEA) or the United Kingdom, the table below sets out the legal bases we rely on:

Some features use AI models provided by OpenAI. They include assignment summaries, progress insights, analytics explanations, and suggested fields for tracking templates.

To generate these, we send OpenAI the training records needed for the task. Depending on the feature, that can include tracking logs, triggers, progress data, session notes, the dog’s name, and notes written by the client. We do not add trainer or client names or contact details to these requests, although free-text notes are sent as written. OpenAI does not use data sent through its API to train its models.

AI output is shown to the trainer as an aid. It is not used to make decisions that have legal or similarly significant effects on anyone.

Within a workspace

Team members in a workspace can see that workspace’s clients, dogs, schedules, and records, according to their role.

Documents are more narrowly controlled. A trainer can access a document only when they have direct permission or permission through its folder. Viewer, editor, and manager permissions determine what they can do, and access can expire or be revoked.

Between a trainer and a connected client

A connected client sees the assignments, plans, bookings, messages, and announcements their trainer shares with them. The trainer sees the profile details, dogs, logs, notes, and videos the client chooses to share. Clients choose which dogs to share when they connect, and they can disconnect at any time. Disconnecting ends future access to the companion account; it does not erase the historical information already stored in the trainer’s workspace or documents uploaded by the trainer.

For forms and waivers

A recipient can see the items the trainer assigns through the secure completion link and receives a PDF receipt after completion. The trainer and authorised workspace members can see assignment status, submitted answers, agreement or decline, completion evidence, and the completed PDF according to their workspace and document permissions. We use email and private-storage providers to deliver the invitation and receipt and to store the completed PDF.

For paid bookings

The trainer receives the Client and booking information needed to decide whether to accept and deliver a service, provide support, issue a refund, and respond to a dispute. The Client receives the trainer’s seller identity, public contact information, service details, price, tax, cancellation terms, and payment status. We share payment and connected-account information with Stripe, and Stripe may share transaction, risk, verification, and account-status information with us and the trainer as its terms allow.

Banks, card networks, wallet providers, tax services, professional advisers, insurers, regulators, courts, and law-enforcement authorities may receive information where needed to process a transaction, investigate fraud, handle a dispute, protect safety, establish or defend legal claims, or comply with law.

Service providers

We share information with service providers only as needed for them to provide services to us and under contracts that require them to protect it. Section 7 describes the categories of services they provide.

Legal and safety reasons

We may disclose information if required by law or valid legal process, or where necessary to protect the rights, safety, or property of our users, the public, animals, or Reacpaw.

Business transfers

If we are involved in a merger, acquisition, or sale of assets, information may be transferred as part of that transaction, subject to this Policy. We will notify you before your information becomes subject to a different privacy policy.

Within Reacpaw

A small number of authorised Reacpaw staff can access account and workspace information when needed to provide support, investigate problems, or keep the Service secure. They are bound by confidentiality.

We use service providers to support cloud hosting, databases, private file storage and delivery, authentication, subscription billing, connected accounts, booking-payment processing, fraud screening, tax calculation, email and push notifications, optional integrations, location search, security, analytics, error monitoring, customer support, and AI-assisted features. These providers may process personal information only as needed to provide their services to us and are required by contract to protect it. Some providers process information outside Quebec, as described in Section 11.

Essential

The public marketing website and trainer web app use a cookie that remembers your consent choice for 180 days. The trainer web app also uses a session cookie to keep you signed in and a security token to protect against cross-site request forgery. These are needed for the Service to work.

Analytics and error monitoring

On the public marketing website and in the trainer web app, Google Analytics is only turned on if you allow analytics in the cookie banner. The trainer web app also uses Sentry (performance monitoring and session replay) only with that permission. You can change your choice at any time from the privacy settings link. If you withdraw consent, we stop these tools and remove Google Analytics cookies. Ad personalisation signals are always turned off. The Reacpaw mobile app uses Sentry and Firebase Crashlytics for crash and error reports.

We keep information only as long as we need it for the purposes in this Policy:

When we no longer need information, we delete it or anonymise it so that it no longer identifies anyone.

Our safeguards include:

• Encryption in transit (HTTPS/TLS)
• Authentication through Firebase, with session cookies and protection against cross-site request forgery
• Signing in again before sensitive actions such as deleting an account
• Workspace-based access controls, with additional direct and folder permissions for documents
• Private file storage, delivered through signed, time-limited links
• One-time email verification for form and waiver links, and tamper-evident hashes for completion records and event history
• Rate limiting, bot protection, and monitoring

No system is completely secure. If a security incident creates a risk of serious harm, we will notify the people affected and the relevant authorities as the law requires. Please report security concerns to [email protected].

We are based in Quebec, Canada, and our main infrastructure and providers are in the United States. Your information may therefore be stored and processed outside your province, state, or country, including outside Quebec. Paid-booking data may be processed in Canada and the United States by Reacpaw, Stripe, financial institutions, and other providers, where it may be accessible to courts and authorities under local law.

Before transferring personal information outside Quebec, we assess whether it will be adequately protected. For transfers from the EEA, the UK, or Switzerland, we rely on adequacy decisions (including the EU–US Data Privacy Framework where the provider is certified), the European Commission’s Standard Contractual Clauses, or the UK International Data Transfer Addendum, as applicable.

Depending on where you live, you have some or all of these rights over your personal information:

• Find out whether we hold information about you, and get access to it or a copy of it
• Correct information that is inaccurate or incomplete
• Delete your information
• Receive your information in a structured, commonly used format (portability)
• Withdraw your consent, for example to analytics cookies, at any time
• Object to processing based on our legitimate interests, or ask us to restrict processing
• Have your information de-indexed or stop being disseminated, where Quebec law gives that right

How to exercise your rights

Trainers can update most profile and workspace information in Settings and delete their workspace from Settings → Account. For any other request, email [email protected]. We will verify your identity and respond within 30 days, or within the time the law that applies to you allows. We will not treat you differently for exercising your rights. If you are a client of a trainer, see Section 2.

A deletion request does not require us or a trainer to erase transaction, tax, consent, fraud, safety, or dispute records that must be kept by law or are reasonably needed to establish, exercise, or defend legal claims. Where appropriate, we restrict those records to the permitted purpose instead.

Completed form and waiver evidence is designed to preserve the integrity of what was submitted and is not edited in place. To correct an answer after submission, contact the trainer; the trainer can document the correction or send a new item. Access, correction, objection, and deletion requests still apply according to the law and the retention limits above.

Complaints

• Quebec: Commission d’accès à l’information du Québec
• Elsewhere in Canada: the Office of the Privacy Commissioner of Canada, or your provincial commissioner
• EEA and UK: your local data protection authority, or the UK Information Commissioner’s Office

Please contact us first so we can try to help.

United States residents

Residents of California and other states with consumer privacy laws can make the requests above, and can use an authorised agent to do so. We do not sell personal information or share it for cross-context behavioural advertising, and we do not use sensitive personal information to infer characteristics about you. If we deny your request, you can appeal by replying to our decision.

The Service is for adults acting in a professional capacity, and trainer accounts are only available to people aged 18 or older. Forms and waivers are intended for adult Clients or a parent, guardian, or other authorised representative where one is required. Trainers must not use them to collect a child’s personal information without the authority, notice, and consent required by law. If you believe a child’s information was collected improperly, contact the trainer or [email protected] so the request can be investigated and handled as the law requires.

We may update this Policy. We will post the new version here and update the date at the top. If a change is material, we will also notify workspace owners by email or in the Service before it takes effect.

For privacy questions or requests, contact: