Use
Terms
The product boundaries for calculations, readings, accounts, source data, and licensed assets.
Last updated May 7, 2026Use Theonyma as a calculation and reference tool, not as medical, legal, financial, emergency, or religious authority.
Do not bypass sign-in, overload public routes, scrape private surfaces, or redistribute licensed assets.
Public coverage is limited to what Theonyma has actually reviewed or source-verified.
Use of Theonyma
Theonyma provides deterministic calculation tools, checked reference discovery, and private reading workflows. Use it respectfully and do not try to bypass authentication, scrape private routes, or overload public APIs.
Calculator totals, date/year paths, reductions, transliterations, and token traces are product outputs from the implemented engine. They are not medical, legal, financial, religious, or emergency advice.
Accounts and private features
Account features require Clerk authentication. Keeps, future private readings, settings, and paid features are bound to the signed-in account.
Users are responsible for the text, notes, birth details, or relationship details they choose to enter into private flows. Do not enter personal data about another person unless you have a proper reason and permission.
Checked data and source limits
Public matches and references are limited to reviewed or source-verified data available in the product. Theonyma does not claim to contain every word, every book, every scripture, or every source collection.
Source citations, values, transliterations, and review labels can evolve as the corpus is checked and corrected.
Licensed assets
Theonyma uses licensed fonts and private design references. Purchased UI8 archives, source packages, raw font files, and vendor terms are not public assets and must not be redistributed.
Users may view the public app, generated pages, and allowed outputs. They may not extract, resell, or republish private asset files from the repository or build pipeline.
Availability and changes
Theonyma may change calculation policies, corpus coverage, account behavior, or reading workflows as the product is verified. Versioned calculation provenance is kept so old results can be explained when rules change.
Public APIs are provided for stable product behavior, but private account APIs and paid workflow APIs are not public discovery surfaces.