Privacy Policy

1. Who We Are

Midas Journal is developed and operated by Nebula Craft Design Ltd (Company No. 17180534), registered in England & Wales at 61 Bridge Street, Kington, HR5 3DJ, United Kingdom. Midas Quant is a product and brand name of Nebula Craft Design Ltd.

For personal data processed in connection with application licensing, optional account identity, subscriptions, and customer support, Nebula Craft Design Ltd acts as the responsible data controller under applicable data protection laws.

2. Local Journal Storage (On-Device)

Your trade journal entries, P/L calculations, risk amounts, execution durations, notes, setup tags, mistake tags, trading profiles, and review notes are stored locally on your device within the iOS app sandbox using SQLite / GRDB.

Your local database is protected by iOS Data Protection under the completeUntilFirstUserAuthentication standard. Nebula Craft Design Ltd does not operate an independent central database of your raw trade records.

3. Private iCloud Sync (CloudKit)

If you enable iCloud sync, your journal records are synchronized across your own Apple devices using Apple CloudKit. This synchronization takes place within your private Apple iCloud container.

Nebula Craft Design Ltd does not have access to your private iCloud container, nor do we operate a secondary cloud copy of your synchronized trade records.

4. Sign in with Apple (Optional)

Signing in with Apple is optional. If you choose to sign in, Apple provides a unique user identifier, and you may choose to share or hide your email address using Apple's private relay service.

Your sign-in identity details are stored locally in the secure iOS Keychain. Your raw Apple user identifier is not transmitted directly to third-party marketing services.

5. In-App Purchases & Entitlements

All purchases and subscriptions are processed directly through Apple's App Store via StoreKit. We utilize RevenueCat solely to validate purchase receipts and manage subscription entitlements.

RevenueCat receives a deterministic pseudonymous customer identifier and transaction metadata necessary to confirm your active entitlement status. RevenueCat does not receive your trade journal content.

6. Account Deletion Infrastructure

When you initiate an account deletion within the app (under Account > Danger Zone > Delete Midas Account), a stateless Cloudflare Worker coordinates the revocation of your Apple authorization tokens and instructs RevenueCat to delete your pseudonymous customer record.

This deletion worker does not process or receive your trade journal content, and does not retain account tokens after the request completes. Standard Cloudflare infrastructure logging applies at the network layer.

7. Trading Routine Notifications

Trading Routine preparation and review reminders are scheduled locally on your device by iOS. We do not maintain a remote notification server or track when you open notification prompts. Lock-screen notifications are designed to avoid exposing sensitive trade numbers.

8. Data Portability (JSON & CSV)

You can export complete JSON backups or CSV files at any time directly under Account > iCloud & Data. Once you export a file outside the iOS app sandbox (e.g. to Files, AirDrop, or email), you are responsible for the storage and security of that external copy.

9. Customer Support

If you contact our support team at hello@midasquant.com, we receive the email address and message contents you provide to respond to your inquiry and resolve technical issues.

10. Data Retention & Account Deletion

• Local Journal: Remains on your device until you manually delete individual trades, clear database records, or delete the Midas Journal app.
• iCloud Container: Remains in your private Apple iCloud account until removed via iCloud settings or app reset.
• Midas Account Deletion: In-app account deletion revokes Apple authorization, deletes the RevenueCat customer mapping, and clears CloudKit account records. Local journal entries remain on device unless explicitly removed by the user.
• App Store Subscriptions:Deleting an in-app account does not automatically cancel an App Store subscription. Subscriptions are billed by Apple and must be cancelled through iOS Settings > Subscriptions.

11. Third-Party Service Processors

Midas Journal integrates with the following third-party infrastructure providers:

• Apple: Operating system sandbox, StoreKit payment processing, CloudKit sync, and Sign in with Apple.
• RevenueCat: Pseudonymous subscription validation and receipt verification.
• Cloudflare: Stateless Account Deletion Worker and static website edge delivery.