Acceptance and eligibility
By using Halenor, submitting a request, approving a scope, or purchasing a service, you agree to these terms and the project-specific documents you accept. You must be legally able to enter the agreement and authorized to act for the identified person or organization.
Requests, proposals, and project formation
An intake creates a request for review. It does not approve a charge or establish final scope, price, timing, feasibility, or a guarantee. A binding project begins when the customer accepts the written scope, price, recurring plan, timing, responsibilities, and additional project terms.
Project briefs, suggestions, ranges, examples, and preliminary timing remain planning material until incorporated into an accepted scope.
Pricing and billing
- The accepted scope identifies the one-time build price, recurring plan, usage charges, provider fees, taxes, billing schedule, and payment method.
- Monthly plans include a 3-month minimum commitment billed monthly; early cancellation during that window leaves the remaining committed months due at the regular monthly price (see Payment Terms).
- Payment authorizes Halenor and the approved payment provider to process the stated charges.
- Past-due balances may pause work, launch, hosting, automation, updates, support, or access after applicable notice.
- Refunds, credits, milestones, disputes, and cancellation follow the accepted project terms and the published Payment Terms and Cancellation Policy.
Recurring plans and included updates
Recurring plans cover only the hosting, infrastructure, monitoring, maintenance, usage, updates, integrations, and support identified in the approved plan. Included minor updates use the approved structure. New pages, major redesigns, new databases, roles, payment behavior, integrations, or automation are separately scoped before work proceeds.
Customer responsibilities
- Provide accurate information, lawful instructions, timely decisions, content, files, and necessary access.
- Protect passwords, secure links, devices, domains, and provider accounts.
- Review scopes, previews, revisions, content, pricing, settings, and launch approvals carefully.
- Maintain licenses, notices, policies, permissions, and industry-specific obligations applicable to the customer’s operation.
Customer content and permissions
Customers retain ownership of materials they provide and grant Halenor permission to use, copy, modify, host, transmit, and display those materials as needed to perform the approved work. The customer confirms it has the rights and permissions required for all supplied content, data, trademarks, images, video, software, accounts, and instructions.
Domains, project ownership, and reusable systems
Domain registration and ownership responsibilities are identified in the accepted scope. Customer-specific ownership, source access, licenses, exports, and handoff obligations are also stated there. Halenor retains its brand, reusable systems, templates, libraries, components, workflows, general methods, internal tools, and non-customer-specific improvements unless the accepted scope states otherwise.
Reviews, revisions, approval, and launch
The approved scope defines included revisions and acceptance criteria. Material requests outside scope receive a change proposal. Customer approval authorizes the identified version for launch or delivery. Halenor may delay launch when required content, access, payment, legal approval, provider approval, or security information is missing.
Third-party services and processing fees
Projects may depend on registrars, hosting platforms, payment processors, messaging and phone providers, AI services, APIs, app stores, search platforms, or other third parties. Their availability, prices, review decisions, policies, outages, and terms remain subject to those providers. Processing and usage charges assigned to the customer are identified before approval when reasonably knowable.
AI-assisted services
Halenor may use AI-assisted tools for planning, drafting, coding, testing, summaries, routing, support, and approved workflow execution. AI output can contain errors and does not replace customer review, professional advice, or required human approval.
Acceptable use and security
Use of Halenor is subject to the Acceptable Use Policy. Halenor may reject, remove, suspend, or investigate content or activity that appears unlawful, infringing, deceptive, malicious, abusive, unsafe, or outside the approved scope.
Service standards and warranties
Halenor performs accepted work according to the written scope and express commitments stated there. Except for those commitments, services are provided on an as-available basis. Halenor does not guarantee revenue, rankings, lead volume, conversion rate, uninterrupted third-party availability, or another result not expressly stated in the accepted scope.
Liability and responsibility
To the extent permitted by law, neither party is liable for indirect, incidental, special, punitive, or consequential damages. Halenor’s aggregate liability for a claim is limited to the amount paid to Halenor for the affected service during the six months before the event giving rise to the claim, unless applicable law requires a different result.
The customer is responsible for claims arising from customer materials, unlawful instructions, unauthorized data, misuse, or violation of third-party rights, except to the extent caused by Halenor’s own breach or misconduct.
Suspension, termination, and updates
Halenor may suspend or terminate access for nonpayment, security risk, unlawful use, material breach, provider restriction, or conduct that threatens the service or another person. Payment, ownership, confidentiality, liability, dispute, and record provisions continue where their purpose requires it.
An accepted project remains governed by the version and project documents applicable when approved unless the parties agree otherwise or a change is required by law.
Questions and notices
Questions, legal notices, billing concerns, and service notices may be sent to support@halenor.com. Include the request reference and project name when the message concerns an active project.
SMS and mobile messaging terms
If you initiate a text conversation with a Halenor-enabled number or otherwise provide the applicable consent, Halenor may send customer-care, transactional, scheduling, support, or approved automation messages related to that interaction or service. Message frequency varies based on your requests and activity. Message and data rates may apply.
Reply STOP to an applicable automated text program to opt out and HELP for help. A request for Halenor services does not by itself enroll you in recurring marketing messages. Any marketing text program requiring consent uses a separate opt-in, and consent to marketing is not a condition of purchasing Halenor services.
Wireless carriers are not liable for delayed or undelivered messages. Messaging availability may depend on your device, carrier, location, provider rules, and network conditions. Halenor's Privacy Policy explains how mobile information and messaging consent records are handled.