Privacy Policy
This page explains the main categories of information RecapKit processes and how local and cloud workflows differ.
Account information
RecapKit uses Google sign-in and may store account identifiers, email address, package entitlement, session records, referral information, and security-related device or risk signals needed to operate and protect the service.
Local browser processing
Compatible Starter Plan video rendering and browser tools run on the user's device. Files selected for a local workflow are not automatically cloud jobs unless the user explicitly starts a cloud-supported action.
Cloud processing
When an eligible user starts Cloud Processing, RecapKit may temporarily store uploaded input, processing artifacts, job metadata, status, and final output using its backend storage and worker systems. Temporary cleanup policies may remove these files after the applicable retention period.
AI keys
RecapKit uses a bring-your-own-key model for Gemini features. Browser keys and eligible encrypted background keys follow different workflows. RecapKit does not display a saved background key again after storage, and revoked keys should no longer be usable.
Payments and support
Payment-slip images and transaction information may be processed for manual package approval, duplicate protection, recovery, and administrative records. Telegram may be used for payment or background-job notifications when the user enables the relevant flow.
Your choices
- Use Local Browser processing when available.
- Revoke a saved background AI key.
- Download completed cloud output before temporary retention ends.
- Log out to end the active browser session.
RecapKit