Getting Started

Upod gives your users a privacy-first login and gives your site anonymized profile data (gender, age range, residence) that you can use to personalise the experience. This guide walks you through the supported integration paths.

Prerequisites

Before you write any code:

Register your application as an OIDC client by contacting us. Provide:
- Your website URL(s)
- The redirect_uri(s) users will be sent back to after login
- The post_logout_redirect_uri(s) to use after logout
You'll receive a client_id. Upod clients are public clients — there is no client_secret, so the flow uses PKCE.

Registered redirect_uri and post_logout_redirect_uri values must match what your app sends exactly — same string, including path and trailing slash. https://example.com and https://example.com/ are different URIs.

Choose your path

All-in-one widget

Add one script tag, get a self-contained login widget plus access to anonymized profile data for personalisation. The fastest way to ship.

Cookie modal

Show a full-screen modal before your cookie banner to explain Upod and offer signup, login, or manual dismiss.

Our button in your cookie banner

Drop a single <upod-button /> into your existing UI (e.g. cookie banner). Our client library handles the OIDC callback for you.

For full design control: your own login button

Build your own button and call client.login() yourself. Keeps our session and profile helpers but skips the <upod-button> custom element.

OIDC provider

Treat Upod as a standard OIDC provider and use any OIDC client library. Upod issues public clients only — use Authorization Code + PKCE.

Handling users' cookie consent

Fetch stored cookie preferences from logged-in users and sync them to your cookie banner or CMP.

How to choose

If you want to…	Pick
Ship in 5 minutes with zero UI work, and personalise content	All-in-one widget
Pitch Upod in a full-screen modal before your cookie banner appears	Cookie modal
Place the login trigger inside your own UI (e.g. a cookie banner) but keep the easy path	Our button in your cookie banner
Build a fully custom login button while keeping our session/profile helpers	For full design control: your own login button
Plug Upod into an existing auth stack that already speaks OIDC, with no extra dependencies	OIDC provider
Apply stored cookie consent to your banner or CMP after login	Handling users' cookie consent

All paths give you the same outcome: an authenticated user, an anonymized profile, and zero cookies required.

Next steps

Pick a path above and follow its guide end-to-end
Browse the API Reference for client.fetch(), purpose values, and the profile schema
Try the live examples in your browser