Your files, mail, and calendar belong to you.
Effective date: October 20, 2026. Last Refuge (“we,” “us,” and “our”) operates lastrefuge.ai and publishes Aerie, Overlook, and Omarchy Calendar. This policy explains how this website and these applications access, use, store, and share information, including data obtained through Google APIs.
Website data
This website does not use advertising trackers, marketing pixels, accounts, newsletters, contact forms, or nonessential cookies. Our hosting provider may process limited server logs, including IP address, requested URL, timestamp, and browser information, to operate and secure the service. We do not use those logs to build advertising profiles.
Aerie and Google Drive permissions
Aerie is an independent Google Drive client for Linux. When you choose Connect Google Drive, sign-in happens in your browser through Google; Aerie does not receive or store your Google password. It initially asks for read-only access, then asks for additional consent when you first initiate an operation that needs to change Drive files.
- Browse and download Drive files (
https://www.googleapis.com/auth/drive.readonly): Allows viewing and downloading files you can access in Google Drive. Aerie uses this access to browse and search existing files, cache metadata such as names, identifiers, file types, sizes, folder relationships, modification times, and trash status, and download file content when you request it. Drive also supplies the connected account’s display name, email address, account identifier, and storage usage and limit so the app can display your account and storage status. - Change Drive files and synchronize folders (
https://www.googleapis.com/auth/drive): Allows viewing and managing your Drive files, subject to your access rights. Aerie requests this broader permission when you choose to upload, create a folder, rename, move, trash or restore a file, or enable two-way synchronization. The Google permission covers your Drive files generally; it is not restricted by Google to only the folders you select in Aerie. The app uses it for the file operations you initiate and the folder sync you enable.
How Aerie uses and stores data
Aerie connects directly from your computer to Google’s OAuth and Drive services over HTTPS. No Aerie-hosted backend receives your Drive data. Google continues to store your cloud files: downloads copy content to your computer, uploads send content to Google, and enabled folder synchronization sends file changes between the computer and Drive. Those changes remain subject to the files’ existing Google Drive sharing permissions.
Sign-in refresh tokens are saved in your system keyring rather than in the metadata database or ordinary configuration files. Access tokens are used in memory to make requests to Google. Account information, file metadata, and transfer and sync state are cached locally, normally in ~/.local/state/aerie/. Downloaded files and synchronized copies are stored in the locations you choose. Their protection depends on your device’s access controls, storage encryption, and backups.
When sync is enabled, Aerie’s background service can continue after the app window closes. It checks for changes, uploads and downloads files, and propagates edits, renames, and deletions for the folders you pair. Deletions go to the trash on the other side; conflicting edits keep both versions. Pause or stop synchronization on the Sync page when you do not want it to continue.
Overlook and Google permissions
Overlook is a native desktop mail and calendar client for Linux. Connecting a Google account is optional; you can explore the sample mailbox without connecting one. When you connect an account, Google asks you to authorize the following OAuth scopes. These permissions allow Overlook to provide the mail and calendar features you use on your device.
- Account email address (
https://www.googleapis.com/auth/userinfo.email): Accesses your primary Google Account email address to identify and display the connected account and associate its mail and calendars with the correct account in Overlook. - Google sign-in (
openid): Allows Google to authenticate you and associate the authorized connection with your Google Account. Sign-in happens in your browser; Overlook does not receive or store your Google password. - Read and organize Gmail (
https://www.googleapis.com/auth/gmail.modify): Allows reading, composing, sending, and organizing mail. Overlook uses it to download messages, including sender and recipient details, subjects, message bodies, dates, labels, and attachment information; retrieve attachments you choose to open; and sync actions such as read/unread, star, archive, move to a label, Trash, and Junk. This access supports local search, offline reading, Focused Inbox, and recipient suggestions. Read-only access cannot sync these mailbox changes. Overlook does not bypass Gmail Trash to permanently delete messages. - Send Gmail messages (
https://www.googleapis.com/auth/gmail.send): Allows Overlook to send email on your behalf. It is used when you choose to send a new message, reply, or forward, including the recipients, message text, and attachments you select. Messages you choose to send while offline are queued on your device and sent when you reconnect. - Read Google Calendar (
https://www.googleapis.com/auth/calendar.readonly): Allows viewing and downloading calendars you can access. Overlook uses this permission to read your calendar list and its metadata, including names, identifiers, colors, access roles, primary-calendar status, and default reminders, so you can see the right calendars in the app. It does not use this permission to change calendars or their sharing settings. - Manage calendar events (
https://www.googleapis.com/auth/calendar.events): Allows viewing, creating, editing, and deleting events on calendars where you have the necessary access. Overlook reads event details such as titles, descriptions, dates and times, locations, organizers, attendees, meeting links, and reminders to display Day, Week, Month, and Agenda views and provide notifications. It syncs event changes and invitation responses you make in the app. Read-only access would not allow these changes or responses.
How Overlook stores and protects data
Overlook communicates directly with Google’s authentication, Gmail, and Calendar services over HTTPS. Your Google account credentials, mail, attachments, and calendar data are not routed through or uploaded to a Last Refuge server. Background synchronization checks for changes and sends your queued actions to Google so the desktop app stays current.
Mail, calendar events, drafts, preferences, and pending offline actions are stored in a local SQLite database. Downloaded attachments and attachments queued for sending are stored locally too. The usual data directory is ~/.local/share/overlook; Settings → About shows the location on your device. This local storage supports reading, searching, composing, and organizing while offline.
OAuth access and refresh tokens are stored in your operating system’s keyring, rather than in the mail database or ordinary configuration files. A refresh token lets Overlook maintain the connection without asking you to sign in for every sync. If the keyring is unavailable, Overlook reports the problem instead of saving tokens to a plain file. The mail database and attachment files are not encrypted by Overlook itself; their protection depends on your device’s access controls, disk encryption, and backup settings.
Remote images in received messages are blocked until you choose to load them. Loading an external image contacts its host, which may receive your IP address and record that the image was requested. Sending mail shares the message and selected attachments with your recipients through Google. Calendar changes and invitation responses may be visible to organizers and attendees according to Google Calendar’s sharing and notification settings.
Omarchy Calendar and Google data
When you choose to connect a Google account, Omarchy Calendar requests access to the following Google user data:
- Email address and account identifier (
emailandopenid): Your Google account email address and a unique Google account identifier are used to identify and display the account you connected. - Calendar list (
calendar.calendarlist): The list of Google calendars you subscribe to, including calendar identifiers, names, and related calendar information, is used to show and select calendars in the app. This permission also allows the app to add or remove calendars from that list. - Calendar events (
calendar.events): Events on Google calendars you can access, including details such as titles, descriptions, dates and times, locations, attendees, and reminders, are used to display and manage your schedule in the app. This permission allows the app to view, create, edit, and delete events on those calendars.
Omarchy Calendar handles authentication credentials and calendar data on your device, subject to the permissions you grant. Google user data is not transferred to a Last Refuge-hosted backend. Communication with Google provides the app’s calendar and synchronization features.
Google data use and sharing
Aerie, Overlook, and Omarchy Calendar adhere to the Google API Services User Data Policy, including the Limited Use requirements, when using or transferring information received from Google APIs.
Google data is used only to provide the applications’ visible file management, synchronization, mail, calendar, and account features described above. This includes locally derived information, such as file and search indexes, sync state, recipient suggestions, and Focused Inbox classifications. We do not sell or rent Google user data, share it with advertising platforms or data brokers, use it for advertising or credit decisions, or use it to develop, improve, or train generalized artificial intelligence or machine-learning models.
Last Refuge does not receive your Google Drive, mail, or calendar content through these applications, and our staff cannot browse it remotely. If you choose to share specific content with us for support, we use it only to handle that request. Any disclosure of Google data is limited to providing features you authorize, necessary security or legal purposes, or a business transfer with your explicit prior consent, as permitted by Google’s Limited Use requirements.
Retention, deletion, and your choices
You can decline Google access or revoke it at any time through your Google Account’s third-party connections. Revocation prevents further authorized access; it does not erase data already downloaded to your device.
In Aerie, Sign Out stops the current session’s sync and transfers, removes the saved sign-in from the keyring, and clears that account’s cached metadata. Signing out leaves files on Google Drive untouched and keeps files already downloaded or synchronized to disk. To remove local copies, first stop sync or sign out, then delete the copies and any backups you made. Deleting files while two-way sync is enabled can also move the corresponding Drive files to the trash. Signing out locally does not replace revoking access in your Google Account.
In Overlook, Settings → Accounts → Remove account removes that account’s locally stored mail, events, drafts, and sign-in tokens. Removing an account from Overlook does not delete its messages or events at Google and does not replace revoking access in your Google Account. Downloaded files, exported copies, and backups may remain outside the account database and must be removed separately if you want to delete them.
Overlook keeps its local data until you remove it. Uninstalling the application leaves its data directory in place. To remove remaining app data, close Overlook and delete the data directory shown in Settings → About; also remove any remaining Overlook credentials from your system keyring and any copies or backups you made. Omarchy Calendar’s local data can be removed through its available controls or by removing its local app data. Last Refuge cannot remotely erase files on your device.
For privacy questions or requests about information you have voluntarily shared with Last Refuge, use our Contact page. Please do not send passwords or OAuth tokens; share only the information needed for your request.
Changes
We will post material policy changes here and update the effective date. If an application needs additional Google permissions or uses Google data for a new purpose, we will explain the change and obtain your consent before accessing or using that data in the new way. This policy does not limit rights you may have under applicable law.