How Tilorah site content, brand assets, demos, downloads, and intent: trade software may be used.
Plain-English summary. Tilorah keeps ownership of the website, brand, app code, designs, demos, screenshots, and downloadable files unless a separate written agreement says otherwise. Product users receive only the limited right to use the relevant product for its intended purpose.
All content published on tilorah.co, including text, layouts, screenshots, demos, downloadable files, product names, logos, and visual designs, is owned by Tilorah or its licensors and is provided for viewing, evaluation, and product support only.
You may not copy, scrape, crawl, mirror, republish, resell, sublicense, train models on, or commercially reuse Tilorah site content, demos, screenshots, downloadable files, or brand assets without written permission, except where a specific file or agreement grants that right.
| Product | License posture | User/customer responsibility |
|---|---|---|
| intent: trade | Proprietary Tilorah app/service. Users receive a limited, non-transferable license to use enabled features during their active access period. | Users retain their trade journal content and are responsible for trades, risk management, tax/accounting records, broker reconciliation, and verifying AI/OCR output. |
Internal, local-only, draft, or personal-use projects are not licensed to the public unless Tilorah later publishes them under a separate agreement, notice, or app-specific license.
Tilorah public pages and intent: trade may include open-source libraries, CDN assets, fonts, app-store SDKs, cloud providers, AI providers, or other third-party services. Third-party components remain governed by their own licenses and terms.
Distributed apps should include a current THIRD_PARTY_NOTICES.md file. These notices must be regenerated before each release because package versions, CDN assets, and license obligations can change. The current public-site inventory is available in Third-Party Notices.
If Tilorah signs a customer contract, statement of work, source-code assignment, reseller agreement, or app-specific EULA that conflicts with this overview, the signed or app-specific agreement controls for that product and customer.