Terms of Use

Operator and scope

These Terms of Use ("Terms") cover access to haltseal.com (the "Website"), its public materials and the hosted Workspace Sandbox (the "Workspace"), operated by HALTSEAL Inc., a Delaware corporation ("HALTSEAL," "we," or "us").

Please read these Terms before using the Website or Workspace. Workspace sign-up presents an acceptance notice beside the relevant action. A person acting for a company must have authority for the action they take; a company role or account login does not itself authorize a payment.

The sections on public materials govern Website reading and review. The Workspace, source-connection and offboarding sections also govern those supported Sandbox functions when enabled. Paid services and customer operations require their separately accepted agreements. These Terms do not amend an existing customer agreement or add services to its scope. Software and downloadable components retain their supplied licenses; these Terms do not narrow permissions expressly granted by those licenses.

Evaluation workspace

The free evaluation workspace, when enabled, keeps saved synthetic sandbox results, SDK installation guidance, workflow outlines, scope review and existing pilot progress. You must control the email address you use to sign in and keep your session secure. Submit only information you are authorized to provide. Do not put credentials, live account details or confidential customer records in workflow outlines, support messages, public forms or the AI guide. Only an explicitly labeled, separately enabled Sandbox connection flow may request the specific test credential or source record described for that feature. Use only authorized Sandbox organizations and permitted test data. Never submit production credentials or private signing keys to these forms. The connection sections below and the Privacy Notice describe the different data paths.

Workflow configuration saves a plan for the selected systems, shared payment reference and decision owner. It does not grant provider access, activate monitoring or enable payment control. Saved synthetic results do not establish production protection or qualify a provider path. The workspace does not issue production API keys, submit real payments or automatically buy services. Optional scope inquiries take no payment. New standard pilot sales have ended. Existing orders remain available through order support under their originally accepted terms. Free Sandbox use does not automatically convert to a paid plan. Production fees require an agreed scope and operating approval. Progress records describe the recorded request and operator updates, not a guarantee of acceptance or completion.

You may export or delete evaluation data in Settings. Evaluation records expire after 180 days without account activity; authentication, submitted inquiry, commercial, log and backup records are separate as described in the Privacy Notice. We may restrict access to protect the service, address abuse or comply with applicable obligations.

Private Workflow Evaluation Kit access requires a saved scope, readiness review and acceptance of the supplied release evaluation license. Access is account-specific and time-limited. Keep the supplied engine and reports private. The kit is for authorized synthetic local evaluation; a passing reference or customer-hook test does not qualify production payments. Optional implementation assistance is separately scoped and requires an accepted written agreement before paid work begins. Existing accepted pilot orders retain their accepted terms.

A company workspace is owned by its company account and shared with its current authorized team. Company roles govern workspace configuration and access; they do not grant source payment approval. Personal evaluation remains separate. A reviewed copy into a company Sandbox does not transfer native bindings or reserved payment authority. Each company environment has its own evaluation records and 180-day inactivity period. Company ownership and administrative history remain separate operating records. An authorized Owner can contact us about shared company data. Production payment activation requires separate qualification and operating approval.

The company treasury reference application is for the disclosed fictional Increase sandbox scope on one Linux host. Scheduled funding and local operator recovery share the installed engine’s retained source authority. Keep its keys and history secure; do not use a fresh exercise to replace an unresolved installation. Company access and a provider API key do not constitute fresh source payment approval. The hosted Workspace receives bounded signed observations and verifies sandbox account access; the installed host performs scoped execution. This qualification does not cover manual portals, other credentials, cross-provider paths, real customers, bank settlement or production money movement.

The pinned company workflow operations addon supports the same retained fictional Sandbox workflow and narrow application requests. Operational health, assignment and incident acknowledgement confer no source payment approval or production permission. Reporting loss or unverifiable retained state keeps new controlled submissions on HOLD. Same-host ledger repair requires the independently retained live witness, unchanged configuration and audit history, and exact signed snapshot; it does not resume execution automatically. Preserve unresolved original attempts and retained state during reinstallation. Do not use a new qualification fixture to replace an existing history. Host loss, joint witness/ledger rollback and multi-host disaster recovery require separate qualification.

Payment authority and execution scope

Workspace access and company roles govern who can view or configure the service. A source connection permits only its disclosed data access. An Agent assignment or handoff concerns the identified workflow and current assignment. None of these steps, a tracking identifier or a completed example itself creates original financial approval, restores reserved capacity or qualifies a release path.

Original financial approval, the exact proposed request, current execution eligibility, installation evidence and operating approval remain distinct. A technical ACCEPT applies only under the identified contract and conditions; it does not by itself prove provider submission, successful execution or final settlement. HOLD and REFUSE describe the evaluated request. They do not cancel the underlying obligation, extend a payment deadline or resolve the original provider outcome.

Your accountable payment owner must address unresolved outcomes, deadlines and any manual or external paths. Supported checks cover only their identified source, host, package, credentials and included release paths. A company or Agent change, retry, reinstallation or route change does not itself supply fresh financial approval or clear retained unresolved history. Live operation requires a separately agreed scope, qualification and operating approval.

Workspace content and access

You retain your rights in content you submit. You authorize HALTSEAL to process submitted content and display permitted Workspace records to your current authorized company members, within the access limits described for the feature, as needed to provide, secure and support the requested functions, comply with law and carry out separately accepted agreements. This permission does not transfer ownership or grant a general right to reuse your content for unrelated purposes. The Privacy Notice and applicable data-processing terms also govern their respective subject matter.

Provide only information you may lawfully share, manage company membership and protect your sessions, keys and installed host. Use the dedicated connection controls for the permissions they describe. HALTSEAL's obligations under applicable law and any separately accepted confidentiality, security or data-processing commitments remain intact. Arrange the permitted inputs and appropriate handling terms before sharing confidential customer material for a separate engagement.

Service acceptance, a source-access confirmation, an accepted commercial offer and an original financial approval serve different purposes. A receipt or document hash identifies recorded content and scope; its evidentiary value depends on its stated provenance and verification. It is not itself financial authority. Public examples and these Terms do not create an accepted customer order or a financial permission.

Paid services and existing orders

Paid services with HALTSEAL Inc. require an accepted written agreement, which may be an existing accepted pilot order or a separately signed proposal. The agreement identifies the contracting parties, scope, deliverables, fees, timing, customer participation, and applicable access, confidentiality, and data handling terms.

The agreement may be an acknowledged online order, signed proposal or service agreement, with a statement of work and any additional terms it expressly incorporates. The agreement governs the services it covers and any order of precedence among its documents. These Terms do not amend an existing customer agreement. The version accepted for a paid order governs that order even if the current website terms change. The standard pilot records its customer identity, full agreement and offer, acceptance time and document digest and provides an order copy. Its agreed confidentiality, quality remedies, deliverable use rights and liability allocation are set out in the Integration Pilot Agreement.

Document review and technical testing have separate scopes. Additional work, testing, or deployment requires the applicable written agreement and authorization. An inquiry, demo booking, or AI-guide conversation does not accept a proposal, create a paid engagement, or authorize access to your systems.

Existing integration pilot orders remain fixed-scope nonproduction evaluations. Their quoted duration starts after both parties accept readiness. The originally accepted purchase terms state the deliverables, exclusions, payment timing and refunds for each order. Custom engagements use a separately accepted proposal. No production deployment, native-provider qualification or availability commitment is purchased through a pilot request.

Production commercial scope

Production pricing is an agreed monthly base plus new unique governed obligations within the accepted operating scope; Platform uses an annual agreement and committed volume. Rates, scope, the usage definition, billing period, commitments, cancellation and operating responsibilities must be agreed in writing before charges begin. Retries, Agent handoffs, lookups and repeated HOLD decisions for the same obligation do not create another obligation unit. Current Sandbox metering records observations only. Live Production subscriptions and usage charging are not activated. See current pricing and qualification.

