Privacy Policy

Streamsnip ("we," "our," or "us") is committed to protecting your privacy and ensuring the security of your personal information. This comprehensive Privacy Policy explains in detail how we collect, use, disclose, and safeguard your information when you use our innovative stream clipping service.

We understand that privacy is a fundamental right, and we've designed our service with privacy-by-design principles at its core. By choosing to use Streamsnip, you acknowledge that you have read, understood, and agree to be bound by this Privacy Policy and our data handling practices as described herein. If you do not agree with any part of this policy, please discontinue use of our service immediately.

1. Google User Data Collection and Use

1.1 What Google User Data We Collect

When you connect your YouTube channel to Streamsnip, we collect only the minimum necessary Google user data required to provide our service. This includes your public YouTube channel identifier, which serves as the primary key for associating your streams with your Streamsnip account. We also access public stream metadata, including stream titles, descriptions, and timestamps, which are essential for creating accurate clips at the moments you specify.

Additionally, we retrieve public video information for streams you choose to clip. This data is limited to publicly available information that any YouTube user could access through the platform. We do not, and cannot, access any private user data, private videos, unlisted content (unless explicitly shared with us), or any personal information beyond what is publicly displayed on your YouTube channel.

1.2 How We Use Google User Data

Our use of Google user data is strictly limited to providing and improving the Streamsnip service functionality. When you request a clip, we use the stream timestamp data to identify the exact moment in your stream and create a clip reference. This process involves accessing the public stream data to verify the clip boundaries and ensure the clip is created accurately according to your specifications.

We also use this data to provide you with clip management capabilities, allowing you to view all your created clips, edit their descriptions, and organize them effectively. The Google user data enables us to maintain the connection between your clips and their source streams, ensuring you can always trace a clip back to its original broadcast. All uses of Google user data are directly related to features you've explicitly requested by using our service.

1.3 Prohibited Uses of Google User Data

We maintain a strict policy against using Google user data for any purpose beyond providing the core Streamsnip functionality. We will never use your Google user data for targeted advertising, behavioral profiling, or any form of user tracking unrelated to our service. We do not sell, rent, or trade your Google user data to any third parties, including data brokers, information resellers, or marketing companies.

Furthermore, we do not use Google user data for determining credit-worthiness, lending decisions, or any financial assessments. We do not create user profiles for advertising purposes, nor do we engage in any form of personalized, retargeted, or interest-based advertising using your data. We do not build databases with your Google user data for purposes other than providing the Streamsnip service, and we do not use your data to train artificial intelligence models or machine learning systems beyond what is necessary for improving our clip creation algorithms.

1.4 Google User Data Sharing and Disclosure

We maintain the highest standards of data protection when it comes to Google user data. We do not transfer, share, or disclose your Google user data to third parties except in very specific and limited circumstances. When you explicitly configure Discord webhooks for clip notifications, we share only the minimum clip information necessary to send notifications to your specified Discord channels. This sharing occurs only with your explicit consent and configuration.

In cases where we are legally required to disclose information by valid legal process, court order, or governmental request, we will comply with such requirements while making every effort to limit the disclosure to what is legally necessary. Our trusted service providers, such as our secure cloud storage provider AWS, may process your data under strict confidentiality agreements, but only to the extent necessary to help us provide the Streamsnip service to you. These providers are contractually bound to protect your data and use it only for the purposes we specify.

2. Information We Collect

Understanding what information we collect and why we collect it is crucial for transparency. We believe in data minimization and only collect information that is necessary for providing you with an excellent clipping experience.

2.1 Information You Provide Directly

When you set up Streamsnip, you provide us with your YouTube Channel ID, which is essential for identifying your streams and ensuring clips are created from the correct source. This public identifier allows us to connect your Streamsnip commands to your actual YouTube streams. If you choose to enable Discord notifications, you may optionally provide Discord webhook URLs, which we store securely and use exclusively for sending you clip notifications according to your preferences.

Throughout your use of the service, you may provide clip descriptions and titles when creating clips. This information helps you organize and identify your clips later. You also configure various command preferences through our settings page, such as default clip duration, privacy settings, and notification preferences. All of this information is provided voluntarily and can be modified or removed at any time through your account settings.

2.2 Information Collected Automatically

To provide you with a seamless service and improve Streamsnip over time, we automatically collect certain technical and usage information. This includes clip metadata such as creation timestamps, clip duration, and source stream information, which are fundamental to the clip management functionality. We track basic usage patterns, including the number of clips you create and which commands you use most frequently, to understand how to improve our service.

When commands are executed through Nightbot, we receive and store Nightbot user IDs to track who created which clips and enforce permission settings you've configured. Our servers also maintain standard access logs that include IP addresses, request timestamps, and error information, which are essential for debugging issues, maintaining security, and ensuring service reliability. These logs are automatically purged after 30 days and are never used for tracking or profiling purposes.

2.3 Information We Explicitly Do Not Collect

We want to be clear about what we don't collect. We do not collect or store personal names, email addresses, phone numbers, or any other personally identifiable information unless you voluntarily provide it when contacting support. We never store payment information directly; all payment processing is handled by our trusted third-party payment processor, Stack, which maintains its own security standards and privacy policies.

We do not store or process the actual video content of your streams beyond the timestamp references needed for clipping. We cannot access private Discord messages, server contents, or any Discord user data beyond what you explicitly share through webhook configurations. We also do not access private or unlisted YouTube videos unless you specifically grant us permission, and we never attempt to circumvent YouTube's privacy settings.

3. How We Use Your Information

Transparency about data usage is fundamental to building trust. We use your information exclusively for providing, maintaining, and improving the Streamsnip service, and we want you to understand exactly how your data contributes to your experience.

3.1 Core Service Provision

The primary use of your information is to deliver the core functionality you expect from Streamsnip. When you issue a clip command, we use your YouTube Channel ID and the timestamp information to create an accurate clip reference from your stream. Your configured preferences determine how long the clip should be, whether it should be public or private, and where notifications should be sent. This information is processed in real-time to ensure your clips are created quickly and accurately.

We use your clip metadata to provide comprehensive clip management features. This includes displaying your clip library, allowing you to search through past clips, edit descriptions, and manage clip visibility. The usage data we collect helps us understand which features are most valuable to our users and where we should focus our development efforts. For instance, if we notice many users creating clips of similar duration, we might adjust our default settings to better match user preferences.

3.2 Service Improvement and Optimization

Beyond basic functionality, we analyze aggregated usage patterns to continuously improve Streamsnip. By understanding how users interact with different commands, we can streamline workflows and make common tasks more efficient. Performance metrics help us identify bottlenecks and optimize our infrastructure to ensure fast, reliable clip creation even during peak usage times.

We use error logs and debugging information to quickly identify and resolve technical issues before they impact your experience. This proactive approach to maintenance means fewer service interruptions and a more stable platform overall. User feedback, combined with usage analytics, guides our feature development roadmap, ensuring we're building features that genuinely benefit our community.

3.3 Communication and Support

When you configure Discord webhooks, we use these endpoints to send you real-time notifications about your clips according to your preferences. These notifications might include clip creation confirmations, sharing notifications, or important updates about clips that affect you. We carefully respect your notification preferences and never send messages beyond what you've explicitly configured.

If you contact our support team, we use the information you provide to resolve your issues effectively. This might include accessing your clip history to diagnose problems or reviewing your settings to ensure everything is configured correctly. We maintain records of support interactions to provide consistent service and track recurring issues that might indicate broader problems requiring attention.

4. Data Sharing and Disclosure

4.1 Our Fundamental Position on Data Selling

We want to be absolutely clear: Streamsnip does not sell, rent, lease, or trade your personal information or Google user data to any third parties for any purpose whatsoever. This is not just a current policy but a fundamental principle upon which our service is built. We believe your data belongs to you, and our role is merely as a custodian helping you manage your clips effectively.

We have never engaged in data selling, and we commit to never doing so in the future. This includes all forms of data commercialization, whether direct sales, data licensing arrangements, or participation in data broker networks. Your trust is more valuable to us than any potential revenue from data sales, and we structure our business model around service subscriptions rather than data monetization.

4.2 Limited Circumstances for Data Sharing

While we do not sell data, there are specific, limited circumstances where we may share certain information, always with appropriate safeguards and limitations in place.

Consensual Sharing: The most common form of data sharing occurs when you explicitly configure it. When you set up Discord webhooks, you're instructing us to share clip notifications with your specified Discord channels. This sharing includes only the clip information necessary for meaningful notifications: the clip title, description, timestamp, and a link to view it. You maintain complete control over this sharing and can disable it at any time by removing the webhook configuration.

Service Provider Arrangements: We work with carefully selected service providers to deliver Streamsnip reliably and securely. Our primary infrastructure partner is Amazon Web Services (AWS), which provides secure cloud storage and computing resources. AWS processes your data under strict contractual obligations that prevent them from using your data for any purpose other than providing infrastructure services to us. They cannot access your data's content or use it for their own purposes. All service providers we work with are bound by confidentiality agreements at least as stringent as our own privacy commitments.

Legal Compliance: In rare circumstances, we may be legally required to disclose certain information. This could occur in response to a valid subpoena, court order, or other legal process. If we receive such a request, we carefully review it to ensure it's legally valid and appropriate. We will only disclose the minimum information necessary to comply with the legal requirement, and where legally permissible, we will attempt to notify affected users about the disclosure. We also maintain the right to challenge overly broad or inappropriate legal requests.

Business Transfers: In the unlikely event that Streamsnip is acquired, merges with another company, or sells substantially all of its assets, user information would be among the transferred assets. However, any successor entity would be bound by this privacy policy's commitments, and we would notify users of such a change in ownership or control. Users would have the opportunity to delete their accounts before any transfer if they object to the new ownership.

4.3 What We Never Share

To provide additional clarity, we want to explicitly state categories of sharing we will never engage in. We never share your data with third-party advertisers or advertising networks. We do not participate in any advertising exchanges or real-time bidding systems. We never share your data with marketing companies, lead generation services, or customer acquisition platforms. We do not provide data to credit agencies, financial institutions, or any services that assess creditworthiness or financial status.

We also never share your data with data brokers, information resellers, or any entities whose business model involves aggregating and selling user information. We do not share data with AI companies for training machine learning models, except where necessary for improving our own service's clip detection algorithms, and in such cases, the data never leaves our control.

5. Data Protection and Security

Security is not an afterthought at Streamsnip; it's a fundamental design principle that influences every technical decision we make. We understand that trust is earned through consistent, demonstrable protection of your data, and we've implemented comprehensive security measures to ensure your information remains safe.

5.1 Technical Security Measures

All data transmission to and from Streamsnip occurs over encrypted connections using industry-standard SSL/TLS protocols. This means that whether you're creating a clip, adjusting settings, or viewing your clip library, all communication between your device and our servers is encrypted and protected from interception. We regularly update our SSL certificates and maintain an A+ rating on SSL security tests.

Data at rest in our databases is encrypted using AES-256 encryption, the same standard used by governments and financial institutions worldwide. This means that even in the extremely unlikely event of unauthorized database access, your data would remain protected and unreadable. Encryption keys are stored separately from the data itself and are rotated regularly according to security best practices.

Access to our systems is strictly controlled through multiple layers of authentication. Administrative access requires multi-factor authentication (MFA), and all access is logged and regularly audited. We employ the principle of least privilege, meaning team members only have access to the systems and data necessary for their specific roles. Production systems are isolated from development environments, and all code changes go through rigorous security review before deployment.

5.2 Sensitive Data Protection

Certain types of data require extra protection, and we've implemented additional safeguards for these sensitive elements. Discord webhook URLs, for instance, are not just encrypted but are also stored in a separate, specially secured portion of our database with additional access controls. These URLs are only decrypted at the moment they're needed to send a notification, minimizing exposure.

Authentication tokens and session identifiers are generated using cryptographically secure random number generators and are designed to be resistant to prediction or brute force attacks. These tokens expire automatically after a period of inactivity, requiring re-authentication to ensure that forgotten sessions don't create security vulnerabilities.

5.3 Infrastructure and Operational Security

