A Server Maintenance Script Sent Every MetaCity User Their Complete 4-Year Activity Log as a Private Message — Logs Include Timestamps for Every Profile They Visited and How Long They Stayed

At 5:50 AM EST, a server maintenance routine running on MetaCity's data audit infrastructure executed a function intended for internal diagnostics — a full user activity log export — and routed its output to the platform's private messaging system instead of the internal log archive. Every one of MetaCity's 41 million active users received a private message from the handle '@system.export.auto' containing a downloadable archive of their complete behavioral record going back to their account creation date or to January 2022, whichever was more recent. The log file includes every search query run, every profile visited, the duration of each visit, every item browsed without purchasing, and a column labeled 'Repeated Visits (7+ Days)' tracking profiles the user had returned to more than once in a week. MetaCity Support confirmed the message is authentic and that the logs are accurate. The platform has not indicated it will delete the messages from inboxes.

MetaCity's data audit infrastructure runs nightly maintenance cycles designed to verify data integrity across user account records. The cycle includes a logging function that exports behavioral records to an internal diagnostics archive, where they are reviewed by data quality systems and then stored for internal use. The function has run successfully without incident for three years. At 5:50 AM on April 12th, a configuration update to the maintenance job's output routing — part of a larger infrastructure refactor that has been in progress for several weeks — pointed the export function's output destination to the wrong endpoint. Instead of the internal diagnostics archive, the records were routed to MetaCity's private messaging system, which interpreted the input as a standard bulk message job and executed delivery to all 41 million active accounts simultaneously. Each user received a message from '@system.export.auto' with a subject line reading: 'Your MetaCity Activity Archive — April 12, 2026.'

The archive files vary in size depending on account age and activity level. The most active and longest-tenured accounts received files running to several hundred pages of logs. The structure is consistent across all files: a header section with account metadata, followed by a chronological activity record organized by category. The search query log contains every term entered into MetaCity's search function with timestamps. The profile visit log contains every account profile accessed, the time of the visit, and its duration in seconds. The browse log contains every item viewed in MetaCity's marketplace or creator catalog without being added to cart or purchased — a record some users described, in early community reactions, as 'a complete list of everything I wanted and did not buy, which is not something I needed to see.' The final column, labeled 'Repeated Visits (7+ Days),' is the section that has generated the most community response.

You Have Mail. It Is About You.

The 'Repeated Visits (7+ Days)' column tracks, on a per-account basis, every profile that the user visited on seven or more distinct days within any rolling seven-day window. The column contains the profile name, the number of qualifying visit windows, the average visit duration, and a sub-column labeled 'Last Visit.' Community responses to this column have been extensive, varied, and largely characterized by an absence of surprise at the accuracy of the data combined with a significant discomfort at seeing it formatted. Users have described finding in the column: ex-partners, estranged friends, professional rivals, celebrities they follow without following, and, in several widely circulated posts, their own profiles — visited repeatedly via incognito browsing sessions the platform apparently logs regardless. MetaCity Support confirmed in response to a direct inquiry from MetaCelebrityNews that incognito mode on MetaCity reduces visible engagement signals to other users but does not affect internal behavioral logging. This clarification was posted at 9:00 AM. It has received 1.4 million engagements.

MetaCity issued a statement at 11:00 AM confirming the incident was caused by a routing configuration error and describing it as 'unintended.' The statement confirmed the data in the logs is accurate. The statement did not commit to deleting the messages from user inboxes, noting that MetaCity's data deletion processes 'require a formal data rights request from each individual user' and that the platform 'cannot perform bulk inbox deletions on user messages.' The MetaCity Data Rights portal, which handles such requests, crashed at approximately 8:30 AM under request volume and has been intermittently accessible since. The platform's privacy policy, which multiple community accounts have now excerpted and begun reading publicly for the first time, contains a disclosure noting that MetaCity retains 'behavioral interaction data for platform optimization and safety purposes.' The disclosure does not specify how long. The logs sent this morning go back to January 2022. That is four years and three months. Several users have posted that reading their own four-year behavioral record is 'the most honest thing the platform has ever said to them.'