Developer terms and data processing

Developer Terms and Data Processing Bundle

Revision: developers-production-2026-10-25

These Developer Terms and Data Processing Bundle govern the ForeverLearning AI API for an organization that accepts this revision and receives an authorized production assignment. A separate signed agreement controls where it expressly changes these terms. Staging remains for synthetic test data and uses its separately versioned staging terms.

1. The service and your authority

ForeverLearning provides governed conversation capabilities through product listings and assignments. An assignment identifies the product, release, environment, rate and workload allowance available to your organization. Your organization, rather than an API key or an individual end user, holds the account and is responsible for its integrations. You represent that you are an adult authorized to act for that organization and that this is business use, including where you operate independently through a personal workspace.

Self-service eligibility is limited to adults in the United States and Canada, excluding Quebec. Education, use involving children, and companion experiences require a separate written agreement and the applicable safeguards before access is granted. Health use is unavailable under self-service. A staging account does not waive these restrictions. You must give accurate account, audience and business information and update it when it changes.

2. Accounts, roles and credentials

Each person must use their own sign-in. Console and operator access require multi-factor verification; sensitive changes require recent verification. The owner controls ownership and closure. Administrators, developers, billing members and viewers receive the permissions recorded for their role and, where applicable, their assigned products. Inviting a person does not confer ownership. You are responsible for keeping membership and contact information current and for promptly removing access that is no longer needed.

API keys are server credentials. Keep them out of browsers, mobile application bundles, public repositories, logs and messages. Restrict each key to the required products and permissions, apply appropriate budgets, and rotate or revoke a key if it may have been exposed. ForeverLearning displays a newly issued secret once; it cannot recover that secret for you. Key revocation can interrupt your integration. Your integration must handle authentication refusals, service limits and incomplete responses safely.

3. Product access and permitted integration

You may embed an assigned capability in your own product, including a paid product, within the assignment and applicable policies. You may not sell, sublicense, share or expose raw API access or API keys to another party. Access to one product does not grant access to another product, its sessions or its data. Do not attempt to bypass those boundaries, derive restricted implementation details, evade admission limits or represent output as a guaranteed professional determination.

Your organization owns its submitted content and retains responsibility for its lawful collection and use. You authorize ForeverLearning to process it only as needed to provide the assigned service and as described in the data processing terms below. ForeverLearning retains its service, software and product materials. No ownership of an underlying third party’s intellectual property is transferred by these terms. ForeverLearning grants only the service and product rights stated here or in a separate signed agreement; it does not grant rights in material it does not own or have permission to license.

4. Prices, workload allowances and changes

Each published rate is denominated in USD and applies to the versioned unit stated for the assignment. The price is fixed within that assignment’s declared workload allowance; it is not a promise of unlimited input, output, context, conversation length or request frequency. The service may refuse requests before processing when they exceed a declared boundary. It may limit sustained unusually expensive traffic while a suitable allowance or prospective rate is arranged.

Rates and limits change prospectively. A rate or limit change receives at least 30 days’ notice unless your organization expressly accepts an earlier effective date. No change reprices completed usage, silently moves an existing assignment to another band, or changes the rate recorded for a completed charge. A listing shutdown receives at least 90 days’ notice unless security, abuse, law or an urgent service risk requires earlier action. A signed managed-account agreement may specify a different agreed commercial arrangement. The current assignment and its rate version are the record of what applies.

5. Balance, charges and refunds

The service uses prepaid paid credit, promotional credit and audited adjustments as distinct lots. Paid credit does not expire in the initial service. Promotional credit may have disclosed restrictions and an expiry. Credit is for the organization’s permitted API use and is not transferable cash. Applicable taxes and the total payable are shown before a permitted payment. Payment methods are available only when enabled for your account. Staging checkout uses test payments and creates no right to a real-money refund.

For Conversation API usage, each billable text turn costs $0.03. A successful saved whole-turn audio generation adds $0.05, covering the participating voices and spoken coaching ($0.08 total for a billable text turn with audio). Audio is charged once only after the complete audio generation is saved successfully; an unsuccessful or partial generation is not an audio purchase. Replaying saved audio is free for 24 hours from creation, subject to earlier deletion. Explicit regeneration is a new audio purchase. Voice requires sufficient balance; text grace and safety credits remain available under their existing rules. Other capabilities use the rate recorded in their assignment. A governed text turn is charged when processing is dispatched. A charge is returned when the service observes a failure before any content is sent. A completed durable closeout is one separately charged unit; an unsuccessful closeout is not charged. Closeout may be triggered by an explicit end, a new session for the same end user or a conversation limit. The service permits at most three closeout attempts per session. A turn positively classified as critical by the service’s safety disposition is credited back. Missing or unevaluated safety information is not itself grounds for a credit. Managed-account completion terms remain governed by their agreement.

