LEGAL

Damru Legal, Fork, Copy, and Commercial Use Policy

Part of Damru — the open-source, Android-native stealth browser automation framework (Redroid + Playwright + CDP) for web scraping, automation testing, and anti-bot / fingerprinting research.

Part of the Damru open-source browser automation project.

Damru is published under the PolyForm Noncommercial License 1.0.0. This file summarizes the project policy in plain language. The LICENSE file controls if there is any conflict.

Official repository: https://github.com/akwin1234/damru

Official contact: contact@damru.dev

Damru is publicly visible source code, not public domain material.

Covered Material

This policy applies to the whole Damru project, not just the name or logo. Covered material includes Damru source code, native code, Python modules, CLI code, documentation, README text, examples, tests, configs, package metadata, release artifacts, proof assets, screenshots, videos, diagrams, and any substantial derived work based on them.

Allowed Without a Commercial License

• Personal noncommercial research.
• Educational use.
• Noncommercial security testing on systems you own or have written authorization to test.
• Noncommercial forks and pull requests that preserve the license, notices, and attribution.

Not Allowed Without Written Permission

• Selling Damru, hosted Damru access, managed scraping, botting, fingerprinting bypass, or automation services based on Damru.
• Rebranding Damru, Damru source code, or a Damru-derived project as an unrelated original project.
• Publishing any copy or derived work that removes Damru's license, notices, credits, or source attribution.
• Publishing Damru source code, docs, assets, releases, or derived code in a way that hides the Damru origin.
• Claiming original authorship of Damru, Damru-derived code, documentation, proof assets, package metadata, release artifacts, or any substantial copied portion.
• Relicensing, sublicensing, dual-licensing, or publishing Damru-derived material under terms that remove, weaken, or conflict with Damru's license, attribution, or noncommercial restriction.
• Publishing repositories, packages, websites, releases, binaries, docs, or proof assets that are likely to confuse users into believing they are official Damru releases.
• Using Damru for customer work, SaaS, paid tools, paid consulting, paid traffic operations, or any activity directed toward monetary compensation.
• Using Damru trademarks, logos, project name, screenshots, or proof assets to imply endorsement by the Damru maintainers.

Fork, Mirror, and Attribution Rules

Public forks, mirrors, source copies, readme copies, package copies, release copies, asset copies, or substantial reposts must:

• Keep the PolyForm Noncommercial License 1.0.0.
• Keep this policy file or an equivalent notice that points back to the original Damru project.
• Keep the original copyright, license, and attribution notices in every redistributed copy.
• Put visible attribution near the top of the README or repository description: Based on Damru by akwin1234 with a link to the official repository.
• Clearly state Unofficial fork/mirror near the top of the README unless the repository is maintained by the Damru maintainers.
• Prefer using GitHub's fork feature for public GitHub copies. If a separate repository is used, it must still preserve attribution, license, and the unofficial notice.
• Not publish Damru proof assets, logos, or benchmark claims in a way that implies the fork is the official project.

These rules apply even if only part of Damru is copied, including individual modules, native patches, setup scripts, documentation sections, examples, tests, or release assets.

Modified versions, renamed repositories, translated documentation, package reuploads, copied README content, copied examples, copied tests, and partial module copies remain Damru-derived material when they are based on Damru.

Repositories that use the damru name without being a GitHub fork or without clear top-level attribution may be treated as confusing or misleading copies. The maintainers may ask the owner to convert the repository into a proper fork, add attribution, rename it, or remove it.

Commercial Licensing

Commercial licenses are available for paid/business use, SaaS use, hosted services, enterprise deployments, custom engineering, and support. To buy or request a commercial license, contact contact@damru.dev or use the official community channel listed in the README.

Enforcement

If a public copy violates these terms, the maintainers may request attribution fixes, license restoration, removal of copied material, removal of misleading branding, takedown of infringing assets, removal of unauthorized commercial use, GitHub abuse/impersonation reports, package registry reports, or DMCA notices where appropriate.

---

Related

• Main README
• Contributing Guide
• Security Policy

_{Keywords: Android browser automation · stealth automation · antidetect · web scraping · Redroid · Playwright · CDP · fingerprinting research}