1.1 These NFT Enrolment Terms and Conditions govern NFT Enrolment in connection with the Version 1 Closure, the Pollen Reset, the transition from SpringBees Version 1 to SpringBees Version 2, and NFT Allocation.
1.2 These Terms apply to each User who accesses, participates in, submits, confirms or completes any part of NFT Enrolment through the Official SpringBees Interface.
1.3 By completing the acceptance, confirmation or enrolment process made available through the Official SpringBees Interface, the User confirms that the User has read, understood and accepted these Terms. If the User does not agree to these Terms, the User must not proceed with NFT Enrolment.
1.4 These Terms supplement any general SpringBees terms, SBees terms, Spring Development Group rules, Spring Development Bank rules, platform rules, privacy terms, community rules, campaign rules, operational procedures, directives, policies or other applicable requirements issued or adopted from time to time.
1.5 In the event of inconsistency, these Terms shall prevail in respect of NFT Enrolment, Version 1 Closure, Pollen Reset, the transition to SpringBees Version 2, NFT Allocation and NFT Claim, unless a Relevant Spring Entity determines that another Applicable Framework requirement must prevail.
1.6 These Terms do not create any investment, banking, deposit, savings, lending, payment, securities, custody, trust, agency or advisory relationship between the User and any Relevant Spring Entity, unless expressly stated in separate written terms issued by an authorised Relevant Spring Entity.
In these Terms, unless the context otherwise requires:
Account means a registered SpringBees user account.
Applicable Framework means the rules, orders, regulations, directives, policies, platform terms, operational procedures, governance requirements and internal requirements issued, adopted or applied from time to time by Spring Development Group, SBees, SpringBees, Spring Development Bank or any relevant authorised body within the Spring Development Ecosystem.
Bee ID means the unique SpringBees identifier generated for a User.
Criteria and Highlights means the NFT enrolment criteria, eligibility notes, key information, risk notices, transition information and Pollen Reset information made available to Users through the Official SpringBees Interface for information and acceptance in connection with NFT Enrolment.
Enrolment or NFT Enrolment means the process by which an eligible User registers or confirms participation to be considered for NFT Allocation.
Enrolment End Date means the final date and time by which NFT Enrolment must be completed, as announced through an Official Channel.
Enrolment Start Date means the date and time on which NFT Enrolment begins, as announced through an Official Channel.
Issuer means the Spring Development entity responsible for issuing, allocating, distributing or making available the NFT, as determined or announced by SpringBees, SBees, Spring Development Group, Spring Development Bank or another Relevant Spring Entity.
NFT means a non-fungible token or other digital collectible issued, allocated, distributed or made available by or on behalf of the Issuer in connection with NFT Enrolment.
NFT Allocation means the process by which NFTs are allocated, distributed, claimed, issued or otherwise made available to eligible Users who have completed Successful Enrolment, subject to these Terms.
NFT Claim means any process, step or action required for a User to claim, receive, access or redeem an NFT following NFT Allocation.
Official Channel means any official communication channel designated or used by SpringBees, SBees, Spring Development Group, Spring Development Bank or another Relevant Spring Entity for announcements, notices, instructions or support, including the Official SpringBees Interface, SpringBees Version 2, official community channels, official Facebook Page, Telegram channels, email, web application or any other official channel designated from time to time.
Official SpringBees Interface means the official SpringBees application, web application, Telegram interface, transition page, enrolment page, review page or other official digital interface designated by SpringBees for NFT Enrolment, Version 1 Closure, the transition to SpringBees Version 2, Pollen Reset, NFT Allocation, NFT Claim or related User actions.
Pollen means the Pollen points, rewards, balances or other in-platform units earned or held by Users in SpringBees Version 1. For the purposes of these Terms, Pollen refers only to SpringBees Version 1 Pollen and does not include Pollen Plus or any other successor points, credits, rewards, balances or units introduced in SpringBees Version 2, unless expressly stated otherwise by a Relevant Spring Entity.
Pollen Reset means the reset of all SpringBees Version 1 Pollen balances to zero following the closure, migration or transition of SpringBees Version 1.
Relevant Spring Entity means Spring Development Group, SBees, SpringBees, Spring Development Bank, the Issuer, or any authorised affiliate, administrator, operator, service provider, representative, successor or assignee involved in operating SpringBees, administering NFT Enrolment, verifying eligibility, resetting Pollen, managing Version 1 Closure, supporting the transition to SpringBees Version 2, allocating NFTs, handling NFT Claim or handling related matters.
Review Function means any button, link, page, prompt or feature made available through the Official SpringBees Interface that allows Users to review information, access transition details or be redirected to SpringBees Version 2 or another official page designated by SpringBees.
SBees means the SpringBees-related operating, administrative or platform entity, project or team responsible for supporting, managing or administering SpringBees, as applicable.
SDB or Spring Development Bank means Spring Development Bank and any relevant system, interface, identifier, process or service made available by or through Spring Development Bank.
SDB UID means the Spring Development Bank unique identifier provided or made available through Spring Development Bank channels.
SpringBees means the SpringBees platform, including SpringBees Version 1, SpringBees Version 2, the Official SpringBees Interface, and related SpringBees services, features, records and user-facing processes.
SpringBees Version 1, Version 1 or SpringBees V1 means the SpringBees tap game operated through Telegram.
SpringBees Version 2, Version 2 or SpringBees V2 means the SpringBees web application or successor platform introduced following the transition from SpringBees Version 1.
Spring Development Ecosystem means Spring Development Group, SBees, SpringBees, Spring Development Bank and their related platforms, projects, products, services, digital assets, operational processes, authorised channels and supporting infrastructure.
Spring Development Group means the relevant Spring Development group, project, organisation, ecosystem or authorised body responsible for, connected with or supporting SpringBees, SBees, Spring Development Bank or related digital products, as applicable.
Successful Enrolment means completion of NFT Enrolment in accordance with these Terms and the Applicable Framework, as determined by SpringBees based on its internal system records.
Terms means these SpringBees NFT Enrolment Terms and Conditions, as amended, updated, supplemented or replaced from time to time.
Third-Party Platform means any external platform, service, application, wallet, blockchain, network, marketplace, hosting provider, analytics provider, messaging platform, payment service, identity service, communication channel or other third-party infrastructure used in connection with SpringBees, NFT Enrolment, NFT Allocation or NFT Claim.
Transition Period means the period during which SpringBees Version 1 remains available for transition purposes after the SpringBees Version 1 tap game is stopped in Telegram. Unless announced otherwise through an Official Channel, the Transition Period shall be 30 days.
User, you or your means a person who holds, accesses, uses or seeks to use an Account, or who participates or seeks to participate in NFT Enrolment.
Version 1 Closure means the stopping, closure, shutdown, withdrawal, migration or discontinuation of SpringBees Version 1, including the point at which SpringBees Version 1 is no longer accessible through Telegram.
we, us or our means SpringBees and, where the context requires, any Relevant Spring Entity responsible for the relevant function, process, obligation, decision, communication or action under these Terms.
3.1 A User shall be deemed to have accepted these Terms when the User completes the acceptance, confirmation or enrolment process made available through the Official SpringBees Interface.
3.2 The method by which a User accepts these Terms, confirms the Criteria and Highlights, submits or confirms an SDB UID, or completes NFT Enrolment shall be determined through the relevant Official SpringBees Interface from time to time.
3.3 A Relevant Spring Entity may require the User to provide electronic confirmation, platform confirmation, checkbox acceptance, button confirmation, account confirmation, SDB UID confirmation or any other form of digital acknowledgement considered appropriate.
3.4 The User must not proceed with NFT Enrolment unless the User has read, understood and accepted these Terms and the Criteria and Highlights.
3.5 A Relevant Spring Entity may require the User to re-confirm or re-accept these Terms where these Terms are updated, corrected, supplemented or republished.
4.1 To be eligible for NFT Enrolment, a User must satisfy all of the following requirements:
(a) the User must have registered an Account before the Enrolment Start Date;
(b) the Account must not be suspended, restricted, deactivated, blacklisted, duplicated, fraudulent or otherwise disqualified;
(c) the User must complete NFT Enrolment before the Enrolment End Date;
(d) the User must accept the Criteria and Highlights;
(e) the User must accept these Terms;
(f) the User must provide, confirm or link a valid SDB UID where required;
(g) the User must comply with the applicable platform instructions; and
(h) the User must satisfy any verification, security, anti-fraud, operational or technical checks required by a Relevant Spring Entity.
4.2 Any Account registered on or after the Enrolment Start Date shall not be eligible for NFT Enrolment unless a Relevant Spring Entity expressly decides otherwise.
4.3 Eligibility shall be determined based on internal system records. Screenshots, User statements, unofficial records, third-party records, community comments or external materials shall not override internal system records unless accepted at the discretion of a Relevant Spring Entity.
4.4 Eligibility for NFT Enrolment does not guarantee NFT Allocation, receipt of an NFT, successful NFT Claim, future utility, financial value or any other benefit.
4.5 A Relevant Spring Entity may reject, suspend, freeze, review or disqualify any Account or Enrolment where it considers that the Account does not satisfy the eligibility requirements or where the integrity of NFT Enrolment may be affected.
5.1 NFT Enrolment does not require any minimum Pollen balance.
5.2 NFT Enrolment does not require any minimum number of resource items, hive level, completed tasks, in-game assets, activity level, tap count, referral count or other Version 1 gameplay criteria.
5.3 Users are not required to enter, declare, allocate, stake, lock, spend, burn, transfer or provide any Pollen amount for the purpose of NFT Enrolment.
5.4 Account records, registration records, SDB UID records, Enrolment records, anti-fraud records and other platform records may be used to determine whether a User is eligible.
5.5 The absence of a minimum Pollen requirement does not prevent the application of verification, security, duplicate-account, technical, abuse-prevention or anti-fraud checks.
6.1 Each NFT Enrolment must be linked to one valid SDB UID, unless an alternative process is expressly announced through an Official Channel.
6.2 One SDB UID may be used for one NFT Enrolment submission only.
6.3 A User may not use, copy, borrow, sell, purchase, share, rent, transfer or submit another person’s SDB UID.
6.4 Where a User submits or confirms an SDB UID, the User confirms that:
(a) the SDB UID is accurate and valid;
(b) the User is authorised to use that SDB UID;
(c) the SDB UID is not already linked to another Account for NFT Enrolment;
(d) the SDB UID has not been obtained by fraud, impersonation, unauthorised access or breach of platform rules; and
(e) the User understands that incorrect SDB UID submission may result in failed, frozen, delayed, rejected or disqualified Enrolment.
6.5 Once NFT Enrolment has been successfully completed, the submitted SDB UID may not be changed unless correction is allowed at the discretion of a Relevant Spring Entity.
6.6 If the same SDB UID is submitted by more than one Account, one or more affected submissions may be rejected, frozen, investigated or disqualified.
6.7 If an SDB UID is invalid, unverifiable, incorrectly entered, inactive, duplicated or otherwise suspicious, the Enrolment function may be temporarily frozen.
6.8 During a freeze, the Enrolment function may be disabled and a countdown or other status notice may be displayed.
6.9 Where the Enrolment function is frozen due to invalid SDB UID submission, a freeze period of four hours or such other period as considered appropriate may be applied.
6.10 The User is responsible for obtaining the correct SDB UID from the official Spring Development Bank interface. No Relevant Spring Entity shall be responsible for Enrolment failure caused by use of an incorrect, incomplete, inactive, duplicated or unauthorised SDB UID.
7.1 NFT Enrolment must be completed through the Official SpringBees Interface within the period announced through an Official Channel.
7.2 The User is responsible for ensuring that all information submitted, confirmed or linked during NFT Enrolment is complete, accurate, current and authorised, including any SDB UID or Account information required.
7.3 The format, sequence, content and technical requirements of NFT Enrolment may be determined from time to time, including any account verification, SDB UID confirmation, acceptance confirmation, eligibility check, countdown, warning message, frozen status, inactive function, review page or other system feature.
7.4 A Relevant Spring Entity may prevent, suspend, freeze or reject NFT Enrolment where:
(a) required information is missing, incomplete, inaccurate or invalid;
(b) the Account is not eligible;
(c) the SDB UID is invalid, duplicated, inactive, unauthorised or unverifiable;
(d) the User has not completed the required platform confirmations;
(e) the Enrolment End Date has passed;
(f) the Account or submission is subject to review; or
(g) technical, security, verification, fraud-prevention, compliance or operational reasons require such action.
7.5 The User is solely responsible for completing NFT Enrolment before the Enrolment End Date. No Relevant Spring Entity is obliged to extend the Enrolment End Date for any User.
7.6 Incomplete, incorrect, late, duplicated, manipulated, automated, suspicious or unauthorised submissions may be rejected.
7.7 Internal system records shall be the primary evidence of whether NFT Enrolment was submitted, completed, accepted, rejected, frozen or disqualified.
8.1 Successful Enrolment means that the User has completed NFT Enrolment in accordance with these Terms and the Applicable Framework, and that the submission has not been rejected, frozen, reversed or disqualified.
8.2 Only Users with Successful Enrolment shall be considered for NFT Allocation.
8.3 Successful Enrolment does not guarantee receipt of an NFT.
8.4 Further checks may be conducted after Successful Enrolment. If it is later determined that a User was not eligible or breached these Terms, the Enrolment may be cancelled, NFT entitlement may be withdrawn, NFT Allocation may be refused, NFT Claim may be blocked, or such other action as considered appropriate may be taken.
8.5 Any display of Successful Enrolment is subject to final verification, internal system records and anti-fraud review.
9.1 If a User does not complete NFT Enrolment before the Enrolment End Date, the User shall not be entitled to participate in NFT Allocation.
9.2 Enrolment may be treated as incomplete or failed where:
(a) the User does not accept the Criteria and Highlights;
(b) the User does not accept these Terms;
(c) the User does not submit or confirm a valid SDB UID where required;
(d) the SDB UID is duplicated, invalid, inactive or unverifiable;
(e) the Account was registered on or after the Enrolment Start Date;
(f) the Account is suspended, restricted, deactivated, duplicated or disqualified;
(g) the submission is not completed before the Enrolment End Date;
(h) the User uses unofficial links, unauthorised tools, bots, scripts or manipulation methods; or
(i) a Relevant Spring Entity reasonably determines that the submission should not be accepted.
9.3 No Relevant Spring Entity shall be responsible for failed or incomplete Enrolment caused by User error, poor internet connection, device problems, Telegram issues, SDB account issues, email verification issues, Third-Party Platform issues, wrong SDB UID, missed deadline or failure to follow instructions.
10.1 Following Version 1 Closure, all SpringBees Version 1 Pollen balances shall be reset to zero.
10.2 The Pollen Reset applies to all Users, whether or not they complete NFT Enrolment.
10.3 A User who does not complete NFT Enrolment shall still have their Pollen reset to zero and shall not be entitled to NFT Allocation.
10.4 Users are not required to provide a Pollen amount for NFT Enrolment because all Pollen balances will be reset to zero in connection with Version 1 Closure and the transition to SpringBees Version 2.
10.5 Pending, unclaimed, incomplete, delayed, disputed, reversed, rejected, failed or undistributed Pollen as at Version 1 Closure may be excluded and shall not be carried forward unless expressly announced otherwise through an Official Channel.
10.6 Pollen has no guaranteed cash value, redemption value, exchange value, asset value or future platform value unless expressly stated otherwise by a Relevant Spring Entity.
10.7 No User shall be entitled to compensation, refund, replacement, credit, damages or other remedy as a result of the Pollen Reset, except where a Relevant Spring Entity expressly decides otherwise.
11.1 When the SpringBees Version 1 tap game is stopped in Telegram, Users may be shown a single transition page.
11.2 The transition page may display a Review Function.
11.3 Upon selecting the Review Function, the User may be redirected to SpringBees Version 2 or such other official page as may be designated through the Official SpringBees Interface.
11.4 SpringBees Version 1 shall remain available for the Transition Period for transition purposes, unless announced otherwise through an Official Channel.
11.5 After the Transition Period, SpringBees Version 1 shall no longer be accessible through Telegram.
11.6 The User is responsible for reviewing all relevant information, completing NFT Enrolment, confirming SDB UID details, and taking any required action before the applicable deadlines.
11.7 The Transition Period may be modified, shortened, extended, suspended or terminated if required for technical, operational, security, platform, migration or project reasons.
12.1 SpringBees Version 2 is intended to provide a fresh SpringBees experience following the transition from SpringBees Version 1.
12.2 Access to SpringBees Version 2 may be made available through the Review Function, official SpringBees links or other Official Channels.
12.3 A User’s access to SpringBees Version 2 does not by itself mean that the User has completed NFT Enrolment or is entitled to receive an NFT.
12.4 Users may be required to complete registration, login, verification, profile setup, SDB UID confirmation, email verification or other platform steps in order to access or use SpringBees Version 2 features.
12.5 SpringBees Version 2 features, including missions, referrals, rewards, Pollen Plus, HoneyDrops, partner rewards, wallet functions, loyalty status, profile functions and other services, may be introduced, amended, restricted or removed in accordance with applicable platform rules.
13.1 NFT Allocation shall be conducted only amongst Users who satisfy the eligibility requirements and complete Successful Enrolment.
13.2 NFT Allocation shall be subject to:
(a) the number of NFTs issued or made available;
(b) Successful Enrolment;
(c) verification and anti-fraud checks;
(d) technical availability;
(e) User compliance with these Terms;
(f) issuer, wallet, platform, blockchain and operational requirements; and
(g) any further criteria, process, schedule or instructions announced through an Official Channel.
13.3 No minimum Pollen balance, resource item, hive level, completed task count or in-game item requirement shall apply to NFT Enrolment.
13.4 Where the number of eligible and successfully enrolled Users exceeds the number of available NFTs, NFTs may be allocated according to such allocation method as is considered appropriate, provided that the allocation process shall not impose a minimum Pollen or item requirement unless expressly announced through an Official Channel.
13.5 Different NFTs, NFT categories, NFT ranks, NFT designs, NFT metadata, claim rights or benefits may be allocated to different Users, provided that such allocation is determined in accordance with the announced process or internal allocation controls.
13.6 A Relevant Spring Entity is not obliged to disclose the full details of fraud detection methods, security checks or internal allocation controls where disclosure may compromise the integrity of NFT Allocation.
13.7 NFT Allocation may be delayed, modified, cancelled or re-run if technical errors, fraud, duplicate submissions, data corruption, platform failures or other issues affecting fairness or integrity are identified.
14.1 Successful Enrolment allows a User to be considered for NFT Allocation. It does not guarantee that the User will receive an NFT.
14.2 No statement, screenshot, countdown, user interface display, eligibility indicator, community announcement, support message or system status shall constitute a binding guarantee of NFT receipt unless expressly confirmed in final allocation records.
14.3 Errors in eligibility displays, Enrolment status, NFT status, Pollen records, SDB UID records, allocation records or other user-facing information may be corrected at any time.
14.4 No Relevant Spring Entity shall be liable for any User expectation, reliance, opportunity loss, perceived loss, market loss or disappointment arising from non-allocation of an NFT.
15.1 NFT Claim, redemption, distribution, delivery, wallet connection or receipt instructions shall be announced through an Official Channel.
15.2 Users must follow official instructions only. No Relevant Spring Entity shall be responsible for loss caused by fake websites, phishing links, impersonators, unofficial groups, unauthorised messages, malicious links or third-party scams.
15.3 Users are responsible for maintaining access to their Account, Telegram account, SDB account, email, wallet, device, private keys, seed phrases and any other credentials or accounts required for NFT Claim or receipt.
15.4 No Relevant Spring Entity shall be responsible for loss of private keys, seed phrases, wallet access, account credentials, email access, device access or Third-Party Platform access.
15.5 If a User fails to complete NFT Claim within the announced claim period, the NFT may be treated as forfeited, unclaimed, expired or otherwise unavailable.
15.6 NFT delivery may be subject to blockchain, wallet, marketplace, network, smart contract, metadata, gas fee, Third-Party Platform or technical limitations.
15.7 NFT delivery may be refused, paused or delayed where a User’s Account, SDB UID, wallet or claim activity is under review.
16.1 A Relevant Spring Entity may reject, freeze, suspend, investigate, cancel, reverse or disqualify any Account, Enrolment, NFT Claim or NFT Allocation if it reasonably suspects or determines any of the following:
(a) duplicate Accounts;
(b) duplicate SDB UID usage;
(c) use of another person’s SDB UID;
(d) fake, invalid, inactive, stolen or unauthorised SDB UID;
(e) automated activity, bots, scripts, crawlers, emulators or unauthorised tools;
(f) manipulation of Pollen, tasks, referrals, hive status, resource items or Account activity;
(g) exploitation of bugs, vulnerabilities, loopholes, incorrect rewards, technical errors or system defects;
(h) false, misleading, incomplete or inconsistent information;
(i) account sharing, account sale, account transfer, identity masking or impersonation;
(j) suspicious device, IP, network, behavioural or transaction patterns;
(k) breach of these Terms or any applicable platform rules;
(l) conduct that undermines the fairness, security, reputation or integrity of SpringBees; or
(m) any other conduct considered abusive, dishonest, inappropriate or harmful.
16.2 Disqualification may occur before or after Successful Enrolment, before or after NFT Allocation, and before or after NFT Claim.
16.3 Reasons or detailed evidence for disqualification may be withheld where disclosure may compromise fraud prevention, security controls, platform integrity or other Users’ rights.
16.4 A User may be permanently restricted from future campaigns, rewards, NFT allocations, Pollen activities or SpringBees services where serious abuse or fraud is identified.
17.1 The User is responsible for:
(a) reading these Terms and the Criteria and Highlights;
(b) completing Enrolment before the Enrolment End Date;
(c) submitting accurate Account and SDB UID information;
(d) ensuring email, SDB, Telegram, wallet and platform access;
(e) using Official Channels only;
(f) checking Official Channels for announcements;
(g) maintaining device, internet, account and wallet security;
(h) avoiding scams, phishing links, impersonators and unofficial support channels;
(i) paying any network, wallet, transaction, claim or Third-Party Platform fees where applicable; and
(j) seeking independent professional advice where the User considers it necessary.
17.2 The User shall not use NFT Enrolment for unlawful, fraudulent, deceptive, abusive, automated, commercial resale or manipulative purposes.
17.3 The User shall not attempt to interfere with, reverse engineer, overload, disrupt, scrape, bypass, exploit or manipulate SpringBees, the Official SpringBees Interface, SDB UID validation, NFT Enrolment, NFT Allocation or NFT Claim.
18.1 NFT Enrolment, the transition page, the Review Function, the Enrolment function, eligibility displays, countdowns and related features are provided on an “as is” and “as available” basis.
18.2 No Relevant Spring Entity guarantees uninterrupted, error-free, timely, secure, compatible or continuous access to:
(a) SpringBees Version 1;
(b) Telegram;
(c) SpringBees Version 2;
(d) the transition page;
(e) the Review Function;
(f) the Enrolment function;
(g) SDB UID validation;
(h) NFT Claim pages;
(i) wallets;
(j) blockchains;
(k) marketplaces; or
(l) any Third-Party Platform.
18.3 Any feature may be suspended, disabled, restricted, modified or withdrawn where required for maintenance, security, operational reasons, migration, fraud prevention, technical failure, third-party dependency or project requirements.
18.4 No Relevant Spring Entity shall be responsible for loss caused by network congestion, device incompatibility, Telegram downtime, wallet failure, blockchain delay, smart contract issue, marketplace restriction, internet disruption, Third-Party Platform failure or User-side technical error.
19.1 SpringBees may rely on Third-Party Platforms in connection with SpringBees, NFT Enrolment, NFT Allocation, NFT Claim, communications, hosting, analytics, wallet access, blockchain transactions, marketplace display or support.
19.2 No Relevant Spring Entity controls Third-Party Platforms and no Relevant Spring Entity shall be responsible for their acts, omissions, downtime, restrictions, errors, security incidents, fees, policies or service changes.
19.3 Users may be required to accept third-party terms when accessing wallets, blockchains, marketplaces, Telegram, SDB services or other external platforms.
19.4 Any issue between a User and a Third-Party Platform shall be handled directly between the User and that Third-Party Platform, unless a Relevant Spring Entity expressly decides to assist.
20.1 NFTs are digital items recorded or represented through blockchain or similar technology. Their availability, transferability, visibility, metadata, compatibility, utility and value may depend on third-party systems and technical conditions.
20.2 No Relevant Spring Entity guarantees that any NFT will:
(a) have monetary value;
(b) increase in value;
(c) retain value;
(d) be transferable;
(e) be tradable;
(f) be visible on any marketplace;
(g) have ongoing utility;
(h) be compatible with all wallets;
(i) remain accessible indefinitely; or
(j) be free from metadata, network, marketplace or smart contract limitations.
20.3 NFT Allocation is not an investment offer, financial promotion, deposit, savings product, loan, security, profit-sharing arrangement or guarantee of return.
20.4 The User participates at the User’s own risk and is responsible for deciding whether to participate in NFT Enrolment or complete NFT Claim.
21.1 Unless expressly stated otherwise, receipt of an NFT does not transfer ownership of SpringBees’ name, logo, brand, artwork, characters, designs, software, platform, content, trademarks or other intellectual property.
21.2 A User who receives an NFT receives only such rights as are expressly granted in relation to that NFT.
21.3 Users shall not use any NFT, SpringBees content, artwork, brand or materials in a manner that is misleading, unlawful, defamatory, offensive, commercial without authorisation or damaging to the reputation of any Relevant Spring Entity.
21.4 NFT-related metadata, artwork, benefits, display features or related platform features may be modified, updated, replaced, restricted or removed where required for technical, security, operational, brand or project reasons.
22.1 NFT Enrolment, NFT Allocation, NFT Claim, transition and Version 1 Closure information may be communicated through Official Channels.
22.2 Users must rely only on Official Channels and official links.
22.3 No Relevant Spring Entity shall be bound by unofficial statements, User comments, community speculation, third-party summaries, screenshots, translations, rumours or unauthorised communications.
22.4 Where there is inconsistency between the Official SpringBees Interface and these Terms, the correct interpretation may be determined in good faith, taking into account internal system records, official project records and announced rules.
23.1 By participating in NFT Enrolment, the User acknowledges that information may be collected, used, verified, stored, reviewed and processed where reasonably required for Enrolment, transition, allocation, claim, audit, support, reporting, security, fraud prevention and operational purposes.
23.2 Such information may include Account details, Bee ID, SDB UID, email, nickname, registration date, Pollen records, task records, referral records, activity records, device information, technical logs, IP-related information, claim status, wallet information where applicable, support records and communication records.
23.3 Relevant information may be shared with affiliates, service providers, technical partners, SDB-related systems, blockchain or wallet service providers, advisers, auditors or support providers where reasonably required for NFT Enrolment, NFT Allocation, platform transition, fraud prevention or service operation.
23.4 Records may be retained as reasonably required for audit, dispute handling, fraud prevention, reporting, operational or administrative purposes.
24.1 A Relevant Spring Entity may correct any error, omission, display issue, calculation issue, eligibility issue, Pollen record issue, SDB UID issue, NFT Allocation issue, user interface issue, countdown issue or technical defect at any time.
24.2 If an error results in an incorrect indication of eligibility, Successful Enrolment, NFT entitlement, Pollen balance or NFT Allocation, the relevant status or record may be reversed, amended, corrected or cancelled.
24.3 No User shall be entitled to benefit from an obvious error, system defect, duplicated record, incorrect reward, technical issue or unauthorised allocation.
25.1 NFT Enrolment rights are personal to the eligible User and relevant Account.
25.2 A User may not sell, assign, transfer, sublicense, pledge, lend, rent, exchange or otherwise deal with any Enrolment status, NFT entitlement, allocation expectation, claim right, SDB UID linkage or related benefit.
25.3 Any attempted transfer or sale of Enrolment rights may result in disqualification.
26.1 The User is solely responsible for any tax, duty, fee, charge, network fee, gas fee, wallet fee, marketplace fee, exchange fee, internet fee, device cost or other cost arising from or connected with NFT Enrolment, NFT Claim, NFT receipt, NFT transfer or NFT use.
26.2 No Relevant Spring Entity provides tax, legal, financial, investment, accounting or professional advice to Users through these Terms.
26.3 Users should obtain independent advice where they consider it appropriate.
27.1 No Relevant Spring Entity shall be liable for any loss arising from or connected with:
(a) failure to complete Enrolment;
(b) incorrect SDB UID submission;
(c) duplicate or invalid SDB UID;
(d) Pollen Reset;
(e) non-allocation of NFT;
(f) failed NFT Claim;
(g) User error;
(h) loss of account, wallet, email, Telegram or SDB access;
(i) phishing, scams, impersonation or unofficial links;
(j) Third-Party Platform failure;
(k) blockchain, wallet, smart contract, metadata or marketplace issues;
(l) technical interruption or delay;
(m) correction of errors;
(n) disqualification or fraud prevention action;
(o) change, suspension or cancellation of the Enrolment or allocation process; or
(p) loss of profit, loss of opportunity, loss of value, loss of goodwill, indirect loss, consequential loss or speculative loss.
27.2 Nothing in these Terms shall exclude liability which cannot be excluded under the Applicable Framework.
28.1 The User shall be responsible for and shall indemnify each Relevant Spring Entity against losses, claims, costs, expenses, liabilities, damages and proceedings arising from:
(a) the User’s breach of these Terms;
(b) false, inaccurate or unauthorised information submitted by the User;
(c) misuse of another person’s SDB UID, Account, wallet or credentials;
(d) fraud, abuse, automation, manipulation or unlawful activity by the User;
(e) infringement of third-party rights;
(f) misuse of SpringBees intellectual property; or
(g) any claim brought by a third party in connection with the User’s participation in NFT Enrolment or NFT Claim.
29.1 If a User believes there is an issue with their Account, Enrolment, SDB UID, Pollen Reset, eligibility status, NFT Allocation, NFT Claim or any related matter, the User must contact SpringBees through the official support or dispute channel.
29.2 Support requests, complaints and disputes must be submitted within any timeframe announced through an Official Channel. Late, incomplete, misleading, abusive, duplicate, fraudulent or unofficial submissions may be rejected.
29.3 The User may be required to provide information, screenshots, Bee ID, SDB UID, Account details, device information, Telegram details, email records, transaction records or other materials to verify and assess the issue.
29.4 A dispute may be resolved, rejected, escalated, investigated, suspended or deferred where further verification, technical review, fraud review, compliance review or operational review is required.
29.5 Internal records shall prevail over screenshots, User statements, unofficial records, third-party messages, community comments, rumours or externally generated materials, unless such materials are accepted at the discretion of a Relevant Spring Entity.
29.6 The dispute and support process is intended to provide fair review and resolution. It does not guarantee reversal of disqualification, restoration of Pollen, extension of deadlines, NFT Allocation, NFT Claim, compensation, refund, credit or any other remedy.
30.1 These Terms, NFT Enrolment, Version 1 Closure, the transition to SpringBees Version 2, Pollen Reset, SDB UID verification, NFT Allocation, NFT Claim and all related matters shall be governed by and interpreted in accordance with the Applicable Framework.
30.2 These Terms shall be read consistently with the Spring Development Bank framework and any related rules, procedures or instructions applicable to Spring Development Bank, SpringBees, SBees, NFT-related activities, crypto-related activities, payment processing, digital products, platform operations and User participation.
30.3 If there is any inconsistency between these Terms and any mandatory rule, order, directive or internal governance requirement applicable to Spring Development Group, SpringBees, SBees, Spring Development Bank or another Relevant Spring Entity, these Terms may be interpreted, modified or applied in a manner consistent with such Applicable Framework.
30.4 Any complaint, disagreement, claim or dispute arising out of or in connection with these Terms, NFT Enrolment, SDB UID submission or verification, Version 1 Closure, the transition to SpringBees Version 2, Pollen Reset, NFT Allocation, NFT Claim, Account eligibility, disqualification, fraud review, technical issue or any related matter shall first be submitted through the official support or dispute channel designated by SpringBees.
30.5 The User must provide all information reasonably requested for the review of the dispute, including the User’s Bee ID, SDB UID, Account details, screenshots, transaction records, device information, email records, Telegram details or other supporting materials.
30.6 The dispute shall be reviewed in good faith based on internal system records, Account records, SDB UID records, Enrolment records, technical logs, anti-fraud records, platform records and any supporting information submitted by the User.
30.7 If the dispute is not resolved through the initial support review, the matter may be referred to internal escalation, management review, compliance review, technical review or any other internal review process considered appropriate.
30.8 If the dispute remains unresolved after internal review, the parties shall attempt to resolve the matter through good faith mediation or facilitated settlement discussions using a mediator, mediation panel, community dispute process, internal mediation process or other neutral dispute resolution process designated or accepted by a Relevant Spring Entity.
30.9 The parties shall participate in any mediation process in good faith and shall use reasonable efforts to resolve the dispute amicably.
30.10 Unless expressly determined otherwise, participation in a dispute review or mediation process shall not suspend, extend or delay any Enrolment End Date, Transition Period, NFT Allocation schedule, NFT Claim deadline, Pollen Reset, Account restriction, disqualification decision, fraud review action or platform operation.
30.11 Internal system records shall be the primary evidence for determining Account registration date, Enrolment status, SDB UID status, Pollen balance, Pollen Reset, eligibility, disqualification, NFT Allocation and NFT Claim status.
30.12 Nothing in this clause shall prevent a Relevant Spring Entity from taking immediate action where required to protect Users, SpringBees, the Spring Development Ecosystem, system integrity, fraud controls, security, intellectual property, digital assets, platform operations or NFT Allocation.
31.1 A Relevant Spring Entity may amend, suspend, cancel, delay, withdraw, extend, shorten, replace or terminate:
(a) these Terms;
(b) NFT Enrolment;
(c) the Enrolment Start Date;
(d) the Enrolment End Date;
(e) the Transition Period;
(f) NFT Allocation;
(g) NFT Claim;
(h) NFT benefits;
(i) SpringBees Version 1 access;
(j) SpringBees Version 2 access; or
(k) any related feature, process or announcement.
31.2 Such action may be taken for technical, security, operational, project, fraud prevention, Third-Party Platform, blockchain, wallet, issuer, business or other reasonable reasons.
31.3 Where practicable, material updates may be published through an Official Channel.
31.4 Continued participation after an update shall constitute acceptance of the updated Terms.
32.1 Notices and announcements may be made through Official Channels.
32.2 A notice shall be treated as received when made available through an Official Channel, whether or not the User actually reads it.
32.3 Users are responsible for checking Official Channels regularly during NFT Enrolment, the Transition Period, NFT Allocation and NFT Claim periods.
33.1 Headings are for convenience only and shall not affect interpretation.
33.2 Words in the singular include the plural and vice versa.
33.3 References to “including” shall be construed as “including without limitation”.
33.4 Any discretion given to a Relevant Spring Entity under these Terms may be exercised reasonably, in good faith, and with regard to the integrity, security and operation of the Spring Development Ecosystem.
33.5 If any part of these Terms is held to be invalid or unenforceable under the Applicable Framework, the remaining parts shall continue in effect.
33.6 Failure or delay by a Relevant Spring Entity to enforce any right shall not amount to a waiver of that right.
33.7 These Terms constitute the entire terms applicable to NFT Enrolment and supersede prior user-facing NFT enrolment terms, summaries, FAQs, screenshots and informal statements, except where expressly incorporated by a Relevant Spring Entity.
By completing the acceptance, confirmation or enrolment process made available through the Official SpringBees Interface, the User confirms that:
(a) the User has read, understood and accepted these Terms;
(b) the User has read, understood and accepted the Criteria and Highlights;
(c) NFT Enrolment has no minimum Pollen requirement;
(d) no resource item, hive level, completed task count or in-game item requirement applies to NFT Enrolment;
(e) only Accounts registered before the Enrolment Start Date are eligible;
(f) one SDB UID may be used for one NFT Enrolment only;
(g) all Pollen balances will be reset to zero following Version 1 Closure;
(h) the Pollen Reset applies whether or not the User completes NFT Enrolment;
(i) failure to complete NFT Enrolment means the User will not be entitled to NFT Allocation;
(j) Successful Enrolment does not guarantee receipt of an NFT;
(k) SpringBees Version 1 will cease to be accessible through Telegram after the Transition Period;
(l) submissions may be verified, rejected, frozen, corrected or disqualified in accordance with these Terms; and
(m) disputes shall be handled through the official support, internal review and mediation process described in these Terms.