An idempotency key, where supported by the assigned API version, identifies the same operation and body for retry. Do not change the body under an existing key. An interrupted connection alone does not establish whether a turn was charged. Inspect the operation result and account usage before initiating a different operation. The API reference states the guarantees actually implemented by each route and version; these terms are not evidence that a future guarantee is already enabled.

New conversation admission may stop as funds run low. The intended self-service policy permits a bounded continuation of an existing conversation, subject to an organization floor and per-conversation limits shown by the service. It does not grant an unlimited overdraft or a new conversation. Crisis handling that the service identifies for a safety exception is funded by ForeverLearning. Your application must handle a refusal without hiding the outcome from the end user.

An owner or billing member may request a refund of unused paid principal. An authorized finance operator reviews and initiates an eligible refund after accounting for active reservations and previous refunds. Promotional credit is not refundable. A request receipt is not a completed refund. Refunds and disputes are recorded as compensating entries, not by rewriting past charges. On account closure or platform shutdown, unused paid principal is to be returned subject to outstanding lawful obligations and the applicable payment process. Dormant paid balances are not treated as income solely because they are inactive; unclaimed-property treatment requires the applicable accounting review.

6. Safety and your end users

You are responsible for your product’s audience, age and eligibility checks, AI disclosures, notices and consents, accessibility, lawful data collection, and any professional or regulated duties. Provide an appropriate human escalation path and comply with reporting obligations applicable to your product. Do not present the API as an emergency service or as monitored by a person in real time. You must evaluate whether the assigned product’s published safety protocol is appropriate for your audience before deployment.

ForeverLearning’s operating model uses aggregate alerts about service and safety patterns. An opt-in developer webhook may provide pseudonymous safety signals when that capability is enabled. A delivery failure must not block the conversational response. ForeverLearning does not provide staffed per-event monitoring or contact your end users unless a separate written agreement expressly assigns those duties. An absent signal is not an assurance of safety. Your organization remains responsible for receiving and acting on the signals it agrees to consume.

7. Acceptable use

Do not use the service for unlawful activity, exploitation or sexual abuse of children, targeted violence, threats, fraud, credential theft, malicious software, non-consensual intimate material, harassment, privacy violations or attempts to obtain another organization’s data. Do not conduct regulated medical, legal, financial or other professional decision-making under a general self-service assignment. Education, children and companion uses require the separate agreement described above. Do not bypass safeguards, conceal prohibited use, defeat rate limits or conduct destructive security testing without written authorization.

Applicable third-party usage restrictions are identified in the platform policy set supplied for your assignment. Report suspected abuse to safety@foreverlearning.ai and suspected security issues to security@foreverlearning.ai. These reporting routes do not provide an emergency service or a guaranteed response time. Enforcement may include a warning, reduced limits, key revocation, product restriction, suspension or termination according to severity. Urgent risks may require immediate action without a prior warning.

8. Data processing instructions and responsibilities

For customer end-user content, your organization acts as the controller or business deciding the purposes of processing, and ForeverLearning acts as its processor or service provider. The subject matter is providing the assigned conversation capability. Processing includes receipt, storage, retrieval, generation of conversational responses and related memory or profiles, transmission to authorized service infrastructure, export and deletion. The affected individuals are the end users and authorized personnel you permit to use the integration. Data may include prompts, responses, pseudonymous identifiers, conversation history and the profile or memory derived from that content. Do not submit special-category, health, children’s or other restricted data without the required agreement and safeguards.

ForeverLearning will process customer content only on your documented instructions, including the assignment, these terms and authorized API requests, unless law requires otherwise. It will not use that content to train general-purpose systems or for unrelated secondary purposes. Aggregate service metrics may be used to operate and improve the service without exposing customer content. Personnel access must be limited to authorized purposes and subject to confidentiality obligations. If an instruction appears unlawful, ForeverLearning will notify the customer unless prohibited by law and may suspend the affected processing while it is resolved.

The customer must provide a lawful basis, required notices and consents, an authorized contact and instructions that it is entitled to give. The customer must use pseudonymous end-user identifiers where possible, avoid unnecessary personal data and verify that an export or erasure request is authorized. An assignment-specific erasure must not erase another assignment’s lawful data through a shared identity.

9. Security, subprocessors and incidents

