Does Orvial take screenshots?

Normal Orvial workspace control does not depend on continuously recording the screen. It is being designed to work through the macOS Accessibility APIs, which identify and control windows without capturing their contents.

Does Orvial upload my window titles or URLs?

The intended product does not upload window titles, URLs, file paths, or document names by default. They are treated as potentially sensitive, and enabling more detailed local troubleshooting is not intended to transmit anything by itself.

Do I need an account to use Orvial?

The local deterministic product is designed not to require an Orvial account.

Does Orvial need the cloud or AI to work?

The local core is being designed not to require cloud services or AI. Any later feature that does need them should say so clearly and remain refusable.

Privacy principles

A workspace can reveal a lot about a person.

Window titles, project names, documents, URLs and display setups all expose context about what you do and who you do it for. Orvial is being designed with that assumption from the start.

Orvial is in development. These are the commitments the product is being built to, not claims about shipped behaviour. Looking for what this website collects? That is the website privacy notice.

The commitments

How does Orvial handle my data?

Eight specific behaviours, rather than an adjective.

Local first

Scenes, Environments and the orchestration between them are designed to work on your Mac. The deterministic core should not need a round trip to a server to put a window where it belongs.

No account required

The local product should not require an Orvial account. Signing in to arrange your own desktop is not a trade anyone should have to make.

No continuous screenshots

Normal workspace control does not depend on continuously recording your screen. Orvial expects to work through the macOS Accessibility APIs, not through capture.

Telemetry off by default

Local logs and transmitted telemetry are separate things. Turning on more detailed local troubleshooting should never, by itself, start sending anything anywhere.

Content-sensitive data is treated as sensitive

Window titles, URLs, file paths, document names, Scene names and context are all capable of revealing what you are working on and who you work for. They are designed to be handled on that assumption rather than as incidental metadata.

Diagnostics are reviewable

If a diagnostic package is ever produced, you should be able to read it and redact it before it is transmitted — not send an opaque bundle and hope.

AI stays optional

Cloud intelligence must not become a hidden dependency for core orchestration. If a feature needs it, that should be visible and refusable.

Export safely

Portable configuration should leave machine-specific and sensitive values out by default, so sharing a Scene does not quietly share your desk.

Why it needs so much permission

Is Accessibility permission a privacy risk?

It is a real question, and it deserves a real answer rather than reassurance.

Accessibility permission lets an approved app control interface elements in other applications. That is genuinely powerful, and it is the reason the principles above matter more here than they would for a tool that only touched its own window.

What Orvial needs, what it deliberately does not ask for, and what happens when you revoke it are all on permissions.

Follow the build

One useful update at a time.

Occasional notes as Orvial moves from engine evidence toward its first macOS release.