Purple Lithium: Privacy policy missing or incomplete

The fix: rejected → fixed

-Removed: We respect your privacy and never misuse your data.+Added: # Privacy Policy for Tidy - Group and Save Tabs+Added: Data we collect: the URLs and titles of tabs you choose to save.+Added: How we use it: only to restore your saved sessions. Stored in chrome.storage on your device.+Added: What we send: anonymous usage events (feature name, version) to [ANALYTICS PROVIDER].+Added: Sharing: we do not sell or share data with third parties except the provider above.+Added: Retention and deletion: uninstalling removes local data; contact [EMAIL] to delete analytics.+Added: Contact: [EMAIL]. Last updated: [DATE].

The policy names the extension and covers the four things reviewers check: collection, use, sharing and handling. Host it at a public URL with no login.

Why you got Purple Lithium

• Sending page URLs, page text or selections to your API without a privacy policy in the dashboard.
• Any analytics or error tracking, even "anonymous" ones.
• A privacy policy link that 404s, needs a login, or goes to a homepage.
• A generic policy that doesn't mention the extension or the data it handles.
• Privacy practices answers ("I do not collect…") that contradict what the code sends.

Pre-resubmit checklist

Your ticks are saved in this browser.

1. Make a list of every network request your extension makes and what data each one carries.
2. Map that data to the dashboard's categories, such as web history, website content, user activity and personally identifiable information.
3. Write a policy that names the extension and covers collection, use, sharing, retention and contact details.
4. Host it at a public HTTPS URL that loads without a login.
5. Paste the URL into the privacy policy field on the Privacy practices tab.
6. Tick the matching data categories and certify the limited-use statements.
7. Resubmit.

Common mistake: If the extension collects user data that users would not expect, a policy alone may not be enough. Purple Nickel requires an in-product disclosure and consent screen.

Appeal or resubmission note

Replace the [BRACKETS], then use the appeal link in your rejection email. Keep it short and factual, and list only changes you actually made.

Hello Chrome Web Store team,

My item [EXTENSION NAME] (ID: [ITEM ID]) was rejected with reference Purple Lithium.

I have reviewed the policy and made the following changes in version [NEW VERSION]:
- Published a privacy policy at [URL] covering collection, use, sharing and retention.
- Added the link in the Privacy practices tab.
- Updated the data disclosures to match the extension's behavior: [CATEGORIES].

[ONE SENTENCE ON WHAT THE EXTENSION DOES AND WHY IT NEEDS WHAT REMAINS.]

I have resubmitted the updated package. If anything still does not comply, I would appreciate a pointer to the specific file or listing field so I can fix it.

Thank you,
[YOUR NAME]

Other fix guides

• Blue Argon Remotely hosted code (Manifest V3)
• Blue Zinc Prohibited products
• Yellow Magnesium Functionality not working
• Yellow Zinc Missing or insufficient metadata
• Purple Potassium Excessive permissions
• Red Nickel Deceptive behavior
• Red Titanium Obfuscated code