This content is for informational and educational purposes only and is not legal, financial, or tax advice. No attorney-client relationship is created by reading or using this article. Federal, state, and local rules may differ and may change without notice. A qualified professional can review specific circumstances. The author and publisher assume no liability for actions taken based on this content.
Key Facts
- National overview: The legacy ABANow page returned 404, so the original app list and framing could not be verified directly.
- National overview: Smartphone apps can access contact lists, and that access can raise confidentiality concerns when contacts include client information.
- Federal level: The FTC treats app security as context-specific and says there is no single checklist that fits every app.
- State level: New York State Bar Association Ethics Opinion 1240 says a lawyer may not consent to share smartphone contacts with an app if confidential client information is included unless no human being will view it and it will not be sold or transferred without consent.
- National overview: Apple’s App Privacy Report lets users see how often apps access data and network activity, and Apple says the report data is encrypted and stored only on the device.
- National overview: Apple’s support text limits App Privacy Report to iOS 15.2 or later and iPadOS 15.2 or later.
- National overview: This rebuilt article is an archival legal information explainer, not a verified reconstruction of specific app reviews.
Last reviewed: May 2026. Legal rules, forms, deadlines, and procedures can change by jurisdiction, agency, and court system.
- Why contact permissions matter in this archival topic
- Federal guidance treats app security as a data problem
- New York illustrates a state specific ethics rule
- Apple’s App Privacy Report shows one way device privacy is presented
- What the recovery can and cannot verify
- The topic in one sentence for readers of the archive
- Related legal information
- Sources
The recovered ABANow page could not be retrieved directly, so this article does not attempt to recreate specific app names, rankings, prices, or availability. It treats the topic as archival legal information about mobile apps, contact permissions, and privacy concerns in legal practice.
Why contact permissions matter in this archival topic
Smartphone apps can ask for access to contact lists, and that access can expose client names, phone numbers, email addresses, or other identifying details. The ABA Litigation News piece used that issue as context for confidentiality concerns, tying the discussion to duties under Rule 1.6 and the need for reasonable efforts to prevent unauthorized disclosure.
That framing matters because the legal issue is not limited to one product or one year. The basic question is whether a contact list can contain information that a lawyer treats as confidential, and whether an app’s access settings create a disclosure risk. The reviewed sources point to that risk without identifying any current app as automatically acceptable or unacceptable.
Federal guidance treats app security as a data problem
The FTC’s current guidance describes mobile app security as context-specific. It says apps and devices often rely on consumer data such as contact information, photos, and location, and it says there is no checklist that fits every app.
That federal framing is important because it is not a lawyer-ethics rule. It is consumer-protection guidance about reasonable data security practices. The FTC’s approach focuses on the nature of the data, the app’s design, and the reality that different products present different risks.
| Topic | Federal context | State context |
|---|---|---|
| Contact data | The FTC treats contact information as consumer data that can face security risks. | New York’s ethics opinion treats client contact data as potentially confidential information under Rule 1.6. |
| App security | The FTC says reasonable security depends on the app and does not follow one universal checklist. | State ethics rules vary, so one jurisdiction’s opinion does not become a national rule. |
| Device privacy | Apple offers App Privacy Report as a device-level transparency feature on supported systems. | State ethics rules still control lawyer conduct questions inside the jurisdiction that issued them. |
New York illustrates a state specific ethics rule
New York State Bar Association Ethics Opinion 1240 gives a narrower answer than a national rule would. The opinion says that if contacts on a lawyer’s smartphone include a client whose identity or other information is confidential under Rule 1.6, the lawyer may not consent to share those contacts with a smartphone app unless no human being will view the confidential information and the information will not be sold or transferred to additional third parties without consent.
That state-specific analysis is useful because it shows how professional-responsibility rules can turn a routine permission prompt into a confidentiality question. It also shows why state ethics materials need careful jurisdiction labeling. The New York opinion is a New York interpretation, not a general rule for every state.
Apple’s App Privacy Report shows one way device privacy is presented
Apple’s App Privacy Report gives users a way to see how often apps access data and network activity. Apple says the report data is encrypted and stored only on the device.
Apple’s support text also limits the feature to iOS 15.2 or later and iPadOS 15.2 or later. That limitation matters in an archival article because it keeps the feature in its current device-specific context instead of treating it as a universal Apple setting across all products and operating-system versions.
What the recovery can and cannot verify
The missing legacy page leaves one important gap: the exact 2013 app list is not verified. That means no current statement here identifies which apps the original post discussed, which ones were ranked first, or whether any specific app remained available later.
The rebuilt article therefore focuses on the legal information that can be supported today. It explains why lawyers, app developers, and privacy-focused readers pay attention to contact permissions, client data, and device transparency tools, while keeping the federal and state boundaries separate.
The Sources reviewed for this explainer are current official pages and one unavailable legacy page used for archival recovery context. That mix is why the article can explain the legal issue clearly without claiming a line-by-line recovery of the original post.
The topic in one sentence for readers of the archive
The old headline points to a practical modern issue: mobile apps can improve efficiency, but contact access and data handling can create confidentiality and privacy questions that depend on the federal consumer-protection lens, the state ethics rule, and the device settings in use.
