We may collect the following types of information when you use our library:

• Personal information, such as your name and email address, when you sign up or contact us.
• Technical information, including device type, operating system, and usage data, for improving our product.
• Analytics data that helps us understand how you interact with our UI components and libraries.
• Preference information to personalize your experience with our components.

The UI library may collect:

• User input, such as data entered into forms or control states.
• Cached or locally stored user interaction data for performance optimization.
• Temporary files created during UI operations, which are cleared when no longer needed.
• Component state information to enable persistence between sessions if configured.
• Theme and accessibility preferences to improve your experience.

The library processes user input data for:

• Transforming or manipulating data for compatibility with UI components.
• Storing data temporarily in memory, which is cleared after its purpose is fulfilled.
• Optimizing user interface elements based on interaction patterns.
• Implementing state management for complex form controls.
• Enabling data validation and formatting features.

We prioritize security by:

• Implementing AES256 encryption for sensitive data handling.
• Using SHA512 hashing to ensure data integrity.
• Securing data transmission between forms and components.
• We use AES256 encryption with SHA512 for protecting user-generated files from controls, ensuring safe storage and transmission. These protection options are enabled when the user chooses to generate encrypted files only.
• Regular security audits and vulnerability testing of our UI components.
• Implementing industry-standard input sanitization to prevent injection attacks.

The library integrates with third-party components, including:

• Microsoft WinForms and related components (e.g., gdi+, user32.dll).
• These components may process user data solely for rendering UI and functionality.
• .NET Framework and .NET Core runtime libraries.
• Standard web libraries for ASP.NET applications.
• Open-source UI components that have been vetted for security.

For security-related queries, feel free to contact us anytime.

Click here to view Our Contacts

Q: Does the UI library transmit my data to external servers?

A: By default all data processing occurs locally in the client components and device. The library only transmits data when it explicitly needs to do so, such as when registering and de-registering Trial Periods and Premium Licenses. This only happens during design time, meaning no communication with our server will ever happen during runtime.

Q: How long is user input data stored?

A: Most data is only held in memory while the application is running. Any persistent storage is managed by your application code, not our UI library. When you export data from a Siticone component, it will be saved to the location of your choice until you manually delete such data.

Q: Is the UI library GDPR compliant?

A: Yes, our library is designed with privacy by default principles. Since it primarily processes data locally and doesn't collect personal data without explicit configuration, it helps your applications maintain GDPR compliance. During runtime, such as when your Apps are deployed, no data is transmitted unless a components manually saves data to the client device, which is a user initiated action.

Q: How are security updates handled?

A: We regularly release security patches and updates. We recommend always using the latest version of our UI library to ensure you have the most secure implementation.