1. Agreement and eligibility
These proposed terms govern access to Atomic’s app builder and associated services. Once finalized, they will identify the legal provider and explain how you accept the agreement. A person accepting on behalf of an organization must have authority to bind it.
To finalize: provider legal name, address, registration, minimum age, service territories, effective date, and acceptance flow. This draft does not create a subscription or bind a visitor merely by viewing it.
2. The service and early access
Atomic helps users describe, generate, refine, inspect, and publish applications. AI-generated results may be incomplete, inaccurate, insecure, or unsuitable for a particular use. You must review and test results before using them with real users or data.
Early-access features may change, have limited availability, or be withdrawn. Roadmap descriptions are not delivery commitments. Homepage demonstrations use local sample data and do not create live applications or transactions.
3. Accounts and workspace access
You are responsible for providing accurate account information, protecting credentials, and controlling access granted to your workspace. Notify the team promptly if you suspect unauthorized access. Do not share credentials in prompts, source repositories, or support messages.
Organizations are responsible for the actions of authorized users within their workspace, subject to applicable law and the final agreement.
4. Plans, fees, and credits
The pricing page currently describes proposed plans, not an offer to start a paid subscription. The final checkout must disclose the plan, currency, taxes, billing frequency, included usage, extra charges, renewal terms, and cancellation process before payment.
Any credit system must define how units are consumed, how failed or retried operations are treated, when balances expire, and whether unused balances roll over. Auto-renewal, top-ups, and automatic replenishment require clear disclosure and any required authorization.
To finalize: all allowances and rates, payment provider, renewal notices, cancellation method, credit expiry, refunds, charge disputes, and applicable consumer withdrawal rights. Mandatory consumer rights prevail over conflicting terms; no blanket non-refundable rule is established by this draft.
5. Content, source, and licenses
You retain rights you hold in the content you provide. As between you and the provider, the proposed arrangement is that you receive the provider’s transferable rights, if any, in generated output, subject to applicable law and third-party rights. AI output may not be unique or eligible for intellectual-property protection.
You grant the provider the limited rights needed to process your content to supply, secure, and support the service on your instructions. The provider retains rights in Atomic’s platform, branding, and pre-existing materials. Third-party dependencies and open-source components retain their own license terms.
To finalize: confirm output-rights language against model-provider contracts and approve any separate training or improvement use. This clause does not authorize unrestricted training on customer data.
6. Your apps and responsibilities
You are responsible for the information you submit, rights to use supplied materials, and the apps you choose to publish. Review generated code, permissions, business rules, notices, and third-party integrations. Follow the Acceptable Use Policy.
You are responsible for your relationship with the people using your app, including appropriate privacy notices, lawful data collection, customer support, and any regulated activity. Atomic’s own policies do not replace the documents your app may require.
7. Privacy, data, and portability
The Privacy Notice describes the provider’s own processing. A completed DPA governs processing on a customer’s behalf where applicable.
Source downloads do not include customer accounts, business records, or hosting infrastructure. Restoring source or rolling back a frontend release does not restore business data. Broader packaging and deployment options are roadmap items. Confirm supported export and recovery procedures before relying on them.
8. Suspension and termination
The proposed service terms allow proportionate restrictions where necessary to address unlawful use, a material breach, nonpayment, or a credible security risk. Where appropriate, the provider should explain the issue and allow an opportunity to resolve it, except where immediate action or confidentiality is required.
To finalize: notice periods, appeal process, consequences of cancellation, app availability, export access, deletion timing, prepaid-fee treatment, and treatment of unused credits. These consequences must be disclosed before a subscription begins.
9. Warranties and liability
Generated output requires review, and no early-access material should be read as a guarantee of uninterrupted availability, error-free software, regulatory compliance, or fitness for a particular purpose. Any agreed service levels must be documented separately.
To finalize with counsel: express warranties, permissible disclaimers, liability caps and exclusions, intellectual-property claims, indemnities if appropriate, and exceptions for liability that cannot legally be limited. No numerical liability cap is established in this draft.
10. Changes, disputes, and contact
Material contractual changes should be communicated in advance as required by applicable law and the final agreement. Any separate signed order or enterprise agreement should specify how it interacts with these terms.
Contact info@absmach.eu about a service or contractual concern.
To finalize: governing law, courts or dispute mechanism, consumer protections, notice methods and periods, assignment, severability, and order of precedence. No jurisdiction is inferred from a brand name or website address.