Skip to main content

Cookie Policy

Last updated: 1 June 2026

UpDoc (Pty) Ltd(Registration No. 2026/344997/07) — Version 1.0, effective 1 June 2026. This Cookie Policy explains how cookies are used on the UpDoc platform (the locum portal, the hospital/department portal, and the agency portal, together the “Platform”). It forms part of, and should be read with, our Privacy Policy and Terms of Use.

1. What cookies are

A cookie is a small text file placed on your device by a website so the site can recognise your device and remember certain information — for example, that you are signed in. Cookies set by the site you are visiting are “first-party” cookies; cookies set by another domain are “third-party” cookies.

2. The cookies we use

UpDoc uses strictly necessary cookies only. These are required to sign you in and keep you securely signed in as you move between pages. They are set by our authentication provider, Supabase, through the @supabase/ssr library, and are stored as HTTP-only, Secure cookies— they cannot be read by client-side scripts.

  • Authentication session cookie (sb-<project>-auth-token, which may be split into numbered chunks) — maintains your signed-in session and securely refreshes it so you do not have to log in on every page. It is a strictly necessary, first-party, HTTP-only cookie that persists for the lifetime of your session and is cleared when you sign out or the session expires. Without it you cannot log in.

3. Cookies we do not use

We do not use advertising, marketing, behavioural-tracking, or cross-site cookies, and we do not use analytics cookies that profile individual users. Because we use strictly necessary cookies only, no cookie-consent banner is required for the Platform as it currently operates. Our error-monitoring provider (Sentry) and our application-hosting provider (Vercel) do not set tracking cookies in the Platform.

4. Managing cookies

You can block or delete cookies through your browser settings. Because the only cookies we use are strictly necessary for authentication, blocking them will prevent you from signing in and using the Platform.

5. Future changes

If we introduce optional cookies in future (for example, analytics or preference cookies), we will update this Cookie Policy, present a cookie-consent mechanism on first access, and obtain your consent before setting any non-essential cookie. Material changes are notified as set out in our Privacy Policy.

6. Contact

Questions about cookies can be sent to our Information Officer, Mark Trevor Verryn, at mark@updocsa.co.za, or to support@updocsa.co.za.