4.1 Purpose of Beta Testing
Keepr may offer early access to new or experimental features through a voluntary beta testing programme. The purpose is to gather real-world feedback, identify issues, and improve the reliability, accessibility, and quality of upcoming functionality before public release.
4.2 Nature of Beta Features
- Beta features are experimental and may contain defects or incomplete functionality.
- Features may change, be refined, or be removed based on testing outcomes.
- Access may be limited, paused, or withdrawn at any time without notice.
- Beta features are not guaranteed to become part of the final product and are provided “as is”.
4.3 Data Handling During Beta
- Beta data is protected under the same privacy, security, and governance standards as the main service.
- Diagnostic and performance data may be collected to identify issues and support development.
- No beta data is used for advertising, profiling, or external AI training.
- Any additional data collection specific to a beta feature is communicated before participation.
- Beta data is retained for 30 days after a feature is released or removed.
4.4 Responsibilities of Beta Testers
- Use beta features responsibly and in accordance with the Terms of Service.
- Report issues, bugs, or unexpected behaviour where possible.
- Avoid relying on beta features for critical, irreplaceable, or time-sensitive information.
- Respect confidentiality requirements for unreleased or restricted features.
- Provide constructive feedback and do not share access codes with unauthorised users.
4.5 Keepr's Responsibilities
- Provide clear information about the experimental nature of beta features.
- Protect user data with the same security and privacy standards as the wider platform.
- Act on feedback to improve reliability, accessibility, and experience.
- Communicate significant risks, changes, or known issues where appropriate.
- Provide support for beta issues and respect tester confidentiality.
4.6 Leaving the Beta Programme
Users may opt out of beta testing at any time. Some beta features may require data migration or may revert to standard functionality. Where data cannot be migrated, users will be informed before opting out.
4.7 NDA and Confidentiality
Beta testers may be required to sign a Non-Disclosure Agreement (NDA) for unreleased or restricted features. Testers agree not to disclose unreleased features to third parties, share screenshots or recordings without permission, publish reviews without authorisation, or reverse-engineer beta features.
4.8 Feedback and Attribution
By participating, you grant us the right to use your feedback to improve Keepr. You may be acknowledged in release notes or credits if you wish.