1. Agreement and service boundary
These Terms govern use of the hosted Hyfens Cloud service by the person or organization identified in the applicable checkout, order, or written agreement. The operating entity, notice address, governing law, and any negotiated service commitments must be completed in the approved order or agreement before these draft terms are published as final contractual terms.
Hyfens Cloud is a managed service for account administration, application and environment management, signed release and patch delivery, usage reporting, and related support. The open-source Hyfens software is a separate offering governed by its applicable license. A self-hosted deployment is operated by the customer and does not create a Cloud subscription or transfer Cloud operating obligations to Hyfens.
2. Accounts, organizations, and authority
You must provide accurate information, maintain a verified account email, protect authentication factors, and ensure that each person using your organization has the authority and access appropriate to their role. You are responsible for activity performed through your account and for promptly reporting suspected compromise.
Organization owners and administrators control membership, applications, environments, releases, patches, billing actions, and support requests within the permissions the service exposes. Do not share credentials or use another person’s session. Hyfens may rely on authenticated organization instructions until a security concern or legal requirement requires a hold.
3. Customer content and application responsibility
You retain your rights in application source, binaries, releases, patches, names, content, and other material submitted to Cloud. You grant Hyfens the limited rights needed to host, process, verify, deliver, secure, back up, and provide support for that material under your instructions.
You are responsible for your application, end-user notices and consents, intellectual-property rights, privacy obligations, export and sanctions compliance, release decisions, and the behavior of code delivered to your users. Do not submit personal or regulated data unless your organization has a lawful basis and the applicable Cloud configuration and data-processing terms support it.
4. Supported delivery boundary
Cloud can validate eligibility and deliver a signed patch, but it does not guarantee that an application change is safe, compatible with every device, accepted by an app store, or compliant with a customer’s obligations. The runtime’s release, capability, digest, sequence, and signature checks remain authoritative.
You must test releases and patches, maintain an appropriate rollback plan, and avoid using a patch to change native code, permissions, entitlements, dependencies, manifests, or other unsupported surfaces. Unsupported changes require the normal store or base-release workflow.
5. Acceptable use and security controls
You must use Cloud lawfully and in accordance with the Acceptable Use Policy. You may not bypass authentication, authorization, signatures, usage limits, tenant boundaries, billing controls, or safety checks; interfere with service operation; distribute malware; abuse delivery infrastructure; infringe another party’s rights; or test against organizations and resources you do not control.
Security testing, load testing, scraping, automated enumeration, and vulnerability research require prior written permission where they could affect other customers or production systems. Report suspected vulnerabilities through the support or security contact rather than exploiting them.
6. Plans, usage, and commercial terms
The effective Cloud catalog, checkout, order, or Enterprise contract identifies the plan, price, billing interval, entitlements, usage unit, limits, taxes, and any enabled overage. The backend catalog and recorded contract snapshot—not a browser value or marketing description—control billing and access.
Usage allowances reset according to the applicable plan. A delivery request, failed download, failed installation, retry, or other event that is not the authoritative successful usage event is not automatically billable. Overage collection is only permitted when the applicable catalog and launch gates expressly enable it.
Enterprise and negotiated terms may override public plan details only through an authorized written contract and immutable contract snapshot. No public plan should be assumed to include a service level, data location, retention period, volume commitment, or custom support term that is not stated in the applicable agreement.
7. Payment, taxes, and provider processing
Paid subscriptions are billed in advance at the amount and interval shown before confirmation. Prices may exclude applicable GST, VAT, sales tax, withholding, or similar charges. You are responsible for accurate billing information and any taxes assigned to you by law or contract.
A payment provider may process payment credentials and provider-side settlement. Hyfens stores only the provider references, status, plan terms, and audit information required to administer the subscription. Provider terms apply to provider-hosted checkout and payment methods.
8. Upgrades, downgrades, and cancellation
A customer-initiated cancellation stops the next renewal and normally leaves the current paid period active until its provider-confirmed end. A lower-plan change is scheduled for the applicable cycle boundary. The organization, application, and data are not deleted merely because renewal is cancelled or a plan is downgraded.
An upgrade or other plan change is an explicit checkout or contract operation. Hyfens does not promise automatic proration, credit, repricing, or a refund of the previous period unless the applicable checkout, order, provider result, or written exception expressly says otherwise. Plan changes cannot be used to transfer a discount or entitlement to an ineligible plan.
Cancellation does not create a reusable balance. Re-subscribing does not reset prior promotion eligibility, consumed usage, or audit history.
9. Refunds and promotions
Hyfens does not provide routine refunds or credits for ordinary cancellation, downgrade, unused time, plan changes, or a change of mind. The Refund Policy describes the narrow reviewed exceptions, including legal requirements, duplicate or system-error charges, fraud or unauthorized payment, provider correction, and an explicitly authorized billing exception.
Promotion terms are fixed when accepted. Promotional charges are ordinarily non-refundable and do not become cash, account credit, or a reusable code after cancellation or refund. Any exception requires an authorized review and does not silently restore promotion eligibility.
10. Privacy, data processing, and subprocessors
The Privacy Policy describes personal information processed by Hyfens, the Cookies Policy describes browser storage and similar technologies, and the Subprocessors and Data Processing pages describe the operational and contractual data-processing boundary. If Hyfens processes personal data for an organization as a processor, the applicable data-processing agreement and customer instructions control that processing relationship.
11. Availability, support, and changes
Cloud is an evolving managed service. Maintenance, provider outages, security events, feature changes, and emergency controls may affect availability. Backups, recovery objectives, response times, and service levels apply only where expressly included in the applicable plan or written agreement.
Hyfens may modify, suspend, or discontinue features for security, legal, operational, or product reasons. Material changes to contractual terms will be communicated through the channels and notice period required by the applicable agreement and law.
12. Suspension and termination
Hyfens may restrict or suspend access when required to protect customers, investigate abuse, address non-payment, comply with law, or respond to a security incident. Where reasonably possible, Hyfens will provide notice and an opportunity to cure. Suspension does not erase audit records or waive payment obligations already incurred.
After termination, data export, deletion, retention, and backup handling follow the applicable plan, agreement, Privacy Policy, Data Processing terms, and legal obligations. Customers remain responsible for maintaining their own source and release backups.
13. Intellectual property and confidentiality
Hyfens and its licensors retain rights in the Cloud service, software, documentation, trademarks, and service design. Except for the rights expressly granted in these Terms or an applicable license, neither party transfers ownership to the other.
Each party must protect non-public information received from the other and use it only for the relationship. Confidentiality obligations do not prevent a legally required disclosure, security response, or use of information that is independently public or already lawfully known.
14. Disclaimers, liability, and required legal terms
To the extent permitted by law, Cloud is provided subject to the commitments expressly stated in the applicable agreement, and no online service can promise uninterrupted or error-free operation. Hyfens does not control third-party stores, devices, networks, payment providers, or customer application behavior.
The final warranty disclaimers, liability allocation, indemnities, dispute process, governing law, notice address, and mandatory consumer rights must be supplied and approved by the responsible legal owner before these drafts are used as the final Cloud agreement. Nothing in these Terms limits rights that cannot lawfully be limited.
15. Contact and precedence
For account, billing, or policy questions, use the Customer Workspace support channel or contact support@hyfens.com. If an order form, Enterprise agreement, or mandatory law conflicts with these general Terms, the more specific approved contract or mandatory rule controls for that subject.
This page is a structured Cloud policy draft. The published CMS record, effective date, document version, and approval record must be reviewed together before production launch.