ForeverLearning maintains access controls, scoped credentials, multi-factor console access, transport encryption, segregation of organizations and assignments, audited privileged changes, appropriate retention controls and an incident response process. The security description and platform-level subprocessor register supplied for the assignment identify the applicable infrastructure and processing locations. No certification or insurance coverage is represented by these terms.

ForeverLearning will provide at least 30 days’ advance notice of a proposed material change, with an opportunity to raise a documented data-protection objection before the change. Processing locations must follow the agreed content region and the reviewed transfer terms; selecting a conversation region does not imply that all account, billing or operational records are stored only there. ForeverLearning remains responsible for imposing appropriate processing and confidentiality obligations on its authorized subprocessors.

ForeverLearning will notify the customer without undue delay and within 72 hours after confirming a personal-data breach affecting the customer’s processor data. The notice will describe known facts, likely consequences and mitigation, and will be supplemented as the investigation develops. The customer remains responsible for its own required notifications, with reasonable assistance from ForeverLearning. Neither party should treat an incomplete initial notice as proof that the investigation is finished.

10. Rights requests, retention and deletion

End-user rights requests received by ForeverLearning in its processor role will be directed to the customer. ForeverLearning will assist with a documented request within 10 business days, subject to verifying authority and scope. The customer controls requests submitted through the export and erasure capabilities. The service returns an auditable receipt and identifies any lawful retention exception rather than claiming that unrelated financial records were deleted.

The default retention is 180 days from last activity for live conversation content and 30 days for sandbox content, with derived memory and profiles following the same clock as their source conversation. An assignment may state a different agreed policy. Minimal pseudonymous safety records contain no transcript and are retained for 24 months unless an agreement requires a different period. Financial records contain no conversation content and are retained for the period established by the applicable accounting and legal requirements. Saved Conversation audio expires 24 hours from creation, or earlier on session or user deletion. Staging uses synthetic data only.

On termination, customer processor content will be returned or deleted at the customer’s choice within 30 days, except where law requires retention. Deleted content may remain in isolated backups for up to eight days, during which it is not used for ordinary processing and is removed through backup expiry. A legal retention exception must remain access restricted and limited to its required purpose. The customer may request information reasonably needed to assess compliance with these processing obligations, subject to confidentiality and protection of other customers’ information.

11. Account privacy

ForeverLearning acts as controller for developer account, contact, membership, authentication, billing and security-administration data used to manage the business relationship. It uses those records to authenticate people, administer access, provide receipts and notices, prevent abuse, resolve support requests, maintain financial records and meet legal obligations. Customer conversation content is governed by the processor terms above rather than repurposed as account marketing data.

Account information may be disclosed to authorized service providers under appropriate obligations or when law requires it. It is not made public merely because a person joins a developer workspace. Retention follows the purpose of the record and applicable obligations; closing a workspace does not erase records that must lawfully be preserved. Account privacy questions and rights requests may be sent to privacy@foreverlearning.ai. The account privacy terms in this section apply separately from the customer-content processing terms above.

12. Availability and commercial responsibility

The staging environment has no uptime commitment, service-level agreement or production-support promise. It may be interrupted, reset or withdrawn during testing. Generated output may be incomplete or incorrect and must be reviewed in the context of your product. No regulated, emergency or professional outcome is warranted. Production service is provided without a contractual uptime guarantee unless a separate signed agreement states one. These terms do not represent insurance coverage, audited compliance or a warranty of third-party rights.

Any additional service warranties, negotiated liability cap, indemnities, governing-law selection or exclusive venue must be stated in a separate signed agreement. These terms do not create such additional warranties, a negotiated liability cap, an indemnity or an exclusive forum. Each party remains responsible for its obligations under these terms and applicable law, including rights and liabilities that cannot lawfully be excluded. A successor to ForeverLearning through a lawful corporate conversion or reorganization may assume this agreement only with its obligations and required notice; a conversion does not extinguish customer credit or data-protection duties.

13. Acceptance, notices and versioning

The console records the accepting person, organization, time, revision and SHA-256 digest of the terms presented, together with the eligibility and business declarations. Acceptance of this production revision binds the organization to these terms for its authorized production assignments. Earlier staging acceptance does not accept this revision. Material changes require advance notice and any acceptance required by applicable law or a separate signed agreement; prospective commercial changes follow section 4. Keep a copy of the revision your organization accepts and maintain a reachable contact for notices.

For developer support, use developers@foreverlearning.ai. Do not include API keys, payment data or real end-user content in a support message. The request ID displayed by the console is the preferred reference for a specific operation.