Privacy Policy

Effective date: 14 July 2026

We store basic Google identity information, encrypted personal integration keys, source links, job metadata, cloud project identifiers, result links, rights declarations, audit records, copyright reports, counter notices, and enforcement records as needed to provide and protect the service.

We do not receive or store your Google password. Each user's OpusClip key is encrypted at rest and isolated by user account. It is not displayed in full after saving and is sent only to OpusClip when processing or checking that user's jobs. Remoxus does not use a site-wide OpusClip key.

Cloud video processing

When you submit a clip job, the source URL, job preferences, and related technical information are sent using the personal provider account you connected. The provider may import, copy, transcribe, analyze, reframe, caption, render, and temporarily store the video and generated output under its own terms and privacy policy. The provider may process data in another country.

Remoxus stores cloud project IDs, limited provider responses, the last four characters of the processing key used for a job record, and preview or export URLs. The full API key is not written into the job record or audit log. Generated media may remain hosted by the provider and may expire according to that provider's retention rules.

Billing and payment records

Remoxus does not receive your OpusClip provider billing details. OpusClip usage, credits, invoices, and subscription management occur directly between you and OpusClip. A verification request may be sent when you test a key.

For Remoxus Premium or VIP purchases, we obtain a USD-to-IDR reference rate from an external exchange-rate data provider, then send the plan name, IDR checkout amount, payment reference, return URL, notification URL, and basic buyer identity to iPaymu. We store the USD plan price, the exchange rate and rate date used, the IDR amount, discount, coupon, status, provider session or transaction identifiers, and limited callback records for subscription activation, support, accounting, fraud prevention, and dispute handling. Card or bank credentials are entered on the payment provider page and are not stored by Remoxus Clipper.

Security and legal records

For fraud prevention and legal records, we store a keyed hash of the submitting IP address rather than the raw IP in rights confirmations and copyright forms. We may store a browser user-agent with job consent records.

Copyright reports and counter notices may contain names, contact details, signatures, and legal statements. These may be shared with the affected user or relevant parties when reasonably necessary to resolve a complaint, subject to applicable law and safety considerations.

Administrators should define retention periods, backups, deletion procedures, access controls, vendor agreements, and cross-border processing before production use. Users may contact the administrator to request access or deletion where applicable, but legal and security records may be retained when required.