Security commitments · V3.7.9

Safety first, privacy always

EIJE never redraws official pages and never auto sends drafts. Local isolation, server side authority and data minimization define the product boundary.

Download V3.7.9

Security

Which security commitments can you verify?

Six commitments cover page boundaries, credentials, sending, storage, quotas and data scope. Every one of them can be verified directly in product behavior, not just promised.

Official pages are never redrawn or blocked?

EIJE loads the official pages of each platform as they are. Nothing is redrawn, no interface is modified, and no official feature is intercepted. The chat window you see is exactly the platform's own page.

No second entry of platform credentials?

Sign in still happens on the platform's own page. EIJE never asks you to re-enter credentials for third party platforms and never stores them.

Editable drafts that never auto send?

Everything AI generates is a draft. You edit freely and send manually. EIJE never sends a message on your behalf.

Local sessions isolated per account?

Sessions and settings stay on the local device, isolated per account. Context never bleeds across accounts or platforms, and data is not synced between devices.

Character quotas verified server side?

Plans and character usage are recorded and verified by the EIJE service side, in real time and auditable. No local change can alter billing results.

Only the data a task needs gets processed?

EIJE reads only what the current conversation needs to finish the task, keeps nothing beyond the session, and follows data minimization throughout.

Security

How do messages and quota data flow through EIJE?

Conversation data stays on the local device, isolated per account, with no cross device sync. Translation requests carry only what the current conversation needs.

Character quotas are recorded and verified by the EIJE service side. Plans, character counts and purchases are visible in real time, and no local change can alter billing.

Security

How do registration and local sessions protect accounts?

Creating an EIJE account completes a secure verification, credentials are encrypted locally, and the principle of least privilege applies throughout. Platform logins still happen on the platforms' own pages, so EIJE never touches those credentials.

Every account keeps an isolated local session. After a device change you sign into each platform again, which is exactly what data staying on the device looks like.

Security

How does the privacy policy define data boundaries?

The privacy policy follows data minimization: only what the current conversation needs is processed, nothing sensitive is kept beyond the session, and nothing unrelated is collected.

The full policy text will be published on this page. For data processing questions, reach the team through Telegram @Eijefy.

Security

How do the terms of service define usage?

The terms cover accounts, plans, character quotas and compliant usage. Holding the right to use your platform accounts is a precondition of using EIJE.

The full terms text will be published on this page. Questions reach the team through Telegram @Eijefy.

Updated August 14, 2026