Privacy policy

1. Information we collect

• Account information: Google account identifier, email address, name, and profile information returned during sign-in. Account records include your username, account creation time, and access role. Profile pictures may be displayed from Google-hosted URLs. Existing password accounts may retain a password hash; Google passwords are never received or stored.
• Google authorization data: OAuth access tokens, refresh tokens, granted scopes, and token expiry times. These let the server access only the Google and YouTube features you authorize.
• Connected YouTube information: authorized channel IDs, channel names and thumbnails, video IDs and metadata, titles, descriptions, tags, publishing dates, visibility and scheduling status, and available views, likes, and comments counts. Analytics can include watch time, average view duration, average percentage viewed, and subscribers gained. We do not request access to Gmail, Google Contacts, or Google Drive.
• Content and settings you provide: video links, uploaded video and audio, subtitles and transcripts, clip selections, generated media and thumbnails, captions, watermarks, publishing drafts, channel preferences, and automatic workflow settings.
• Service and security information: job history, upload results, errors, subscription and usage records, session cookies, and limited request information such as IP address, request path, browser or device information, and access times in server logs.

2. How and why we use your data

We use account information to sign you in and keep your projects separate from other users. We process your media, transcripts, and settings to select moments, render videos, generate captions or metadata, provide previews and downloads, and run workflows you enable. Channel information identifies the destination for your uploads and displays your channel and video library. Performance data provides the analytics you request. Usage records enforce plan allowances and support service operation, troubleshooting, and abuse prevention.

Google permissions are used for these specific functions:

We do not sell Google user data, use it for advertising or credit decisions, or use it to develop or train generalized artificial intelligence or machine learning models. ProClipper' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3. Sharing and third-party services

• Google and YouTube: sign-in and authorization requests go to Google. When you publish, video files and the metadata, visibility, and scheduling settings you choose are sent to YouTube. YouTube controls who can see those videos according to your settings. The service uses YouTube API Services; Google's handling of information is described in the Google Privacy Policy.
• Hosting: the app's cloud server and storage run on Amazon Web Services. Infrastructure providers process information as needed to host and operate the app.
• AI features: when you use model-based moment selection, generated titles or metadata, or enable workflows with those features, relevant transcripts (which may include a full source transcript), titles, descriptions, and your instructions may be sent to configured providers such as Google Gemini, Anthropic Claude, or Groq. Local or rule-based processing is also available for supported features. OAuth tokens are used for Google API authorization and are not included in these AI prompts. Provider processing and retention depend on the provider and the operator's service settings. Do not submit sensitive information in media or prompts you do not want processed by an external provider.
• Other requested features: source URLs, media search queries, or narration text may be shared with the video, image, or speech services needed for the feature you use. Your browser may request fonts, thumbnails, or profile pictures from their hosting services, exposing standard connection information such as your IP address.
• Support, security, and legal requests: the operator may access information to resolve a support request you authorize, investigate security incidents or abuse, or meet a legal obligation. We do not otherwise disclose Google user data for unrelated purposes.

4. Storage and protection

Account, channel authorization, and publishing records are stored in the server's application database. Media, transcripts, settings, and job files are stored on server storage. Production web and Google API connections use HTTPS. Signed, HTTP-only session cookies protect sign-in, and authenticated routes check account ownership before serving private projects or media. Administrative access is restricted to operator accounts. OAuth credentials stay on the server and are not returned by account-information APIs.

These safeguards reduce unauthorized access; no internet service can guarantee absolute security. We do not claim that every stored file or database field is separately encrypted.

5. Retention and deletion

Clip-job files normally expire six hours after the job finishes. You can choose 24 hours, three days, seven days, or "Keep until I delete" for supported jobs. Video Studio projects and scheduled or active uploads may be kept longer so the requested work can finish. Abandoned or incomplete uploads are handled by separate cleanup rules. The applicable expiry is shown in the app; you can delete eligible finished projects earlier.

Account information, channel authorizations, publishing records, preferences, usage records, and job-history summaries can remain after media files expire, for as long as needed to operate your account and the features you use. Analytics caches are refreshed when you request updated information. Server logs are rotated. We do not promise that deleting a media file also deletes every account or publishing record.

To request deletion of your account and associated stored Google user data, email 2015n1546@gmail.com from the email associated with your account and identify the account or channel. We may verify that the request comes from the account owner before removing data. We will process verified deletion requests within 30 days, except records we must retain for legal or security reasons, which will be limited to that purpose. Deleting local data does not delete videos already published to YouTube; manage or delete those videos in YouTube Studio.

6. Your choices and revoking access

You can disconnect individual channels in the app's account settings. This removes the locally stored authorization for that channel. Disconnecting the last channel also attempts to revoke its Google token. With multiple channels, unlinking one does not necessarily revoke the shared Google grant.

You can revoke ProClipper' access at any time through Google Account third-party connections (also available through Google security permissions). Revoking access prevents further authorized Google API requests but does not itself erase your ProClipper account or previously saved projects. Contact us to request deletion of retained information. You may need to sign in and authorize again to use connected-channel features.

7. Cookies and device storage

The website uses session and OAuth security cookies to keep you signed in and protect authorization requests. "Remember me" changes session persistence, subject to the app's consent-session expiry. The website and Android app may save preferences and service or download state locally. You can clear cookies or app storage through your browser or device settings; doing so may sign you out. The app does not use Google user data for advertising cookies or targeted advertising.

8. Children

ProClipper is intended for video creators and is not directed to children under 13. If you believe a child has supplied personal information to the service, contact us so we can investigate and remove it.

9. Changes and contact

We will update this page and its date when our practices change. If we introduce a new use of Google user data, we will provide the required notice and obtain additional consent before that use. For privacy questions or requests, contact 2015n1546@gmail.com.