This draft reflects the reviewed application and the confirmed legal entity. It is not legal advice or a claim of compliance. Unconfirmed business practices are listed below instead of being presented as settled promises.
Publication checklist
- Confirmed: SORA Labs, LLC is the legal entity.
- To confirm: A monitored privacy-request email and support channel.
- To confirm: business address, customer locations, applicable laws, and any regional supplements.
- To confirm: retention periods for active records, frozen evidence, audit logs, and backups; the deletion/export process.
- To confirm: the actual production providers, processing locations, contracts, and analytics/consent settings.
- To confirm: AI-provider use, model training, and any use of private documents beyond providing the workspace service.
- To confirm: sale, targeted-advertising sharing, and opt-out practices before making a blanket “we never sell or share” statement.
Who this covers
Keystone is a product of SORA Labs, LLC (“we,” “us,” or “our”). This notice covers personal information processed through the public website, user accounts, organizations, the Investor Portal, support, and authorized integrations.
For account administration, website operation, security, and our own support activities, we determine how the information is used. For personal information an organization places in its workspace, that organization generally determines the purpose of the processing, and we provide the service on its behalf. The applicable agreement and law determine the parties’ precise responsibilities.
A resident, broker, contractor, or invited partner may appear in a workspace record without having a Keystone account. The organization supplying that information is responsible for having the rights and permissions needed to provide and use it.
Information we handle—and why
| Category | Examples | Purpose |
|---|---|---|
| Account & access | Name, email, membership, role, invitations, and authentication information. | Sign-in, workspace access, verification, and account communications. |
| Workspace content | Deals, files, rent rolls, T12s, assumptions, notes, decisions, loan terms, ledgers, and supporting evidence. | Document review, calculations, comparisons, workflows, and requested sharing. |
| People in source files | Resident names or codes, units, rent and lease information; broker, investor, and vendor contact details where supplied. | Process the records provided for the workspace’s real-estate work. |
| Activity & diagnostics | Account identifiers, access and API events, timestamps, device/browser information, IP addresses, and error information. | Service operation, security, troubleshooting, and configured usage analysis. |
| Support communications | Contact information, messages, and material supplied to explain an issue. | Respond to requests and investigate reported problems. |
Only upload information you are authorized to provide. Avoid including Social Security numbers, bank-account details, identity documents, or other sensitive information that is not necessary for the intended workflow. A file may contain more personal information than the fields shown in its imported summary.
Where information comes from
Information can come directly from you, your organization, an inviter, an authorized integration, or a recipient interacting with shared materials. Property and market context may also come from broker listings, publicly available records, location services, and government datasets.
Public availability does not make every item non-personal or remove the need to respect access restrictions and source terms. We distinguish source observations from verified facts and keep source dates and provenance where available. The date we first observe a listing is not necessarily its original publication date.
Workspaces and property identities
Private workspace content is associated with its organization and governed by permissions. An independently verified public property identity can connect records for the same building, including historical names and location evidence, without combining the private contents of different workspaces.
Connecting two deals to the same building does not, by itself, expose one organization’s resident data, documents, notes, financial statements, or underwriting to another organization.
Current operating benchmarks use information available within the requesting workspace. Public property observations are separate from private operating evidence. This notice does not authorize a new cross-workspace pool of private rent rolls or financial statements.
Property history, source history, and a specific acquisition are different records. Removing a deal from an active view does not necessarily remove its historical evidence or a separate public property observation.
Imports and automated processing
Keystone processes documents and structured data to extract and map fields, identify possible matches, run checks, and calculate underwriting results. It also tracks supported source observations and workflow events. These results assist review; they do not replace checking the source files, confirming an identity match, or making an investment decision.
Imports can be incomplete or incorrect. User corrections and mapping revisions can be stored so the workflow can reproduce or explain a result. Automated checks are not a certification that a financial statement, property, or proposed investment is accurate.
The reviewed import paths use parsing and mapping. Before publication, confirm whether any other workflow or service provider receives private content for AI processing or training, and the relevant controls and agreements. This draft makes no blanket “never used for training” promise without that confirmation.
Cookies, browser storage, and technical data
Keystone and its authentication tools use browser storage or cookies as needed to maintain sessions and remember settings. Blocking or clearing them can sign you out or reset preferences. Infrastructure may process connection information such as IP addresses and request times.
When configured, diagnostics and product analytics can process limited technical events and account identifiers. The application’s analytics integration disables session recording and automatic page-text capture, and applies redaction controls to outgoing diagnostic information. These controls reduce unnecessary exposure; they are not a guarantee that no personal information can enter a diagnostic system.
Browser or device controls can affect storage and tracking, but a browser setting is not the same as a verified product-wide opt-out. Before publication, confirm which optional tools are active, their storage behavior, and any consent or opt-out mechanisms required for the places where Keystone operates.
Retention and deletion
Retention depends on the type of record, the workspace’s use of the service, applicable instructions and agreements, security needs, and legal obligations. Source files, parsed data, frozen decision evidence, audit events, support records, and backup copies do not necessarily have the same lifecycle.
Changing the active source, archiving a record, removing a member, and deleting information are different operations. Some records remain available as history or evidence after an item disappears from the main view. Deletion from an active system may not immediately remove a backup or a recipient’s external copy.
The published notice needs verified periods or clear retention criteria, including backup handling and legal exceptions. No immediate-deletion guarantee or fixed number of days is being promised in this draft.
Security and integrations
Keystone uses authentication, role and organization checks, private document storage, and additional verification for sensitive operations. API access uses scoped, expiring credentials; the application retains a hash rather than the full API token secret. Relevant credential and access events are recorded.
Protect your account, devices, and integration credentials. API scopes that read rent rolls can expose resident information to the integration you authorize. You are responsible for securing the receiving system and any copies it creates. No application or security control can guarantee that information will never be lost, misused, or accessed without authorization.
Your requests and choices
Depending on the applicable law and our role in processing the information, you may be entitled to request access, correction, deletion, a copy of information, or other choices such as restriction, objection, or an applicable opt-out. These rights can have exceptions, and we may need to verify your identity and authority before acting.
For records supplied by an organization, begin with that organization’s administrator. If a request should be handled by SORA Labs, LLC, use the privacy contact below. Tell us the nature of the request and the relevant workspace if known; do not send a password, API token, full resident file, or other unnecessary sensitive information.
The publication review must establish the applicable request methods, response periods, appeal or complaint paths, authorized-agent handling, and any jurisdiction-specific rights. A general product support page is not a substitute for a working privacy-request channel.
Processing locations and legal requirements
Processing locations depend on the infrastructure and service providers used for the feature. Access or processing may occur in a different location from the person or organization providing the information.
Confirm hosting and provider regions, the business address, the locations served, applicable legal grounds and transfer safeguards, and any state or international supplements before publication. This draft does not claim US-only storage, GDPR compliance, or that a particular privacy law necessarily applies.
Children and notice changes
Keystone is intended for professional real-estate work, not use by children. If you believe information was supplied inappropriately, contact the responsible workspace administrator or our confirmed privacy contact.
A published version will include its effective or updated date. When practices materially change, the notice should be revised and any additional notice or choice required by the applicable law provided. The design-review date is not an effective date for a new privacy policy.
Contact SORA Labs, LLC
For privacy questions and requests: the monitored privacy contact is still to be confirmed.
This review draft has no request-submission destination. Do not publish it as a completed privacy notice until the contact and other review items are resolved.
For workspace-specific questions, contact your administrator. For general product guidance, browse the FAQ.