DMCA & Copyright

CuteMods publishes information about applications and about modified builds of them. We do not claim to be the author or the owner of any of that software, and we act on copyright complaints that arrive complete. This page is written so a rights holder, or the person acting for one, can find what to send and what will happen next without needing to ask first.

1. Copyright Ownership

Application developers, publishers and copyright holders retain ownership of their respective applications, trademarks, logos and copyrighted materials. That includes the software itself, its name and version identifiers, its icons and artwork, its store screenshots, its interface, its music and its documentation.

Those marks and materials appear on cutemods.com for one purpose only: to identify the application a listing describes. Their presence is descriptive. It is not a claim of ownership by us, and it does not suggest that the rights holder is affiliated with this site, has authorised it, has contributed to it, or endorses it. No licence, no transfer of rights and no mandate to act on anyone's behalf is granted or implied by anything published here.

Where a page describes a modified build — a "MOD APK" — that modification was made by third parties and not by the original developer. The underlying application and all of its elements remain the rights holder's property.

2. What We Publish About Your Application

A listing on this site consists of:

• The application's name and version number, as a way of saying which product the page is about.
• Our own written description of what a modified build is reported to offer.
• An icon or artwork used to identify the product, and screenshots of its interface.
• A link that leads towards a file or a source, and metadata such as file size and an update date.

If any of that is inaccurate, or if the description attributes something to your company that your company did not do, tell us and we will correct it — a correction is often faster and easier than a takedown, and we would rather fix a wrong page than lose a useful one.

3. Copyright Complaints

If you are an application developer, a publisher, a copyright owner or an authorised representative, and you believe that your copyrighted application has been modified, distributed or published on cutemods.com without proper authorisation, you can submit a formal copyright complaint.

A complaint must be sent by the owner of the rights or by someone authorised to act for that owner. A fan, a customer, an unofficial reseller and a competitor are not the right sender, and a complaint from one will not be actioned on its own.

The statement below is the commitment this site makes to rights holders, and it is the process the rest of this page describes:

4. Information and Documents Required

A complaint that is missing these details cannot be verified, so it will be returned with a question instead of actioned. Please include all of the following:

5. How to Submit a DMCA Notice

1. Collect the items from section 4 and the evidence from section 6.
2. Email them to cutemodsupport@gmail.com with the subject line DMCA Takedown Request — <application name>. Send the complaint from your official address, not a disposable one.
3. Wait for the acknowledgement. A complaint is read by a person, so there is no instant automated reply and no fixed turnaround we would promise you over email.
4. If we need more to verify the claim, we will ask for that specific item. A complaint is not rejected for being imperfect — it is paused until it can be checked.

6. Required Evidence

Evidence is what lets us act without a legal order. Send what applies to your case; do not send material you would rather we never hold.

• Proof you own the rights — a copyright or trademark registration number and certificate, official store listings showing you as the publisher, or company records that identify the work as yours.
• Proof you may act — if you are an agent, a law firm or a enforcement service, a written authorisation from the owner naming you.
• Identification of the work — which asset is infringed: the application binary, its artwork, its name and marks, its code, or its paid features.
• Identification of the infringing page — the exact URL on this site, plus the download link or file the page points to if that is separate.
• A short explanation — what permission was missing: no licence at all, a licence that does not cover modification or redistribution, or a build that misrepresents your product.

7. Review and Verification Process

Each complaint goes through the same steps, in this order:

1. Completeness. Is every item from section 4 present? If not, we ask for what is missing.
2. Standing. Does the sender appear to own the rights, or to be authorised to act for the owner? We compare the details you send against public records for the product — store listings, the developer's own domain, registration data.
3. Scope. Which pages on this site are actually affected, including any duplicate or related listing under another URL.
4. Merits. Is the material described as infringing present on those pages? A complaint about something this site does not host is closed with an explanation, not with a removal.
5. Decision. The claim is either verified — and section 8 is carried out — or it is not, and we tell you why.
6. Record. The complaint, the documents and the decision are kept on file so a repeat claim about the same work is handled consistently.