Company sandbox subscriptions

A current company Owner may review the stated monthly test price and select one company Sandbox workflow before entering Stripe Checkout, when enabled. This sandbox subscription uses test payments and creates no live charge. The saved offer identifies the price, currency, monthly interval, workflow scope and acceptance. It does not alter an existing pilot order or authorize a production subscription. Unique obligation observations carry no usage overage.

Verified subscription access remains subject to current company access, installation qualification and independently signed source payment approval. Payment, a Checkout return or an invoice does not approve a source transaction or qualify production. If payment or its current verification is unavailable, new financial commands remain on HOLD. Original lookup and closure evidence remain available with current installation authority.

An Owner can pause new financial commands and request cancellation at the period end. Safe offboarding is recorded only after current terminal evidence for the retained outcomes is verified. Cancellation does not release an unresolved reservation, erase payment history or restore spent capacity. Rejoining the same company and workflow preserves the original operating history and usage identity. Keep the original host stores and witness; any transfer requires separate qualification.

BILL Sandbox source collector

The optional collector reads the existing USD 1 test bill and vendor in your authorized BILL Sandbox organization. It retains exact source material on your computer and submits dedicated-key-signed observations to the company workspace. Keep its private key, journal and separate witness secure and preserve their complete history. Use only the disclosed Sandbox fixture and information you are authorized to provide. Authorizing or renewing collector access does not authorize a payment, transfer a financial grant or qualify an execution path. A recorded approval is an observation of the selected source, not a BILL-signed payment permission or a guarantee against remote changes, host compromise or manual portal bypass.

Customer BILL Sandbox data connection

The separately enabled customer connection is a company-scoped source observation service. A current authorized company administrator supplies a BILL AP/AR sync token after Workspace MFA and selects one supported Sandbox invoice. HALTSEAL retains encrypted source material and signed observations under the original invoice identity. Use information and a Sandbox organization you are authorized to connect. Connection, source observations, tracking IDs and example completion grant no financial authority or production qualification. This dedicated flow may receive the specified Sandbox sync token and source records; it is separate from the local collector whose credentials remain on your computer. See customer BILL connection data and retention. Local disconnect preserves original evidence and does not revoke the original token inside BILL.

Public information, demonstration, and assessment results

The Website explains HALTSEAL and the Cross-Path Payment Assessment and provides materials for business and technical review. The public demonstration uses synthetic information, runs in the browser, and does not initiate payments. The separate SDK sandbox uses fixed synthetic HTTP fixtures and a short-lived session. Its injected observations do not verify signed customer sources or native-provider evidence; no real payment instruction is accepted. Downloaded clients and fixture software retain their supplied licenses.

The prepared shared Workspace demo uses public demo credentials for a separately isolated synthetic session. It cannot access customer Workspace records, connect payment providers or grant payment authority. Its session data and necessary cookie are described in the shared demo privacy section.

Published technical results apply only to the versions, environments, assumptions, and conditions identified with those results. The Evidence page distinguishes synthetic fixtures, installed Sandbox reference results, source observations and controlled integration tests. A result applies only to its disclosed scope; one profile does not qualify another. A Sandbox or controlled result does not establish customer acceptance, an untested native payment path or live Production protection.

An assessment report applies to its identified workflow, routes, evidence, versions, and test conditions. Its conclusions should be read with its tested coverage, exclusions, assumptions, and inconclusive findings. They do not certify untested systems or guarantee outcomes after the assessed environment changes.

Public materials do not authorize a real payment, approve a production deployment, or provide a general certification of security or regulatory compliance. Any customer deployment requires its separately agreed scope, authorization, and operating arrangements.

Permitted use and intellectual property

