Analytics status
Analytics is not configured for this deployment, so UGP does not load a public analytics script or report visitor countries yet.
UGP
Cookie Policy
This Cookie Policy explains how UGP uses cookies and similar browser storage on by-ugp.com. The website uses necessary session cookies for sign-in, account security, and reliable portal access. Optional analytics is loaded only when a real provider is configured, documented here, and you explicitly accept it.
Cookie preferences
Choose whether UGP may load configured optional website analytics in this browser. This choice does not affect necessary sign-in, security, or account-session cookies.
Current cookie and storage list
authjs.session-token / __Secure-authjs.session-tokenNecessary session cookie
Keeps a signed-in website session for account pages protected by NextAuth.
next-auth.session-token / __Secure-next-auth.session-tokenNecessary session cookie
Legacy-compatible session cookie names cleared by middleware and logout flows.
ugp_rtNecessary account cookie
Optional HttpOnly refresh-cookie transport used to restore a UGP portal session when the backend sets it.
ugp_cookie_consentNecessary preference storage
Stores the cookie banner choice so the site can remember accepted or necessary-only consent.
Stripe cookiesPayment provider cookies
May be set by Stripe after a user opens Checkout or the Customer Portal for billing.
Google OAuth cookiesAuthentication provider cookies
May be set by Google after a user chooses Google sign-in or account linking.
1. Why UGP uses cookies
UGP uses necessary cookies to keep users signed in, protect account pages, connect the website session to backend account state, clear sessions on logout, and avoid showing the cookie banner after a choice has been saved.
These cookies support security and account reliability. Without them, sign-in, protected account pages, billing routes, device pages, team pages, and API key pages may not work correctly.
2. Necessary cookies
Necessary cookies are used for authentication, session continuity, protected routes, account restoration, and logout behavior.
They are not used to publish advertising claims, build marketing profiles, or claim analytics behavior that has not been implemented.
3. Local storage
The cookie banner preference is stored in the browser as local storage rather than as a server cookie.
Local storage stays in the browser until it is cleared by the user, browser settings, or site data removal. Clearing site data may cause the banner to appear again.
4. Stripe and Google
Stripe may set its own cookies when you open a payment, subscription, invoice, or Customer Portal flow. Stripe uses those cookies under its own policies.
Google may set its own cookies when Google sign-in or account linking is configured and used. Google handles those cookies under its own policies.
UGP should not represent third-party cookies as controlled by the UGP website after the browser moves into a third-party flow.
5. Analytics and advertising
UGP can load a configured analytics provider for aggregate website traffic, page views, referrers, browser data, and country-level traffic reports. The provider is loaded only when the required production environment values are present and you explicitly accept optional analytics.
UGP does not add advertising cookies, retargeting pixels, or marketing trackers in this website source. If those tools are added later, this page must be updated with the provider, purpose, storage type, retention, consent behavior, and opt-out route.
6. Managing cookies
You can clear or block cookies in your browser settings. Blocking necessary cookies may prevent sign-in, account pages, billing pages, and protected routes from working.
Use the controls below to accept optional analytics or return to necessary-only cookies. Returning to necessary-only prevents the website from loading optional analytics on subsequent page views. Necessary cookies may still be used because they are required for the service.
7. Changes
UGP may update this Cookie Policy when authentication, billing, analytics, provider, or account behavior changes.
The updated date should change when material cookie or storage behavior is added, removed, or meaningfully changed.