Zero Data Retention Statement
NEXTBIT 256, S.L. — Data Handling Attestation 4 November 2026
1. Purpose and Scope
This statement is issued by NEXTBIT 256, S.L. ("Nextbit") in response to requests from customers and prospective customers seeking attestation of our data retention practices in connection with the use of our AI inference Services.
It summarizes commitments set out in Nextbit's Terms of Service, Privacy Policy and Data Processing Agreement, which are the binding documents. For questions or to request copies of Nextbit's binding data protection agreements, contact [email protected].
2. Service Endpoints
Nextbit's API is available through two endpoints:
| EU Endpoint | Global Endpoint | |
|---|---|---|
| Base URL | https://eu.api.nextbit256.com/v1 | https://api.nextbit256.com/v1 |
| Available models | https://eu.api.nextbit256.com/v1/models | https://api.nextbit256.com/v1/models |
| Label in the website model catalogue | EU | Multi |
| Where inference runs | European Union: Nextbit-owned servers (own data center or colocation) and servers of third-party cloud infrastructure providers | Third-party cloud infrastructure, nodes outside the EEA |
| Third parties performing inference | Third-party cloud infrastructure providers, for models not served on Nextbit-owned servers | Third-party cloud infrastructure providers |
For both endpoints, API traffic is received by an API gateway hosted within the European Union, which handles request content only transiently, in transit, and does not store it.
3. Summary of Commitments
"Request Content" means the prompts, inputs and files submitted in a model inference request through the API, the outputs generated in response, and any logs containing them. Request Content does not include: (i) Request Metadata, including usage data (such as token counts) and indicators of request characteristics (such as whether tools, structured output or images were used); (ii) prompt cache and one-way hashes used for caching and request routing; or (iii) information provided outside an inference request, such as account data, support requests, feedback or other communications with Nextbit, even if it contains prompts or outputs.
| Commitment | EU Endpoint | Global Endpoint |
|---|---|---|
| Request Content retained after the request is completed | Never* | Never*, save where required by law — and then max. 30 days |
| Request Content written to persistent storage or logs | Never* | Never*, save the legal exception above |
| Request Content used to train, fine-tune or develop AI models | Never (Nextbit and its infrastructure providers) | Never (Nextbit and its infrastructure providers) |
| Request Content disclosed to third parties | Never, save to the infrastructure provider processing the request or where required by law | Never, save to the infrastructure provider processing the request or where required by law |
| Inference performed within the EU | Yes | No |
| International transfer safeguards | SCCs / DPF for the API gateway provider and, where applicable, the cloud infrastructure provider | SCCs |
* Excluding the prompt cache described in Section 6.
4. EU Endpoint — Zero Data Retention
Subject to Section 6, Request Content submitted through the EU Endpoint is processed in memory on servers located within the European Union for the sole purpose of generating the response, and is discarded once the request has been completed. It is not written to persistent storage or logs, is not accessible to Nextbit personnel after the request is completed, and cannot be retrieved, reproduced or disclosed afterwards — including in response to a legal request — because it no longer exists.
Some of these servers are owned by Nextbit and hosted in its own data center or in colocation facilities, and others are provided by third-party cloud infrastructure providers. Those providers are contractually bound not to use Request Content to train, fine-tune or otherwise develop any model, not to disclose it to any third party save as required by law or legal process, and not to retain it after the request has been completed.
5. Global Endpoint — No Retention, with a Narrow Legal Exception
Subject to Section 6, Request Content submitted through the Global Endpoint is processed on third-party cloud infrastructure providers' nodes located outside the EEA. Neither Nextbit nor those providers retain Request Content after the request has been completed, save where retention is required by applicable law, in which case it is retained for no longer than thirty (30) days and used for no purpose other than compliance with that legal requirement.
The infrastructure providers are contractually bound (i) not to use Request Content — including prompts, outputs and logs — to train, fine-tune or otherwise develop any model; (ii) not to disclose it to any third party, save as required by law or legal process; and (iii) not to retain it beyond the limits stated above.
6. Prompt Caching — Exception
On both endpoints, to accelerate subsequent requests that share the same initial content, Nextbit may cache key-value tensors computed by the model from Request Content after the request is completed. Such cache may be reused only for requests to the same model from the same customer account or, for requests received through a third-party gateway, router or marketplace that routes requests to the Services (an "AI Gateway"), from the same AI Gateway, and is never made available to the customer or any other customer. The cache: (i) contains only key-value tensors and a one-way lookup hash, and never Request Content in plain text or token identifiers; (ii) is not written to logs, backups or any durable storage outside the cache; (iii) is held only on the serving infrastructure of the endpoint called, which may include servers of a third-party infrastructure provider, and, where held in persistent storage, is encrypted at rest; and (iv) is evicted automatically when capacity is needed or upon expiry of a maximum retention period, and is never retained indefinitely. Such caching does not constitute storage or retention of Request Content for the purposes of this statement.
7. Request Metadata
To operate, bill and secure the Services, Nextbit records technical metadata for each API request that does not contain Request Content — such as timestamps, model used, token counts, API key identifier, IP address, response status and latency. This metadata is retained for as long as necessary for billing, security, abuse prevention and compliance with legal obligations (including accounting and tax obligations). It is not used for any other purpose.
8. No AI Model Training — Contractual Basis
The prohibition on using customer data for AI model training is a binding contractual commitment, not merely a policy statement. Nextbit's agreements with all customers include the following commitments:
- "Nextbit does not use Request Content to train, fine-tune, evaluate or otherwise develop any AI model, and its infrastructure providers are contractually prohibited from doing so." (Terms of Service, Section 5.3)
- "Your Personal Data and Request Content will not be used to train, fine-tune or otherwise develop AI models, whether by Nextbit or by any of its providers." (Privacy Policy)
- "Nextbit does not use Personal Data submitted by the Controller, whether through the EU Endpoint or the Global Endpoint, to train, fine-tune, or otherwise develop any AI model." (Data Processing Agreement, Section 11)
These commitments apply to all customers and all endpoints.
9. International Data Transfers and Governmental Access
EU Endpoint. Inference and storage take place within the EEA. The API gateway provider and any cloud infrastructure provider used for the EU Endpoint may be incorporated in, or have its parent company established in, a third country (including the United States); any resulting transfer is covered by Standard Contractual Clauses (SCCs) approved by the European Commission and, where applicable, the EU–US Data Privacy Framework (DPF).
Global Endpoint. Request Content is processed outside the EEA under SCCs approved by the European Commission (Commission Implementing Decision (EU) 2021/914).
Infrastructure providers, or their parent companies, may be subject to the laws of third countries that allow public authorities to compel access to data. Nextbit's no-retention commitments substantially reduce this exposure, but contractual measures cannot fully eliminate it. Customers for whom third-country governmental access represents a material risk should use the EU Endpoint exclusively. The EU Endpoint may also use third-party infrastructure providers and does not by itself eliminate this exposure.
10. Special Categories of Personal Data
Nextbit's Services are not designed or intended for the processing of Special Categories of Personal Data as defined in Article 9 GDPR (including health data, genetic data, biometric identification data, and data concerning racial or ethnic origin, political opinions, religious beliefs, sexual orientation, or sex life). Submission of such data through the standard Services is prohibited. Customers requiring such processing must execute a separate written addendum with Nextbit prior to use.
11. Customer Rights and Deletion
As Request Content is not retained, there is no Request Content to delete or return upon termination. Any prompt cache is evicted automatically as described in Section 6. Upon termination of a customer's agreement with Nextbit, account data and Request Metadata associated with that customer are deleted within 60 calendar days, except where retention is required by law. Customers may also request deletion in writing at any time by contacting [email protected].
Customers retain the right to request information about their data, correct inaccuracies, object to processing, and request data portability, in accordance with applicable data protection law (GDPR, LOPDGDD). All such requests should be directed to [email protected].
12. Enterprise and Custom Arrangements
Customers operating in regulated sectors or with specific compliance requirements — including enhanced audit rights or dedicated infrastructure — are invited to contact Nextbit at [email protected] to discuss available arrangements. Nextbit does not guarantee the availability of any specific custom arrangement but will engage in good faith with customers who present documented compliance requirements.
13. Contact
For questions regarding this statement or Nextbit's data handling practices:
NEXTBIT 256, S.L. Carrer del Moll de la Duana, s/n, Edificio Lanzadera 46024 Valencia, Spain [email protected] https://www.nextbit256.com
This document reflects Nextbit's data handling practices as of 4 November 2026. It may be updated to reflect changes in Nextbit's Services or applicable law. The current version is available upon request from [email protected].