Privacy Policy — Morph AI
Effective date: October 5, 2026
This Privacy Policy applies to all mobile applications, software, and services (collectively referred to as "Applications") developed and published by Ruby Digital Studio (including SonicTTS, MorphAI, and other apps). ("we", "us", or "our").
1. General Privacy Principles
Ruby Digital Studio is committed to protecting user privacy. Our Applications are designed with a Privacy-First architecture, prioritizing local data processing and user autonomy.
2. Information Collection and Storage
No Central Data Collection: Unless explicitly stated in a specific Application, our Applications do not collect, transmit, store, or sell your personal data, chat histories, prompts, or generated media on external servers.
No Tracking/SDKs: We do not include third-party analytics, advertising, or tracking SDKs. The only exception is in-app purchase processing described in Section 2a.
2a. In-App Purchases (Sonic Morph)
Sonic Morph uses RevenueCat (revenuecat.com) to process in-app purchases and subscriptions made through Google Play. To provide this, the app sends to RevenueCat: (a) your purchase history (purchased products and entitlement status), and (b) an identifier derived from your device (a one-way hash of the device identifier combined with the app package name; the raw identifier is not sent), along with standard technical information needed to process these requests.
This data is used only to unlock paid features, restore purchases, determine the length of the free usage period, and prevent abuse. It is transmitted over encrypted connections and is not sold to third parties. RevenueCat processes this data on our behalf; see RevenueCat's privacy policy for details.
The app does not collect your location, contacts, files, or generated audio. All audio generation happens locally on your device.
3. Device Permissions
Our Applications may request local device permissions (such as access to storage) solely to perform core features requested by the user (e.g., reading model files or exporting backups). These permissions process data strictly inside your device's isolated environment.
4. User-Configured External Services
If an Application allows you to connect to custom remote endpoints or third-party APIs (e.g., self-hosted servers or external AI services), those interactions occur directly between your device and the configured server. Ruby Digital Studio has no access to these data streams.
5. Changes to This Policy
We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated effective date.
6. Contact Us
If you have any questions regarding privacy across any of our Applications, please contact us: