Attribution, takedown & report a problem
Last updated:
Source attribution and reuse
TaskToTool credits grokbot.dev entries to the listed author and grokbot.dev, each by name and link. The repository’s content licence notice licenses content under content/ as CC BY 4.0; its README licensing section specifies attribution. Entry pages and API responses carry no licence notice themselves.
In the 22 Oct 2026 review, all 13 grokbot.dev titles and 10 summaries were reproduced verbatim. One summary is shortened by removing engagement figures; two use AI-written TaskToTool replacements. Per-listing change notes identify these treatments, formatting, normalized tags and added context. Linked posts and media retain their own rights. We do not reproduce prompts, including curator-reconstructed use-case prompts.
We retain supplied attribution and notices, identify modifications and link the licence. No separate content copyright or disclaimer notice was supplied in the material checked on 22 Oct 2026. The repository’s MIT code copyright notice does not apply to entry content. See the CC BY 4.0 legal terms. Source notice checks do not independently establish ownership of every underlying contribution.
GitHub entries link repositories and identify their names. Nine summaries are AI-assisted paraphrases or shortenings of repository descriptions; the two repositories with no stated licence use AI-written neutral descriptions. We do not reproduce README files, code or media. Repository licence labels are metadata: check current terms and scope at the source. Public visibility does not establish general reuse permission. See GitHub’s terms on user-generated content and our Licensing and attribution page.
Report a concern
Email contact@tasktotool.net if a listing is inaccurate, infringes your rights, exposes unnecessary personal information or links to harmful content. There is no website submission form. Please include:
- The TaskToTool page URL and the specific material concerned.
- Your concern and the correction, attribution change or removal you request.
- Relevant source or licence evidence and, where needed, your authority to act.
Do not send passwords, unnecessary identity documents or unrelated private information.
How we respond
Bogdan Mihaila is responsible for editorial decisions. We will assess the concern and supporting evidence, correct or remove content where justified and explain our decision. Credible urgent harm may warrant temporary restriction during review. If you disagree, reply with further evidence for reconsideration. This is an editorial handling policy; we do not promise a fixed response time for ordinary reports.
If a licensor requests removal of attribution information covered by CC BY 4.0 section 3(a)(3), we will comply to the extent reasonably practicable. This obligation is separate from deciding whether to remove the listing itself.
For a justified correction or removal, we will update authoritative records and affected histories, archives and generated output, then rebuild and deploy as appropriate. We will address stored snapshots and caches and prevent a later CSV reimport from restoring removed material. The metadata refresh observes existing listings; it does not import new listings. We cannot guarantee deletion of copies independently held by others.
Personal-data requests
Access, correction, erasure, restriction and objection requests follow our privacy notice, rights and complaint information, including statutory response deadlines and the right to complain to ANSPDCP. Reports and correspondence are handled as described there.