Publisher and contact
Bayat is an independent team based in Iran. General and legal enquiries: [email protected]. Privacy: [email protected]. Product help: [email protected].
This website uses the public name Bayat. The applicable product listing and agreement must identify the responsible contracting party where required by law. The public brand alone does not establish a registered company or a particular legal form.
Product scope
The company website privacy policy and website terms apply to the informational website. Toranj and Twins each have a permanent product document directory. Platform-specific behavior and store terms may differ.
Products are currently in development. Planned worldwide distribution does not promise availability in every territory or store.
Third-party materials
Third-party names and trademarks belong to their respective owners. Mention of a platform, provider, or store does not imply endorsement, a commercial partnership, or availability on that platform.
This site uses the original Bayat mark, the Space Grotesk and Vazirmatn fonts, Astro, and Starlight. Font licenses are included in the brand kit. Software components retain their own licenses. Product builds must carry their own applicable third-party notices.
Design references do not confer a license to reuse another template’s source code, artwork, or identity. This implementation uses its own layouts and copy.
Language and versions
English is the primary drafting language for legal documents. Persian pages correspond to the displayed revision; their review status is shown on each page. Mandatory local-language or consumer-law requirements remain applicable.
A draft is not an effective agreement or a final statement suitable for a store submission. A current published revision stays at its canonical URL. Earlier published revisions, when present, have permanent archive links in the document footer.
Reporting a concern
For a rights complaint, identify the material, its public URL, your relationship to the rights holder, and how to reach you. Please provide a clear description and relevant evidence without unnecessary sensitive information.
For accessibility barriers use the accessibility contact route; for vulnerabilities use the security reporting route.