/* global React */

function ProcessorsPage({ navigate }) {
  const email = <a href="mailto:sarah@peoplecake.com">sarah@peoplecake.com</a>;
  const privacyLink = (
    <a href="#privacy" onClick={(e) => { e.preventDefault(); navigate("privacy"); }}>Website Privacy Notice</a>
  );

  return (
    <div className="route">
      <section className="hero" style={{ paddingBottom: 64 }}>
        <div className="container" style={{ position: "relative", zIndex: 1 }}>
          <div className="t-label hero__label">Legal</div>
          <h1 className="t-h1" style={{ maxWidth: 820 }}>Third-Party Processors</h1>
          <p className="t-body-lg hero__lead" style={{ marginTop: 24 }}>
            Last updated: 6 October 2026
          </p>
        </div>
      </section>

      <section className="section bg-white">
        <div className="container">
          <div className="privacy-doc">
            <h2 className="t-h2">About this page</h2>
            <p>
              We use some third-party processors to run this website. A processor is a company
              that handles personal data on our behalf and on our instructions. This page
              explains who they are and what they do for us. It supports our {privacyLink}, where
              you can find how we use your personal data more generally.
            </p>

            <h2 className="t-h2">Web3Forms</h2>
            <p>
              Web3Forms is a form-processing service. It is the third-party processor behind the
              forms on this website.
            </p>

            <h3 className="privacy-sub">What it does for us</h3>
            <p>
              When you submit one of our diagnostic forms (the Career Health Check or the Team
              Diagnostic), your submission is sent to Web3Forms, which passes it to us by email.
              We use it only to receive your responses and to send your report to you.
            </p>

            <h3 className="privacy-sub">What data it handles</h3>
            <p>
              The information you enter into the form, such as your name, email address, your
              message and any diagnostic responses. To protect against spam, Web3Forms may also
              pass the IP address and email address of the person submitting a form to
              spam-prevention services (currently CleanTalk and Akismet).
            </p>

            <h3 className="privacy-sub">Where your data may be processed</h3>
            <p>
              Web3Forms operates from India and uses infrastructure providers, including Amazon
              Web Services, Cloudflare and Hetzner, that may process data in more than one
              region. Web3Forms states that it transfers personal data from the UK under
              appropriate safeguards, including standard contractual clauses, set out in its{" "}
              <a href="https://web3forms.com/dpa" target="_blank" rel="noopener noreferrer">data processing agreement</a>.
            </p>

            <h3 className="privacy-sub">How long it keeps your data</h3>
            <p>
              Web3Forms keeps form submissions for a maximum of three years and then deletes them
              automatically. We keep the emails we receive from you only as long as we need them,
              as set out in our {privacyLink}.
            </p>

            <h3 className="privacy-sub">More information</h3>
            <p>
              Read the{" "}
              <a href="https://web3forms.com/privacy" target="_blank" rel="noopener noreferrer">Web3Forms privacy policy</a>.
              To ask about your own data, or to request deletion of a form submission, email {email}.
            </p>

            <h2 className="t-h2">Calendly</h2>
            <p>
              Calendly is the online booking calendar we use for &ldquo;Let&rsquo;s talk&rdquo; calls.
              The buttons on this website take you to our Calendly booking page. Nothing is sent to
              Calendly until you choose a time and book.
            </p>

            <h3 className="privacy-sub">What it does for us</h3>
            <p>
              Calendly lets you pick a time for a call with us, sends you a confirmation and adds
              the booking to our calendar.
            </p>

            <h3 className="privacy-sub">What data it handles</h3>
            <p>
              The details you enter when you book, such as your name, email address and the time
              you choose, together with anything else you add to the booking. For these
              bookings, Calendly acts as our processor.
            </p>

            <h3 className="privacy-sub">Where your data may be processed</h3>
            <p>
              Calendly is a US-based company. It states that it relies on the UK Extension to the
              EU-US Data Privacy Framework, Standard Contractual Clauses and the UK Addendum for
              transfers of personal data from the UK.
            </p>

            <h3 className="privacy-sub">Cookies on the booking page</h3>
            <p>
              Our own website sets no cookies. The Calendly booking page is run by Calendly and
              may show its own cookie banner and use its own cookies, which you can manage there.
            </p>

            <h3 className="privacy-sub">More information</h3>
            <p>
              Read the{" "}
              <a href="https://calendly.com/privacy" target="_blank" rel="noopener noreferrer">Calendly privacy notice</a>.
              To ask about your booking data, email {email}.
            </p>

            <h2 className="t-h2">Website hosting provider</h2>
            <p>
              Our website is hosted by Hostinger. Like most hosting providers, it keeps standard
              server logs, such as IP addresses, browser details and the pages requested. We use
              this information to keep the website secure and running properly.
            </p>

            <h2 className="t-h2">Changes to this page</h2>
            <p>
              If we start using a new third-party processor, or change how we use one, we will
              update this page and, where needed, our {privacyLink}.
            </p>

            <div className="privacy-back">
              <button className="btn btn--ghost" onClick={() => navigate("privacy")}>
                ← Back to the Privacy Notice
              </button>
            </div>
          </div>
        </div>
      </section>
    </div>
  );
}

window.ProcessorsPage = ProcessorsPage;