You may view the Website, follow its public links, and save or share reasonable copies of its public materials for internal business, procurement, legal, security, and technical review. Please preserve attribution and relevant notices and do not present altered excerpts as original HALTSEAL statements. Uses otherwise permitted by law remain available.

Materials, software, trademarks, and other intellectual property belong to their respective rights holders. The Website operator does not necessarily own every patent, trademark, or component discussed on the Website. Except for the permissions above and any applicable separate license, these Terms grant no patent, trademark, or other intellectual property license.

Responsible use

Do not use the Website unlawfully; misrepresent your identity or affiliation; interfere with its availability; introduce malicious code; evade access controls; or access another person's information without authority. Automated access must respect access controls and must not disrupt the Website.

Security research within the scope and conditions of the Responsible Disclosure Policy is permitted under that policy. That policy describes the authorized scope and reporting process. It does not authorize testing customer systems or services operated by third parties.

Inquiries and privacy

Business inquiries are welcome. Sending an inquiry does not by itself create a service contract or confidentiality agreement. Keep the first message to the business issue you want to discuss, and arrange any confidential exchange and appropriate transfer channel with us first. You retain your rights in information you submit; sending an inquiry does not give us ownership of it.

Hana provides AI-generated guidance for public product questions and can make mistakes. Its replies do not approve a scope, fee, customer commitment, or payment. Confirm commercial and customer-specific matters with us in writing.

The Privacy Notice describes personal information handled through the Website, Workspace, supported Sandbox connections and direct inquiries. These terms do not replace that notice or any rights under applicable privacy law.

Leaving Workspace and retained history

You may stop using free Sandbox and contact us about company access, account closure or records that Settings does not delete. Use each connection's disclosed disconnect or revocation process; local withdrawal does not necessarily revoke access at the provider. Removing a member blocks future service access but does not remove copies already downloaded.

Evaluation-data deletion, subscription cancellation and safe technical offboarding are separate actions. Cancellation does not release unresolved reservations, erase payment history or restore spent capacity. Retained unresolved history does not itself renew a paid term or authorize an additional charge. The accepted agreement governs any paid continuation or transition assistance.

Keep the original host records and independent witness available for the supported recovery process. Original lookup and closure evidence remain subject to current installation authority. We retain separate operating records only for the applicable reconciliation, security, accounting and legal needs described in the Privacy Notice, subject to applicable rights and agreements. Contact us about the records and retention needs for your company.

Availability and responsibility

We may correct, update, remove, or restrict Website content or access, including to protect the Website or respond to misuse. Public Website access does not carry a service-level commitment. Separate customer agreements govern any customer-specific availability or support obligations.

To the extent permitted by law, the Website and public materials are provided "as is" and "as available." We do not warrant uninterrupted or error-free access, complete information, or suitability for a particular use. This does not override any express commitment in a separate agreement or a warranty that applicable law does not allow us to exclude.

To the extent permitted by law, we are not liable for indirect or consequential losses arising from use of the Website or its public materials. Nothing in these terms excludes or limits liability for fraud, willful misconduct, gross negligence, death or personal injury caused by negligence, or any liability or statutory remedy that cannot lawfully be excluded or limited. These Terms do not change the allocation of responsibility in a separate customer agreement.

External links are provided for reference. We do not control external sites, their availability, or their terms.

Law, changes, and contact

These Terms are governed by the laws of Delaware, United States, excluding conflict-of-laws rules. This does not deprive you of mandatory protections or rights to bring a claim available under the law that applies to you. These terms do not require arbitration or waive class, jury-trial, or other nonwaivable rights. A separate customer agreement determines the law applicable to the services it covers.

We post changes with an updated date, effective date, and version. Changes apply prospectively from publication or the stated effective date, whichever is later, subject to any notice or agreement required by law. Updating the Website operator does not itself assign, replace, or amend a customer agreement. If a provision cannot be enforced, the remaining provisions continue to the extent permitted by law. You can read the previous published version.

For questions about these terms, email scott@haltseal.com with "HALTSEAL Terms" in the subject line.