Your files are work in progress—not an archive.

The rent-roll and T12 examples use invented data and run in the browser. There is no document-submission or account-creation mechanism on this site.

The site loads Google Fonts from Google’s servers. A visitor’s browser may therefore make a request to Google and disclose ordinary connection information, such as an IP address and browser details. Google controls its handling of that request under its own terms and settings.

When the site is publicly hosted, hosting and access-control providers may also process connection and request records to deliver and protect the service. Those operational records are separate from temporary document-processing files.

If deployed, the hosted app accepts documents such as rent rolls, T12 operating statements, and offering memoranda to prepare reviewed exports for supported model templates. Customer source documents, parsed-document support artifacts, and generated exports are temporary session artifacts; the hosted workflow does not deliberately save them in durable application storage.

Account, access, and security records are separate from customer session artifacts and may be maintained to operate and protect an invite-only service. Bundled or administrator-managed model templates are also separate.

Offline CLI and local Deal Inbox workflows may deliberately save files on the user’s own computer. Those local workflows are outside this hosted policy, and this policy does not delete or alter existing local projects.

• A fixed deadline is set when the first customer upload appears. Every server-side session file—including later generated or failure-package downloads—expires by that original deadline, no later than one hour after the first upload; reprocessing does not restart the clock.
• Temporary source-file copies on disk are removed when processing finishes; generated downloads remain available only until delete-now, the original deadline, or logout.
• A background sweep runs at least once a minute while the service is running; it does not wait for another user request.
• The app’s Delete this session’s data now action requests immediate deletion of that session’s temporary files and clears its derived results and download state.
• Hosted mode provides no option to retain customer files durably.

Uploads and parsed values may also exist in active session memory. Delete-now and logout clear that state; expired session state is cleared when the app next evaluates the session. Background cleanup revokes server-side download access. Copies you download or share separately remain under your control and are not removed by session deletion.

Deletion removes active temporary copies on a best-effort operational basis. A failed cleanup, interrupted process, filesystem behavior, or other system infrastructure can leave residual copies. Temporary deletion is not a promise of forensic erasure, and these technical limits do not remove the operator’s responsibility to protect data, investigate failures, and honor applicable obligations.

Supported, pre-mapped layouts can use rule-based processing. When an unfamiliar layout requires OpenAI API layout review, the app asks for explicit session authorization before sending document content or excerpts to OpenAI. If permission is declined, provider-dependent formats may not be processed.

Optional OpenAI support diagnostics require a separate authorization and may include parsed rent-roll rows, T12 values, and processing findings. Authorizing layout review does not also authorize diagnostics.

OpenAI’s data-controls documentation says default abuse-monitoring logs may retain API prompts and responses for up to 30 days, with possible longer retention for legal or safety reasons, and that Zero Data Retention requires approval. Actual retention depends on the applicable provider agreement and account settings; the operator must verify them rather than promise provider-side zero retention.

Provider infrastructure is outside the app’s direct technical control, and deleting a hosted-app session does not delete a copy retained by a provider. The service operator remains responsible for provider selection and configuration, limiting payloads, obtaining authorization, accurate disclosure, and responding to applicable data obligations.

Upload only documents you are authorized to share. Remove or redact sensitive information when your organization requires it. If your permissions or policies do not allow external processing, decline the OpenAI authorization and do not submit a provider-dependent document.

Only authorize external processing if you accept these third-party data-handling risks. This choice does not waive rights or obligations that apply under law.

To remove an active hosted session’s temporary material, use Delete this session’s data now inside the app. There is no deletion-request inbox on this website because this site does not accept uploads or create accounts.