Sarai Hannah Ajai Incident Report Complaint for Apple iPhone 17, Apple Mac Mini M1, Apple Notes application, X.com account interface, M*d*o*t*n*n* C*m*u*i*a*i*n* Inc. (“M*d*o”) home internet service, V*r*z*n mobile service

 Incident Report / Redacted

Subject: Suspected Unauthorized Interference With Apple Device Connectivity, Account Session Presentation, and Storage Behavior During M*d*o Service Activity

Reporting Party: Sarai Hannah Ajai
Date of Incidents: April 1, 2026
Location: Apartment Unit **5, 
Related Devices / Services: Apple iPhone 17, Apple Mac Mini M1, Apple Notes application, X.com account interface, M*d*o*t*n*n* C*m*u*i*a*i*n* Inc. (“M*d*o”) home internet service, V*r*z*n mobile service

I. Executive Summary

On April 1, 2026, I observed multiple unusual and concerning technology-related events involving my Apple iPhone 17, Apple Mac Mini M1, M*d*o home internet service, and V*r*z*n mobile service. These incidents occurred during the same general period in which a M*d*o technician was present at or near the building cable/internet room associated with my apartment building unit, **5. The events included: an unexpected X.com login/account-interface irregularity on my Apple iPhone 17, an abrupt and unexplained Apple iPhone 17 storage spike associated primarily with the Apple Notes application, unusual storage fluctuations on my Apple Mac Mini M1, and a loss of expected connectivity involving both my home internet and what appeared to be my separate V*r*z*n cellular connectivity while M*d*o service work was underway.

I am documenting these events because the behavior I observed was unusual, disruptive, and alarming, and because I believe the incidents may be relevant to broader concerns regarding an unauthorized access, session interference, account irregularities, network manipulation, or device/account synchronization issues affecting my Apple iPhone 17 and MAC Mini M1 ecosystem and communications services. This report is intended as a preservation-oriented record of my firsthand observations and the supporting screenshots I identified as exhibits.

II. Background and Context

On April 1, 2026, a M*d*o technician was present in the building cable/internet room that is visible from outside my bedroom window on the second floor. I understood that the technician was there to replace or update an older wire associated with the building internet infrastructure. During this period, I personally observed changes in Apple iPhone 17 device behavior and connectivity that I found irregular and concerning.

I cannot independently determine the technical cause of the events described in this report. I therefore present this report as a factual summary of what I personally observed, the approximate times involved, the sequence in which the events occurred, and the device screenshots and images I preserved as supporting evidence.

III. Incident Timeline

A. Apple iPhone 17 Storage Irregularity Involving Notes Application

Date: April 1, 2026
Approximate Time: 6:15 AM

At approximately 6:15 AM, I navigated on my Apple iPhone 17 to Settings → General → iPhone Storage and observed that the device storage usage had abruptly risen to approximately 185.83 GB of 256 GB, leaving approximately 70.17 GBfree. Upon further review, I observed that the Apple iPhone 17’s Notes application appeared to be consuming approximately 116 GB of storage, despite my understanding that my Notes content should have been far smaller, approximately 30.8 MB.

I attempted to inspect the Apple iPhone’s Notes application and related deleted or recently deleted content to determine whether legitimate documents, media, or other stored items could explain the unusually large storage consumption. I did not locate content that reasonably accounted for the amount of storage then being reported. Because I could not identify a valid explanation for the abnormal storage use, I temporarily deleted the Apple iPhone’s Notes application from my Apple iPhone 17 in an effort to restore the device to a more normal storage condition. I preserved screenshots of these storage conditions as evidence.

B. Apple Mac Mini M1 Storage Fluctuations

Date: April 1, 2026
Approximate Times Reflected in Screenshots: 7:15 AM, 7:18 AM, 7:33 AM, and 7:55 AM

Later that same morning, I also observed unusual storage fluctuations on my Apple Mac Mini M1. The screenshots I preserved reflect changing storage totals and category distributions in the macOS storage settings panel, including changes in Applications, Mail, and System Data. The screenshots were captured at approximately 7:15 AM, 7:18 AM, 7:33 AM, and 7:55 AM.

These variations appeared inconsistent and concerning to me, particularly because they occurred on the same date and within a relatively short time period after I had already observed the abnormal storage behavior on my Apple iPhone 17. I am preserving these screenshots because they may be relevant to determining whether there was any unauthorized access, synchronization anomaly, account-level irregularity, or other technical issue affecting my Apple iCloud ecosystem.

C. X.com Account Interface Irregularity While M*d*o Technician Was Away Obtaining a Key

Date: April 1, 2026
Approximate Time: 11:32 AM

