Privacy, with clear boundaries.
This privacy notice separates the current website, a proposed development test, and future services.
A. Public website
The current OREA Systems website provides information about product direction and development. Public inquiry submission is not enabled. The Contact page provides preparation guidance; it has no working inquiry form or delivery channel.
The current website source does not implement its own analytics integration, cookie-writing logic, or browser-storage tracking. This describes the website source, not all processing by hosting platforms or other providers.
OREA Systems has not enabled Cloudflare Web Analytics for this website. The setting was confirmed disabled for the current Cloudflare Pages project at the time of review.
Hosting providers may still process ordinary technical request information needed to deliver the site. The Web Analytics setting does not establish that providers process no data, set no cookies, keep no logs, or follow any particular retention period. Provider logging and retention periods have not been verified for this notice.
B. Proposed Teams development sandbox
The proposed discovery session is limited to an approved development tenant, Team, and standard channel, with one fictional message that directly mentions the development app. The live session has not occurred. This notice does not authorize testing or extend its scope.
Normal support intake, customer linkage, Jira ticket creation, and an Orea reply are not authorized in that proposed session. Fictional message content does not make the surrounding account or channel metadata anonymous.
Incoming activity and retained metadata
Authentication and scope checks inspect incoming activity data. The reviewed candidate collector retains a bounded set of identifiers, service and resource references, timestamps, and validation provenance in memory. These records describe the origin and validation of the activity. The retained metadata is distinct from the message body excluded from the candidate export.
A proposed private export
Session preparation proposes a private metadata export during shutdown, subject to separate authorization. The candidate export excludes tokens, keys, raw headers, raw activity, and message body. It is a proposed step, not evidence that an export has already occurred.
Log sanitization is implemented at the Orea sandbox boundary. This does not establish that every external platform or process collects no logs.
Other service providers
Microsoft Teams and any tunnel or hosting provider involved in an authorized test process data through their own services. Orea’s local development evidence does not establish those providers’ retention policies or all of their data-handling practices.
Provider-specific processing, access, and retention need review for the services actually used.
Development-evidence retention and access
For the limited OREA Teams development sandbox, any separately authorized exported discovery evidence is retained for no more than 30 calendar days after the relevant test session ends, unless a documented security, legal, or operational reason requires a longer period. Deletion is currently a manual, operator-controlled process.
Access to that exported development evidence is initially limited to the designated OREA development operator. Additional access requires an explicit need and separate authorization.
This retention policy applies to separately authorized exported Teams development-discovery evidence. It does not define retention for future production services, customer records, source-control history, historical project evidence, or other business records.
In-memory candidate collection is distinct from a separately authorized private export. This policy does not establish retention periods for Microsoft Teams or any tunnel, hosting, or other external provider.
C. Future products and services
Product and roadmap descriptions are not evidence that those services are operational. This notice does not describe future contact delivery, production integrations, or customer services as already enabled.
Any such service needs its own review of actual data use, permissions, providers, retention, and applicable notices before it is offered. Nothing here claims legal or regulatory certification, production readiness, or government-cloud readiness.
Responsibility and privacy contact
Orea Systems LLC is the responsible legal entity for OREA Systems.
Privacy inquiries may be sent to [email protected]. This mailbox is monitored for OREA Systems privacy inquiries.
The Contact channel status explains the current website inquiry limitation; the Contact page has no submission channel. Qualified legal review may be appropriate or required before external customer or commercial use.
For the limits on website use and development testing, read the Terms.