Privacy Policy

Controller and contact

The service operator and data controller is Bartłomiej Brzozowski, trading as Nagame, NIP 9561854023, EU VAT ID PL9561854023, REGON 385636679, Poland. For privacy enquiries and requests, use the contact section on the Nagame homepage.

Data processed

When you use the inference API, Nagame processes prompts, messages, supplied files or tool data, and model completions as necessary to provide the requested inference. Please do not submit personal data or confidential information unless it is necessary and you are authorised to do so.

Operational systems may also process timestamps, requested routes, response status, token counts, latency, backend selection, error diagnostics, and source IP addresses. API credentials are processed for authentication. They must not be included in application logs.

For accounts and purchases, Nagame processes email address, billing contact details, country, tax status and identifiers, purchase and refund records, credit balances, and usage charges. Stripe collects and processes payment-card or other payment-method details; Nagame does not receive complete card numbers.

Purposes and legal bases

• Providing, authenticating, securing, and supporting the service: performance of a contract or steps requested before entering one under Article 6(1)(b) GDPR.
• Operating, troubleshooting, protecting, and improving service reliability: Nagame's legitimate interests under Article 6(1)(f) GDPR, balanced against users' rights.
• Accounting, billing, and responding to binding legal requirements: compliance with legal obligations under Article 6(1)(c) GDPR.

Inference content

Nagame does not store or retain inference input or output content after delivering the response. This includes prompts, messages, supplied files, tool data, and model completions submitted through the API or public live chat. Content is processed transiently only to provide the requested inference and is not used to train or fine-tune models.

Retention

Inference input and output content is not written to persistent storage and is not included in backups. Nagame retains non-content usage and operational records as needed for accounting, billing, security, troubleshooting, and legal obligations. These records may include a request identifier, account or API-key identifier, model, timestamps, response status, input and output token counts, cost, latency, backend selection, error diagnostics that exclude inference content, and source IP address. Retention varies by system and record type; Nagame does not promise a fixed retention period. Records required by law may remain for longer.

Recipients and transfers

Infrastructure, hosting, DNS, connectivity, email-delivery, and marketplace services may process limited personal data as processors or independent controllers, as applicable. Stripe processes account, billing, tax, fraud-prevention, and payment data for Checkout and payment operations under its own applicable privacy terms. Data is disclosed only where needed to provide and protect the service or where legally required. If personal data is transferred outside the European Economic Area, Nagame will use an applicable GDPR transfer mechanism and safeguards where required.

Security

Nagame uses technical and organisational measures intended to protect data, including HTTPS at the public edge, encrypted private connectivity between infrastructure components, access controls, and authentication controls. No system can guarantee absolute security.

Your rights

Subject to the GDPR and applicable limitations, you may request access, correction, deletion, restriction, portability, or object to processing based on legitimate interests. You may also withdraw consent where consent is the legal basis. Deletion requests may be limited by legal, billing, security, backup, and technical requirements.

Submit requests through the contact section on the Nagame homepage. Nagame may need to verify your identity. You may lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych) in Poland or another competent supervisory authority.

Changes

This policy may be updated as the service or legal requirements change. The effective date above identifies the current version. Material changes will be communicated through an appropriate service channel.