Cyrenza, Inc. ("Cyrenza," "we," "us," or "our") is building a professional work system for commercial real estate firms. This policy explains the principles guiding how Cyrenza develops and intends to use artificial intelligence, deterministic software, evidence, and human review in that system.
Our starting point is simple: technology should expand professional capacity without weakening professional responsibility. Cyrenza is intended to help professionals carry more rigorous work from instruction to evidence, analysis, calculation, review, and decision. It is not intended to transfer professional judgment or final authority from people to software.
1. Scope of this policy
This policy applies to the design, development, evaluation, and intended use of artificial intelligence in the Cyrenza system. It also explains the role of deterministic methods, source evidence, professional review, and human approval in the system Cyrenza is building.
This policy is not a customer services agreement, a data processing agreement, a security addendum, or a promise that a particular capability is available. If Cyrenza provides product access, the applicable written customer agreement will govern that access. Where a customer agreement sets a more specific requirement, that agreement will control.
The Privacy Policy and Cookie Policy govern Cyrenza's public website. The handling of customer documents, Deal information, prompts, outputs, and other customer content must be addressed in the applicable customer agreement and, where required, a data processing agreement before a customer deployment.
2. Cyrenza is still being built
Cyrenza is under development. Descriptions in this policy of how the system is intended to operate state our design standard and direction. They do not represent that every capability is complete, available, or authorized for production use.
A capability should not be treated as ready merely because it can produce an output. Its evidence requirements, deterministic methods, review behavior, failure conditions, and human authority boundaries must also be defined and validated for the work it is intended to support.
Cyrenza may change its methods, models, providers, interfaces, and available capabilities as the system develops. We will not describe a development goal as a current operational guarantee.
3. Work begins with a bounded assignment
Cyrenza is being designed so that a commercial real estate firm can delegate a bounded assignment. A bounded assignment identifies, as applicable:
- the work the firm wants completed;
- the Deal, Property group, leases, documents, or other subject concerned;
- the evidence the system is authorized to use;
- assumptions approved by the firm;
- the method, standard, or policy that should govern the work;
- the required work product; and
- the professionals authorized to review, approve, or decide.
The assignment defines the system's authority. Cyrenza should not silently broaden the assignment, invent missing authority, or treat an unknown fact as an approved assumption.
If required evidence, authority, or an approved assumption is missing, the system should identify the issue and return it to the appropriate customer professional rather than conceal the gap.
4. Human judgment and final authority
The customer's authorized professionals retain institutional judgment, professional responsibility, and final authority over their work.
Cyrenza may be used to prepare analysis, reconcile evidence, perform defined calculations, assemble work products, surface issues, and record review. It does not independently have authority to:
- approve or reject an investment, loan, valuation, acquisition, disposition, development, lease, workout, or other transaction;
- make a credit or investment decision for a customer;
- bind a customer or another person to a transaction;
- approve an exception reserved for professional judgment;
- determine that a customer has satisfied a legal, regulatory, fiduciary, or professional obligation; or
- replace any approval required by a customer's policies or applicable law.
The presence of an AI-generated recommendation, score, summary, analysis, or draft does not constitute approval. A decision is a human authority event and must remain separate from the production work used to support it.
5. What the system is intended to do
Depending on the assignment and the capabilities made available, Cyrenza is being built to help firms:
- organize and classify relevant documents;
- extract facts and connect them to source evidence;
- build and review structured tables for leases, rent rolls, operating statements, and other transaction information;
- reconcile sources and record variances;
- identify material diligence issues and unresolved questions;
- perform calculations through defined, testable methods;
- prepare reviewable analysis and professional work products;
- support review, revision, and approval; and
- preserve the record of evidence, work, and human decisions.
Not every assignment requires every capability or follows one universal sequence. The system should use only the components required for the bounded work and should preserve the Deal record when work concerns a transaction.
6. Evidence and traceability
Cyrenza's design standard is that material claims in professional work should remain connected to their basis. The system should distinguish among:
- Source facts, which come from identified evidence;
- Assumptions, which are supplied or approved for the assignment;
- Calculations, which result from an identified method and inputs; and
- Firm precedent, which comes from authorized prior firm work or governed firm standards.
These categories should not be silently substituted for one another. An assumption must not be presented as a source fact. A prior Deal must not silently become firm policy. A model-generated statement must not be treated as evidence merely because it is stated confidently.
Where a work product makes a material factual claim, the intended standard is that an authorized reviewer can inspect the supporting source. Where it uses a material calculation, the intended standard is that the reviewer can inspect the inputs and method.
7. The role of artificial intelligence
Artificial intelligence can help interpret instructions, coordinate work, interact with documents, identify patterns, explain results, surface questions, and prepare drafts. It can make professional production more capable, but it can also produce incorrect, incomplete, inconsistent, or misleading content.
In Cyrenza's architecture, AI coordinates work. It is not intended to become the authoritative source for calculations, transaction state, evidence, or customer approval.
Where a result can be determined through a defined calculation or state transition, Cyrenza is being designed to use deterministic software as the source of truth. AI may help invoke, interpret, or explain that work, but it should not silently replace the governing method with an improvised answer.
An AI output should be treated as part of a reviewable work process, not as an independent professional opinion or final decision.
8. Review, material issues, and exceptions
Professional work can contain missing documents, conflicting facts, unsupported assumptions, unusual terms, calculation errors, and matters that require judgment. Cyrenza is being designed to make those issues visible.
Material variances and review findings should be recorded, not buried in a spreadsheet, narrative, or chat response. A blocking issue should be resolved or explicitly accepted by an authorized customer professional before the affected work proceeds where the assignment requires it.
Exceptions should be routed according to their nature:
- a system-production failure should be corrected by the product or fail explicitly;
- a missing-evidence issue should return to the customer for evidence or an authorized instruction; and
- a matter reserved for professional judgment should return to the customer's authorized professional.
Cyrenza's internal personnel should not become an undisclosed manual fallback that prepares, reviews, approves, or clears exceptions in customer work.
9. The role of Cyrenza's commercial real estate experts
Cyrenza's internal commercial real estate experts work on the Cyrenza system, not on a customer's Deal. Their role is to help define and validate:
- evidence requirements;
- deterministic methods;
- professional-work standards;
- evaluation materials;
- materiality rules; and
- capability-readiness criteria.
They do not provide the institutional judgment of the customer, approve the customer's work, or make the customer's transaction decisions. A customer must not assume that a Cyrenza expert has reviewed an output unless Cyrenza and the customer enter into a separate written agreement that expressly says so.
10. Responsibilities of customers and users
People and organizations using Cyrenza remain responsible for using it within their authority and for applying review appropriate to the assignment. They should:
- provide accurate instructions and identify the required scope and output;
- provide or authorize the relevant evidence;
- identify approved assumptions, standards, and methods where required;
- ensure they have the rights and lawful basis needed to provide data to the system;
- assign appropriate reviewers and decision-makers;
- examine material sources, assumptions, calculations, limitations, and unresolved issues;
- correct errors and withhold approval where the work is not adequate; and
- comply with applicable law, professional obligations, firm policy, and transaction requirements.
Users should not present an unreviewed output as approved professional work or rely on Cyrenza as the sole basis for a consequential decision.
11. Uses Cyrenza is not intended to support
Cyrenza is not intended to be used:
- to make a legally or similarly significant decision about a person solely through automated processing;
- to evade professional review, customer approval, or a legal requirement;
- to fabricate, conceal, or misrepresent evidence;
- to discriminate unlawfully or facilitate unlawful profiling;
- to obtain or process information without appropriate rights or authority;
- to mislead another person about the source, status, or approval of work;
- to compromise the security or integrity of a system; or
- for any unlawful, fraudulent, deceptive, or harmful purpose.
More detailed acceptable-use restrictions may be included in a future customer agreement before product access is provided.
12. Customer data and model providers
This policy does not establish the data-use terms for a customer deployment. Before Cyrenza accepts customer documents, Deal information, prompts, outputs, or other customer content, the applicable agreements should state:
- the purposes for which Cyrenza may process the content;
- the respective privacy roles of the customer and Cyrenza;
- the providers that may process it and the functions they perform;
- applicable retention, deletion, and return requirements;
- whether and under what authority content may be used for service improvement or model training;
- applicable international-transfer terms; and
- the security and incident-response commitments that apply.
Cyrenza should not make a public claim that customer content is never retained or never used for model training unless that claim is supported by the architecture, provider terms, operating controls, and binding customer agreement that apply to the deployment.
When third-party models or infrastructure are used, their role should be evaluated and documented before customer use. Cyrenza remains responsible for the commitments it makes to its customers and cannot treat a provider's marketing statement as proof of compliance.
13. Development, evaluation, and readiness
Cyrenza's development approach is intended to evaluate the complete work process, not only whether a model produces fluent text. Depending on the capability, readiness work may include:
- defining the evidence contract for the assignment;
- specifying and testing deterministic methods;
- testing source attribution and calculation traceability;
- evaluating performance against representative professional work;
- testing materiality thresholds, variance handling, and failure behavior;
- confirming that authority boundaries and reserved approvals are enforced;
- testing tenant isolation, access control, audit, and data handling; and
- determining whether the capability is ready for a defined use, requires restrictions, or must fail explicitly.
Evaluation reduces risk but does not eliminate it. Capability readiness may be limited by assignment type, evidence quality, jurisdiction, customer configuration, or other conditions.
14. Transparency in work products
Cyrenza is being designed so that reviewers can understand the status and basis of material work. Depending on the work product, this may include:
- source references for factual claims;
- identified assumptions;
- calculation inputs and methods;
- unresolved variances and diligence issues;
- the version of the work reviewed;
- required approval checkpoints; and
- the identity or role of the person who approved a decision.
Transparency does not mean exposing private model reasoning. The visible record should contain the evidence, method, result, limitations, review findings, and authority events needed to evaluate the work.
15. Privacy, security, and compliance statements
Cyrenza's handling of public-site Personal Data is described in the Privacy Policy. Product privacy, confidentiality, security, retention, data-location, and incident-response commitments must be stated in the applicable customer agreements before a deployment.
Cyrenza will not claim a certification, audit result, compliance status, service level, data-residency commitment, or security control unless the claim is current, documented, and applicable to the service being offered. The absence of such a public claim should not be interpreted as a guarantee that a particular standard has been achieved.
16. Changes to this policy
We may update this policy as Cyrenza, applicable law, and our development practices evolve. We will post the updated policy and revise the "Last updated" date.
If a future change affects binding customer rights or obligations, the change will be handled under the applicable customer agreement and will not be made solely by changing this public policy.
When a previous version exists, Cyrenza will make it available through the Legal Center or on request.
17. Contact
Questions about this policy may be sent to legal@cyrenza.com.
Registered office for corporate identification:
Cyrenza, Inc.
131 Continental Dr
Suite 305
Newark, DE 19713
United States