Trust, Methodology, and Data Handling
1) Methodology and calculation transparency
Forecasting is journal-driven for opening BS, transaction definitions, and linked period movement to PL, BS, and CF. The model is built to keep tables aligned across statements, and mismatch checks are included for review before export.
- Opening BS is the basis of every period’s first balance.
- Transaction definitions define timing, frequency, growth, and account flow.
- Projected journals are generated before linked statement aggregates.
2) Data handling and privacy boundaries
We do not require user accounts and do not persist scenario history by default. Forecast payloads and TB imports are sent to the backend for calculation and can be reviewed via application logs and issue reporting when needed.
- Only needed fields for calculation are required.
- Issue reports capture compact metadata (type, summary, context) for quality review.
- We do not claim to use trial data as targeted ad personalization.
3) Reliability signals for operational use
Trust is not just about “feature completeness”; it is about repeatability and correction speed. We expose checks, provide issue reporting for suspected journal/template/calculation problems, and maintain a feedback record path for continuous improvement.
- Checks for mapping and balance consistency are surfaced in the UI.
- Users can report suspected issues directly from the result screen.
- Paid output is scoped to formula-linked workbook generation.
4) Security and retention boundaries
The public static site is designed to run through Cloudflare Pages, while forecast and export APIs are served by the configured backend. Server responses include restrictive browser security headers such as frame blocking, content-type sniffing protection, and a content security policy for the known application and advertising scripts.
- No public user account system is required for the browser preview.
- No full forecast scenario library is intentionally stored for end users by default.
- Feedback records are compact and intended for issue triage, not full model reconstruction.
- Local-only feedback review is separated from public static pages.
5) Validation workflow before external sharing
A forecast should be reviewed before being used in a board, financing, valuation, or operational planning workflow. The recommended order is opening BS, transaction timing, Checks tab, account-level review, then Excel export.
- Use browser checks before paying for Excel output.
- Compare direction and timing before checking detailed presentation format.
- Keep exported workbooks as review artifacts, not as a substitute for professional advice.
6) Pricing and access policy
The standard flow is free web preview, while formula-linked Excel output is a paid output. Reward-based unlock logic may also apply when configured by deployment.
7) For direct users and search visibility
If this is your first visit and you are evaluating for business planning, start with the free setup guides, then move to pricing clarification and data-policy checks before sharing results externally.
A concise AI-readable summary is also published at /llms.txt. It lists the product boundary, pricing boundary, important guide pages, and trust limitations in plain text for search and answer engines. The detailed calculation flow is available at /methodology, and release-level trust notes are published at /changelog. Security and data handling notes are available at /security. Quality review scope and review limits are available at /quality-review-policy. Guide review and correction policy is available at /editorial-policy. Frequently asked questions are listed at /faq, and the full guide index is available at /guides.
8) Related help pages
- How to build a free three-statement forecast
- How to import a trial balance CSV
- Web forecast vs paid Excel output
- Trial balance to three-statement forecast
- Cash flow forecast with collection and payment lag
- Three-statement forecast for DCF assumptions
- Loan draw and debt repayment forecast
- Capex and depreciation forecast
- Startup cash runway forecast
- COGS, inventory, and working capital forecast
- Bank loan covenant and DSCR forecast
- VAT and sales tax cash flow forecast
- SaaS deferred revenue and MRR forecast
- Payroll withholding and social insurance forecast
- Grant and subsidy cash flow forecast
- Lease liability and right-of-use asset forecast
- Acquisition goodwill and PPA forecast
- Equity financing and share issuance forecast
- Deferred tax and temporary difference forecast
- Asset retirement obligation forecast
- Bond issuance and redemption forecast
- Journal template coverage and account mapping
- FAQ
- Guide index
- How to validate a forecast before export
- Why a balance sheet does not balance in a forecast
- Security and data handling
- Quality review policy
- Editorial policy and corrections
- Public changelog and verification log
9) 日本語版（信頼性 / 方法論 / データ取扱い）
本ページの要点は「開始BSと取引をもとに、PL・BS・CFを連動」「無料Web利用と有料Excelの境界」「課題報告導線の存在」です。 外部監査や社内レビュー前提で利用する場合は、PDF保存や履歴保全の運用要件を別途確認してください。
- 開始BS、取引タイミング、Checksタブ、勘定科目別確認、Excel出力の順で確認します。
- 入力された財務データを広告ターゲティング目的に意図的に利用する設計ではありません。
- 不具合報告は、対象月・対象勘定・想定値・観測値を短く残す運用です。