Privacy
HUB account and wallet
The HUB uses your Terra Classic address and a signature requested through Keplr to authenticate access. The site does not request your recovery phrase or private key. Member records include the wallet address, chosen profile (name and avatar), role, access status and dates, and participation, points and referral information used by the HUB. Transaction references are used for access and points checks.
Contributions and conversations
Posts, replies, drafts, attachments, favourites, notifications and reports are stored to provide HUB features. Posts and replies are visible according to HUB access rights. Private conversations and attachments are restricted to authorised participants with active access; expiry is checked. This is not an end-to-end encrypted messaging service.
Sessions and preferences
Session cookies maintain HUB and administrator sign-ins. The rv_lang cookie remembers the language for one year. The connected wallet address is also kept in browser session storage to track the Keplr connection.
Security and logs
Session, signature and authorisation checks protect access. The administration log records the administrator, action, date and IP address. Server logs may record requests, errors and IP addresses depending on hosting configuration. Authorised administrators and operators can access the data needed for their tasks.
Translation and external services
When translation is used, public page text may be sent to DeepL. The HUB uses a LibreTranslate service configured by the operator: displayed text, including contributions and conversations being viewed, may be processed and stored in a translation cache. Keplr manages the wallet in your browser. Terra Classic queries use services including PublicNode and Binodes; market and validator data may come from CoinGecko and Valopers. Blockchain queries may include wallet addresses and transaction references. On-chain data is public and its deletion is not controlled by the site.
Retention and requests
The cleanup provided for expired private conversations deletes their records, messages and resources when it runs. This does not guarantee simultaneous removal from translation caches, backups or logs. The project has no general automatic purge of all other HUB records. The operator must specify actual retention periods below. You can contact the operator to request access, correction or deletion of your data and exercise other applicable rights; you can also contact the competent data protection authority.
Additional information
The operator still needs to specify the legal bases, retention periods, recipients and any international transfers.