Our infrastructure is hosted on Amazon Web Services (AWS), leveraging their world-class physical security and compliance certifications. This includes 24/7 physical security at data centers, redundant power and networking systems, and regular third-party security audits. We've configured our AWS environment according to security best practices, including network isolation, security groups, and regular security patching.

We maintain comprehensive monitoring and alerting systems that notify our team immediately of any suspicious activity or potential security issues. Our intrusion detection systems analyze patterns of access and usage to identify potential threats before they can cause harm. All security events are logged and retained for forensic analysis if needed.

5.4 Incident Response and Breach Notification

Despite our best efforts, no system is completely immune to security incidents. We maintain a comprehensive incident response plan that ensures swift, effective action if a security issue is detected. Our response team is trained to quickly assess the scope of any incident, contain the threat, and implement fixes to prevent recurrence.

In the unlikely event of a data breach that affects your personal information, we commit to notifying affected users within 72 hours of becoming aware of the breach. Our notification will include a clear description of what occurred, what information was potentially affected, what steps we've taken in response, and what actions you might want to take to protect yourself. We will also notify relevant regulatory authorities as required by law and will cooperate fully with any investigations.

5.5 Ongoing Security Improvements

Security is not a destination but a journey, and we continuously work to improve our security posture. We regularly conduct security assessments and penetration testing to identify potential vulnerabilities before they can be exploited. Our development team receives regular security training to ensure they're aware of the latest threats and best practices for secure coding.

We actively monitor security research communities and vulnerability databases to stay informed about new threats and patches. When critical vulnerabilities are discovered in systems or libraries we use, we prioritize rapid patching and deployment. We also participate in responsible disclosure programs, welcoming security researchers to report potential issues they discover.

6. Data Retention and Deletion

We believe in data minimization and only retain your information for as long as necessary to provide our service effectively. Our retention policies are designed to balance your need for historical clip access with privacy principles that favor limiting data storage duration.

6.1 Active Data Retention Periods

For active users, we retain your account information and clip data for as long as you continue to use Streamsnip. This allows you to access your complete clip history, manage your content, and maintain consistent settings across sessions. Your clips remain available indefinitely while your account is active, giving you a permanent archive of your streaming highlights that you can reference, share, or download at any time.

Server logs, which contain technical information about requests and potential errors, are retained for 30 days before automatic deletion. This limited retention period allows us to diagnose technical issues and investigate security incidents while ensuring that detailed usage patterns aren't retained longer than necessary. After 30 days, these logs are permanently purged from all systems, including backups.

For accounts that become inactive, we maintain data for 12 months to allow users to return to the service without losing their clip history. After 12 months of inactivity, accounts may be marked for deletion, and users will receive a notification (if contact information is available) providing an opportunity to reactivate their account before permanent deletion occurs.

6.2 Data Deletion Processes

You maintain complete control over your data and can request deletion at any time. Individual clips can be deleted instantly using the !delete command, which immediately removes the clip from our active databases and marks it for purging from backups. When you delete a clip, it becomes inaccessible immediately, and all associated metadata is also removed.

For complete account deletion, you can contact our support team to request full removal of your data. Upon receiving such a request, we verify your identity to prevent unauthorized deletions, then proceed with comprehensive data removal. This includes your account information, all clips and metadata, configured settings and preferences, and any associated Discord webhook configurations. The deletion process is thorough and irreversible, ensuring your data is completely removed from our systems.

When you revoke Streamsnip's access to your YouTube account through Google's permissions settings, we immediately delete all stored Google user data associated with your account. This automatic deletion ensures that we don't retain access to your YouTube data beyond your explicit consent period.

6.3 Post-Deletion Data Handling

After deletion is requested, your data is immediately removed from our production systems and becomes inaccessible through any user interface or API. However, we maintain backups for disaster recovery purposes, and deleted data may persist in these backups for up to 30 days. After this period, as backups are rotated and replaced, deleted data is permanently purged from all systems.

Some anonymized, aggregated statistics derived from your usage may be retained even after account deletion. For example, general metrics like "average clips per user" or "most popular clip durations" help us understand usage patterns and improve the service. These statistics cannot be linked back to any individual user and contain no personally identifiable information.

It's important to note that deletion from our systems doesn't affect copies of clips or information that others may have saved. For instance, if you shared a clip link and someone saved that information, or if Discord notifications were sent to a server, we cannot delete those external copies. We recommend considering this when deciding what to share through the service.

6.4 Legal and Compliance Holds

In certain circumstances, we may be legally required to retain certain data beyond our standard retention periods. This could occur if we receive a valid legal hold notice related to litigation or a regulatory investigation. In such cases, we retain only the specific data covered by the legal requirement and only for the duration required. Once the legal hold is lifted, the data is deleted according to our standard processes.

We maintain clear internal procedures for handling legal holds to ensure compliance while minimizing the impact on user privacy. Users affected by legal holds are notified where legally permissible, and we work to resolve such situations as quickly as possible.

7. Third-Party Services

Streamsnip integrates with several third-party services to provide comprehensive functionality. We carefully select these partners based on their security practices, privacy policies, and commitment to user data protection. Here's detailed information about each integration and how your data is handled.

7.1 YouTube API Integration

Our integration with YouTube through Google's official APIs is fundamental to Streamsnip's functionality. We use the YouTube Data API v3 to access public information about your streams, including titles, descriptions, timestamps, and thumbnail images. This integration is subject to YouTube's Terms of Service and Google's API Services User Data Policy, which we strictly comply with.

When you authorize Streamsnip to access your YouTube channel, you're granting us permission to read public data about your streams and videos. We cannot and do not access private videos, unlisted content (unless specifically shared), analytics data, or any personal information beyond what's publicly visible on your channel. The authorization can be revoked at any time through your Google account settings, and upon revocation, we immediately delete all stored YouTube data associated with your account.

It's important to understand that while we access YouTube data on your behalf, we do not store video content itself. We only store references (URLs and timestamps) that point to your content on YouTube's platform. This approach ensures efficient operation while respecting YouTube's infrastructure and your content ownership.

7.2 Discord Webhook Integration

Discord webhooks provide an optional way to receive notifications about your clips directly in your Discord server. When you configure a webhook URL, you're providing us with an endpoint to send structured messages containing clip information. We treat these webhook URLs as sensitive data, encrypting them in storage and only using them for sending notifications you've explicitly configured.

The information sent to Discord through webhooks includes the clip title and description, timestamp and duration information, the creator's username (if applicable), and a link to view the clip. We do not receive any information back from Discord about your server, its members, or messages. The webhook integration is strictly one-way communication from Streamsnip to your designated Discord channel.

You maintain complete control over webhook notifications and can disable them at any time by removing the webhook URL from your settings. Once removed, we immediately stop sending notifications and delete the stored webhook URL from our systems.

7.3 Nightbot API Integration

Nightbot serves as the command interface for many Streamsnip users, allowing clip creation through chat commands. When a command is executed, Nightbot sends us limited information including the command text, the user ID of the person who issued the command, and the channel where the command was used. We use this information to process the clip request and enforce any permission settings you've configured.

We do not access Nightbot user accounts, personal information, or any data beyond what's necessary for command processing. The user IDs we receive are Nightbot's internal identifiers, not personal information, and we use them solely for tracking clip ownership and permissions. Our integration with Nightbot is designed to be minimal and privacy-preserving while still providing convenient clip creation.

7.4 Payment Processing via Stack

For premium features and subscriptions, we use Stack (surajbhari.stck.me) as our payment processor. When you make a payment, you're redirected to Stack's secure payment page, where you enter payment information directly. We never see or store your credit card numbers, banking information, or other sensitive payment data.

Stack provides us with limited information about successful transactions, including a transaction ID, the amount paid, and the subscription status. This allows us to activate premium features without handling sensitive financial data. All payment processing is subject to Stack's privacy policy and security measures, which meet industry standards for payment processing.

7.5 Amazon Web Services (AWS) Infrastructure

Our entire infrastructure runs on Amazon Web Services, leveraging their secure, reliable cloud platform. AWS provides the servers, databases, and storage systems that power Streamsnip. While AWS technically has access to the hardware and infrastructure, they are contractually bound not to access customer data and have strong technical controls in place to prevent unauthorized access.

We've configured our AWS environment according to security best practices, including encryption at rest and in transit, network isolation, and regular security updates. AWS's compliance with major security standards (including SOC 2, ISO 27001, and others) provides additional assurance about the security of the underlying infrastructure.

7.6 Third-Party Limitations and Your Rights

While we carefully vet all third-party services we integrate with, it's important to understand that each has its own privacy policy and terms of service. We encourage you to review these policies, particularly for services where you have direct accounts (like YouTube and Discord). You always maintain the right to revoke Streamsnip's access to third-party services, and we will immediately stop accessing and delete any stored data from those services upon revocation.

8. Your Rights

We believe strongly in user empowerment and have built Streamsnip with user rights at the forefront. You have comprehensive rights regarding your personal data, and we've implemented user-friendly tools to help you exercise these rights easily and effectively.

8.1 Right to Access and Data Portability

You have the fundamental right to access all data we hold about you at any time. Through the !clips command, you can instantly view your complete clip library, including all metadata, descriptions, and settings. For a more comprehensive view, our settings page provides access to your configured preferences, webhook settings, and account details. This transparent access ensures you always know what data we have and how it's being used.

Beyond simple access, you have the right to data portability. We provide an export endpoint that allows you to download all your clip data in a machine-readable format (JSON). This export includes all clip metadata, timestamps, descriptions, and configuration settings. The portable format ensures you can easily transfer your data to another service or maintain your own backups. You can request a full data export at any time through our support channels, and we'll provide it within 48 hours.

8.2 Right to Rectification and Modification

Accuracy matters, and you have the right to correct any inaccurate data we hold about you. The !edit command allows you to modify clip descriptions and titles at any time, ensuring your clips are properly labeled and organized. Through the settings page, you can update your channel information, adjust privacy preferences, and modify notification settings. All changes take effect immediately, giving you real-time control over your information.

If you discover any data we hold about you that you cannot directly modify, our support team is available to help make corrections. We process rectification requests promptly and will update any inaccurate information as soon as we verify the correction with you.

8.3 Right to Erasure (Right to be Forgotten)

You have the absolute right to have your data deleted from our systems. Individual clips can be deleted instantly using the !delete command, which immediately removes the clip and all associated data from our active systems. For complete account deletion, a simple request to our support team initiates the comprehensive deletion process we described in the retention section.

We've designed our deletion processes to be thorough and permanent. Once deleted, your data cannot be recovered, ensuring true erasure rather than just hiding information. The only exceptions to immediate deletion are legal holds (rare and disclosed when applicable) and the backup rotation period, after which all traces of your data are permanently removed.

8.4 Right to Control Processing (Privacy Settings)

You have granular control over how your data is processed through our comprehensive privacy settings. The private mode setting allows you to create clips that are only accessible to you, preventing them from appearing in any public listings or searches. You can configure different privacy levels for different clips, giving you flexibility in what you share and what you keep private.

Notification controls let you decide exactly when and how you receive updates about your clips. You can enable or disable Discord webhooks, choose which events trigger notifications, and set quiet hours when you don't want to be disturbed. User permission levels, configured through Nightbot, allow you to control who can create clips on your channel, preventing unauthorized use while still allowing trusted moderators to help capture important moments.

8.5 Right to Object and Opt-Out

You have the right to object to specific types of data processing, and we provide clear opt-out mechanisms for optional features. Screenshot capture can be completely disabled if you prefer not to have visual previews of your clips. Discord integration is entirely optional and can be removed at any time. Analytics participation can be opted out of while still using the core service.

For any processing you object to that doesn't have a direct opt-out control, our support team will work with you to find a solution. We respect your choices and will never penalize you for exercising your privacy rights or opting out of optional features.

8.6 Right to Withdraw Consent

Any consent you provide to Streamsnip can be withdrawn at any time. Revoking YouTube access through Google's permissions immediately stops our access to your YouTube data and triggers deletion of stored YouTube information. Removing Discord webhooks immediately stops all Discord notifications. Canceling your subscription immediately removes access to premium features while preserving your basic rights to access and delete existing data.

Withdrawing consent is always as easy as granting it, with no penalties or complicated procedures. We believe ongoing consent should be an active choice, not a trap you can't escape from.

