Effective date: June 16, 2026. This policy explains how the Reaction Creator Android app collects, processes, stores, and shares information.
Reaction Creator helps you record reaction videos, import video and audio, edit projects, create exports, save media on your device, and share finished media with other apps.
Most media processing happens on your device. The app also uses online services for sign-in, subscriptions, quota enforcement, analytics, crash diagnostics, advertising, privacy choices, app configuration, security, and account deletion.
Reaction Creator is published by Phantom Code.
Support and privacy questions can be sent to reactioncreatorteam@gmail.com.
Reaction Creator is intended for teens and adults who create and edit reaction videos. The app is not directed to children.
Reaction Creator uses Google sign-in and Firebase Authentication. To use account features, the app receives authentication information from Google and Firebase, including your email address, Firebase user ID, and account profile information that Google returns for sign-in, such as display name or profile photo URL.
Firebase assigns a unique user ID to your account. Reaction Creator uses that ID to authorize Firestore and Firebase Functions requests, associate quota and account records with your account, connect your account to RevenueCat subscription status, and attach a shortened diagnostic identifier to Crashlytics reports.
Reaction Creator stores account and quota records in Cloud Firestore. These records can include account status, plan status, daily export quota counters, active quota plan fields, quota reservation details, and account deletion request or cancellation timestamps.
Subscriptions are processed through Google Play Billing and RevenueCat. Reaction Creator does not directly handle your payment card, bank account, or full payment credentials.
Google Play and RevenueCat process purchase history, product identifiers, subscription status, entitlement status, restore results, renewal and expiration information, and related transaction records.
Reaction Creator uses your Firebase user ID as the RevenueCat app user ID. The backend may also send that ID to RevenueCat to verify premium entitlement before applying premium quota behavior.
Deleting your Reaction Creator account does not cancel a Google Play subscription. You must manage or cancel subscriptions in Google Play. Account deletion also does not automatically remove RevenueCat or Google Play purchase records. You may contact reactioncreatorteam@gmail.com to request deletion or removal of associated RevenueCat customer data where supported.
Free accounts may see Google AdMob ads. Premium accounts are intended to use the app without ads.
Rewarded ads are optional actions that grant a stated recording unlock after the reward is earned. Post-export interstitial ads may appear after eligible free recorder exports. They are not payment for an export. If an interstitial is unavailable, ineligible, not ready, or fails, the export flow continues.
Reaction Creator uses Google's User Messaging Platform, also called UMP, to request consent information, show privacy messages where required, and provide ad privacy choices where required. Ads are not requested until UMP reports that ads may be requested.
The Google Mobile Ads SDK may process IP address, ad interactions, diagnostic information, Advertising ID, app set ID, and related device or account identifiers. Whether ads are personalized depends on your region, privacy choices, device settings, and the AdMob account configuration.
Reaction Creator uses Firebase Analytics to understand app usage and improve app reliability and product flows.
Custom analytics events can include sign-in success or failure, media source and layout selections, recording attempts and outcomes, take and preview outcomes, export results, quota counts or limits, paywall choices, purchase and restore outcomes, ad outcomes, and audio setup choices.
Custom event parameters can include plan, layout, source type, duration, render time, watermark or cache flags, quota counts, ad placement, selected plan, purchase path, and sanitized error type. The app is not designed to send media content, filenames, raw private file paths, email address, or full Firebase user ID as custom Firebase Analytics event parameters.
Firebase Analytics also automatically processes app instance and device information, app lifecycle and session activity, in-app purchase or subscription events, Advertising ID when available, and approximate location derived from network signals. Google Analytics and Firebase console settings can affect how this information is used and retained.
Reaction Creator uses Firebase Crashlytics to diagnose crashes and non-fatal errors. Crashlytics may process stack traces, error information, relevant app state, breadcrumbs, device model, operating system, app version, session information, Crashlytics installation identifiers, diagnostic logs, and custom keys.
Reaction Creator sends a short hash derived from the Firebase user ID instead of sending the full Firebase user ID to Crashlytics. Developer-supplied diagnostic strings are filtered to reduce recognizable email addresses, named identifiers, Firestore user paths, private local paths, and file or content URIs. Stack frames remain in reports because they are needed to diagnose errors.
Reaction Creator asks for camera permission for live preview and reaction recording. It asks for microphone permission when microphone audio will be recorded.
The app can process live camera preview, microphone audio, recorded reaction videos, imported video and audio, Creator Library videos and thumbnails, Editor Mode projects, text, templates, My Sounds, rendered previews, temporary files, thumbnails, and exports.
The reviewed app code processes these media files on the device using Android media APIs, local FFmpeg processing, Media3, and on-device ML Kit selfie segmentation. No app-owned media upload path was found in the reviewed code.
Analytics can receive media type, audio mode, duration, layout, and render timing. Analytics is not intended to receive media content itself.
Reaction Creator stores imported and recorded media, recorder exports and thumbnails, Creator Library media and metadata, Editor Mode imports, projects, autosaves, My Sounds, text templates, timeline thumbnails, export files, temporary render files, settings, onboarding state, tools order, local export metadata, audio choices, ad unlock state, and quota recovery state in app storage.
Recorder exports remain app-private when saved to the in-app Exports library. If you choose Download, the app copies the export to public Downloads, where it can be visible to other media or file apps.
Editor Mode exports are copied to public Movies storage when the export finishes. The current public location label is Movies/Reaction Creator exports.
Public Gallery, Movies, and Downloads files are outside app-private storage. They are not removed by uninstalling Reaction Creator or deleting your account. Remove those files using your device Gallery or Files app.
When you choose Share, Reaction Creator uses Android FileProvider to give the app you select temporary read access to the export through a content:// URI. The receiving app controls its own copy after you share an export.
Android backup is enabled. Known media, export, thumbnail, Creator Library, Editor Mode import, My Sounds, and project directories are excluded from backup and device transfer. SharedPreferences are not explicitly excluded, so settings and metadata may be included in Android backup or device transfer.
You can request account deletion in the app after signing in. When you request deletion, your Firestore account document is marked as pending deletion, the app signs you out, and a pending deletion period of up to 24 hours begins.
If you sign in before that period expires, the request is cancelled and the account remains active. After the pending deletion period expires, a scheduled backend process is designed to delete or anonymize the Firebase Authentication account and associated Firestore account data according to the implemented deletion process.
The backend process runs on a schedule, so final processing can occur after the pending period has ended. A successful deletion request means deletion has been scheduled; it does not mean permanent deletion has already finished.
This account deletion process does not automatically remove RevenueCat or Google Play customer, purchase, or subscription records; historical Firebase Analytics or Crashlytics data; Cloud Functions, Cloud Logging, or other operational logs; app-private files still on your device; public Gallery, Movies, or Downloads exports; copies shared to another app; or backend records outside the Firebase user subtree unless they are added to the deletion process.
Retention depends on where the data is stored. Firebase Authentication and associated Firestore account data are retained while the account is active and are intended to be deleted or anonymized after the pending deletion period and scheduled backend deletion process complete.
Google Play purchase records, RevenueCat subscription or customer records, Firebase Analytics aggregate data, Crashlytics diagnostic records, AdMob and UMP records, Cloud Logging and security logs, and user-exported or shared files may remain outside Reaction Creator's direct deletion process according to provider retention rules or user control.
App-private files remain on the device until deleted, cleared, or the app is uninstalled. Public exports remain until the device user deletes them. Shared copies remain under the receiving app's control. Android backups may retain non-excluded app state according to your device and Google backup settings.
Reaction Creator does not request Android location or contacts permission. No precise-location or contacts API usage was found in the reviewed app code. Firebase Analytics and AdMob may derive approximate location from network signals such as IP address.
Reaction Creator does not directly process payment card or bank details. Google Play and RevenueCat handle subscription purchase processing.
For privacy questions or deletion requests that are not completed through the in-app flow, contact reactioncreatorteam@gmail.com.