Scope
The app uses the same account system as iEmoji.com. This policy covers information sent by the app to the server it connects to, including development or staging servers used by test builds. Current Android builds connect to iEmoji.com.
Website pages opened from the app are covered by the Website Privacy Policy, including browser cookies and Google Analytics described there. Google Analytics may receive browser and page-visit information when you open those website pages; it is not integrated into the native app as an analytics SDK.
Information We Collect
Account information. We collect your name and email address when you register with email, or your mobile number when you register with phone verification where enabled. We process your password to authenticate you and store a password hash. We also store your account ID, username, verification status, verification records, and account session records. Phone verification records include SMS consent time, registration source, and the consent disclosure version.
Google sign-in. If you choose Google sign-in, we receive a verified email address, Google’s account identifier, and a name when supplied. We use this information to create or connect your iEmoji account and authenticate you. Google processes sign-in requests under its own privacy policy.
Chat identity and messages. We store your chat name, screenname, avatar emoji, posted message text, generated message images, and related posting records. The backend links your chat identity and app posts to your account. A randomly generated chat name does not make these records anonymous to iEmoji.
Usage and interactions. When you select an emoji in the app, the app sends an emoji click event. We store the selected emoji, account ID, request ID, and time; the associated activity record also includes your IP address and chat identity. We store likes, message votes, thanks, and notification read status to provide community features. Emoji searches are sent to our server to return results and may appear in server request logs.
Feedback and support. We store the feedback text you submit, an email address if you choose to provide one, your IP address, a user-agent string identifying the app or client, and the submission time. Feedback requires sign-in, although the feedback table does not store your account ID. We also receive any information you send in support emails.
Reports, blocks, and moderation. We store reports and their reasons, optional details, relevant message snapshots, reporter account IDs and IP addresses, author identities and IP addresses, personal blocks, moderation decisions, and support replies with read status. These records support safety reviews and are available to authorized administrators. Report replies are delivered privately to the reporting account. Public messages may be held or hidden under our moderation rules.
App devices. When you sign in or restore a saved login, we store an app-generated device identifier with your account. We also store the device manufacturer and model, hardware model, Android version, app version and build, application identifier, screen dimensions and density, language and region settings, and time zone. We record first and latest use, sign-in time and count, IP address, and client user agent. Each account has its own device record, so one account can use multiple phones and multiple accounts can use the same phone. These records help us support app compatibility and diagnose problems.
Technical records. Our servers receive network request information such as IP address, requested URL, time, and client user agent. We use session and request identifiers, error records, and abuse-prevention records to authenticate requests, diagnose problems, and limit repeated attempts. These records may be linked to your account or other information you provide.
Public Messages and Emoji Activity
Messages posted through the app are public community posts, not private conversations. Your message, generated image, chat name, screenname, and avatar emoji can appear in the app and on the website. Other people may copy or share public content.
Emoji clicks also contribute to the public activity stream and emoji counts. The activity stream can display the selected emoji with your chat name, screenname, and avatar emoji. Your account email, mobile number, password, and stored IP address are not included in the app's public message or activity responses.
Do not put private or sensitive information in public messages or your chat identity. Changing your chat identity affects new activity and does not automatically rewrite older posts or activity records.
How We Use Information
We use this information to create and verify accounts, keep you signed in, provide emoji search and personal usage features, publish community content, process interactions, show notifications, respond to feedback, improve the service, and prevent spam, duplicate requests, or abuse.
The native app does not include a third-party advertising or analytics SDK and does not use an advertising identifier or track you across other companies' apps or websites. App usage records are collected by our own backend for the features described above.
The app does not request access to your address book, location, camera, or microphone. If you choose to save a generated message image, the app adds it to your device’s Pictures collection. On Android 9 and earlier, saving requires storage permission; on newer Android versions, no storage permission is requested for this feature. The app does not read or upload your existing photos. Copy controls write selected emoji or message text to the system clipboard; the app does not automatically upload unrelated clipboard contents.
When Information Is Disclosed
We do not sell app personal information, provide it to data brokers, or share it with third parties for their marketing or advertising. Public posts and activity are visible to others as described above.
Liquid Web hosts our server and processes the information stored on it. Amazon Simple Email Service (SES) processes email addresses and account verification or other service emails for delivery. Where SMS verification is enabled, Twilio processes your mobile number and verification message for delivery. Amazon S3 stores generated public message images and Amazon CloudFront delivers them; image requests can include your IP address and request metadata. These providers process information to operate the service on our behalf. SMS consent and mobile information are not sold or shared for marketing or promotional purposes.
We may disclose information when required by law or when necessary to protect the service and its users from abuse. If you choose to share a message using another app or visit an external link, that service handles information under its own policy.
Device Storage, Retention, and Security
The app encrypts its saved sign-in token using a key held in Android Keystore and stores the encrypted token in private app preferences. A separate, randomly generated app device identifier is stored in private app preferences. Signing out preserves that device identifier for later sign-ins. App data is excluded from Android cloud backup and device transfer. Clearing app data or reinstalling the app can create a new device identity. The app also uses device storage for settings, pending activation email, message drafts, and account-specific queued emoji clicks or pending messages so requests can be retried. Signing out ends the current session; it does not delete your backend account, device records, posts, feedback, or usage records. Deleting your account removes its device records; device records for other accounts on the same phone remain.
We currently retain the information we collect indefinitely, including account details, messages, feedback, usage events, verification and session records, and backups, unless it is removed in response to a data request, applicable requirements, or service maintenance. Production website server logs are automatically deleted after one month. Apart from those logs and the account-deletion flow described below, we do not have a scheduled automatic deletion period. Verification codes and session tokens have validity limits; expiry does not delete their stored records. You can delete your account in Account → Delete account, as described below.
The app uses HTTPS for backend requests, and we use authentication and other safeguards to protect account access. No service can guarantee perfect security.
Your Choices and Contact
In iEmoji Companion, open Account → Delete account and confirm in the deletion dialog. This permanently removes your shared iEmoji account and associated account details, chat identity, posts, feedback, and account-linked usage and verification records, and signs you out. Uploaded post image cleanup may take up to 24 hours. We retain only an anonymous deletion reference, request/completion dates, and total post and search-selection counts. You can register again with the same email or phone number as a new account; previous data cannot be restored.
You can leave the feedback email field blank, choose email registration instead of SMS, avoid public posting, and change your chat identity in Account. For SMS verification, reply HELP for help or STOP to opt out; message and data rates may apply.
You can also request account and data deletion by email without accessing the app. See that page for request steps and retained records.
To ask a privacy question or request access, correction, or removal of your messages, feedback, or usage records, email eric@iemoji.com. Please identify the account or content involved. We may need to verify account ownership before acting. Some records may need to be retained for security or legal reasons, and we cannot remove copies of public content held by other people.
Children
iEmoji Companion is not directed to children under 13. If you believe a child under 13 has provided personal information, contact us so we can review and address it.
Policy Updates
We may update this policy when the app or our practices change. The effective date above identifies the latest revision.