8.7 Rights Regarding Automated Decision Making

While Streamsnip uses algorithms to process clip creation and determine clip boundaries, we do not engage in automated decision-making that significantly affects you without human oversight. All major decisions about your account, such as suspension or termination, involve human review. You have the right to request human intervention in any automated process and to express your point of view if you disagree with an automated decision.

9. Cookies and Tracking

Our approach to cookies and tracking reflects our privacy-first philosophy. We use minimal cookies necessary for functionality and security, avoiding the extensive tracking common on many modern websites. Here's exactly what we do and don't do with cookies and similar technologies.

9.1 Essential Cookies We Use

Session cookies are essential for maintaining your logged-in state when accessing administrative functions or the settings page. These temporary cookies expire when you close your browser and contain only a session identifier that allows our server to recognize you during your visit. Without these cookies, you would need to re-authenticate with every page navigation, making the service unusable.

Preference cookies remember your non-sensitive settings to improve your experience. For example, if you prefer a certain view in your clip library or have specific display preferences, these cookies ensure you don't need to reconfigure these options with every visit. These cookies are long-lasting but contain no personal information and can be cleared at any time through your browser settings.

Security cookies help protect against common web attacks like cross-site request forgery (CSRF). These cookies contain tokens that verify requests are coming from you and not from malicious third parties attempting to perform actions on your behalf. They're essential for maintaining the security of your account and data.

9.2 Analytics and Performance Measurement

If you opt in, we use basic analytics cookies to understand how users interact with Streamsnip in aggregate. These analytics help us identify popular features, common user paths, and potential usability issues. The data collected is anonymized and aggregated, meaning we see patterns across all users but cannot identify individual behavior. You can opt out of analytics cookies at any time without affecting your use of the service.

We do not use Google Analytics, Facebook Pixel, or other third-party analytics services that might track you across websites. Our analytics are self-hosted and limited to understanding Streamsnip usage only. We never sell or share analytics data with third parties, and we don't use it for advertising or user profiling.

9.3 What We Don't Do

We do not use advertising cookies of any kind. There are no third-party advertising networks placing cookies through our service, no retargeting pixels following you around the internet, and no interest-based advertising profiles being built. We don't participate in any advertising exchanges or data broker networks.

We don't engage in cross-site tracking or browser fingerprinting. We don't attempt to identify you across different devices or link your Streamsnip activity to your activities on other websites. We don't use supercookies, Flash cookies, or other persistent tracking technologies designed to evade user control.

9.4 Your Cookie Controls

You have complete control over cookies through multiple mechanisms. Your browser settings allow you to block all cookies, delete existing cookies, or receive notifications when new cookies are set. Our service is designed to remain functional even with strict cookie settings, though you may need to log in more frequently.

We provide a cookie preference center where you can granularly control which types of cookies you accept. You can allow essential cookies while blocking analytics, or accept all cookies for the fullest experience. These preferences are respected immediately and persist across sessions.

9.5 Do Not Track (DNT) Signals

We respect Do Not Track signals sent by your browser. When we detect a DNT signal, we automatically disable any non-essential cookies and ensure no analytics data is collected from your session. This happens automatically without requiring any action on your part beyond enabling DNT in your browser.

9.6 Local Storage and Similar Technologies

In addition to cookies, we may use browser local storage for certain features. For example, draft clip descriptions might be temporarily saved locally to prevent loss if your browser crashes. This data never leaves your device unless you explicitly submit it. Local storage can be cleared through your browser settings just like cookies, and we don't use it for tracking purposes.

10. Children's Privacy

Protecting children's privacy online is a responsibility we take seriously. Streamsnip is designed for content creators who are streaming on platforms that have their own age requirements, and we align our policies with these platform requirements while adding our own protections for young users.

10.1 Age Requirements

Streamsnip is not intended for use by children under the age of 13. This age restriction aligns with the Children's Online Privacy Protection Act (COPPA) in the United States and similar regulations worldwide. We do not knowingly collect personal information from children under 13, and our service is designed with the assumption that all users meet this minimum age requirement.

