HOW AISONA WORKS

Data security and control

Your own API accounts

Each user connects their own keys and has a separate history and cost log. The service does not replace a missing key with the administrator's key. Profiles and analyses of other users are not available via the panel or account API.

Access protection

API keys and service mail passwords are encrypted on the server using AES-256-GCM. User passwords are stored as salted scrypt hashes. Sessions feature random hashed tokens, HttpOnly/Secure/SameSite cookies, and CSRF protection. Open registration requires email confirmation. Reset links are short-lived and single-use.

Data and model training

Hub does not use customer content to train models. Separate terms apply at providers: OpenAI API and Anthropic API as a rule, they do not train on business data without consent. In the event of Google Gemini the service type and region matter; apps made available in the EEA require Paid Services with active billing. Terms DeepSeek and providers accessed via OpenRouter must be checked before sharing confidential data. Using an official API does not guarantee in all cases that data will not be used for training, that there will be zero data retention, or that data will be processed in the EU.

Protection limits

Tasks and responses are processed on the Hub server and by selected AI providers. This does not provide end-to-end encryption against access by the infrastructure operator. Using your own key does not automatically ensure compliance with company requirements, processing in a specific region, or a specific retention period at the provider. The privacy policies and agreements must be appropriate for your use case.

Resilience and recovery

The platform runs over HTTPS with process isolation and resource limits. Database and configuration data backups are rotated on a 7-day cycle and protected by access controls. Canceling an analysis limits further calls; requests already in progress may still incur charges. After a server restart, interrupted tasks are not automatically retried to avoid unexpected costs.

Control on your side

You can switch profiles, view usage, export data, invalidate other sessions, and delete your account. Send security information and vulnerability reports to ai@solution-systems.pl. Do not publish API keys or other people's materials in your report.

Choose where your data goes

Direct DeepSeek API use can involve processing and storage in China. Before sending company data, review the current provider terms and your transfer requirements. OpenRouter is also an intermediary: only an explicitly supported regional endpoint and suitable provider settings can constrain routing. This integration currently uses OpenRouter’s global endpoint and does not guarantee EU-only processing.

Provider privacy policy