At approximately 11:32 AM, while the M*d*o technician had temporarily left the area to obtain a key from the property manager for the cable/internet room, I experienced a separate irregular event involving the X.com application/account interface on my Apple iPhone 17. When I opened the X.com application, I observed a “Log in to X” screen that displayed account options in a manner I regarded as inconsistent with my expected normal setup. Specifically, I observed that my @VaultInbox account did not appear in the way I expected on the login interface.

Because the screen presentation appeared abnormal to me, I became concerned that my Apple iPhone 17 account environment or iCloud-linked device session may have been altered, substituted, or otherwise affected without my authorization. In response, I powered off my Apple iPhone 17 and then powered it back on. After rebooting the device and logging back in with my assigned credentials, including my current device passcode and V*r*z*n PIN, I observed that the account display appeared to return to its expected normal state, and my @VaultInbox X.com account again appeared properly restored. I preserved screenshots reflecting both the irregular state and the restored state after reboot.

I document these facts exactly as observed:

1. I observed an unexpected X.com login/account display condition.
2. I restarted the device.
3. After reboot, the account presentation appeared to return to normal.

I do not claim technical certainty as to the cause of this event. However, from my perspective, the abrupt account-interface change followed by restoration after reboot was highly irregular and contributed to my concern that my device or account session may have been subject to unauthorized interference.

D. M*d*o Technician Visit and Loss of Expected Connectivity

Date: April 1, 2026
Approximate Time: 12:15 PM

At approximately 12:15 PM, while the M*d*o technician was actively engaged in work involving the building cable/internet room, I was seated at my bedroom office desk monitoring the behavior of my Apple iPhone 17. During that period, I observed through my Apple iPhone 17 settings that my Wi-Fi connection had dropped, which was consistent with the temporary interruption to my M*d*o home internet service.

However, I also observed that my Apple iPhone 17 did not appear to maintain expected internet access through my V*r*z*n cellular service, and I further observed what appeared to be a loss of expected V*r*z*n 5G connectivity during the same period. Because my V*r*z*n service is separate from my M*d*o home internet service, this simultaneous interruption caused me substantial concern. Based on what I observed at that time, I became distressed and concerned that my Apple iPhone 17 connectivity may have been affected in a manner I did not understand and did not authorize. How is it possible that M*d*o can control Apple iPhone 17 telecommunication?

I cannot independently determine the technical cause of that behavior. Nevertheless, I am documenting that, from my perspective, when M*d*o’s work interrupted my apartment home internet line, my Apple iPhone 17 also appeared to lose separate connectivity that I would have expected to remain available through V*r*z*n cellular service. This raised serious concern for me regarding possible interference with my V*r*z*n Account’s Apple iPhone 17 telecommunications services, device routing, or account environment.

IV. Evidentiary Observations

Based on the information and screenshots I preserved, the evidence set presently includes screenshots and images reflecting:

• the unexpected X.com login/account-interface condition on my Apple iPhone 17,
• the apparent restoration of the expected account presentation after reboot,
• the abnormal iPhone 17 storage condition, including unusually high storage attributed to the Notes application, and
• the Apple Mac Mini M1 storage screenshots showing changing storage distributions at multiple times that same morning.
• 
  

These materials do not, by themselves, prove a specific technical cause. However, they do preserve the visual conditions I personally observed at or near the time of the incidents and therefore may be relevant to later review by service providers, investigators, technical personnel, legal counsel, or law enforcement.

---

V. Legal Significance and Potentially Implicated Statutes

The following statutes and legal frameworks are potentially relevant to the conduct and events described above, depending on what a later technical or forensic review may show. This section is not a final legal conclusion that a specific crime or civil violation occurred. Rather, it is a preservation-oriented analysis identifying statutes commonly implicated where a person reports suspected unauthorized device access, electronic account interference, communications disruption, unlawful interception, or improper handling of telecommunications-related customer information.

1. Computer Fraud and Abuse Act — 18 U.S.C. § 1030

Federal law prohibits certain forms of intentional access to a protected computer without authorization, or in excess of authorization, including conduct that obtains information, causes damage, or results in loss. The statute also addresses transmission-based conduct that intentionally causes damage to a protected computer. (U.S. Code)

If a later review were to show that any person intentionally accessed the reporting party’s Apple iPhone 17, Apple Mac Mini M1, related Apple account environment, or associated session/authentication state without authorization, then 18 U.S.C. § 1030 could be relevant. This statute is commonly implicated where the reported concern involves suspected unauthorized entry into devices, manipulation of account sessions, interference with normal device functioning, or alteration of stored or displayed system information. (U.S. Code)

