Your messages are personal. Here is what the service can see.

1. Who operates ICQ2

ICQ2 is operated by I Seek You Too LLC, an Oklahoma limited liability company in the United States. Questions and privacy requests may be sent to support@icq2.net. For this policy, “ICQ2” includes the service currently offered under that name and any successor service name adopted by I Seek You Too LLC. A rename or rebrand does not reset or narrow this policy.

2. Information we process

Account and authentication information

We process the e-mail address used to register or recover an account, the UIN you select, password hashes, e-mail verification records, sessions, and security information needed to authenticate you and protect the service. We do not store your password in readable form.

Profile, contact, and presence information

We process the profile fields you choose to enter, their visibility settings, your contact list, groups, aliases, authorization requests, block list, privacy preferences, and presence status. Profile fields are shared with other users only according to the visibility and contact rules supported by the service. Your private login e-mail is separate from any public e-mail field you deliberately add to a profile.

Messages and invitations

We process message content and delivery metadata such as sender and recipient UINs, message identifiers, timestamps, and delivery state. Messages are not end-to-end encrypted: the service can read and store their content for delivery, including offline delivery and retry handling. Friend invitations also process the invited e-mail address and delivery or registration state.

Device, network, and operational information

We may process client version, session timing, IP address, connection and error information, and privacy-minimized operational counters to keep the service available, enforce rate limits, prevent abuse, and diagnose failures. Application logs are designed not to record message bodies.

3. Information stored on your Windows computer

The Windows client stores account-scoped preferences and a local message-history database on your device. Message bodies in the current local-history format are protected with Windows Data Protection API (DPAPI) for the current Windows user. Routing and history metadata may remain readable in that local database. Session credentials are stored with Windows Credential Manager.

DPAPI protection is not an export or recovery system. Copying the history database to another computer or Windows account will normally not make it readable there. Losing the Windows profile can make the protected message bodies unavailable. Uninstalling ICQ2 does not necessarily remove local user data, and the alpha does not yet provide a history export or recovery interface.

4. How we use information

• create, authenticate, secure, and recover accounts;
• deliver messages, presence, contact requests, and invitations;
• apply profile-visibility, blocking, and privacy choices;
• operate, troubleshoot, measure, and protect the service;
• respond to support, safety, legal, and rights requests; and
• comply with applicable law and enforce service rules.

We do not use message content to target advertisements, and we do not sell personal information to data brokers or advertisers.

5. When information is shared

Information may be shared only as needed with:

• the people you message or the users allowed to view a profile field;
• infrastructure, e-mail delivery, software distribution, security, and support providers acting for us;
• government authorities only under valid legal process or a narrowly reviewed emergency involving danger of death or serious physical injury;
• other parties only for a targeted disclosure permitted by law and reasonably necessary to protect a person from imminent death or serious physical injury, or to establish, exercise, or defend a legal claim; and
• a successor if the service or company is reorganized, acquired, or transferred, subject to applicable law.

We do not voluntarily disclose nonpublic user information to foreign governments for ordinary investigations. A genuine emergency involving imminent danger of death or serious physical injury is the only proposed narrow voluntary exception and remains subject to legal and human-rights review. We otherwise require targeted legal process, review demands for jurisdiction, scope, sanctions, and human-rights risk, seek to narrow or challenge improper demands where lawfully available, notify the affected user whenever permitted, and disclose only the minimum required. The proposed details are in our Government Requests Draft Declaration, which remains a draft until its operational and legal-review conditions are complete.

The preceding safety and legal-claims category is not a shortcut for a government demand. A request routed through a contractor, infrastructure provider, private party, international organization, or another country remains subject to the Government Requests Draft Declaration when a government is the origin or ultimate beneficiary.

External websites linked from ICQ2.net have their own privacy practices. The ICQ2.net site does not add advertising trackers or analytics cookies, although hosting and network providers may process ordinary request and security logs.

6. Retention and deletion

Account, profile, contact, message, invitation, and security records may be retained while they are needed to operate and protect the service, resolve delivery, preserve integrity, answer disputes, or meet legal obligations. The current alpha does not promise that server-side message records are automatically deleted immediately after delivery.

Android users can permanently delete an account from Preferences → Delete Account. An accepted in-app request removes the account's authentication records, profile, contacts, preferences, invitations, and server-stored messages and revokes every active session. People who cannot sign in can use the external account-deletion path. Messages or profile information already received and stored on another person's device are outside the service's control and are not erased from that device.

A valid preservation demand may temporarily require us to retain specified records that already exist while an authority seeks proper legal process. Preservation does not itself authorize disclosure and does not authorize new prospective surveillance.

You may request access, correction, or deletion by contacting support@icq2.net. We may need to verify that you control the account. If applicable law requires a narrow legal hold, we will explain the material limit that applies to a request.

7. Security

ICQ2 uses encrypted network transport, password hashing, opaque sessions, access controls, bounded queues, and platform protections for local credentials and message bodies. No system is perfectly secure.ICQ2 is not end-to-end encrypted, and users should not send secrets or highly sensitive information through the current alpha.

8. International processing

ICQ2 and its providers may process information in the United States, the European Union, and other locations where infrastructure or service providers operate. Privacy protections and legal rights can differ by location. We apply this policy and the same government-request baseline regardless of the user's country or official ICQ2 client.

9. Children

ICQ2 is not directed to children under 13, and we do not knowingly collect personal information from a child under 13. A parent or guardian who believes a child provided information should contact us so the issue can be reviewed.

10. Changes and contact

We may update this policy as the alpha and its features change. A new effective date will be shown here, and material changes may also be announced through the website or application.

Effective date: August 27, 2026

Contact: support@icq2.net