Privacy Policy

1. Scope and operator

This policy covers Clipripper, its related support, and these documentation pages. AndWhatNot Studio operates the application and is responsible for its processing described here. Contact: admin@andwhatnotstudio.com. Discord and server administrators have separate responsibilities for their platforms, communities, and copies of content.

2. Information processed and its sources

Information comes from Discord messages and reactions, source clip services, publishing providers, and the Summerizer reward service.

• Submitted clip URLs, message and channel identifiers, the submitter’s Discord identifier and display name, reaction counts, approving members’ identifiers and relevant roles, and approval timestamps.
• Source titles, descriptions, durations, downloaded videos and audio, reformatted versions and compilation files. Media can contain people’s voices, likenesses, or usernames.
• Queue and processing status, publication identifiers and public links, platform/channel identifiers, performance metrics, errors, and scheduling records.
• For rewards: the submitter’s Discord identifier, credit amount, source-message reference, reason, grant status, attempts, and returned balance. The bot may cache server member and role information to check approval permissions.

3. How information is used

We use this information to detect supported links, check approval roles, prevent duplicates, download and prepare authorized media, publish clips, track delivery and performance, select compilation candidates, grant Summerizer rewards, and operate or troubleshoot the workflow.

We do not sell personal information, disclose Discord data to advertisers or data brokers, or use Discord message content to train our own AI models.

4. Recipients and service providers

• Discord: submissions, reactions, approval and progress messages. Other members may see these according to channel permissions.
• Twitch and Kick: requests to retrieve the submitted clips and their metadata.
• Buffer, YouTube, and TikTok: media delivery URLs, video, titles, captions, and publication details needed to publish and manage posts. Captions may identify the submitter by Discord display name. Published media is available to the audience of the destination account and may be public.
• Summerizer: the submitter’s Discord identifier, approved-message reference, reward amount, and reason, used to grant credits and prevent duplicate grants. See Summerizer’s Privacy Policy.

Clipripper’s current publishing workflow does not send clips to an AI model. The separate Summerizer service has its own AI features and data practices.

Authorized operators and hosting or infrastructure providers may access information needed to run, secure, and support the application. Information may also be disclosed where required by law or necessary to investigate abuse and protect rights. External services apply their own terms and data controls.

5. Storage, retention, and deletion

Clipripper stores submission and approval records, downloaded and processed media, publications, metrics, compilation records, and reward bookkeeping locally. These support publishing, retries, compilations, reward reconciliation, and complaints. There is currently no scheduled automatic deletion of these underlying records or media files; they remain until manually removed.

Temporary delivery links normally expire after 14 days. Expiry removes access through that link; it does not delete the underlying file, database record, or published post. Published copies remain with Buffer, destination platforms, viewers, and account operators under their own controls and policies.

Support correspondence and operational records may be retained to resolve requests, investigate failures or abuse, and meet legal obligations. We assess deletion requests against these purposes and any applicable retention requirements. Existing backups and provider-held records may require separate deletion or expiry; we do not promise immediate removal of copies outside our control.

6. Legal bases

Where European or UK data-protection law applies, we rely on performance of a contract for features a user requests; legitimate interests in operating the disclosed service, protecting the community, and maintaining reliability, balanced against affected people’s rights; legal obligations where applicable; and consent where specifically requested and required.

Processing of messages written by other members is not justified merely because another person submits a command. Server administrators must provide appropriate notice and configure the application on a valid basis. You may contact us to object to processing or ask about the basis that applies to your information.

7. Your choices and rights

Do not submit a clip if you do not want it considered for the described publication workflow. To cancel an accepted item, request removal, or object to attribution, contact admin@andwhatnotstudio.com promptly with the relevant links. Deleting the original message or reaction does not automatically withdraw a queued job or a public post. We cannot guarantee removal of copies saved or republished by others.

Depending on your location and the circumstances, you may request access, correction, deletion, restriction, or portability, object to processing, withdraw consent where processing relies on it, or complain to a data-protection authority. Send requests to admin@andwhatnotstudio.com, identifying the bot, your Discord user ID, and the relevant message, channel, clip, or stored fact. We may need reasonable verification; do not send passwords or account tokens.

8. Security and international processing

We use restricted service credentials and access controls to protect the service. No online system can guarantee complete security. Discord, service providers, and infrastructure may process information outside your country. Where data-protection law requires safeguards for international transfers, the relevant processing must use a lawful transfer mechanism. Contact us for information about the arrangements applicable to your data.

9. Documentation website

These documentation pages do not set tracking cookies, load analytics scripts, or require a login. The web server may log technical request information such as IP address, requested page, browser information, and time for delivery, security, and troubleshooting. Following an external link brings you under that destination’s own policies.

10. Children

The application is not directed to children under 13 or anyone below Discord’s minimum age in their country. Contact us if you believe a child’s information has been processed inappropriately.

11. Updates and contact

We may update this policy when features, data practices, or applicable requirements change. The date above identifies this version. Material changes will be communicated through an appropriate service channel where practical. Questions, requests, and complaints: admin@andwhatnotstudio.com.