Tag: Mobile

Trademarks for Apps

If you are a typical person today, you’ve likely used at least three different apps before 9 am.  You get up in the morning and click on your weather app of choice to figure out what to wear and whether to take your umbrella.  Then you grab an UBER® to get to the office and during the ride, you order your coffee so it is ready for you as you breeze through the building on the way to the elevator.  No sense in waiting for the coffee, as this is a needless waste of time.  With more and more people relying on apps, app design, branding, marketing, and protection are more important than ever.

The number of mobile apps is exploding. In June 2016, Apple® reported approximately 2,000,000 total apps in its app store.  By May 2017, that number had increased by approximately 200,000.  Mobile apps may be discussed in three categories – mobile web apps that enhance web browsing, apps that offer users a new service not previously available via a smart phone, and traditional brands whose business is widely known (such as WALGREENS®).  With all of the competition in the marketplace, companies must consider how to protect their app brand as a trademark, before it launches the new app into the marketplace.

To be “protectable” as a U.S. trademark, an app must have a few key characteristics.  First, consider the name of the app.  Does it describe a feature or function of the app?  If so, the owner may want to reconsider, as the U.S. Patent & Trademark Office typically does not allow registration of descriptive marks.  Instead, the owner of the app will need to come up with a name that is either merely suggestive of the service the app provides or is arbitrary.  Arbitrary names of apps are those that do not describe or suggest anything about the app.  APPLE® itself is a good example of an arbitrary trademark, as APPLE® is a trademark for computers, pads, phones and other goods and services, all having nothing to do with fruit.  Suggestive trademarks may be the happy medium where the function of the app is not outwardly described, but the app name hints at the meaning.  For example, ENLIGHT® is a photo editor app and would be considered suggestive because it suggests something about photo editing but does not describe it.

In considering the name of the app, owners will also want to pay attention to the color and icon they will use with the app.  Will these elements convey a unique design that may lend itself to trademark protection?  While color is sometimes not claimed as part of a design trademark in the trademark application or emphasized in a typical enforcement setting, in the app setting it is important to claim color, as it is one mechanism to set the app apart from others.

Registration of an app name and design provides many benefits.  The most important benefit is having the presumption that the owner has the right to use the name, design, and color of the app nationwide over all others, subject to certain exceptions.  Another important benefit is that when the app name or design (or both) is a registered trademark, all others are put on notice of the owner’s rights.  That is, all others are held to know about the registered app, even if they did not actually know about it.  Finally, federally registered trademarks may obtain relief from an infringer without a lawsuit.  If the owner simply wants the infringer to stop using the confusingly similar name, design and/or color scheme, the owner need only submit proof to the marketplace on which the app is available, and the marketplace, such as the Apple® App Store, will assist in removing the infringing app.

For further inquiries pertaining to apps and trademark protection and related questions regarding your intellectual property, please contact:

Natalie A. Remien at:

312.368.0100 or nremien@lgattorneys.com.

*UBER®, WALGREENS®, APPLE®, and ENLIGHT® are all registered trademarks of their respective owners.

(Please note that we are not endorsing any products or services mentioned in this blog).

Unexpected Liability for Service Providers

With “hacking” and identify thefts becoming all too common place, each service provider must place more and more emphasis on protecting itself from legal liability caused by not only its own actions, but the actions of the company(ies) to whom it outsources. This article provides an introduction to contracting for service providers with an eye toward gaining legal platform upon which to adequately defend itself, if necessary.

In addition to government compliance, which will vary depending upon the industry, any company that collects personal information during the course of providing its services must take steps to safeguard itself from legal liability arising due to unwanted disclosures.  One way to provide a legal safety net is to consider the applicable issues in the service provider’s agreement.  The following is an abbreviated checklist.

  1. Whether personally identifiable information will be provided to service provider’s employees, and if so, what measures are taken to narrowly tailor the need to expose such information to only those employees or third parties who need to know in order to provide the service.  In considering this, a service provider may want to consider identifying types of employees or third parties that may be exposed to such information, or even listing such persons and having them sign a confidentiality agreement with respect to such information.
  2. When does a service provider have to notify a customer of a security breach?   Is there an obligation to notify customers of a potential privacy-related compliance issue?  Or, only when a security breach has occurred?  If a security breach is defined, service providers will be required to undertake all tasks from notification to remediation and payment for such remediation upon receipt of a complaint.
  3. While necessary, service providers will want to limit their contractual obligations to comply with compliance with IT management standards such as the International Organization for Standardization certification.
  4. If the service provider receives credit card information of customers, then at the very least, the following issues must be considered:
    1. Limitation of access of personal information to authorized employees or parties
    2. Securing business facilities, data centers, paper files, servicers, backup systems and computing equipment (mobile and other equip with info storage capability;
    3. Implementing network/ device application, database and platform security
    4. Securing info transmission storage and disposal
    5. Implementing authorization and access controls with media, apps, operating systems and equipment
    6. Encrypting highly sensitive personal information stored on any mobile media
    7. Encrypting highly sensitive transmitted over public or wireless networks
    8. Strictly segregating personal information from and info of service provider or its other customers so that personal information is not commingled;
    9. Implementing appropriate personnel security and integrity procedures and practices (conducting background checks, and providing appropriate privacy and info security training to service providers’ employees.

If you have any questions regarding your liability for disclosure of personal information, please contact:

Natalie Remien at:

nremien@lgattorneys.com or (312) 368-0100.

testimonials

"We've worked with Levin Ginsburg since the 1980s...we have grown with them and have a very high level of comfort and confidence with this firm." Jay Nichols, President,
Badger Murphy
"Astute, responsive and practical. Those are three reasons why we work with Levin Ginsburg." Bryan L. Oyster, V.P. and General Manager,
Bentley Forbes