Security & privacy

Your conversations are processed in Uzbekistan

Text conversations are processed by the EYWA model on servers in Uzbekistan. Images and video are generated by external models — and we say so plainly.

Your data
What protects your chats
Data center · UzbekistanText conversations are processed here
TLS 1.3 encryptionData is protected in transit
The model doesn't learn from your chatsConversations and documents aren't used for training
Role-based accessEven inside our team

Protection at a glance

  • Uzbekistanservers and processing — text chat never goes to external AI
  • TLS 1.3encryption for data in transit
  • By roleaccess to data — even inside our team
Said plainly

What stays with us and what external models receive

Your chats are processed by the EYWA model. External models receive only the image or video request.

Servers in Uzbekistan
EYWA model
Your chats with EYWA
Conversation history
Your documents
External models
Image and video generation only
The generation request
Materials attached to the request
Conversation history and documents
Not shared
Policy

How we handle your data

Where data lives, how it's protected, who can see it and how long it's kept.

Data center in Uzbekistan

Conversations are processed by the EYWA model on servers in Uzbekistan. Your chats are not sent to OpenAI, Anthropic, Google, or any other external chat service.Image and video generation runs on external models. They receive only the generation request and the materials attached to it — not your conversation history or your documents.This approach reduces sanctions and legal risks and keeps your conversations within the local perimeter.

Encryption

Data in transit is protected by TLS 1.3, and data at rest is encrypted at the infrastructure level.Histories, files and user materials are isolated at the access level and linked only to your context.Even within the team, access to data is limited by roles and purpose.

Not used for training

Your conversations and documents are not used to train the EYWA model further.We don't sell or transfer this data to third parties for ML tasks.For corporate clients, separate legal terms and NDAs are possible.

Moderation and protection

The service checks requests for dangerous or prohibited content without turning the product into a total surveillance tool.Flagged cases are separated from regular user sessions and processed in a limited perimeter.This helps protect the service without breaking the everyday experience of a normal user.

Retention periods

Conversation history is kept for memory, projects and continuation of work until you delete it yourself.Temporary files and auxiliary materials are cleared according to internal retention policies.When an account is deleted, associated user data is removed from the active perimeter and backup cycles per regulation.

Control stays with you

You can request data export, account deletion and clarification on the stored user context.For sensitive scenarios, it's always better to agree on storage and access requirements with our team in advance.If you have compliance requirements, we discuss them before launch, not after an incident.

Still have questions?

Questions about data and security — write to us directly

Need separate storage terms, compliance answers, an audit or a private deployment? We'll agree on it with you before launch.