Privacy & Permissions
Privacy and permissions, explained before you need them.
Aurora is designed to keep behavior local wherever possible and to ask for permissions only when a feature needs access. This page explains what each permission is for.
Privacy philosophy
Aurora is a desktop utility, not a data platform. Its job is to keep useful controls close to your workflow, not to collect unnecessary information.
Core app behavior stays local wherever possible. Features that need macOS permissions ask for access in context, and optional integrations such as Google Calendar are only used when you connect them.
Writing help and text tools
Aurora's text tools appear in Clipboard and Quick Notes workflows. They run only when explicitly triggered. When Apple's on-device model is available, Aurora uses it; otherwise, Aurora falls back to local text processing where supported.
Permissions
Accessibility
Used for top-edge interaction, quick-action overlays, keyboard-driven workflows, and window positioning.
Automation
Used when Aurora needs to communicate with supported apps such as Spotify, Apple Music, or supported Google Chrome web playback.
Screen Recording
Used only for screen-aware surfaces that require local context.
Calendar and Google Calendar
Used when you connect calendar features or a Google account. Aurora supports direct Google Calendar integration and multiple Google accounts.
Camera and Microphone
Requested only for widgets or surfaces that need live camera or audio-device access.
Payments
Payments are processed securely by Lemon Squeezy, Aurora's merchant of record. Aurora does not store your card details.