AENC — Privacy Policy & Conditions of Use

Last updated: 13 July 2026  ·  Publisher: AENC Corp ("AENC", "we", "us")

In one sentence: AENC is an offline encryption tool. It has no user accounts, no servers that receive your content, and it collects no personal data. Your private keys live on a removable drive you control, and everything you encrypt or decrypt is processed on your own device.
Contents

Part A — Privacy Policy

  1. Introduction
  2. General principles
  3. No accounts and no server-side profiles
  4. Your identity keys (removable-key architecture)
  5. Messages, files and media
  6. What leaves your device
  7. Data we collect
  8. Permissions
  9. Google Play edition: subscriptions & license verification
  10. Contacts and pairing certificates
  11. Analytics, advertising and tracking
  12. Data retention, deletion and emergency wipe
  13. Security
  14. Third-party services
  15. Changes to this policy
  16. Contact

Part B — Conditions of Use

  1. The client application
  2. Your responsibility for keys and data
  3. Lawful use only
  4. No access to emergency services
  5. Your rights and ownership of content
  6. Repudiation (deniability)
  7. Disclaimers — "as is"
  8. Limitation of liability
  9. Availability and changes to the app
  10. Changes to these conditions
  11. Contact

Part A — Privacy Policy

1. Introduction

AENC is a tool for offline, end-to-end encryption of text, files, photos and voice notes. It is not a messenger: it does not transmit, route, relay, or store your content anywhere. You produce an encrypted package on your device and share it over whatever channel you already use (email, a messaging app, cloud storage, a USB stick). Only the intended recipient, holding the corresponding private key, can open it.

Because of this design, most of the privacy questions that apply to online services simply do not apply to AENC: there is no account, no server that sees your messages, no address book upload, and no metadata about who you talk to.

2. General principles

3. No accounts and no server-side profiles

AENC has no sign-up, no login, no username, no phone number and no email requirement. Any identity you create exists only as an encrypted key file on your removable drive and in your device's memory while unlocked. We keep no record of it. We cannot enumerate users, because there is no user list.

4. Your identity keys (removable-key architecture)

An AENC identity is a set of cryptographic keys (an X25519 encryption key, an Ed25519 signing key, and optionally a post-quantum sntrup761 key). The private parts of these keys are:

We never receive, escrow, back up, or have any way to recover your private keys. If you lose the removable drive or forget the passphrase, the keys — and anything only they could decrypt — are unrecoverable. This is intentional.

5. Messages, files and media

When you encrypt something, AENC creates a self-contained encrypted package using authenticated encryption (X25519 key agreement with AES-256-GCM, and Ed25519 signatures; an optional hybrid post-quantum mode adds sntrup761). The sender's identity is encrypted inside the package ("sealed sender"), so it is not exposed on the outside.

We have no servers involved in any of this and therefore hold none of your content or metadata.

6. What leaves your device

AENC is distributed in two editions:

7. Data we collect

We collect no personal data. AENC contains no analytics SDK, no crash-reporting that sends data to us, no advertising identifiers, and no telemetry. We do not collect your IP address, location, contacts, device identifiers, or usage statistics. Because there is no server receiving anything from the app's core functionality, there is no dataset for us to hold, share, or be compelled to produce.

8. Permissions

9. Google Play edition: subscriptions & license verification

The Google Play edition may offer an optional paid subscription. This feature is off unless you actively subscribe. When you do subscribe:

If you never subscribe, none of the above occurs and nothing is sent. The standard offline edition has no billing and never contacts any server.

10. Contacts and pairing certificates

You add a contact by importing their public "pairing certificate" — a small self-signed blob containing only public keys and a display label — typically by scanning a QR code in person. Contacts and contact books are stored encrypted (on a removable drive you control, or on the phone) and never on any server. AENC never uploads, syncs, or reads your device's system address book.

11. Analytics, advertising and tracking

None. AENC contains no advertising, no third-party trackers, no analytics, and no fingerprinting. We do not use cookies or identifiers to follow you across apps or sessions.

