EVO CAPABILITIES / Private and business data
Use valuable context with a boundary you can explain.
Private AI work starts with clear choices about what is available locally, what a task may use and what may leave the device.
Mac development · See current scopeThe real problem
Useful AI needs context, and some of the most useful context is sensitive: internal plans, customer feedback, financial assumptions or unpublished product material. Teams need a practical way to get help without treating access to one document as access to everything. Individuals need the same clarity for personal files, memory and correspondence.
What chat history leaves you to do
Attaching a file to a chat can make several decisions feel like one: store it, read it, share it, remember it and use it later. A broad privacy slogan cannot explain those choices. For a business review, the important questions are concrete: which content entered this task, where was it processed, what result was saved and what did the user actually authorise?
How EVO approaches it
Separate storage from use
In EVO's supported local workflow, importing a reference document does not automatically add it to every conversation or promote it to long-term memory. Selected document content, approved memory and the recent conversation are different inputs. This lets you keep material ready for a task without treating its presence on the device as permission for every future use.
Make the cloud boundary visible
A supported cloud request has its own data-sharing choice and record of the selected categories used for that purpose. Local processing does not silently acquire cloud rights. You can decide whether a particular task justifies sharing chosen material, rather than infer that a general preference or an earlier approval covers every future request.
Keep review tied to the actual action
EVO distinguishes reading, proposing, applying and checking the result. A document may contain instructions, but those words are source material, not a new permission from you. A memory about your preferred workflow cannot authorise sending correspondence. These distinctions help make a useful assistant easier to supervise without turning all assistance into manual work.
Understand what each privacy control changes
Forgetting a memory affects its later use; deleting an improvement record affects its local guidance; removing a source or revoking a choice can make pending work unusable. Those actions do not retroactively recall material already transmitted or erase separately retained exports. EVO's approach is to make each control's effect understandable rather than describe every deletion as complete erasure.
A concrete example
ILLUSTRATIVE WORKFLOW · NOT A CUSTOMER RESULT
Illustrative workflow: review an internal proposal
A business owner wants help comparing an internal proposal with selected public information. The internal material must not be treated as a general source for unrelated tasks.
Keep the proposal in the selected local file area and identify the exact question to answer.
Choose an available local workflow or separately review which material a supported cloud request would receive.
Inspect the result and its sources, then decide what should remain with this Work and whether any lasting preference deserves its own memory review.
What you take away
The intended outcome is a useful review with an explainable scope: which material supported it, which decisions were made and what remains private or unshared. It is a concrete basis for evaluation, not a blanket compliance assurance.
Your choices
- Select files, memory and supported tools for the specific task; local storage alone does not authorise sharing.
- Inspect data choices, required approvals and saved outcomes, and revoke future use where supported.
- Manage original files, workspace records, memory and backups as separate retention decisions.
Current scope
Implemented foundation
- Selected file access, reviewed memory and account-scoped storage are implemented with controlled isolation tests.
- Local processing and encrypted backups have different boundaries. No blanket end-to-end encryption, certification or zero-retention promise is made.
Next milestones
- Public Alpha service and a complete enterprise deployment offering are not released. Organisation-wide administration, customer contractual terms, residency commitments and certifications require their own completed review.
- No claim is made that every system is end-to-end encrypted or that third-party processing has zero retention or training use. Business suitability must be assessed against the applicable service terms and documented controls before sensitive adoption.
These are development capabilities, not a public release. See platform availability before requesting a trial.
Platforms and availabilityRelated questions
Does adding a file upload it?
No. Adding a reference file to the Mac workspace does not automatically upload it or make it a shared memory.
Storage, selection for a task and cloud processing are separate choices. A conversation receives supported content you have selected within that task’s scope.
You can keep a project brief locally, then choose an appropriate extract for a specific comparison.
Review selected material before sending and choose the processing mode. Manage reference files separately from memories and conversation records.
Supported formats and extraction limits vary. Removing a local file does not recall a copy already sent elsewhere or erase separate backups.
How is my information protected?
EVO gives you separate controls for selected files, memory, cloud sharing and supported actions, alongside an encrypted offline backup option in the Mac development build.
These controls let you decide what a task may use and keep an inspectable history of relevant choices.
You can retain a local reference document while sharing only the supported material selected for a particular task.
Review data choices before sending, revoke reusable permissions and manage copies and backups deliberately.
Backup encryption is not encryption of the entire running workspace. No blanket privacy, end-to-end encryption or compliance certification is claimed.
What is EVO Mail intended to do?
EVO Mail brings an inbox, drafts and message organization into a dedicated app, with separate choices for AI reading, reply help and sending.
The development foundation covers internal delivery and review of the actual recipients, content and attachments before a send.
The intended workflow is to select a message for help, review a proposed reply and independently decide whether to send it.
Mailbox reading, cloud sharing and sending are separate permissions: permission to read is not permission to send. Signing in with Google does not grant access to Gmail.
Real mail service, Internet delivery and Gmail linking are not publicly available. Operational recovery, account verification and external-mail security still need qualification.
Will business documents become other users’ memory or training data?
The implemented workspace controls do not make selected business files shared memory for other accounts. Cloud processing and training terms need to be evaluated separately.
Task selection limits what EVO uses; a local correction record is not a model-training job or permission to circulate the original document.
A team can first evaluate a workflow with non-sensitive sample material and determine which data may be shared under its policy.
Review the chosen processing route, applicable terms and organizational requirements before providing confidential information.
No blanket promise about every service’s training or retention practices is made here. A signed enterprise data agreement and deployment controls are not yet an available offering.
What should a business evaluate before adopting EVO?
Start with the workflow and data boundary: what the team needs to accomplish, which records may be used and who must approve consequential actions.
The existing Work, evidence and review concepts provide material to evaluate. Organization-wide identity, retention, deployment and support require their own assessment.
For a research workflow, agree which sources are permitted, what counts as a complete result and who accepts it before introducing confidential material.
Use the business inquiry route to define requirements without uploading sensitive records into a general product request.
Enterprise SSO, certified compliance, organization-wide retention and service-level commitments are not verified or commercially available capabilities on this site.
Try the workflow
Bring a task you want to move forward.
Explore the Mac release, or tell us which workflow you would like to evaluate. An application does not guarantee an invitation.