VELORIA HUB/PRIVACY / 02
PRIVACY / 02

Privacy Policy

What information may be received through sign-in and security checks, and how it is used by Veloria Hub.

VELORIA HUBLAST UPDATED · 12 OCT 2026READING TIME · 2 MIN
AT A GLANCE

Profile details may come from your chosen sign-in provider. Security checks may process limited network metadata.

Section 01

Information received from sign-in

When you sign in through an available OAuth provider, Veloria Hub may receive basic profile information returned by that provider, such as your account ID, display name, email address, avatar, and provider name.

The information available depends on the provider and the permissions involved in the sign-in flow.

Section 02

How information is used

This information is used to authenticate you, maintain your dashboard session, and associate the session with the account you used to sign in.

Security-related data may also be processed when needed to check access or validate a security challenge.

Section 03

Sessions and tokens

Authentication uses a secure, HTTP-only session cookie. OAuth tokens are exchanged on the server and are not displayed to the dashboard.

Keep your device and account secure, and avoid sharing a signed-in session with anyone else.

Section 04

Security verification

If a security or anti-bot challenge is shown, the provider may process IP address or network metadata and related technical information needed to assess the challenge.

The provider's own privacy policy explains how it handles information processed by its service.

Section 05

Third-party providers

Veloria Hub may use third-party providers for sign-in and security verification. When you interact with one of those services, its own privacy policy and terms may also apply.

Veloria Hub does not control the privacy practices of those providers.

Section 06

Security and limitations

The sign-in flow is designed to keep OAuth tokens on the server and use an HTTP-only session cookie. No website or online service can guarantee that every transmission or system will always be free from risk.

Do not send passwords, session cookies, or private authentication tokens to support channels.

Section 07

Changes and questions

This policy may be updated when the service or its sign-in and verification flows change. The latest version will be published on this page.

If you have a question about account information or privacy, use the support channel provided by Veloria Hub. You can return to the main site for current service information.

Return to Veloria Hub