LEGAL

Privacy Policy

Last updated: September 22, 2026

Your source videos, camera recordings and editing projects are processed locally on your Android device. ReactOX does not upload their content to the ReactOX backend.

1. Who is responsible

The data controller and operator of ReactOX is Damian Cholewa, based in Poland. The public creator and developer pseudonym is nahdayoff. Privacy questions and requests can be sent to support@reactox.app.

2. Local media and permissions

ReactOX requests camera and microphone access only for recording a reaction. A source video is selected through Android's system media picker. Source clips, camera recordings, drafts, thumbnails and exported videos are stored locally in app-private storage or in a user-selected/shared location.

3. Backend information

To prevent abuse and manage ReactOX Pro, the service may process:

The backend does not need your name, source video, reaction recording or exported video.

4. Advertising and consent

The Free plan uses Google AdMob. Depending on your region and consent choices, Google's Mobile Ads SDK may process IP address, general location inferred from IP, interactions, diagnostics, advertising identifiers and other device or account identifiers for advertising, analytics and fraud prevention. ReactOX uses Google's User Messaging Platform to request and manage choices where required. A privacy-options entry is provided in the app where required.

See How Google uses information for advertising and the Google Privacy Policy.

5. Purchases and integrity

Subscriptions are processed by Google Play. ReactOX receives purchase status and tokens needed to verify and provide Pro access but does not receive your full payment-card details. Google Play subscription notifications are delivered through Google Cloud Pub/Sub so the backend can process renewals, expirations and revoked access. The app may store a time-limited access authorization locally to reduce repeated verification requests. Google Play Integrity may assess whether the app, installation and device interaction are genuine and may return risk or integrity verdicts used for fraud prevention.

6. Infrastructure providers

Cloudflare provides the ReactOX API, database and website. Cloudflare may process network information such as IP address, request metadata, security events and limited service logs to deliver and protect the service. See the Cloudflare Privacy Policy.

7. Purposes and legal grounds

8. Retention

Local projects remain until you delete them, clear app storage or uninstall the app. Trash follows the retention period shown in the app. Subscription records are retained while needed to provide access, process changes and meet legal or accounting obligations. Security and integrity information is retained only as long as needed to prevent abuse and protect the service. Support correspondence is retained only as long as needed to resolve and document the request.

9. Choices and rights

You can delete local clips in ReactOX, clear all app storage through Android settings, withdraw advertising consent through Settings → About & Legal → Privacy choices where available, manage advertising identifiers in Android settings and manage subscriptions through Google Play. Depending on your location, you may request access, correction, deletion, restriction or objection regarding personal data processed by ReactOX by contacting the address above.

10. Age and children

ReactOX is intended for users aged 18 and over. It is not designed or marketed to children, and children are not included in the declared target audience for the initial Google Play release. If the target audience changes, the app, advertising treatment and this policy will be updated before the change takes effect.

11. Security and changes

ReactOX uses encrypted HTTPS connections, app-private Android storage, scoped sharing, server-side purchase checks and restricted access to production credentials. No system is completely secure. Material changes to this policy will be reflected by updating the date above and, where required, by an in-app notice or consent flow.