Brand Policy

Open-source rights remain intact

The Meforash source code and documentation identified as licensed under the Apache License 2.0 remain available under that license. This Brand Policy does not narrow, revoke, or replace those copyright and patent permissions. Third-party code, model components, biblical editions, fonts, and other materials remain subject to their own notices and licenses.

Trademark rights and copyright licenses address different uses. The Apache License 2.0 lets you copy, modify, and distribute covered code and documentation, subject to its terms. It does not grant permission to present your version as the official Meforash service or to use Meforash branding in a way likely to confuse people about source, sponsorship, or endorsement.

If a logo or other brand asset is expressly distributed under an open-source license, the copyright permissions already granted by that license remain in place. This policy governs source-identifying use of the Meforash name and brand; it does not retroactively revoke copyright permissions for existing licensed material.

This policy does not restrict lawful fair use, nominative use, criticism, commentary, news reporting, or other uses protected by applicable law.

Uses that do not require permission

You may use the word Meforash accurately and in plain text to:

• identify or link to the official project or service;
• describe the project’s code, model, methods, results, or history;
• review, discuss, teach about, criticize, or report on Meforash;
• state truthfully that software is compatible with, uses, connects to, or was derived from Meforash; or
• provide the attribution or notices required by an applicable license.

Make the relationship clear. A modified distribution may say, for example, “Derived from the Meforash open-source project” if that statement is accurate and the distribution is also clearly labeled as an independent, unofficial version.

Forks and modified versions

You may exercise all rights provided by the applicable open-source licenses. If you distribute or operate a modified version:

• choose a distinct product and service name;
• remove or replace Meforash logos and visual branding from the user interface, except where needed for accurate attribution;
• state prominently that the version is independent and is not an official Meforash release; and
• do not imply that Rowant Labs sponsors, endorses, certifies, or supports the version.

These requirements concern branding and source identification. They do not prevent accurate notices that the software includes or derives from Apache-licensed Meforash code.

Uses that require written permission

Please obtain written permission before you:

• use a Meforash logo or a confusingly similar logo as your product, service, organization, event, publication, domain, social-media, or account identity;
• name a commercial product, hosted service, company, organization, or event in a way that suggests it is an official Meforash offering;
• use Meforash branding on merchandise or promotional goods; or
• claim sponsorship, certification, partnership, endorsement, or official status by Rowant Labs.

Permission for one use does not authorize a different use.

Misleading uses

Do not use the Meforash name, logo, trade dress, or a confusingly similar identifier in a way likely to mislead people about who provides a product or service, whether it is an official release, or whether Rowant Labs sponsors or endorses it. Do not alter a Meforash logo and present it as an official logo, or combine the brand with unlawful, deceptive, or defamatory material in a way that attributes that material to Rowant Labs.

Third-party names

Names and marks belonging to Thinking Machines, Railway, Supabase, Resend, Cloudflare, Google, GitHub, source-edition publishers, and other third parties belong to their respective owners. References to them describe project dependencies or sources and do not imply endorsement.

Requests and questions

For brand-use permission or questions about this policy, contact: