DMCA Policy

Copyright Concerns?

We respect intellectual property. If you believe content on our site infringes your copyright, please send us a takedown request.

Please include enough detail for us to identify whether the concern is about an app description, screenshot, icon, package listing, developer attribution, or a link to an external source.

opskd is an independent catalog and does not claim ownership of third-party apps, trademarks, icons, screenshots, store descriptions, or developer materials. We use public listing information to help visitors identify the app they are researching. If that use is inaccurate, unauthorized, or should be removed, we need a clear notice so we can locate the material and review the request responsibly.

How to File a Request

Email us at dmca@opskd.com with:

• Description of the copyrighted work
• URL of the infringing content on our site
• Your contact information
• Statement that you believe the use is unauthorized
• The specific material you want removed or corrected
• Any official source we should use to verify ownership or current app details
• Your signature (electronic is fine)

A useful notice identifies the exact opskd page and the exact material at issue. Please do not send only a domain name or a broad complaint about a category. If the concern is a screenshot, include the screenshot URL or describe where it appears. If the concern is app text, quote the specific passage. If the concern is a link, include both the opskd page and the external destination.

Required Statements

To help us process a copyright notice, include a good-faith statement that you believe the disputed use is not authorized by the copyright owner, its agent, or the law. Also include a statement that the information in the notice is accurate and, under penalty of perjury, that you are the copyright owner or authorized to act for the owner. These statements help separate valid notices from vague automated complaints.

Response Time

We aim to respond within 24-72 hours on business days. Complex requests may take longer if they involve multiple pages, unclear ownership, missing URLs, or a need to compare app-store material with developer-owned sources. When a request is complete and valid, we may remove the material, disable access, replace it with safer attribution, add context, or ask for clarification before taking action.

Counter-Notice

If you believe your content was removed by mistake, you may submit a counter-notice to the same email address.

A counter-notice should identify the removed material, explain why you believe the removal was mistaken or misidentified, provide your contact information, include a statement under penalty of perjury that you have a good-faith belief the material was removed by mistake, and include your physical or electronic signature. We may forward the counter-notice to the original complainant when required or appropriate.

Trademark, Attribution, and Metadata Issues

Not every listing issue is a copyright takedown. If an app name, developer name, privacy policy, package value, source status, or store link is inaccurate, a listing correction may be faster than a DMCA notice. Send those reports to support@opskd.com with the affected page URL, the corrected value, and an official source we can verify. If the issue involves trademark confusion, explain which mark is affected and what change would reduce confusion.

Repeat Issues and Abuse

We may keep records of valid notices, rejected notices, counter-notices, and repeated correction issues so we can avoid restoring disputed material by mistake. We may also ignore abusive, fraudulent, incomplete, or automated messages that do not identify specific material or authority to act. False claims can harm lawful speech and useful catalog corrections, so please send accurate information.

What Happens After a Valid Notice

After receiving a complete notice, we review the identified page and decide what action is appropriate for the material at issue. That may mean removing a screenshot, changing a description excerpt, disabling a link, adding clearer attribution, or removing a listing from public navigation. We try to preserve useful non-infringing information when possible, such as package identity and correction context, while respecting valid rights requests.