Privacy Policy
Effective Date: July 27, 2026
At Ferasa Technologies, we are committed to protecting your privacy. This Privacy Policy describes how the **EmojiCode** mobile application collects, uses, and protects your information.
1. 100% Offline Integrity & Zero Message Upload
EmojiCode is designed as an **offline-first security application**. * **No Messages are Uploaded:** Your raw text, passwords, ciphers, and converted emoji messages are processed entirely locally on your device. We do not operate databases that store your messages. * **Local Keys:** All cryptographic operations (AES-256-CBC and PBKDF2-HMAC-SHA256 stretching) occur inside the sandboxed memory of your mobile device. Keys are never shared or sent to any cloud server.
2. Optional Preferences Sync (Google Sign-In)
You can use the application entirely without creating an account (Guest Mode). If you choose to sign in with Google to synchronize your preferences: * **What we Sync:** We securely store your application configuration (such as theme choice, custom emoji pack mappings, and default pack ID) in our Firestore database. * **No Security Metadata:** Cryptographic keys, passwords, conversion logs, and message histories are **excluded** from this synchronization and remain exclusively on your device.
3. Device Permissions Used
EmojiCode requests the following device permissions only when necessary: * **Camera Permission:** Used exclusively to scan QR codes for importing and exporting custom emoji packs. Images are processed in real-time on-device; no camera data is recorded or sent. * **Storage/Share Integration:** Used to save exported emoji pack configuration files locally or share them with friends via native Android/iOS share sheets.
4. Local Data Storage
The application saves settings, custom pack configurations, and optional local message conversion logs inside local Hive DB tables on your device. This data is protected by the operating system's application sandbox and is completely deleted when the app is uninstalled or its data is cleared via Settings.
5. Third-Party Services
We use **Firebase (Google LLC)** to support optional Google Sign-in and preferences sync. Firebase handles your credentials and sync data in compliance with Google's privacy protocols.
6. Changes to this Privacy Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by publishing the new Privacy Policy on this page.
7. Contact Us
If you have any questions or feedback about this Privacy Policy, please contact us at **support@ferasa.com**.