What is App Store Guideline 4.1(c)?

Guideline 4.1(c) is Apple's rule against 'Copycats.' It prohibits apps from using another company's brand, product name, logo, or icon without written permission from that brand owner. It applies to your app name, icon, screenshots, and any other metadata visible in the App Store.

Can I build a third-party app for a specific car brand, product, or service at all?

Yes. You can build apps that work with, enhance, or explain third-party products. The app can reference the brand in its content (tips, features, compatibility), but your listing must make it clear it's a third-party tool and avoid trademarked logos and brand names in the icon and title.

Is it enough to say 'unofficial' in the app name to avoid 4.1(c)?

No. 'Unofficial' does not grant you the right to use someone else's trademark. You still need to remove the logo from your icon and restructure the name so the brand isn't the lead element.

What should I change to fix a 4.1(c) rejection?

Three things: rebuild the icon so it contains no brand logos or wordmarks; rename the app as a descriptive tool (e.g., 'Hidden Features for X Cars' instead of 'X Secrets'); and scrub screenshots of any brand logos. Resubmit with these changes and the rejection usually clears on the first try.

[Real Case] Guideline 4.1(c) Rejection: A Lexus Tips & Tricks App

Not every App Store rejection is about bugs. Some come from branding — specifically Guideline 4.1(c), the "Copycats" rule.

This is a case study of a small utility called Lexus Secrets — a collection of hidden settings, tips, and tricks for Lexus car owners. The developer wasn't trying to impersonate anyone. They were building a reference tool for a passionate community. They got rejected under 4.1(c) on the first submission anyway.

The final approved version is live on the App Store: Hidden Features for Lexus Cars.

The One Thing to Remember

You are allowed to mention a brand. You are not allowed to present your app as if it belongs to that brand.

That single distinction is what 4.1(c) enforces. Apple separates two very different uses of a brand name:

Informational use — allowed. Describing what your app does, who it's for, and what it's compatible with. Mentioning the brand in your description, in body content, and as a qualifier in the title ("for Lexus Cars"). You're telling users what the app supports, not claiming the brand as yours.
Trademark use — not allowed without written permission. Putting the brand's logo in your icon, making the brand the lead element of your app name, or using official wordmarks in screenshots. This is what 4.1(c) exists to prevent.

Gut-check before submitting: if your first impression of the icon, title, and screenshots is "this looks like the official app from [Brand]" → rejection. If it's "this is a third-party tool for users of [Brand]" → fine.

The Original Submission

Name: Lexus Secrets
Icon: A stylized badge that included the word "Lexus"
Screenshots: Included the official Lexus logo in a few places for visual context

The app itself was functional and content-rich — menu combinations, buried settings, maintenance tips, trim-specific features. None of that was the problem.

The Rejection

Apple referenced Guideline 4.1(c) directly:

The app's icon and name contain an icon, brand, or product name that belongs to the following developer: Lexus. Apps cannot use another developer's icon, brand, or product name in the app's icon or name, without approval from that developer.

Apple's suggested next step was either remove the brand from the metadata, or attach written permission from Lexus. Getting formal permission from a multinational automaker for an indie app listing isn't realistic — so the only path forward was to rework the metadata.

The Fix — Three Changes

1. Rebuild the Icon

The original icon contained the word Lexus and visual elements inspired by the Lexus badge. Both had to go. The new icon used a neutral visual language (a car silhouette / key fob / settings motif) — no text, no badge, no color scheme that echoed official branding.

The icon is the single most scrutinized piece of a 4.1(c) review. If it contains a trademarked wordmark or logo, the rejection is nearly automatic.

2. Rename the App

"Lexus Secrets" led with the brand name. The new name was Hidden Features for Lexus Cars.

The lead element is now "Hidden Features" — a generic, descriptive phrase. "Lexus Cars" becomes a qualifier describing compatibility. Apple generally tolerates this "Function for Brand" pattern:

✅ "Manual for Tesla Drivers"
✅ "Tips for iPhone Users"
✅ "Hidden Features for Lexus Cars"
❌ "Tesla Manual"
❌ "iPhone Tips"
❌ "Lexus Secrets"

"Lexus Secrets" sounds like an app by Lexus. "Hidden Features for Lexus Cars" sounds like an app for people who own one. Apple draws a real line between those two framings.

3. Scrub the Screenshots

The original screenshots included the official Lexus logo as visual decoration. That had to come out — generic car imagery and text-only section headers instead. The body content of the app could still reference Lexus in text form (that's informational use), but the visual chrome of the screenshots needed to be brand-neutral.

The Result

After these three changes, the app was resubmitted and approved. No long explanation in Review Notes. No appeal. No legal back-and-forth.

The approved version is live here: Hidden Features for Lexus Cars.

Takeaways

Never put a trademark in your icon. Not the logo, not the wordmark, not a stylized version of either.
Structure the name as "Function for Brand," not "Brand Function." Lead with what the app does; use the brand as a descriptor.
Clean up screenshots — Apple evaluates the whole listing, not just the icon and title.
Don't chase written permission. For a small indie app, getting formal approval from a major brand is a dead end. Restructure the listing instead.
"Unofficial" is not a magic word. It doesn't unlock the right to use someone else's trademark.

The good news: 4.1(c) rejections are usually mechanical. Unlike Guideline 4.3 — which often requires real product changes — a 4.1(c) rejection is almost always a metadata problem. Change the icon, restructure the name, scrub the screenshots, resubmit. The app itself stays the same.

For the other common rejection trap, see our Tennis App case study on Guideline 4.3.

Track How Users Respond to Your Relaunch

A forced rebrand — new name, new icon — can affect how users find and rate your app. AppStoreReview monitors reviews across 175+ App Store countries so you can catch confusion, feature requests, or rating drops immediately after a relaunch.

Start monitoring for free →