Last updated: October 24, 2026
AORYN is operated by Brian Behlke, an independent business operator in Germany.
Postal address: Altstädter Straße 15, 75175 Pforzheim, Germany
Privacy contact: [email protected]
This notice explains how information is handled when you use the AORYN iOS app, request or restore an in-app purchase, contact us, or visit this privacy-policy page.
AORYN includes yoga, qigong, breathing and meditation tools, personal tools and practice sequences, a journal with optional photos, settings and practice history. Under the audited design of version 1.6.1, personal practice entries, app-managed photo copies, personal tools, practice sequences, settings and histories are stored locally on your device. AORYN does not automatically send the contents of these entries to our servers or to RevenueCat.
You decide what to enter. Entries may include information about health or personal experiences. AORYN is not a medical or diagnostic service. We generally cannot read or retrieve information that stays only on your device.
When you explicitly export or share information, a copy may be handled by the application or destination you choose. Photos may be referenced in an export rather than embedded in it. Your device or cloud backup settings may also create backups outside AORYN's control. Deleting the app (rather than offloading it) normally removes the app-managed local data from that device, but does not necessarily remove earlier exports, original photos or backups.
These on-device features are provided at your request. As long as information remains solely on your device without being received by us, it is not collected by us for these functions. Any processing by us for purchase, contact or privacy-request purposes is explained below.
AORYN uses Apple's in-app purchase system and RevenueCat, Inc. to show available purchase options, process and verify access to AORYN Full Access, and restore purchases. RevenueCat also provides technical purchase-management functions and purchase-related reports.
For a new user who only uses free tools and has no locally recognised purchase history, the reviewed Build 40 implementation is designed not to initialise RevenueCat or request purchase data merely because the app or its settings are opened. When you expressly ask to see purchase options, restore purchases or check access, the app may initialise RevenueCat and contact its service. For users with a locally recognised prior purchase, the app may check existing entitlements automatically so that paid access continues to work. A locally stored purchase marker does not, by itself, grant paid access. Earlier app versions may initialise RevenueCat on app launch, including when only free features are used, and may already have created a RevenueCat identifier for users who did not make a purchase.
RevenueCat normally creates a random App User ID if we do not supply a separate identifier. The identifier is called “anonymous” in RevenueCat's technical documentation but is treated here as pseudonymous: it may be associated with purchase or technical information. We do not give RevenueCat your name or email address as your app account identifier.
Depending on your use of purchase functions, RevenueCat may process:
Why we process this information and the corresponding legal bases: