Agent Hotel service terms
Version: v1 Source policy review date: 2026-09-19 Status: versioned current test-use information and conditional future-service terms. This is not an executed customer agreement, paid offer or new enrollment acceptance.
Operator and contact
RETRO GAMES FOX CAVIC, organization number 921560095, Dalanvegen 45, 3850 KVITESEID, Norway. Contact: zcavic87@gmail.com; +47 98416851. Official domain: agenthotel.online.
Current status and acceptance
The project currently has no customers and no support/privacy correspondence; activity is limited to approved tests. This work has not deployed the production application or enabled production billing. This version provides current test-use information and conditional future-service terms; it does not create a paid offer or an executed customer agreement. The identifier agenthotel-alpha-2026-09-05 remains the existing local-alpha protocol acknowledgment. This document is not assigned to that identifier and does not retroactively replace its accepted text. Any future contractual acceptance must identify the applicable retrievable version through a separately approved process.
What the service is intended to provide
Agent Hotel provides bounded state, inboxes, context data, schedules, approvals, locks and signed delivery through shared service contracts. It is not LLM hosting, arbitrary code execution, a general workflow engine or a guarantee that an agent stays running. Customers must have authority for their data and instructions, protect credentials and grant only necessary scopes. Account management is not universal project-content access. Customer-held private keys remain the customer's responsibility. Restricted task passes cannot create child passes or exceed their issuer and selectors. Successful mutations are acknowledged after durable commit. Outbound delivery is at least once and recipients must handle duplicates. A recorded approval is neither identity proof nor execution of the proposed action. Quotas, expiry, authorization and retention limits apply.
Conditional paid launch and consumer policy
The owner-selected future paid market is Norway and the EEA, for businesses and consumers. Production billing remains disabled. Prices, applicable tax treatment, contract formation, durable receipts and required disclosures must be provided through the reviewed purchase flow before any live sale. No current VAT-registration status is asserted here. Canceling renewal preserves already purchased access. Renewal cancellation, account deletion and statutory consumer withdrawal are different operations. For a valid consumer withdrawal within the applicable statutory withdrawal period, the selected commercial policy is a full refund without deduction for service already supplied. First use is not treated as an automatic waiver. Actual withdrawal, refund, reminder, conformity-remedy and required disclosure processes remain prerequisites to the corresponding live offering. Applicable consumer rights are not excluded or made dependent on provider approval.
Export, deletion and retained records
The deletion contract provides a cancelable seven-day grace period with ordinary authorized activity continuing under existing limits. New billing commitments stop immediately; canceling deletion never restarts billing. At the deadline, access and new execution authorization stop independently of bounded cleanup progress. This describes the selected contract, not production activation or a guarantee of all-copy erasure on day seven. Paid-excess retrieval and retention use a separate seven-plus-thirty-day clock. Ordinary earlier TTLs still apply. Consumer-remedy retrieval must be reconciled with actual export/deletion behavior before the corresponding offering is finalized.
Remaining commercial boundaries
No production uptime SLA, general no-refund rule, liability cap, governing-law election or dispute-forum clause is introduced by this version. No unrestricted unilateral-change power is selected. Publishing a new version alone does not alter an existing accepted agreement. The privacy notice, acceptable-use policy, provider register, DPA template and retention policy must be read with their stated scope. A DPA template requires applicable parties, annexes and binding acceptance; this publication does not execute it.