Privacy Policy

Builder Hub is an independent community portal for Bitget builders. It is built and operated by the Builder Hub community team, not by Bitget.

Builder Hub does not accept deposits, execute trades or hold funds or crypto assets. References to Bitget reflect the community’s connection with Bitget and do not mean that Bitget operates this website.

This policy applies to visitors, builders and invited guests. Reading full community posts, including Stories, Trade Talk and shared post links, requires sign-in. Access is managed by the community team. General information about Builder Hub, selected story previews, sign-in pages and this policy remain available to visitors.

We process builder records provided by administrators, along with information you provide or generate while using Builder Hub.

Builder profile

Your UID, Lark ID, display name, avatar, team, role, access status and badges. Builder records may also include your country, gender, date of birth and public social media handles where provided.

Builder account

Your Builder Hub identifier, a one-way hash of your Builder Hub password and authentication records used to manage sign-in and access.

Guest account

Guest account passwords may be accessible to authorized administrators, including after the password has been changed.

Community activity

Posts, comments, likes, bookmarks, follows, notifications, course progress, campaign submissions, reward records, prediction entries and community points activity.

Support and live features

Support tickets, replies, chat messages and livestream poll votes. If you choose to broadcast, content from your microphone, camera or shared screen is transmitted to participants in the live session.

AI features

Messages, attachments, conversation history and memories used by Brok to respond to you. Memories may be saved automatically from conversations or added by you. Relevant context may include your Builder Hub profile and community activity.

Technical information

Session and last-active information, request details, and security or error logs. Hosting and delivery services may process IP addresses and browser or device information.

We use your display name to identify your account in the community, check that the name is available and create your profile address. Your display name is saved to your Builder Hub profile. Once set, a builder display name can be changed by contacting an administrator.

We use this information to manage access, provide profiles and community features, review campaign participation, track rewards, respond to support requests and protect Builder Hub against misuse.

Optional features use the information needed to provide them, such as AI conversation context, translation text or livestream content. Country and builder records may also be combined to show public community totals. These totals do not identify individual builders by location.

Full community posts, comments and profile pages require sign-in. Signed-in builders and invited guests may see your display name, avatar, Lark ID, team, role, country, date of birth, badges, social links and contribution statistics where available. Your full UID is shown in profile details only to you, Lead Builders, Managers and Tech Leads. Profile addresses may include the last four UID digits. Account identifiers are also used in internal site data. Sharing a post link does not give someone access without signing in. Selected story previews and testimonials, including featured names and avatars, may appear on the homepage.

Authorized community administrators can access information needed to operate Builder Hub, review campaigns and reward records, and handle support or security issues. Access depends on their role and responsibilities.

Uploaded images and videos may still be accessible to anyone with their direct media link. Do not include confidential information in posts, comments or uploaded media.

We use external services to operate Builder Hub. Depending on the features you use, these services may process the following information:

• Hosting and data storage: profile details, community content, AI conversations and technical information needed to operate Builder Hub.
• Administration and forms: builder profiles, applications, campaigns, submissions and reward records.
• Media services: images, videos and other media uploaded or used in community features.
• Live communication: audio, video, screen sharing and chat when you use livestream features.
• AI and search services: messages, attachments and relevant conversation, profile or community context when you use Brok or other AI features. Search queries may include information from your request.
• Translation services: post text sent when you request a translation.

These providers may process information on systems outside your country and under their own terms and privacy practices. Third-party links and embedded content, including application forms, are handled by the relevant third-party service. Do not include passwords or other sensitive information in uploads, AI prompts or support messages.

When you are signed in, your selected language and light or dark mode are also saved to your account so they can be restored in another browser or on another device. Open tabs in the same browser share these preferences through browser storage.

Cookies help keep you signed in. Browser storage remembers your language, theme, dismissed notices and cached community data. Some cached information is cleared when you sign out.

You can clear cookies and browser storage through your browser settings. Doing so may sign you out or reset your preferences. Builder Hub does not use advertising tracking pixels. Third-party services, media or links may use their own cookies and browser storage.

We may retain display-name reservations and previous profile-address identifiers to prevent duplicate names or the reassignment of old profile links to another account. An old profile address does not necessarily remain accessible.

We keep information for as long as it is needed to operate Builder Hub, provide support, maintain security, manage community activities or resolve disputes. Community content generally remains until you or an authorized moderator removes it.

Each notification is scheduled for removal 60 days after it is received. Livestream chat messages are scheduled for removal after 12 hours and livestream poll votes after 48 hours. Removal may take additional time to complete. You can also clear notifications yourself.

Other information may have different retention periods. Removing or disabling access to Builder Hub does not immediately delete historical posts, submissions, reward records or support messages. Service provider logs and backups may also have separate retention periods.

You can change your language using the language selector. Contact an administrator if your builder display name needs to be corrected or changed.

You can edit available profile fields, delete your own posts or comments where supported, clear notifications and change your password. Brok also provides controls for saved conversations and memories.

To ask about your information or request access, a copy, correction or deletion, open a Support ticket. We may need to verify your identity. If you cannot sign in, contact the admin through your existing Lark contact.

We may retain information when needed to operate Builder Hub, maintain security, keep reward records or resolve disputes. Requests are reviewed based on these needs and any applicable requirements.

We use security safeguards, sign-in checks and access permissions to protect Builder Hub and its restricted features.

No online service can guarantee complete security. Report suspicious activity or unauthorized access to the community team. Do not share invitation links or sign-in credentials with others.

For privacy questions or requests related to your information, use Support. If you cannot access Builder Hub, contact the admin through your existing Lark contact. Questions about eligibility, campaigns or rewards should be directed to the relevant community team.

We may update this policy when Builder Hub or our information practices change. The date at the top shows when this policy was last updated. Significant changes may also be communicated through Builder Hub.