Privacy policy

What data we process

When you visit the site, the server may process standard technical data: IP address, user agent, requested URL and request time. This is needed for security, diagnostics and abuse protection.

If you create an account, we process the data needed to run the account and stay compatible with clients: login identifiers, profile fields and the related service state.

Cookies and analytics

Jimm.online uses essential Laravel cookies for session security and CSRF protection.

We also use Google Analytics 4 to understand page views and product events: downloads and outbound clicks to clients, blog reading, FAQ usage, registration/login and clicks on Telegram links. Analytics helps us improve the project and see where users need help with setup.

Your choice in the cookie notice is stored in the browser's localStorage and does not create an extra request to the server.

Mobile app and push notifications

If you allow notifications in the Jimm app for Android, the app sends our server your UIN, the device notification token (Firebase Cloud Messaging), a random installation identifier, the Android version, language and app version. The password is used only to check that the token was sent by the owner of the UIN and is not stored on the site.

This data is used only to deliver notifications: reminders, project news and messages. Notifications are delivered through Google Firebase Cloud Messaging, so the notification title and text pass through Google servers.

You can turn notifications off in the app settings under "Push notifications". When you do, the device record is deleted from our server. Tokens that Google reports as invalid are deleted as well.

App analytics, crash reports and logs

The Jimm app uses Amplitude to understand how the app is used and where it works poorly. Amplitude receives: your UIN as the user identifier, the device model, operating system version, app version, language, IP address and the country and city derived from it, the mobile carrier, and usage events: opening and closing the app, signing in, disconnects and reconnects, moving between screens, the fact that a message was sent or received and its length, status changes, and adding or removing contacts. Message texts and the numbers of the people you talk to are not sent. Amplitude stores the data on servers in the USA. You can turn this off in the app settings under "Usage statistics".

The Android app uses Google Firebase Crashlytics. When the app crashes or hits a serious error, it automatically sends Google a report: the error and where it happened in the code, the device model, Android version, app version, your UIN and the last lines of the technical log. Reports are used only to fix bugs.

The app keeps a technical log on the device: server connections, disconnects, errors and push notification registration. The log takes up no more than about 1 MB, and old entries are removed automatically. Passwords, message texts and the numbers of the people you talk to are never written to the log. The log is sent to our server only if you tap "Send logs" in the settings yourself; your UIN, platform, system and app versions are sent with it. Received logs are kept for 30 days and then deleted automatically. Instead of sending it to the server, you can also share the log file with us manually.

Third-party services

Google Analytics may set analytics cookies and receive event metadata under Google's policies. Telegram links open the external Telegram service.

We do not sell personal data. Data is used only to run the service, comply with the law, protect the project, and for analytics and hosting infrastructure.

Messages, contacts and account deletion

Messages, contact lists, statuses and profile fields pass through the ICQ-compatible server icq.jimm.online and are stored there while the account needs them: for example, offline messages wait on the server until the recipient signs in. Chat history in the Jimm app is stored only on your device.

The Jimm mobile app connects to the server only over an encrypted connection (TLS). Classic clients — QIP 2005 and Jimm for Java phones — do not support encryption and connect without it, as they did back then; when you chat with them, messages travel from the server to them in plain text. There is no end-to-end encryption: messages are readable on the server. Do not send passwords or other sensitive data through the messenger.

You can delete your account, UIN and related data at any time. See the Account deletion page for instructions.

Jimm browser extension

The Jimm extension for Chrome and Firefox connects to the messaging server at jimm.online and jimm.fun and, for usage statistics, to Amplitude (see below). It does not contact other sites and does not read the content of open pages or your browsing history.

Your UIN and password are entered in the extension only to sign in and are sent to the server to obtain a sign-in token. The password is not stored by the extension. The browser keeps the sign-in token (valid for a limited time, 24 hours by default), the last UIN you entered and your settings: theme, sound and notifications.

Message history is stored only in your browser, on your device, and the extension does not send it anywhere. You can clear it in the extension settings (“Clear history”) or by removing the extension. The messages themselves pass through the server as described in “Messages, contacts and account deletion”.

Notifications about new messages are shown by the browser itself if you turn them on in the extension settings. The extension uses Amplitude to understand how it is used and where it works poorly. Amplitude receives: your UIN as the user ID, the browser and operating system version, the extension version, language, IP address and the country and city derived from it, and usage events: sign-in, disconnects and reconnects, moving between screens, the fact that a message was sent or received and its length, status changes, adding and removing contacts. Message texts and the numbers of the people you talk to are not sent. Amplitude stores the data on servers in the USA. In Firefox statistics are collected only if you allowed technical and interaction data at install time or later in the add-on's permissions. The extension shows no ads and data is not sold.

Contact

For privacy questions, reach us through the Contact page or the Telegram community.