Acceptable Use Policy

Effective Date: January 24, 2025

This Acceptable Use Policy (“Policy”) defines acceptable use of the ShipSilently platform and services provided by Slewsoft (“Company”, “we”, “us”, or “our”). This Policy supplements our Terms of Service.

1. Purpose and Scope

1.1 Policy Purpose

This Policy ensures that all users can enjoy a safe, secure, and productive environment while using ShipSilently.

1.2 Who This Applies To

This Policy applies to all users of ShipSilently, including:

•Individual account holders
•Team members and administrators
•API users and integrations
•Trial and free tier users

1.3 Policy Enforcement

Violations of this Policy may result in:

•Warning notifications
•Temporary service restrictions
•Account suspension
•Permanent account termination
•Legal action where appropriate

2. Acceptable Uses

2.1 Permitted Activities

You may use ShipSilently to:

•Manage feature flags for your applications
•Control software deployments and rollouts
•Conduct A/B testing and experimentation
•Monitor and analyze feature performance
•Integrate with your development workflows
•Collaborate with team members on feature management

2.2 Educational and Research Use

We encourage the use of our service for:

•Learning about feature flag management
•Educational projects and coursework
•Research into software deployment practices
•Open source project development

3. Prohibited Uses

3.1 Illegal Activities

You may not use ShipSilently to:

•Violate any applicable laws or regulations
•Infringe on intellectual property rights
•Engage in fraudulent activities
•Violate export control laws
•Support terrorist activities or organizations

3.2 Harmful Content

You may not upload, store, or transmit:

•Malicious software or code
•Viruses, worms, or other harmful programs
•Content that promotes violence or harm
•Hate speech or discriminatory content
•Harassment or threatening material
•Illegal or inappropriate sexual content

3.3 System Abuse

You may not:

•Attempt to gain unauthorized access to our systems
•Interfere with or disrupt our services
•Overload our systems with excessive requests
•Attempt to bypass security measures
•Use the service to attack other systems
•Reverse engineer our software or APIs

3.4 Commercial Restrictions

You may not:

•Resell our services without authorization
•Use our service to compete directly with us
•Create substitute or competing services using our platform
•Extract or harvest data for commercial purposes without permission

3.5 Privacy Violations

You may not:

•Collect personal information without consent
•Share user data inappropriately
•Violate privacy laws or regulations
•Use our service for surveillance without proper authorization
•Access other users’ data without permission

4. API and Integration Guidelines

4.1 API Usage Limits

•Respect published rate limits and quotas
•Use efficient polling and caching strategies
•Implement proper error handling and retry logic
•Avoid unnecessary or excessive API calls

4.2 Integration Standards

•Follow our integration best practices
•Ensure secure handling of API keys and tokens
•Implement proper authentication and authorization
•Keep integrations up to date with current standards

4.3 Data Handling

•Only access data necessary for your use case
•Implement appropriate data protection measures
•Respect user privacy and consent requirements
•Follow data retention and deletion guidelines

5. Content and Data Guidelines

5.1 User-Generated Content

You are responsible for all content you create, including:

•Feature flag names and descriptions
•Project and environment configurations
•Comments and documentation
•Shared templates and configurations

5.2 Data Accuracy

You must:

•Provide accurate account information
•Keep your profile and settings current
•Ensure data integrity in your configurations
•Report errors or inconsistencies promptly

5.3 Backup and Recovery

While we maintain backups, you should:

•Maintain your own backups of critical configurations
•Document important settings and workflows
•Have recovery plans for your feature flag dependencies

6. Security Requirements

6.1 Account Security

You must:

•Use strong, unique passwords
•Enable two-factor authentication when available
•Keep login credentials confidential
•Report suspicious account activity immediately
•Log out of shared or public computers

6.2 API Security

When using our APIs:

•Secure API keys and access tokens
•Use HTTPS for all API communications
•Implement proper key rotation practices
•Monitor for unauthorized API usage
•Report security incidents promptly

6.3 Network Security

You must not:

•Attempt to scan or probe our network infrastructure
•Use automated tools to find vulnerabilities
•Share network access credentials
•Connect insecure devices to our services

7. Resource Usage Guidelines

7.1 Fair Use

•Use computational resources reasonably
•Avoid monopolizing shared resources
•Scale usage appropriately with your plan
•Contact us before significant usage increases

7.2 Storage Limits

•Stay within your plan’s storage allocations
•Regularly clean up unused configurations
•Archive old or obsolete data appropriately
•Contact us if you need additional storage

7.3 Bandwidth Considerations

•Implement efficient data transfer practices
•Use compression where appropriate
•Cache frequently accessed data
•Minimize unnecessary data transfers

8. Community Standards

8.1 Professional Conduct

When interacting with our community:

•Be respectful and professional
•Provide constructive feedback
•Help others when possible
•Follow communication guidelines

8.2 Intellectual Property

•Respect others’ intellectual property rights
•Share knowledge appropriately
•Give proper attribution when using others’ work
•Report intellectual property violations

9. Monitoring and Compliance

9.1 Monitoring Activities

We may monitor usage to:

•Ensure compliance with this Policy
•Maintain service security and performance
•Investigate reported violations
•Improve our services

9.2 Reporting Violations

To report Policy violations:

•Use our abuse reporting system
•Contact support with detailed information
•Provide evidence when available
•Report urgent security issues immediately

9.3 Investigation Process

When investigating violations:

•We may temporarily restrict access
•We will review evidence objectively
•You will have opportunity to respond
•We will take proportionate action

10. Consequences of Violations

10.1 Progressive Enforcement

We typically follow a progressive approach:

•First Violation: Warning and education
•Repeat Violations: Temporary restrictions
•Serious Violations: Account suspension
•Severe Violations: Permanent termination

10.2 Immediate Termination

Some violations may result in immediate termination:

•Illegal activities
•Security breaches or attacks
•Significant harm to other users
•Repeated serious violations

10.3 Appeals Process

If you believe enforcement action was taken in error:

•Contact our support team with details
•Provide evidence supporting your case
•We will review appeals fairly and promptly
•Our decision on appeals is final

11. Policy Updates

We may update this Policy to address:

•New types of abuse or misuse
•Changes in applicable laws
•Evolution of our services
•Community feedback and needs

Material changes will be communicated through:

•Email notifications to users
•Service announcements
•Website notices
•In-app notifications

12. Contact Information

12.1 Questions About This Policy

For questions about this Acceptable Use Policy:

Slewsoft
6D - 7398 Yonge St Unit # 348
Thornhill, ON L4J 8J2
Canada

Email: support@slewsoft.com or support@shipsilently.com

12.2 Reporting Violations

To report violations of this Policy:

•Email: abuse@shipsilently.com
•Use our online reporting form
•Contact support with “AUP Violation” in the subject line

12.3 Security Issues

For security-related concerns:

•Email: security@shipsilently.com
•Use our security contact form
•Report urgent issues immediately

Last Updated: January 24, 2025