2. Stored Communications Act — 18 U.S.C. § 2701

Federal law also prohibits certain forms of intentional unauthorized access to a facility through which an electronic communication service is provided, where that access results in obtaining, altering, or preventing authorized access to a wire or electronic communication while it is in electronic storage. (U.S. Code)

If the events described in this report involved unauthorized intrusion into stored account-session data, cloud-synchronized content, account-linked communications, or other electronically stored records associated with the reporting party’s Apple ecosystem or related service accounts, then 18 U.S.C. § 2701 may be relevant. This is especially so if any later review suggests unauthorized access to stored communications, account-linked session data, or synchronized device information rather than only local on-device anomalies. (U.S. Code)

3. Federal Wiretap Act / Interception of Electronic Communications — 18 U.S.C. § 2511

Federal law prohibits intentional interception, attempted interception, or procurement of another person to intercept wire, oral, or electronic communications, except as otherwise specifically authorized by law. (U.S. Code)

If a later forensic or provider-side review were to show that the reporting party’s electronic communications, data transmissions, or account-session traffic were intercepted, redirected, monitored, or captured in transit without authorization, then 18 U.S.C. § 2511 may be implicated. This statute is potentially relevant where a user reports unexplained communications interference, suspicious session changes, abnormal account-interface conditions, or unexpected disruptions affecting device connectivity and electronic communications. (U.S. Code)

4. Fraud and Related Activity in Connection With Access Devices / Credentials — 18 U.S.C. § 1029

Federal law criminalizes certain fraudulent conduct involving unauthorized access devices and related credential misuse. Although this statute is more commonly discussed in connection with payment devices, account numbers, and authentication-related instruments, it may become relevant where a later investigation shows misuse of electronic credentials or account access mechanisms for an unlawful purpose.

If any later review were to show misuse of device-linked credentials, authentication factors, PIN-linked recovery elements, or other access mechanisms connected to communications or online-account access, then 18 U.S.C. § 1029 may warrant review as part of a broader credential-compromise analysis. This is not presently asserted as a confirmed violation, but it is a statute commonly reviewed where electronic access irregularities appear connected to authentication misuse.

5. Fraud and Related Activity Involving Identification Information — 18 U.S.C. § 1028

Federal law also criminalizes certain unauthorized uses of identification documents, authentication features, and identifying information. If a later investigation were to show that the reporting party’s identifying information, account identifiers, account-linked profile data, or authentication-related information were used, altered, or leveraged without authorization in connection with the events described here, then 18 U.S.C. § 1028 may become relevant.

This statute is particularly worth preserving in the analysis because the reported incidents include concerns about account presentation, device/session integrity, and possible unauthorized interference with personal digital accounts or communications settings.

6. Aggravated Identity Theft — 18 U.S.C. § 1028A

Where a person knowingly transfers, possesses, or uses, without lawful authority, another person’s means of identification during and in relation to certain predicate offenses, federal aggravated identity theft provisions may apply.

At present, the evidence described in this report supports preservation of suspicion and concern, not a final conclusion that identity theft has occurred. However, if a later review were to show that another person used the reporting party’s identifying information, device-linked identity markers, account credentials, or related authentication data in connection with a predicate federal offense, then 18 U.S.C. § 1028A could become relevant.

7. Telecommunications Privacy / Customer Proprietary Network Information — 47 U.S.C. § 222

Federal telecommunications law requires telecommunications carriers to protect customer proprietary network information and regulates when such information may be used or disclosed. This statutory framework is relevant where a consumer reports concerns involving unexplained service irregularities, account-environment anomalies, or possible improper exposure of carrier-associated account information. (U.S. Code)

To the extent the events described here involved unexplained V*r*z*n service behavior, unusual cellular connectivity conditions, or possible irregularities affecting telecommunications-account handling, routing, or access to customer-associated service information, 47 U.S.C. § 222 may be relevant as part of any provider-side preservation and review effort. This does not itself establish that V*r*z*n or any other carrier committed a violation; rather, it identifies a statutory privacy framework potentially relevant to investigation of telecommunications-account or service anomalies. (U.S. Code)

8. Possible State-Law and Common-Law Issues

In addition to federal statutes, the facts described may also implicate state-law issues depending on what additional evidence shows. These may include unauthorized computer access, invasion of privacy, unlawful interference with property or services, negligence, or related tort-based and statutory claims. Because this report is focused on preservation of observed facts, I am not making a final state-law classification here. However, the incident should be preserved in a manner that would allow later review by counsel under applicable North Dakota law.

Closing Paragraph for the Section

