How site analytics work
CONNEX measures signups, signed-in visits, chat activity, feature use and technical problems to improve the site. Admins can see totals, trends, public-chat keywords, account signup dates, last-seen times, and usernames associated with visits and recorded actions. They can filter and download retained public-chat messages by room, user and date range.
Public chat messages are analysed locally for recurring words and broad discussion topics. These summaries can help plan features, content and contextual advertising or sponsorships. Discussion topics are not treated as proof of anyone’s personal traits or buying intentions.
Country is optional in your account settings. It is not shown on your public profile and is used in aggregate admin charts. Leave it blank, or clear it later, to stop contributing location data. We do not infer locations from IP addresses.
Activity tracking uses your signed-in account to count repeat visits. This analytics feature stores daily activity for up to 365 days and the most recent 50,000 timestamped action records within 90 days. Action records include account identifiers, action types, times, and applicable room/message identifiers, not message text. Technical reports contain a fixed error category, not your message text, passwords, URLs or browser error details. Deleting chat messages removes their content from chat and future log exports. Admin moderation reports retain a copy by default; admins can choose to erase that saved message text as well. Report reasons and review metadata remain. Previously downloaded logs and backups are separate copies.
Room polls keep one changeable vote per signed-in account. Members see aggregate results and their own selection; poll votes are stored on the server. Suggestions are associated with your account and are visible only to admins.
The word filter changes how chat and usernames appear. Administrators choose the site default and word list; each member can override that default in their profile. Original messages and account names stay stored, so admins can review and export original content.
Admins can review sign-in outcomes, blocked requests, live connection checks and moderation actions, including IP addresses, account identifiers and timestamps. Up to 10,000 security event rows are retained for 30 days; repeated events can be grouped. Each account keeps its creation date and recorded signup IP address until the account is deleted, plus up to five recently used IP addresses for 30 days. Signup addresses are visible only to administrators. Older signup addresses may be unavailable. IP bans and their admin-entered reasons remain until removed. IP bans affect everyone sharing the address. Security event records do not include passwords, session tokens or message bodies. The website does not use a VPN detection service.
No external analytics or advertising service receives this data from this feature. Administrators control the site’s stored data. Manage optional location settings.
Visitor counting
A first-party cookie named connex_visitor identifies a browser for up to 365 days, including while signed out. Visitor analytics store a random browser identifier, visit counts, timestamps and associated signed-in account identifiers for up to 365 days. No IP address or browser fingerprint is used for visitor counting. Security IP records are separate.
A visit starts after 30 minutes without observed page activity; a second visit can occur on the same day. Reloading within a visit does not add another visit. Unique visitors estimate browsers, not individual people. Clearing cookies or using another browser can increase the count. Guest traffic can include bots. Admins can view aggregate guest counts and signed-in account details.