12. Data retention, deletion and emergency wipe

Because we hold nothing, there is nothing on our side to retain or delete. On your device, you remain in control: you can delete your key file and contact files, and AENC provides an emergency wipe feature to securely remove sensitive AENC files from the device. Uninstalling the app removes its app-side data. Content you already shared with a recipient is outside your (and our) control once sent.

13. Security

AENC uses well-established cryptography: X25519 (ECDH) with AES-256-GCM authenticated encryption, Ed25519 signatures, Argon2id passphrase hashing, and an optional post-quantum hybrid using sntrup761. Private keys are held in locked, guarded memory and zeroised after use.

No client-side protection is absolute: a determined attacker with full physical control of an unlocked device can, in principle, attempt to extract data from memory. AENC is designed to make this as costly as possible and to leave nothing at rest, but it is not a substitute for physical device security.

14. Third-party services

The only third party involved is Google Play, and only for the Google Play edition's distribution and optional billing. Your use of Google Play is governed by Google's own terms and privacy policy. The standard edition can be installed without any app store and involves no third parties.

15. Changes to this policy

We may update this policy. Material changes will be reflected here with a new "Last updated" date. Because AENC has no way to contact you (we hold no address for you), we recommend reviewing this page after significant app updates. Continued use of the app after an update constitutes acceptance of the revised policy.

16. Contact

Questions about this policy or AENC's privacy practices: tigranavanesyan23@gmail.com.

Part B — Conditions of Use

1. The client application

The AENC app contains no tracking or analytics code and performs no non-essential network activity. It must not be modified in a way that weakens or removes its end-to-end encryption or that causes it to transmit user content or keys.

2. Your responsibility for keys and data

You are solely responsible for keeping your removable key drive, your passphrase, your device, and any exported files safe. AENC cannot recover your keys or data. Loss of the key drive, loss of the passphrase, deletion of files, or uninstalling the app may result in permanent, unrecoverable loss of access to your identity and to anything encrypted to it. Keep backups of your key drive if continued access matters to you.

3. Lawful use only

You may use AENC only for lawful purposes and in compliance with all applicable laws. You are responsible for the content you encrypt and for how you use the encrypted output. AENC provides a general-purpose cryptographic tool and does not monitor, and cannot access, what you encrypt.

4. No access to emergency services

AENC is not a communications carrier and does not provide access to emergency services. Use the normal emergency contact methods available on your device and network.

5. Your rights and ownership of content

You retain all rights to the content you create and encrypt. We claim no license to it and never receive it. Once you share an encrypted package with a recipient, that recipient can retain and decrypt it; any "delete" feature cannot guarantee removal of content already delivered to another person's device.

6. Repudiation (deniability)

Some AENC modes provide a repudiation property: a recipient can verify a message was sent by someone able to use a given key, but cannot cryptographically prove to a third party who authored it. This is a deliberate privacy feature and is not a defect.

7. Disclaimers — "as is"

AENC is provided "as is" and "as available", without warranties of any kind, whether express or implied, including but not limited to merchantability, fitness for a particular purpose, non-infringement, security, or freedom from error or interruption. You use AENC at your own risk. No cryptographic tool can guarantee protection against every possible adversary, and you are responsible for assessing whether AENC meets your threat model.

8. Limitation of liability

To the maximum extent permitted by law, AENC Corp and its contributors will not be liable for any indirect, incidental, special, consequential, or punitive damages, or for any loss of data, keys, profits, or goodwill, arising out of or relating to your use of or inability to use AENC. Where liability cannot be excluded, it is limited to the greatest extent permitted by applicable law. Some jurisdictions do not allow certain exclusions, so parts of this section may not apply to you.

9. Availability and changes to the app

We may change, suspend, or discontinue the app or any of its features at any time. App updates may be required for continued security; you are responsible for installing updates as they become available.

10. Changes to these conditions

We may revise these conditions. Continued use of AENC after revised conditions are posted here constitutes acceptance of the changes.

11. Contact

Questions about these conditions: tigranavanesyan23@gmail.com.