Ships a mobile app, in the United States

15 U.S.C. 1052(a) · Read the law's page

• Do not expect to register on the principal register a name, logo, or other mark that consists of or comprises matter which may falsely suggest a connection with persons, living or dead, institutions, beliefs, or national symbols (s. 1052(a)); this is a ground for refusing registration, not a rule against using the mark.

25 U.S.C. 305e · Read the law's page

• Do not, directly or indirectly, offer or display for sale or sell a good, with or without a Government trademark, in a manner that falsely suggests it is Indian produced, an Indian product, or the product of a particular Indian or Indian tribe or Indian arts and crafts organization, resident within the United States (s. 305e(b)).

Federal Food, Drug, and Cosmetic Act section 524B, 21 U.S.C. 360n-2 · Read the law's page

• It reaches you only if you are the sponsor of an application or submission for a device under section 360(k), 360c, 360e(c), 360e(f) or 360j(m) of title 21 (the Food and Drug Administration reads these as a 510(k), De Novo, premarket approval, product development protocol or humanitarian device exemption submission), and the device is a cyber device: a device that includes software validated, installed, or authorized by the sponsor as a device or in a device, has the ability to connect to the internet, and contains any such technological characteristics validated, installed, or authorized by the sponsor that could be vulnerable to cybersecurity threats (section 524B(a) and (c)).
• Include in the submission such information as the Secretary may require to ensure that the cyber device meets the cybersecurity requirements of section 524B(b) (section 524B(a)).
• Submit to the Secretary a plan to monitor, identify, and address, as appropriate, in a reasonable time, postmarket cybersecurity vulnerabilities and exploits, including coordinated vulnerability disclosure and related procedures (section 524B(b)(1)).
• Design, develop, and maintain processes and procedures to provide a reasonable assurance that the device and related systems are cybersecure, and make available postmarket updates and patches to the device and related systems that address known unacceptable vulnerabilities on a reasonably justified regular cycle and critical vulnerabilities that could cause uncontrolled risks as soon as possible out of cycle (section 524B(b)(2), (A) and (B)).
• Provide to the Secretary a software bill of materials, including commercial, open-source, and off-the-shelf software components (section 524B(b)(3)).
• Comply with such other requirements as the Secretary may require through regulation to demonstrate reasonable assurance that the device and related systems are cybersecure (section 524B(b)(4)).
• A device, or a category or type of device, that the Secretary has identified as exempt is not subject to these requirements (section 524B(d)).

15 C.F.R. 744.11; Supp. No. 4 to part 744 · Read the law's page

• Before you export, reexport or transfer any item subject to the EAR, software included, check whether a party to the transaction is on the Entity List or uses an address the list identifies as a high diversion risk, and obtain the license the entry requires (15 C.F.R. 744.11(a); 748.5(c) to (f)).
• Do not use a license exception for a transaction with a listed party unless the Entity List entry allows it, and do not proceed with a transaction BIS has informed you needs a license because of a circumvention, agent, front or shell company risk (15 C.F.R. 744.11(a), (c)).
• Check whether a foreign entity you deal with is owned 50 percent or more by one or more listed entities; the extension in 15 C.F.R. 744.11(a)(1) is stayed until November 9, 2026, as the eCFR's Effective Date Note records.

15 C.F.R. 744.21 · Read the law's page

• Before you export, reexport or transfer an item listed in Supplement No. 2 to part 744, or any item subject to the EAR where the end use or end user is in Belarus or Russia, find out whether you have knowledge that it is intended for a military end use or a military end user, and get a license if you do (15 C.F.R. 744.21(a); 772.1).
• Do not proceed with an export, reexport or transfer that BIS has informed you needs a license because of an unacceptable risk of use in or diversion to a military end use or end user in Belarus, Burma, Cambodia, China, Nicaragua, Russia or Venezuela (15 C.F.R. 744.21(b)).

45 CFR 84.84 to 84.89 · Read the law's page

• The WCAG 2.1 requirements of this rule do not yet bind: they apply from May 11, 2027 to a recipient with fifteen or more employees and from May 10, 2028 to a recipient with fewer than fifteen (45 CFR 84.84(b), as amended by 91 FR 25496); until then your other obligations under section 504 still reach programs you offer through web content and mobile apps.
• If you receive Federal financial assistance from the Department of Health and Human Services, ensure that the web content and mobile apps you provide or make available, directly or through contractual, licensing, or other arrangements, are readily accessible to and usable by individuals with disabilities (45 CFR 84.84(a)).
• From May 11, 2027, if you have fifteen or more employees, make that web content and those mobile apps conform to Level A and Level AA of WCAG 2.1; the date was May 11, 2026 before the 2026 interim final rule (45 CFR 84.84(b)(1)).
• From May 10, 2028, if you have fewer than fifteen employees, make that web content and those mobile apps conform to Level A and Level AA of WCAG 2.1; the date was May 10, 2027 before the 2026 interim final rule (45 CFR 84.84(b)(2)).
• You need not conform where you can demonstrate that compliance would fundamentally alter the nature of a program or activity or impose undue financial and administrative burdens; the decision must be made by the head of the recipient or a designee after considering all available resources and accompanied by a written statement of reasons, and you must then take any other action that ensures individuals with disabilities receive the benefits or services to the maximum extent possible (45 CFR 84.88).
• Archived web content, preexisting conventional electronic documents not currently used to apply for or take part in your programs, content posted by a third party that is not posting by arrangement with you, individualized password-protected or otherwise secured documents about a specific person, their property or account, and social media posts made before your compliance date are excepted (45 CFR 84.85).
• Use a conforming alternate version of web content only where it is not possible to make the content directly accessible due to technical or legal limitations (45 CFR 84.86); other designs or methods are allowed where they give substantially equivalent or greater accessibility and usability (45 CFR 84.87).
• Noncompliance with WCAG 2.1 is treated as compliance only where you can show its impact on access is so minimal that people with disabilities can still get the same information, engage in the same interactions, conduct the same transactions and otherwise take part with substantially equivalent timeliness, privacy, independence, and ease of use (45 CFR 84.89).