It's important to note that the platforms we integrate with have their own age requirements. YouTube, for instance, requires users to be at least 13 years old (or the minimum age in their country) to have an account. Since Streamsnip requires a YouTube channel to function, users must already meet YouTube's age requirements before they can use our service.

10.2 Parental Controls and Responsibility

If you are a parent or guardian and discover that your child under 13 has created a Streamsnip account or provided us with personal information, please contact us immediately. We will promptly delete the account and all associated data upon verification of your relationship to the child. We appreciate parental involvement in children's online activities and encourage parents to monitor their children's internet use.

For teenagers between 13 and 18, we recommend parental involvement in setting up and using Streamsnip. While we don't require parental consent for users over 13, we encourage open communication between parents and teens about online privacy, data sharing, and responsible content creation.

10.3 Educational Use

We recognize that streaming and content creation can be valuable educational tools. Teachers or educational institutions interested in using Streamsnip for classroom purposes should contact us directly. We can work with educational users to ensure appropriate safeguards are in place and that any use complies with applicable educational privacy laws like FERPA.

10.4 Reporting Underage Users

If you become aware of a user under 13 using Streamsnip, please report it to our support team. We investigate all such reports promptly and take appropriate action, including account termination and data deletion where necessary. We appreciate community help in maintaining age-appropriate use of our service.

11. Changes to This Policy

Privacy policies must evolve to address new technologies, legal requirements, and user needs. While we strive for stability in our privacy practices, changes are sometimes necessary. We commit to handling policy updates transparently and giving you appropriate notice and choices when changes occur.

11.1 When We Make Changes

We may update this Privacy Policy to reflect changes in our practices, new features we add to Streamsnip, evolving legal or regulatory requirements, feedback from our user community, or improvements in how we protect your privacy. Not all changes are equal in impact, and we handle notifications differently based on the materiality of the change.

Minor changes, such as clarifications of existing practices, typo corrections, or formatting improvements, may be made without specific notification. These changes don't affect your rights or how we handle your data; they simply make the policy clearer or more accurate. Material changes that could affect your rights or significantly alter how we handle your data will always be communicated proactively.

11.2 How We Notify You

For material changes, we use multiple channels to ensure you're informed. The "Last Updated" date at the top of this policy is always updated to reflect the most recent changes, providing a quick reference for when the policy was last modified. We post prominent announcements in our Discord server, where much of our community interaction occurs, ensuring active users see the updates.

For users who have configured Discord webhooks, we may send notification messages about major privacy policy changes, though these are kept minimal and only used for the most significant updates. We also maintain a changelog of policy updates, allowing you to see what changed between versions if you're interested in the details.

11.3 Your Choices When Changes Occur

Continued use of Streamsnip after policy updates take effect constitutes acceptance of the new terms. However, we recognize that not everyone may agree with every change, and we respect your right to discontinue use if you object to new terms. Before any material changes take effect, you have the opportunity to export your data using our data portability features and delete your account if you prefer not to accept the new terms.

For particularly significant changes, we may require explicit re-consent rather than relying on continued use. In such cases, you'll be presented with the updated terms upon your next login and asked to actively accept them. If you don't accept, you'll still have access to export and delete your data, but won't be able to create new clips until you accept the updated terms.

11.4 Policy Version History

We maintain a complete history of all privacy policy versions, allowing you to review how our practices have evolved over time. This transparency helps build trust and allows researchers, advocates, and users to understand our privacy journey. Previous versions remain available for reference, though only the current version is legally binding.

12. Contact Information

Open communication is essential for privacy protection. We want to hear from you if you have questions, concerns, or suggestions about our privacy practices. We've established multiple contact channels to ensure you can reach us in the way that's most comfortable for you.

12.1 What to Include in Your Privacy Inquiry

To help us address your privacy concerns efficiently, please include relevant details such as your Streamsnip username or YouTube channel (if applicable), the specific privacy issue or question you have, any relevant dates or clip IDs, and your preferred resolution or outcome. The more context you provide, the better we can assist you.

12.2 Privacy Officer

While Streamsnip is a small team, we take privacy seriously enough to designate a privacy officer responsible for overseeing our privacy practices and responding to user concerns. This ensures accountability and that privacy considerations are represented in all our decisions.