---
title: What Arazio sends, and what it asks permission for
source: https://arazioformac.com/docs/privacy
---

# Privacy and permissions

## Your files never leave your Mac

The conversion engines contain **no networking code at all**. This is not a
policy; it is a property of the binary, and a test fails the build if a
networking symbol turns up in one of those modules.

Nothing is uploaded, nothing is queued for upload, and there is no "processing
server". A conversion works with the Wi-Fi off, on a plane, forever.

## What does leave your Mac

Two things, both of which you can see and one of which you can switch off.

**Licence activation.** One request when you activate, carrying your licence
key. [How that works](/docs/activate).

**Update checks.** Arazio asks whether there is a newer version, sending the
version you are running and nothing else — no licence key, no identifier, no
file names. Switch it off in Settings and Arazio makes no network requests at
all. [More](/docs/updates).

There is no analytics, no telemetry, no crash reporting that phones home, and
no account.

## The permission it asks for

**Accessibility**, and only that.

An app has to be allowed to observe input events to notice that you are holding
<kbd>⇧</kbd> during a drag. macOS puts that behind Accessibility. It is the
whole reason the gesture can exist.

Arazio uses it to see modifier keys during a drag. It does not log keystrokes,
and it does not watch anything outside a drag it is already part of.

## What Arazio can see

The files you drag onto it, while it converts them, and nothing else. It does
not index your disk, does not scan folders you have not pointed it at, and
keeps no history of your files beyond the recent-conversions list in its own
menu, which you can clear.

## The formal version

[The privacy policy](/privacy) and [the terms](/terms).