A clear scope.
A shared understanding.

1. Who we are

Unattended is operated by Stringlearning ApS, CVR 35673539, Sankt Annæ Plads 13, 3., 1250 København K, Denmark, the company behind Seier AI. In these terms, “we” means Stringlearning ApS and “you” means the person using the website or pilot workspace.

Contact the Seier AI team at unattended@seier.ai.

2. What is available now

The website describes a service for building custom applications and managing their ongoing operation. The current version accepts enquiries and provides an invited test workspace for project briefs, feedback and versioned approvals.

It does not take payments or activate building, operating or marketing agents. Live monitoring, billing and security integrations are not connected. Sample dashboards, budgets and workflows are illustrative and do not show actual customer performance or spending.

These terms govern use of the website and pilot workspace. A paid build or managed operation requires a separate written agreement.

3. Enquiries and pilot access

Submitting an enquiry asks us to consider your idea. An operator reviews it. Submission does not guarantee acceptance, reserve capacity, place an order or authorise spending.

You can create an account using email and password and, where supported, add a passkey. Access to pilot test submissions is limited to invited users; creating an account does not by itself grant that access.

Keep your sign-in methods secure and tell us if you suspect someone else is using your account. Use the workspace only for records and projects you are entitled to access. If you represent a business, you must have authority for the information and decisions you submit on its behalf.

4. Information you submit

You retain your rights in the material you submit. You allow us to use it as needed to review your enquiry, provide the workspace and discuss or administer the project, as described in the privacy notice.

Keep enquiry descriptions brief and use test information in the pilot workspace. Do not submit sensitive personal information, customer records, production credentials or material you have no right to share. Do not use the service unlawfully, interfere with its operation or try to access someone else's records.

Pilot approvals record your decision on the proposal version shown. They do not create a paid services agreement, activate agents or authorise a production launch.

5. Before paid work begins

A separate quote and service agreement must define the scope, deliverables, acceptance criteria, delivery process and timeline, included revisions, price, payment schedule and separately billed costs. It must also say whether the engagement is build-only or includes ongoing operation, and state any minimum term, cancellation arrangements and handover responsibilities.

These details are specific to the project. The website does not promise a fixed delivery time, unlimited revisions or an open-ended amount of work. Changes outside the agreed scope require agreement on their effect on price and delivery.

6. Starting prices and costs

Published pilot starting prices are €7,500 for a build and €1,500 per month for managed operation. They exclude VAT and are subject to the written scope and quote. They are not an offer to deliver every application at those prices.

The ongoing service fee and variable allowances are distinct. Infrastructure, development AI, application AI usage and paid marketing may be separately metered. The agreement must identify those costs, any provider markup, billing delays and costs that cannot be strictly capped. A contingency allowance is not an automatic charge.

No charge arises merely from visiting the site, sending an enquiry or testing the workspace. Payments and commercial commitments begin only under the separate agreement you accept.

7. Budgets and approvals for an operating service

The intended operating model uses an agreed objective, permissions and monthly spending authorisation. In that model:

• Authorised is the amount you have explicitly approved. Only you can authorise an increase.
• Recorded means charges providers have reported; billing delays may affect how current that figure is.
• Committed means work or services already ordered that may not yet appear on an invoice.
• Forecast is an estimate of the month-end position, not a guaranteed final invoice.

The proposed default policy protects a reserve for essential operation and pauses optional development or paid marketing first when spending approaches the limit. The agreement must specify how this works, including notifications and any degradation or suspension process if essential operation is at risk. Revenue does not automatically authorise more spending.

You must explicitly approve the MVP and first production launch. After launch, routine work may proceed within standing permissions; material changes require the approval specified in your agreement. These operating controls are not activated by the current pilot workspace.

8. Support, security and outcomes

Support coverage, incident handling and any specialist security work must be defined in the service agreement. Analysing support signals is not the same as providing a complete customer-support service. Automated assessment does not guarantee that an app is free of vulnerabilities.

A feature release or completed experiment is not a promise of growth, profitability or self-funding. We do not guarantee a particular commercial result.

9. Ownership and leaving the service

The paid agreement must distinguish application-specific code and data, domains and accounts, third-party licences and our reusable service platform. It must define the access, exports, deployment information and operational history provided on handover. These website terms do not transfer ownership of a future application or settle rights that belong in that agreement.

10. Availability and ending pilot access

The pilot may change and may be unavailable while we maintain or develop it. We may restrict access needed to protect the service or address misuse, and will explain the reason where lawful and practicable. If we decide to close the pilot workspace, we will notify account holders and explain how to request their records.

You can stop using the workspace and request an export or deletion by writing to unattended@seier.ai. The privacy notice explains the handling of those requests and any information that may need to be retained.

11. Responsibility, law and disputes

Nothing in these terms excludes or limits liability or rights that cannot lawfully be excluded or limited. Responsibilities and liability for a paid build or operating service belong in its separate agreement. These website terms do not impose a blanket waiver of claims.

Danish law governs these terms, subject to any mandatory protections that apply to you. Please contact us so we can try to resolve a disagreement. Nothing here removes a right to bring a claim before a court or authority available to you under mandatory law.

12. Changes to these terms

The version and date above identify these terms. We will publish updates here and notify affected account holders about material changes before they apply. Changes do not retrospectively alter a paid service agreement or a commitment already agreed in writing.