AkkamChat end-to-end encryption

Exactly what AkkamChat end-to-end encrypts

Production traffic is also transmitted through encrypted HTTPS and secure WebSocket connections.

In current supported app versions, the following human-conversation content is encrypted on the sender’s device and can be decrypted only by the intended participants’ devices:

• Direct and group text messages
• Voice messages
• Photos, videos, documents, and other supported attachments
• Shared locations
• Poll questions and votes
• Reactions, replies, edits, and forwarded human-conversation content
• Scheduled-message content
• Stories and broadcasts
• Supported encrypted backups
• Audio and video call media

AkkamChat’s normal backend and storage systems are designed to receive ciphertext rather than readable human conversation content. If a required conversation key is unavailable, supported clients stop the protected operation instead of falling back to plaintext.

Account security

AkkamChat uses established authentication technology to manage account registration, email verification, sign-in, password resets, and authenticated sessions.

Protections may include:

• Secure authentication tokens
• Email verification
• Session validation
• Authorization checks
• Rate limiting
• Device and notification-token management
• Suspicious-request detection
• Blocking and reporting controls

AkkamChat does not intentionally store readable passwords in its application database.

Separate processing and service metadata

Akkam AI is a separate, optional service and is not end-to-end encrypted. Limited operational metadata remains server-visible so AkkamChat can route messages, connect calls, deliver notifications, and protect accounts.

Akkam AI is processed separately from encrypted human conversations. Prompts, AI history supplied for context, AI image uploads, and generated responses must be available to AkkamChat and its AI provider to generate a response, so content intentionally submitted to Akkam AI is outside human-conversation E2EE.

Limited operational metadata remains server-visible so AkkamChat can run the service. This may include account and profile data, contact identifiers used for discovery, contact and group membership, sender and recipient identifiers, timestamps, message and call identifiers, delivery/read/typing/presence state, pin and expiration state, notification routing, call history, group names and descriptions, profile photos, and fixed abuse-report categories.

Notification previews for encrypted human messages are generic and do not include the human message body or attachment name.

Call protection

Call access is managed through authenticated, limited-purpose room tokens and participant validation.

Audio and video call frames use end-to-end encryption in current supported clients. AkkamChat and its calling provider still process the metadata required to invite participants, establish rooms, deliver notifications, enforce membership, and record call history.

Controls may include:

• Group-membership verification
• Call-state validation
• Expiring invitations
• Busy-call protection
• Restricted room access
• Server-generated authorization tokens

Files and media

For human conversations, supported attachments are encrypted on the sender’s device before upload. The service can validate the encrypted envelope, size, authorization, ownership, and conversation membership, but it is not designed to inspect the readable contents of an end-to-end encrypted attachment.

Do not open unexpected files or links from users you do not trust.

Limits and older data

Older human messages and attachments created before the current encryption release may require migration when a conversation is opened. Historical provider backups or logs created before this release cannot be retroactively converted into end-to-end encrypted data by an app update.

AkkamChat’s encryption implementation has not yet received an independent professional cryptography audit.

Device permissions

AkkamChat only requests permissions needed for its features, including:

• Camera for video and photos
• Microphone for calls and recordings
• Notifications for messages and calls
• File access for attachments
• Location when you choose to share it

Permissions can be changed through your device settings. Disabling a permission may prevent the related feature from working.

Protect your account

You should:

• Use a strong, unique password
• Keep your device locked
• Never share verification codes
• Install application and system updates
• Avoid suspicious links and downloads
• Report unexpected account activity
• Sign out of devices you no longer use

AkkamChat staff will never ask for your password through a chat message.