Ripplemuse Privacy Policy
Effective: November 10, 2026
CRAVEWORKS LLC publishes Ripplemuse (package name: com.ripplemuse.motionwave). This document explains which information the App touches, why each category is needed, and how it is guarded. It applies to the App as distributed through Google Play. Installing the App, or continuing to use it after a revision, means the practices below are accepted. A user who does not accept them can uninstall the App, and the relationship ends there.
1. Information the App Works With
The App performs most of its work locally. Only the categories listed in this section are handled off the device or retained for a purpose beyond the immediate task.
Categories the App deliberately avoids:
- No profile is built. No screen requests a legal name, a home address, or a phone number. A guest seat is assembled on the handset at first launch, and creation can begin without any form.
- No output archive. When a job finishes, the App does not keep the result on our servers, and no part of the result is passed to another party.
- No personal identification. The App does not seek or store details that would tie a handset to a named person — no name, no residence, no personal mailbox.
Categories the App does handle:
- A device signature. The backend needs to recognise a handset without learning who owns it. The App derives a signature locally by hashing ANDROID_ID with the package name through MD5. The digest cannot be reversed into an owner. If ANDROID_ID is unavailable, a random UUID kept in local storage supplies the value. Firebase adds an anonymous installation token; for installs classified as direct Meta campaigns, the Facebook SDK adds a second anonymous mark, described in Section 7.
- A guest seat. The seat is created on first launch and anchored to the signature. It carries no password, no login, and no credentials; its only role is to preserve work history and similar conveniences.
- Device and locale facts. Model, Android release, screen size, language, time zone, and similar readings that keep the interface stable across hardware.
- Feature activity. A tally of screens opened and tools used, kept to show where repairs are needed and which features are worth maintaining.
- The Google Advertising ID (GAID). The App may read GAID for attribution. If "Limit Ad Tracking" or "Opt out of Ads Personalization" is enabled, the read stops; the identifier can be reset in system settings at any time.
- Audio from the in-app recorder. While the recorder sheet is open, microphone sound from that take is sent to us. Capture is confined to the take and serves one end: custom audio, including background music, for the video being produced. Section 3 gives the details.
- A push token. The token lets a service message — a finished-generation notice, for instance — find the handset. Alerts can be switched off, and nothing essential depends on them.
2. Material You Supply
Certain creation routes need source material: a photo, a clip, or a video with sound. Files enter through the system photo picker or the system document picker, and only the item selected becomes reachable by the App. Handling follows three rules:
- Role. The file is the raw input for the computation; the finished image or clip is derived from it. It reaches our servers through an encrypted channel.
- Short stay. The upload and the result built from it remain on our servers only while the job is active. When the job closes, both are removed.
- No leftovers. Nothing supplied survives the job, and no identifying detail travels with it.
3. Voice Takes Recorded in the App
An optional recorder sits inside the creation flow. Each press produces one take, capped at five seconds, and the take has a single destination: custom audio, such as background music, for an AI video.
- Permission arrives with the feature. The microphone prompt appears at runtime, when the recorder opens. The user may refuse at that point or withdraw the permission later in system settings.
- What limits a take. Recording begins with a press; the App must be in the foreground; one take is the full extent of collection. Background listening is not part of the design.
- Where it goes. Into the sound layer of the video being built, and nowhere else.
- Transport. Once accepted, the file departs over an encrypted channel and is consumed by the generation.
- Lifetime. Any server-side copy lasts only while processing runs and is deleted when processing finishes.
- No voice analytics. Takes do not pass through speech recognition, speaker separation, or comparable biometric analysis.
- While a take is open. The take sits in a local cache. Clearing the App's data in system settings removes it.
4. Face Signals in Uploaded Media
If a photo or clip the user uploads contains a human face, the App derives a limited set of facial measurements to power its AI image and video tools:
- Measurements taken. Key points around the eyes, nose, and mouth, along with ratios such as face outline and scale — and only from media the user chose to upload.
- What they support. Personalized, higher-quality imagery; more stable visual effects on the subject; a result that stays closer to the original.
- Storage window. Processing happens on encrypted servers. After the result is delivered, the measurements have served their purpose and are erased, normally inside 24 hours.
- Who receives them. No outside party; facial data is never shared.
5. Why the App Processes Data
Each category above serves one or more of the following objectives:
- Delivering the service. Keeping the App's features running and maintained for the people who opened it.
- Sending service notices. Job status and release announcements.
- Improving the product. Activity records point to defects, rough edges, and features worth building next.
- Protecting the platform. Detecting fraud, abuse, and unauthorized access.
- Measuring acquisition. Learning where installs came from and how campaigns performed.
No sale, rental, or release of your information to third parties for their own marketing takes place.
6. Purchases and Membership Records
Payments made inside the App produce a small set of records:
- Order evidence. Purchase tokens, product identifiers, order references, and subscription state are retained so that a purchase can be honoured and restored.
- Payment details stay with Google. Charges are processed by Google Play Billing. Card numbers and payment methods never enter our systems; Google's privacy policy governs that layer.
- Membership state. Whether a plan is active, expired, or cancelled is tracked so member features switch on and off at the correct moment.
- Retention. Order records remain for as long as fulfilment duties, statutes, and dispute handling require.
7. External Processors and SDKs
The App calls on the following outside services. Each one has its own privacy notice, and each is worth reading.
- Google Play Services. Handles distribution, in-app purchases, and subscription administration; Google's own privacy policy covers what Google gathers there.
- Google Play Billing. The payment rail for every purchase and membership; tokens and transaction records travel through it.
- Firebase Analytics. Produces anonymous usage figures and interaction patterns, and may collect device details, events, and anonymous markers. See Firebase Privacy Information.
- Firebase Installations. Mints the unique anonymous installation label the App uses.
- Firebase Cloud Messaging (FCM). The transport under the App's own push channel for generation status and service notices; alerts can be silenced in device settings. See Firebase Privacy Information.
- Google Play Install Referrer. Tells the App how it arrived; used for attribution and measurement only.
- Google Advertising ID. Read solely for attribution; once ad tracking is limited, it is not read.
- Facebook SDK (Meta). Serves one purpose: counting installs that come from our direct Meta (Facebook) campaigns. The SDK ships dormant — no initialization, no reporting — unless an install is classified as direct-campaign traffic. In that case it sends Meta the install/activation event and an anonymous device mark; our backend receives the same mark and reconciles it with Meta's server-side Conversions API. Purchases use the server route only. There is no Facebook login, sharing, or deep-link integration. Details: Meta Privacy Policy.
8. Campaign Attribution and Measurement
Marketing analysis may draw on the following:
- Install-source records. Referrer payloads, advertising identifiers, and anonymous device fingerprints (model, maker, resolution, language, time zone, carrier, network type) kept for attribution.
- Direct Meta measurement. If an install is classified as direct Meta campaign traffic, the Facebook SDK may wake and pass Meta the install/activation event and an anonymous device mark for conversion measurement; otherwise it stays asleep.
- Analytics figures. Anonymous usage counts, feature-interaction totals, and performance numbers reported through Firebase Analytics.
- IP address. An IP may be seen in passing for attribution; linking it to a person is not part of the task.
- User control. "Opt out of Ads Personalization" lives under Settings > Google > Ads, and the advertising ID can be reset at any time.
9. No Commercial Sale of Data
We do not sell personal information, trade it, or hand it to third parties for their own marketing. Anonymized, aggregated figures may reach the providers named in Section 7, but only for the purposes described in this policy. Disclosure can also occur when the law requires it or when defending our rights makes it necessary.
10. Security Controls
The App and its backend apply several layers of protection:
- HTTPS encryption for every leg of the journey;
- encrypted storage on the server side;
- access checks and monitoring at the entry points.
No system is invulnerable. Reasonable safeguards are maintained, but data in transit always carries some residual risk.
11. How Long Information Lives
Each category has its own retention horizon:
- Uploads, voice takes, facial signals: deleted when processing ends, normally inside 24 hours.
- Device signature and session records: retained for as long as the App stays installed.
- Order records: retained as long as statutes and dispute handling demand.
- Analytics: kept only in anonymized, aggregated form.
12. Minors
Ripplemuse is not intended for children under 13, and we do not knowingly gather their information. Anyone who believes a child's data has reached us should write to the address below; removal will begin without delay.
13. Your Rights and Controls
The following controls remain with the user:
- Inspect or correct. Ask for a summary of what we hold and request changes or deletion.
- Delete. A single message to the address below begins removal. Finished images, videos, and personal data are not held in long-term custody, so there is usually little to delete; most information stays on the device.
- Limit tracking. Disable ad tracking in system settings and reset the advertising ID whenever desired.
- Notifications. Every alert follows the on/off choice already made.
- Subscriptions. Memberships are managed or cancelled through the Google Play Store account.
- Uninstall. Removing the App stops collection and takes local storage with it.
14. Processing Abroad
Our servers may sit outside the user's country. Wherever processing happens, appropriate safeguards travel with the data.
15. Revisions
Changes to the App, its features, or applicable law may prompt a revision of this policy; the date at the top will change accordingly. Checking it from time to time keeps the user current.
16. Publisher Contact Details
Questions or objections about this policy, or about how data is handled, may be addressed to:
Registered entity: CRAVEWORKS LLC
Registered office: 7488 N Adobe Ln, Tooele - 84074-8965, United States
Email: hattielewis197179@gmail.com