Code Signing Policy
This policy outlines how Segra handles code signing and related privacy considerations.
1. Privacy Statement
This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it.
For more detailed information about how we handle your data, please refer to our Privacy Policy.
2. Third-Party Components
Segra uses several open-source components. Below are the privacy policies of key third-party components that may affect users:
- OBS (Open Broadcaster Software): OBS is used for screen capture functionality. OBS does not collect or transmit any user data by default. You can review their privacy policy at https://obsproject.com/privacy-policy
- FFmpeg: Used for video processing. FFmpeg is a command-line tool that processes media locally and does not transmit any data over the network.
- libobs-sharp: A C# wrapper for libOBS (Open Broadcaster Software) used to interface with OBS functionality. As an open source library, it operates locally and does not collect or transmit any user data.
3. Team Roles
| Role | Person |
|---|---|
| Authors | @Segergren |
| Reviewers | @Segergren |
| Approvers | @Segergren |
4. Code Signing
Segra's Windows executables are digitally signed to ensure their authenticity and integrity. This helps users verify that the software they're installing comes from a trusted source and hasn't been tampered with.
Free code signing provided by SignPath.io, certificate by SignPath Foundation.
5. Contact
If you have any questions about our code signing policy or privacy practices, please contact us through our GitHub issues page or join our Discord server.