Based on the currently available facts, the most defensible characterization is that the April 1, 2026 events warrant preservation and technical review as a suspected unauthorized interference / device-account-connectivity anomaly matter, not as a proven technical intrusion event. The evidence presently supports documenting unusual Apple device behavior, account-interface irregularities, abnormal storage fluctuations, and unexplained communications disruption occurring during the same general timeframe as service-related work in the building internet infrastructure. Further provider logs, device forensics, account-security records, and network records would be necessary before reaching stronger technical or legal conclusions.

VI. Analytical Assessment

Based on the facts presently available, the strongest and most accurate characterization is that on April 1, 2026, I experienced a series of unusual and concerning device, account-session, storage, and connectivity events affecting my Apple iPhone 17 and Apple Mac Mini M1 devices, including an unexpected X.com account-interface presentation, an unexplained Apple iPhone 17 storage spike heavily associated with the Notes application, storage fluctuations on my Mac Mini, and the apparent loss of both M*d*o Wi-Fi and expected V*r*z*n cellular connectivity during M*d*o service work.

At present, I cannot state with technical certainty whether these events were caused by unauthorized access, a device synchronization malfunction, a software fault, network-routing behavior, an account-session anomaly, or some other service-related issue. What I can state with certainty is that the events were abnormal, occurred on the same date within a relatively concentrated timeframe, and caused me substantial concern regarding the security and integrity of my devices, accounts, and communications environment.

VII. Effect on Me

These incidents caused me substantial fear, distress, and disruption. The repeated devices irregularities, connectivity anomalies, account-presentation changes, and abnormal storage behavior caused me to fear that my Apple devices, accounts, or communications environment may have been accessed or interfered with without my knowledge or consent. I am particularly concerned because these events affected my core personal Apple devices ecosystem used for communications, records, applications, and account access.

VIII. Formal Statement

I, Sarai Hannah Ajai, state that on April 1, 2026, at my apartment Unit 205, I personally observed multiple irregular events affecting my Apple iPhone 17, Apple Mac Mini M1, M*d*o home internet service, and V*r*z*n mobile service. These events included abnormal Apple iPhone 17 storage usage associated with the Notes application, unusual storage fluctuations on my Apple Mac Mini M1, an unexpected X.com login/account-interface condition on my Apple iPhone 17 that appeared to return to normal after a reboot, and a later loss of expected connectivity involving both my M*d*o home internet and what appeared to be my V*r*z*n cellular service during M*d*o-related service activity.

I do not claim technical certainty as to the cause of these events. I am preserving this incident report as a contemporaneous record of my firsthand observations and the supporting screenshots and images I identified as exhibits, for possible use in complaints to service providers, investigators, regulatory agencies, legal counsel, or law enforcement, should further review become necessary.

IX. Uploaded Exhibits / Supporting Evidence

I identify the uploaded exhibits as follows:

Exhibit A
File: iPhone 17 Evidence X.com Account Dated 04-01-26.jpg
Description: Screenshot/image reflecting the “Log in to X” account display condition in which the expected @VaultInboxpresentation appeared irregular or missing.

Exhibit B
File: iPhone 17 Evidence X.com Account Restore after Reboot Dated 04-01-26.jpg
Description: Screenshot/image reflecting the apparent restoration of the expected X.com account environment after I powered the iPhone off and back on.

Exhibit C
File: iPhone 17 restore to the normal state Dated 04-01-26.jpg
Description: Screenshot/image reflecting the iPhone 17 storage condition showing unusually high storage usage, including the storage attributed to the Apple Notes application.
Your source draft left Exhibit C blank, so I preserved a placeholder here for the exact filename.

Exhibit D
File: Screenshot 2026-04-01 at 7.15.28 AM.png
Description: Apple Mac Mini M1 storage screenshot showing storage category usage shortly after the reported iPhone storage concerns.

Exhibit E
File: Screenshot 2026-04-01 at 7.18.20 AM.png
Description: Apple Mac Mini M1 storage screenshot showing a substantially different storage distribution, including a change in Applications and System Data totals.

Exhibit F
File: Screenshot 2026-04-01 at 7.33.49 AM.png
Description: Apple Mac Mini M1 storage screenshot showing additional storage totals and category conditions later that morning.

Exhibit G
File: Screenshot 2026-04-01 at 7.55.13 AM.png
Description: Apple Mac Mini M1 storage screenshot showing later storage values and category totals for comparison and preservation.

X. Preservation Statement

I am preserving this report and the listed exhibits as a contemporaneous record of the events I personally observed on April 1, 2026. This report is based on my firsthand observations of device behavior, connectivity conditions, account-interface changes, and storage irregularities, together with the screenshots and images identified above.

Respectfully,

 

Sarai Hannah Ajai