1. Service provider
The name, address, country, and direct support channels of the provider operating this NULIQ deployment are published in the business card below and on the contact page. Missing details are clearly marked; new payments are disabled until they are complete.
2. Information processed
- Account: name, email, securely hashed password, account creation date, and records of acceptance of the terms.
- Access: session and API-key hashes, key names, creation and last-use information. Technical request information is also processed for security and rate limiting.
- Usage: query time, input byte count, model version, 0/1 result, cost, balance, and transaction identifiers. Raw API and Playground query text is not saved in the application’s usage table.
- Training: uploaded labeled TXT content is processed as a temporary file during training. Raw training files are removed when the job ends. Model weights, training reports, and text fingerprints used to check training/test overlap are retained.
- Quality testing: test content is processed for evaluation. Aggregate metrics, test-set fingerprints, and evaluation reports are stored.
- Payments: prepaid balance, amount, checkout and provider event identifiers, payment status, and transaction records. NULIQ does not store card numbers or security codes.
This describes the application’s data processing. Hosting and network providers may separately process connection and security logs. NULIQ does not guarantee anonymity for uploaded data or zero retention across every system.
3. Purpose and sharing
Data is processed to operate your account and API access, train and evaluate your models, calculate usage, resolve errors, and prevent abuse. This application does not use your account data for advertising targeting or send queries to an external general language-model API.
The hosting provider processes data to run the service. When payments are enabled, Stripe processes amounts, account/transaction identifiers, and information you provide during payment. Stripe’s own privacy policy also applies. Information may need to be shared with authorities in response to mandatory legal requests.
4. Retention and deletion
Account records, model files, and related reports are retained to provide the service. Deleting an inactive custom model from the console removes its weights, training fingerprints, and related evaluation reports. Usage and payment records are not automatically deleted with the model.
Send account and personal data requests through the support channels. Account deletion is currently handled through support. Requests are assessed after identity verification and review of applicable retention obligations. Accounting, security, dispute, and backup records are not guaranteed to be deleted at the same time. Ask the service provider for its specific retention periods and hosting region.
5. Cookies and security
An essential session cookie is used for login. This version does not install advertising or third-party analytics cookies within the application. Stripe’s checkout page may use the provider’s own cookies and security checks.
Passwords and API keys are stored as hashes in the database. Internet access must use HTTPS. No system can guarantee absolute security; do not upload unnecessary personal or sensitive data.
6. Your requests
Use the contact channels to request information, correction, deletion, or other actions relating to data processing. Applicable rights and obligations depend on the laws governing the provider and user. This notice makes no claim of certification or official compliance approval.