AETHER — AI WINGMAN
Privacy Policy
Effective date: May 11, 2026 · Last updated: May 11, 2026
This Privacy Policy explains how RedZen Cloud Solutions ("RedZen," "we," "us," or "our") collects, uses, stores, and shares information in connection with the Aether — AI Wingman iOS application (the "App"), the paired Aether macOS application (the "Mac App"), and the related CDN-hosted relay service (together, the "Service").
Aether is a personal-productivity tool that lets you send natural language commands from your iPhone to your own Mac to perform actions such as opening or quitting applications, typing text, taking screenshots, and similar native macOS tasks. The App does not require you to create an account, and we do not sell your personal information.
1. Summary
- No account is required to use the App.
- Your chat history is stored locally on your iPhone using Apple's SwiftData framework. It is not uploaded to RedZen servers.
- Pairing credentials are stored in the iOS Keychain on your device.
- Commands you type are sent over HTTPS through a secure CDN tunnel to your own Mac, where they are processed locally and forwarded to a third-party large language model ("LLM") provider through our CDN relay for natural language understanding.
- We do not embed third-party analytics, advertising, or tracking SDKs in the App.
- The camera is used only on-device to scan a pairing QR code. No images are recorded or transmitted.
2. Information We Collect
2.1 Information stored on your device
- Chat content and history. Messages you type, the assistant's responses, and the names and results of tool calls (e.g. "open WhatsApp") are stored locally on your iPhone using SwiftData. This history never leaves your device unless you choose to send a new command, in which case the relevant recent messages are transmitted to your paired Mac to provide conversational context.
- Pairing data. When you pair the App with a Mac, the App stores a unique device identifier, a friendly name you choose, the tunnel hostname for your Mac, and a per-device secret. The secret is held in the iOS Keychain. Non-secret pairing metadata is held in UserDefaults.
- App preferences. Onboarding state, theme preferences, the active Mac selection, and optional local-network fallback settings are stored on the device.
2.2 Information processed by the CDN relay
The App communicates with your Mac through a relay hosted on a third-party content delivery network ("CDN") and a secure tunnel provided by the same CDN. The relay proxies calls to the LLM provider on our behalf. To operate the Service, the relay processes the following information:
- Device identifier and authentication. A randomly generated device ID for each paired Mac, plus a salted hash of the device secret used solely to verify that requests came from a paired device.
- Usage counters. Per-device and per-IP counters (number of registrations and number of model calls per day) used to enforce rate limits and prevent abuse. Counters are stored in the CDN's key-value storage with daily expiration.
- Standard request metadata. The CDN's edge logs may include IP address, timestamp, request path, response status, and country, as part of normal operation of any internet service.
- Model payloads in transit. The content of your commands and the messages exchanged with the LLM pass through the Worker so that the LLM provider's API key remains server-side and never touches your devices. The Worker forwards these payloads to the LLM provider and streams the response back. RedZen does not persist the bodies of these requests or responses.
2.3 Information we do not collect
- We do not collect your name, email, phone number, or address through the App.
- We do not require an account, social login, or sign-in.
- We do not collect contacts, photos, health, financial, or location data.
- We do not embed third-party advertising SDKs, analytics SDKs, or attribution SDKs in the App.
- We do not use tracking technologies for cross-app or cross-website tracking, and the App does not request App Tracking Transparency permission.
3. How We Use Information
We use the limited information described above only to:
- Establish and maintain the connection between your iPhone and your own Mac.
- Authenticate that requests reaching the relay or your Mac came from a device you paired.
- Forward your natural-language requests to the LLM provider and return its responses.
- Enforce rate limits to protect the Service from abuse.
- Diagnose crashes, errors, and connectivity issues when you contact us for support.
- Comply with applicable law and Apple's developer requirements.
4. Permissions Requested by the App
- Camera. Used only inside the pairing flow to scan the QR code displayed on your Mac. Frames are processed on-device by Apple's AVFoundation framework, are not recorded, and are not transmitted off the device.
- Local Network (optional). If you enable the local-network fallback, the App may connect to your Mac directly over Wi-Fi instead of the CDN tunnel. iOS will prompt you for permission the first time this is used.
- Microphone (optional, where applicable). If a future version of the App offers voice input, it will request microphone permission separately and transcribe speech using Apple's on-device Speech framework or a similar service. Voice features are not active without your explicit grant.
5. Third-Party Services
The Service relies on the following third parties strictly to deliver core functionality. We do not share information with them for marketing or advertising purposes.
- Content delivery network (CDN) provider. Provides the HTTPS edge, the relay that proxies LLM calls, the per-device secure tunnel, key-value storage for authentication hashes and rate-limit counters, and DNS for the tunnel hostname. The CDN provider's privacy policy is available on request via the contact details below.
- Third-party LLM provider. Processes the text content of your commands and message history in order to generate responses and tool-call instructions. The specific LLM provider may change over time as we improve the Service; in each case the provider acts as a processor on our behalf, the provider's API key remains held only by our CDN relay, and we configure the integration so that API inputs and outputs are not used to train the provider's models by default. The current provider's privacy policy is available on request via the contact details below.
- Apple, Inc. Distributes the App through the App Store and provides system frameworks such as SwiftData, Keychain, and AVFoundation. Apple's standard App Store and platform privacy terms apply.
6. Data Storage and Security
- Local storage. Chat history and preferences are stored locally on your iPhone in standard iOS containers protected by iOS file-level encryption when your device is locked.
- Keychain. Per-Mac secrets are stored in the iOS Keychain, which is encrypted and access-controlled by iOS.
- In transit. All traffic between the App, the CDN relay, your Mac, and the LLM provider is sent over HTTPS / TLS.
- Server-side secrets. The LLM provider's API key and the CDN provider's API token are held only as encrypted server-side secrets within the relay and are never delivered to the App or to your Mac.
- Caveats. No method of transmission or storage is completely secure. While we apply industry-standard safeguards, we cannot guarantee absolute security. You are responsible for keeping your iPhone and Mac up to date and physically secure.
7. Data Retention
- Chat history remains on your iPhone until you delete individual chats, clear all chats, sign out of pairing, or delete the App.
- Pairing records on the CDN relay persist while the device remains paired. You can revoke a device by unpairing it from the menu-bar app on your Mac or by rotating its secret.
- Rate-limit counters in the CDN's key-value storage expire automatically (typically within 24 hours).
- Edge logs are retained per the CDN provider's standard retention policies.
8. Children's Privacy
The App is not directed to children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect personal information from children. If you believe a child has used the App in a way that resulted in collection of personal information, please contact us and we will take appropriate steps.
9. International Users
The Service is operated using a third-party CDN provider's global edge network and a third-party LLM provider's infrastructure. Information processed by these providers may be handled in the United States or in other countries. By using the App, you understand that information you transmit may be processed in jurisdictions other than your own, subject to the safeguards described in this policy.
10. Your Rights
Depending on where you live (including under the GDPR, UK GDPR, and CCPA/CPRA), you may have the right to access, correct, delete, port, or restrict processing of your personal information, and to object to certain processing. Because the App stores chat history locally and we do not maintain user accounts, you can exercise most of these rights directly:
- Delete chats individually inside the App, or delete the App entirely.
- Unpair a Mac to remove its registration from the relay.
- Rotate or revoke a device secret to invalidate previously paired credentials.
- Contact us using the details below for any request we are able to action server-side.
We do not sell or share your personal information for cross-context behavioral advertising as those terms are defined under the CCPA.
11. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes to the App, our practices, or applicable law. When we make a material change, we will update the "Last updated" date at the top of this page and, where appropriate, provide additional notice through the App or on our website. Continued use of the App after a change takes effect constitutes acceptance of the updated policy.
12. Contact Us
If you have questions about this Privacy Policy, or you would like to exercise a privacy right, contact:
© 2026 RedZen Cloud Solutions. All rights reserved.