Beta Terms

These terms apply to the free Local Core Utility 0.9.0-beta.1 Early Access build distributed by Claudiu Cojocaru (the “Operator”). They are intended for pre-release testing and are separate from the commercial EULA that may apply to a future paid or generally available release.

1. Early Access status

Local Core 0.9.0-beta.1 is pre-release software provided for evaluation and testing. Features, storage formats, compatibility, support policy, and availability may change before a later release. The Operator may replace or withdraw a beta build when necessary for safety, compatibility, or product development.

The beta is provided free of charge. Participation does not create a paid subscription, service-level commitment, or entitlement to a future paid product.

2. Software license

Local Core is proprietary software. Subject to these Beta Terms, the Operator grants the user a limited, non-exclusive, non-transferable license to install and use the Early Access beta for personal or internal evaluation and testing during the supported beta period.

Except where applicable law expressly permits otherwise, these Beta Terms do not grant permission to copy or redistribute the installer to third parties, publish or distribute the source code, modify or create derivative works from the first-party software, sublicense or sell the software, or remove proprietary notices. Testers may keep reasonable backup copies needed for their own installation and recovery purposes.

No source-code license is granted. The first-party software remains owned by the Operator. The repository and source code used to build Local Core are not part of the public Early Access distribution.

Third-party components remain governed by their respective licenses and notices.

3. Local file access and recovery data

Local Core requires access to folders the user explicitly chooses to protect. It creates and retains local recovery metadata and historical file-content data in its application-data location. Users should protect only files and folders they are authorized to access.

The current Time Engine is designed to operate locally and does not intentionally upload protected file contents, filenames, recovered versions, or version history to a Local Core service. See the Privacy Notice for the current build's privacy behavior.

4. Beta risk and backup responsibility

The beta must not be treated as the user's only backup. File history can be incomplete or unavailable because of hardware failure, operating-system behavior, permissions, storage exhaustion, filesystem conditions, corruption, unsupported metadata, exclusion rules, user action, or defects that have not yet been discovered.

Users should maintain an independent backup strategy appropriate to the importance of their data and should verify important restores rather than assuming any single recovery system is sufficient.

5. Unsigned Windows build

The first Early Access Windows build is intentionally unsigned. Windows may display an unknown-publisher, reputation, or security warning. The beta must be downloaded only from the official Local Core distribution page, and the published SHA-256 should be used when practical to verify the exact installer.

The Operator does not claim that this beta is Microsoft-signed, production-certified, or generally available software.

6. Unsupported metadata and secure deletion

The current beta versions and restores regular file contents. It does not promise to preserve ACLs, alternate data streams, extended attributes, resource forks, or other filesystem metadata.

Uninstalling Local Core may not securely erase every byte previously written to storage. Users with secure-erasure requirements should use operating-system or storage-device procedures appropriate to their environment.

7. Feedback and security reports

Users may provide bug reports, usability feedback, and product suggestions through the published support route. Feedback should not contain real private files when a synthetic reproduction is sufficient.

Potential security vulnerabilities or unintended file disclosure should be reported privately through the Security Policy, not posted publicly with sensitive reproduction data.

8. Support and beta updates

The beta support route is claudiu2169@gmail.com. Support is provided on a best-effort beta basis and does not include a guaranteed response or resolution time unless separately stated in writing.

Users may be asked to update to a newer beta when an older build is withdrawn or no longer supported. Release notes will identify the supported beta version or versions.

9. Privacy and public identity

The applicable privacy notice is the Local Core Privacy Notice. The Operator's public identity and privacy contact route are stated consistently in the release materials and on this website.

10. Governing terms and mandatory rights

These beta terms do not exclude rights that cannot legally be excluded. Any jurisdiction-specific warranty, liability, governing-law, consumer-rights, or data-protection language required for the selected distribution model may be reviewed and updated before broader public distribution.