yumeeJoin the waitlist

Subprocessors

Last updated

These are the companies that handle information on our behalf, what each one can actually see, and the region it runs in. The boring entries are listed with their limits rather than left out. A list that omits DNS and staff mail is not one you can rely on.

Who processes what

  • Supabase

    What it does for us
    Database and sign-in for the dashboard
    What it can see
    Everything Yumee stores at rest: call records, transcripts within their retention window, bookings, clinic staff accounts, and waitlist signups: an email address, which form it came from, and the site it came from.
    Where it runs
    Australia (Sydney)

  • Retell

    What it does for us
    The voice pipeline that answers the call
    What it can see
    Live call audio and the transcript of the conversation, for the duration of the call.
    Where it runs
    United States / Canada

  • Twilio

    What it does for us
    Phone numbers and call carriage
    What it can see
    The caller's phone number and call metadata: time, duration, and where the call was routed.
    Where it runs
    United States

  • Amazon Web Services

    What it does for us
    Runs the service that handles each call, and our background and scheduled work
    What it can see
    Processes call and booking records, including the caller's phone number, while a call or a job runs. Keeps that service's operational logs for 14 days: call references and clinic identifiers, never what was said on a call.
    Where it runs
    Australia (Sydney)

  • Vercel

    What it does for us
    Hosting for this site and the clinic dashboard
    What it can see
    Serves this site and the dashboard, and runs the code that handles a waitlist signup, so it sees that email address in transit, and the IP address of anyone who loads a page. Request logs only; no patient records are stored there.
    Where it runs
    Global edge network (United States company)

  • PostHog

    What it does for us
    Product analytics for the dashboard and this site
    What it can see
    Which pages are visited and which features are used, by anyone browsing this site, not only signed-in clinic staff, along with the IP address any web request carries. Never patient information: no event we send carries any, and the events are written by hand and reviewed rather than assembled from patient records.
    Where it runs
    European Union

  • Resend (with Amazon SES)

    What it does for us
    Transactional email
    What it can see
    Email addresses of clinic staff and waitlist subscribers, and the messages sent to them. No open or click tracking.
    Where it runs
    European Union (eu-west-1)

  • Cloudflare

    What it does for us
    DNS for getyumee.com
    What it can see
    None. DNS records only. Traffic is not proxied through Cloudflare, so no request ever reaches it.
    Where it runs
    Global

  • Google Workspace

    What it does for us
    Our own staff email
    What it can see
    Correspondence you send us directly, and the notification we send ourselves when someone joins the waitlist, which contains that person's email address. Not part of the call or booking path.
    Where it runs
    Global

Changes to this list

We will give clinic customers notice before adding or replacing a subprocessor. This page is the current list; it is not summarised anywhere else, so there is no second copy to fall out of date.