Use current capabilities
The community is a sample preview and editor saves are local drafts; displays do not establish cloud publishing or service commitments.
Terms of service
Clear terms. Confident creation.
Paid services need confirmation
Pricing provides reference proposals and email inquiries; online payment and automatic subscriptions are not connected.
Statutory rights remain
Content responsibilities, feature limitations and dispute handling remain subject to applicable law, without inventing an operator or jurisdiction.
BLOCKCODE / TERMSPlease read the full document
1. Scope and acceptance
This draft concerns browsing the BlockCode website, account features, the visual Studio, community preview and related tools, and proposes rules between users and the actual operator. The operator identity, contact details and applicable service scope still require verification. This page specifies no unconfirmed company, registered address or effective date and is not legal advice.
Displaying this draft does not form a contract or treat browsing, registration or continued use as acceptance of terms that have not been formally adopted. Before formal service provision, the operator should provide complete terms, a clear acceptance mechanism and necessary notice of important limitations. Differences in a valid separate order or written agreement should be resolved according to that agreement and applicable law, without reducing non-excludable statutory rights.
2. Accounts and eligibility
Registration requires a username, email address and password meeting the input requirements. Provide information you are entitled to use, protect credentials and avoid impersonation or sharing the account with unrelated parties. Confirm your authority when acting for an organization. Sign-in and registration have separate pages and endpoints; their displays do not guarantee identity verification, email verification or absolute account security.
Users who require guardian permission or other legal authorization should use the service only after valid authorization and confirmation of suitability. There is currently no complete age-verification or guardian-consent workflow, and the operator must establish the applicable conditions before adopting terms. Stop risky activity and seek investigation if an account behaves unexpectedly. Responsibility should reflect conduct, fault and applicable law, rather than assigning every account action to the user unconditionally.
3. Preview status and feature boundaries
Community boards, authors, topics, replies and related displays are demonstration samples, not evidence of real users, live engagement or a released community publishing service. Bookmarks, discussion drafts and reply drafts are saved only in the current browser. A save message does not mean publication and creates no promise that others can view, respond to or retain the content.
Studio offers visual editing, responsive previews, local drafts and static HTML export, and can read existing authorized server-side projects. Current editor saving is not connected to cloud synchronization or publishing. Exports do not generate form processing, account, payment or database backends, and the project-list deletion interaction is not a guarantee of completed server deletion. Keep your own backups and verify actual outcomes rather than treating examples or interface text as unconfirmed delivery commitments.
4. Acceptable use and safety
Use must comply with applicable law and respect the rights of others. Do not use the website for fraud, phishing, harassment, malicious-code distribution, unauthorized access or disclosure of personal information, or to bypass permissions, damage systems, abuse resources or impersonate the operator. Legitimate security research should have any required prior authorization and avoid accessing others’ data or disrupting service.
Remote installation should target only servers you are authorized to administer and only after understanding the commands, privileges and data they may overwrite. Depending on the environment, the tool may perform a real SSH connection or a simulation. Simulated success does not establish successful deployment. Verify external installation-script sources, back up data and prepare recovery before execution; a displayed command is not proof of suitability for every system or production workload.
5. Intellectual property and third-party licenses
Rights in branding, interfaces, code, documentation and assets depend on actual ownership and applicable licenses. Display or export access does not transfer all intellectual-property rights. Use features and outputs within the permissions you have obtained. Without an express license, do not assume permission to copy branding, remove rights notices, resell third-party assets or claim official endorsement.
The website uses third-party technologies including PHP, Tailwind CSS and Font Awesome. License, attribution and distribution requirements must be checked for the versions actually used. Images, fonts, text and links you add to exported pages may have separate licenses. This draft does not claim that every dependency has the same open-source license or that sample content is suitable for every commercial purpose. Check rights before publication or distribution.
6. Reference pricing and payment status
The pricing page currently presents Free, Pro and Enterprise reference proposals, with paid-plan actions preparing email inquiries rather than online checkout or automatic subscriptions. Switching monthly and annual views, opening an inquiry or registering does not cause that page to place an order, charge you or activate a paid plan. Reference amounts are in Chinese yuan; the English interface does not convert them to US dollars. Static HTML export is currently available to free accounts as well.
Any future paid service should separately confirm the provider, available features, quotas, billing period, total price, taxes, invoices, activation conditions, renewal, cancellation and refund rules before payment. Hosting, collaboration, API or service-level descriptions in pricing cards do not replace a valid order and verified capabilities. Domains, servers and third-party services may require separate purchases. This draft creates no automatic renewal, refund guarantee or unconfirmed paid entitlement.
7. User content and permission scope
You retain the rights you lawfully hold in text, layouts and other content you create, and should ensure a lawful basis for using third-party material and personal information. Saving a draft does not grant copyright, likeness or privacy permissions belonging to others. When deploying an exported page elsewhere, you must verify content permissions, security settings and necessary notices to visitors.
Current local-draft features do not require permission for the operator to publicly publish, resell or train models on user content. Any future upload, hosting, collaboration or public-community feature should separately explain, before submission, the processing permission needed to provide it, visibility, moderation and deletion rules. This draft obtains no perpetual or unlimited content license and does not imply that the operator has reviewed every draft or can restore cleared local content.
8. External services and self-hosting
Some pages use scripts, styles and fonts from third-party content delivery networks and include external resource, email and panel-installation routes. Those services may have separate terms and privacy policies. A resource link, technology name or icon does not establish a partnership, certification or guarantee. Availability, charges, licenses and processing practices should be explained by the actual provider and checked before use.
Self-hosting requires separate arrangements for domains, servers, HTTPS, backups, maintenance and necessary backend features. Editor export or an installation tool is not a substitute for a hosting agreement, secure operations or compliance review. External images and links may also generate requests when previewing or opening an export. The operator remains responsible for provider selection or its own conduct where applicable law requires; this section is not an unconditional exclusion of all third-party risk.
9. Availability, risks and liability limits
Current features may be interrupted or changed by development, maintenance, browser limits, storage clearing, network issues or dependency failures. Unless a valid separate commitment exists, this draft promises no uninterrupted availability, error-free operation, specific response time, permanent retention or fitness for a particular business purpose. Keep independent backups of important content and test exported files and the deployment environment before real business use.
Any warranty exclusion, damages provision or liability limitation adopted in future can operate only to the extent permitted by applicable law. Statutory consumer rights and liabilities that cannot lawfully be excluded are not waived by “preview,” “as is” wording or risk notices. This draft sets no unconfirmed monetary liability cap and does not require users to waive remedies for unlawful, intentional or other legally non-excludable conduct by the operator.
10. Suspension, stopping use and data handling
Formal rules should permit necessary and proportionate restrictions where there are reasonable grounds to suspect unlawful use, material security risks or substantial breach, with reasons, an appeal route and a reasonable opportunity to address the issue where law and safety permit. Emergency measures should not justify arbitrary appropriation of content or avoidance of legal duties. This draft itself creates no unlimited suspension power.
You may stop visiting and clear local data, while account closure and server-side deletion require separate verification through the contact route; an automatic closure workflow should not be assumed. Export content you need before stopping use. Account closure, sign-out and deletion of local drafts are distinct actions. Legally required retention and settlement of any confirmed paid services should follow applicable law and valid agreements; termination does not erase accrued statutory rights.
11. Applicable law and disputes
For service, content or account disputes, you may first seek review and discussion through the contact route, providing the relevant page, time, description and necessary non-sensitive evidence. Discussion should not prevent complaints to competent authorities, statutory remedies or court action within legal time limits. You do not need to send passwords or complete personal information about others to substantiate a concern.
Because the operator and service territories are not yet confirmed, this draft selects no national or regional law, court, arbitration body or exclusive venue. Applicable law and competent authorities for an actual dispute should be determined under relevant legal rules. Any future choice-of-law or dispute clause requires appropriate review and valid notice while preserving mandatory, non-excludable protections for consumers and others.
12. Changes and contact
Before adopting or changing terms, the operator should verify that capabilities match commitments, distinguish drafts from formal versions and provide necessary notice and legally required acceptance for important changes. Updating this page alone must not retrospectively change a valid existing order or presume acceptance of new charges, expanded content permissions or other materially adverse changes.
For service-rule questions, disputes or feedback on this draft, use the existing footer address contact@blockcode.net. Before publication, the operator must confirm ownership, reachability and responsibility for handling inquiries, and supply legally required identity and contact information. This page does not fill those gaps with unverified names, addresses, response promises or effective dates.
Questions? Let’s clarify them.
Describe your question and the relevant page without passwords, tokens or unredacted personal data. This address is taken from the site footer and must be verified before adopting the policy.
contact@blockcode.netWant to understand how the product works?
Explore the documentation for features, workflows and current limitations.