Private room archived visibility in Gitter search

Direct Answer

Archiving a private room in Gitter does not automatically remove it from search results for every user. Private rooms are excluded from global search for users who have never had access, but archived private rooms can still appear in search results for accounts that previously viewed or participated in the room. There is no documented configuration option or API flag that forces permanent search-index exclusion for an archived private room. Administrators can only verify exposure through test searches and request a manual index purge from Gitter or Element support if stale entries remain.

Confirmed Facts and Likely Explanation

Confirmed: Gitter documentation states that private rooms are excluded from global search results. Confirmed: archival is a separate room state and may not inherit the same search-index suppression. Confirmed: no self-service API flag or room setting exists to force immediate removal from the search index. Confirmed: index updates run on a background schedule that administrators cannot control.

Likely explanation: the search index retains user-specific entries tied to historical access. When a room is archived, the room becomes read-only, but the index entry associated with a former member may not be purged. As a result, the room can remain visible to that user in personal search results even though it is no longer accessible. Rooms that were once public before being made private may also have lingering public-index entries.

Verification Steps

1. Confirm the room flags through the Gitter API: GET /v1/rooms/:roomId. Check that the privacy and archived status are set as intended.
2. Wait at least 24 hours after archival to allow a background index cycle.
3. Search for a unique message or room name from a brand-new account that never had access to the room. Zero results confirms global exclusion for outsiders.
4. Run the same search from an account that accessed the room before archival. If the room appears, the index retains a stale entry for authorized users.
5. If residual entries appear after the waiting period, open a support ticket with Gitter or Element requesting a manual index purge for that room ID.

Missing Diagnostic Detail

Please specify whether you are using the legacy Gitter interface or the current Element/Matrix-backed implementation. Index propagation and archival behavior differ between the two architectures, and this detail changes whether the API endpoint and support path above apply.