Nothing is removed before step 5. That is deliberate: an unverified removal can itself be abused, to knock a listing offline or to censor a competitor's page.

8. Content Removal Procedure

When a complaint is verified, we do the following:

1. The reported listing is taken offline, or access to it is disabled, so the page and its download link are no longer reachable from this site.
2. Any duplicate entry for the same build under another URL is removed in the same pass.
3. The catalog, the search index, the category listings and the site's sitemap are refreshed so the page stops appearing anywhere on the site.
4. The decision is recorded with the complaint and the documents behind it.
5. You are told what was removed and when. If the removal also affects someone who obtained the material through us, they may be notified so that a counter-notification is possible.

Removal from cutemods.com means removal of our page and of the link we provided. We cannot delete a file that lives on someone else's server, take a copy down out of a search engine's cache, or recall builds that were already downloaded. Where the claim concerns the distribution of the file itself, the hosting provider of that file is the next party to contact, and we will say which one that is if we can tell.

9. Counter-Notification

If your material was removed as the result of a complaint and you believe that was a mistake — because you own the rights, because you hold a licence, or because the page described something else — you may send a written counter-notification containing:

• Your name, address, telephone number and email address.
• Identification of the material that was removed, and the URL it appeared at.
• A statement, under penalty of perjury in jurisdictions where that applies, that you believe the removal was the result of mistake or misidentification.
• A statement that you consent to the jurisdiction of the courts where the complaint's owner may pursue the matter against you, or — where you cannot give that consent — an explanation of what you are prepared to accept instead.
• Evidence supporting your position: a licence, a permission email, ownership records.

Where the law the complaint was written under provides for a counter-notification — the U.S. DMCA is the best-known example, and the EU and other frameworks have their own versions — a valid one may allow the material to be restored after the period that law requires. We do not decide that on our own: we forward the counter-notification to whoever filed the original complaint and act on what comes back. A counter-notification is a legal document; if your position is genuinely contested, take advice before sending one.

10. Repeat Infringement

A verified complaint has lasting effect on this site:

• A listing removed after a verified complaint is not republished, by us or through a duplicate entry, unless the rights holder withdraws the complaint in writing or the material is licensed properly.
• If a second, separate claim arrives about the same application, both are read together and the application's whole presence on the site is reviewed, not only the page complained of.
• Someone who submits complaints that turn out to be baseless — or that misrepresent who they are — loses the fast track: future submissions from that sender are held until identity and standing are established independently.
• Knowingly false claims are serious. In jurisdictions that provide for it, a person who misrepresents that they are authorised, or that material infringes, may be liable for the damages and costs that follow. We do not adjudicate that; we simply verify before acting.

11. What This Policy Does Not Do

Honesty about our position saves everyone time:

• We are not a registered agent, we have not filed a designation with any copyright office, and this page should not be read as claiming safe-harbour status or any other statutory protection.
• These procedures are modelled on the notice-and-takedown process of the U.S. DMCA and on equivalent regimes, because that is the structure rights holders expect. Following this page is not the same as a legal notice served under a specific statute, and it does not replace one.
• We do not decide ownership disputes. If two parties both claim the same rights, we take the content down while it is contested, or leave it down, and tell both sides to resolve it.
• We cannot grant permissions, issue licences, or authorise anyone to distribute a product described here.
• Nothing here is legal advice, to you or from you.

12. Copyright Contact

Copyright complaints, counter-notifications and questions about this page go to cutemodsupport@gmail.com.

For anything that is not a copyright matter, use the contact page instead — a broken link, a wrong version number or a business question is answered faster when it arrives as its own message rather than inside a takedown request.

13. Questions Rights Holders Ask

A rights holder who follows sections 4 to 6 gives us everything needed to act. That is the whole point of this page: the process is written down so a legitimate complaint can be resolved without a conversation about the process.