# Service terms Source: https://convergingthought.com/docs/terms > Accounts, usage, payments, and responsibilities. Effective September 27, 2026. Internalize is operated by Steelworks Software LLC, a limited liability company registered in Delaware, United States. These terms cover the Internalize website, console, and API. If you use the service for an organization, you must have authority to act for it. ## Your account and applications [#your-account-and-applications] Provide accurate account information, protect your credentials, and revoke keys you believe are compromised. You are responsible for applications and authorized users operating through your project. Authenticate your own customers and enforce their tenant boundaries in your backend; a memory name or tenant identifier is not an end-user login. Use the service only for content and applications you are authorized to operate. Do not infringe others' rights, conduct unlawful activity, bypass access controls or spending limits, interfere with the service, or try to access another customer's data. Applicable model and infrastructure provider use restrictions also apply to the underlying services. ## Your content and learned state [#your-content-and-learned-state] You retain your rights in submitted content. You authorize us and the service providers described in our [privacy notice](/docs/privacy) to process that content to perform your requests, train your private adapters, host learned state, and maintain the service. This permission does not transfer ownership of your content to us. You are responsible for obtaining the rights and permissions needed to submit data, including data belonging to your customers. Contact us before submitting data that requires a separate processing agreement or controls we have not agreed to provide. ## Usage and payment [#usage-and-payment] Usage is prepaid, with a $10 minimum purchase and no free spend or automatic top-up. [Published pricing](/internalize/pricing) applies to metered usage. Polar is our merchant of record and handles checkout, applicable taxes, payment receipts, and refunds under its checkout terms. Taxes are shown before payment. Each learning request requires a total spending cap. That cap is a maximum authorization, not a fixed charge or a guarantee that the request will complete. Completed compute can be billable when learning does not pass validation or reaches its cap. Infrastructure failures follow the failure policy in our [billing documentation](/docs/billing). There is no flat fee for a successful internalize call. Credits are for service usage and cannot be transferred between customers. To request a refund or dispute a charge, contact us with the project and order reference. We review the payment and usage records and coordinate any approved refund through Polar. Nothing in these terms limits refund rights required by applicable law. A refund or payment reversal removes the corresponding credits and may pause further usage if the remaining balance is insufficient. ## Model results and availability [#model-results-and-availability] Learning and validation do not guarantee perfect recall, understanding, or correctness. Evaluate results for your application and review them before relying on them. A passed validation set is evidence about that set, not a guarantee about every future question. Supported models, API behavior, current limitations, and availability are described in the [documentation](/docs/getting-started/availability). Preview features may be incomplete or unavailable. We do not offer an uptime commitment unless separately agreed in writing. ## Retention and changes [#retention-and-changes] Saved memory versions have an explicit expiration. The initial retention period is 24 hours; automatic paid renewal is not enabled. An expired adapter is unavailable for inference. Keep your original source data and inspect a version's expiration rather than treating hosted memory as a permanent backup. A request retains the pricing version recorded when it is admitted. Future pricing or material service changes will be reflected in the published documentation. Changes do not retroactively alter charges for completed usage. We may suspend access to address abuse, compromised credentials, payment reversals, or a service incident. ## Support and account closure [#support-and-account-closure] Contact [team@convergingthought.com](mailto:team@convergingthought.com) for support, billing questions, account closure, or data requests. Include a project or request reference, never passwords, card details, or API secrets. We may need to verify your authority before changing an account or disclosing its records. Financial, security, and unresolved-operation records may need to be retained after closure as described in our privacy notice.