Steven EnamakelandGitHub
bfaabd3b86
* chore: update AlphaHuman version to 0.49.3 and configure updater plugin in tauri.conf.json - Bumped the AlphaHuman package version in Cargo.lock to 0.49.3. - Added updater configuration in tauri.conf.json to enable automatic updates with specified endpoints. * refactor: rename AlphaHuman to OpenHuman across the codebase - Updated all instances of "AlphaHuman" to "OpenHuman" in comments, tooltips, and constants to reflect the new branding. - Adjusted relevant documentation and prompts to ensure consistency with the new name. * refactor: update documentation and configurations to reflect OpenHuman branding - Replaced all instances of "AlphaHuman" with "OpenHuman" in documentation, comments, and configuration files to ensure consistency with the new branding. - Updated deep link URLs and related authentication flows to use the new "openhuman://" scheme. - Adjusted paths and references in the skills system and other related files to align with the new project name.te * refactor: standardize OpenHuman references and update configurations - Replaced all instances of "AlphaHuman" with "OpenHuman" across documentation, comments, and configuration files to maintain branding consistency. - Updated URLs and paths to reflect the new "openhuman://" scheme. - Adjusted environment variable names and related settings to align with the new project identity. - Enhanced documentation for clarity and accuracy regarding the OpenHuman framework.r * chore: update subproject commit reference in skills directory * refactor: update backend URL to reflect new service domain - Changed default backend URL from "https://api.openhuman.xyz" to "https://api.tinyhumans.ai" in both JavaScript and Rust configuration files. - Ensured consistency across the codebase regarding the new backend service endpoint. * feat: introduce identity and migration modules for OpenHuman - Added a new identity module to support AIEOS v1.1 JSON format, including structures for identity, psychology, linguistics, motivations, capabilities, physicality, history, and interests. - Implemented a migration module to facilitate data migration from OpenClaw memory, including SQLite and Markdown sources, with detailed reporting on migration statistics and warnings. - Established utility functions for handling multimodal content and image processing within the OpenHuman framework. - Enhanced the agent system with new dispatcher and classifier functionalities to improve tool management and message classification. * chore: remove Android project files and configurations - Deleted various Android project files including .editorconfig, .gitignore, build.gradle.kts, gradle.properties, and others to clean up the project structure. - Removed all related resources, layouts, and source files from the Android app directory to streamline the codebase. - This cleanup is part of a larger effort to refactor and simplify the project structure. * refactor: update login flow and remove Telegram integration - Removed the TelegramLoginButton component and its references from the OAuthLoginSection, streamlining the login options. - Updated the AppRoutes to remove the login route, reflecting changes in the authentication flow. - Enhanced the RotatingTetrahedronCanvas component with improved geometry and lighting effects for better visual presentation. - Adjusted the TypewriterGreeting component's styling for consistency. - Cleaned up the Welcome page to integrate the OAuthLoginSection directly, improving user experience. * chore: update subproject commit reference in skills directory * chore: update test configurations and improve test assertions - Modified test scripts in package.json to use a specific Vitest configuration file for consistency. - Updated assertions in loader tests to ensure loading durations are non-negative. - Enhanced tool loading tests to clarify expected behavior regarding localStorage and cache management. - Adjusted agent tool registry tests to improve error handling and ensure accurate statistics. - Refined device detection tests to reflect updated fallback URLs. * fix: enhance parameter formatting and remove unused components - Updated the `formatParameters` function to handle cases where schema properties are empty, returning a more informative response. - Deleted the `DownloadScreen` component and associated device detection utilities to streamline the codebase and remove unused functionality. - Adjusted tests to reflect changes in the tool loading and agent tool registry, ensuring accuracy in assertions. * chore: simplify Vitest configuration by removing unused include patterns - Updated the Vitest configuration to remove unnecessary test file patterns, streamlining the test setup for better clarity and maintainability. * refactor: update paths and comments for AI configuration and file watching - Modified Vite configuration to ignore only the `src-tauri` directory. - Updated logging messages to reflect the correct path for writing AI configuration files. - Adjusted fetch calls in the file watcher to use the new path for `TOOLS.md`. - Revised comments and logic in Rust code to clarify the handling of AI configuration file paths, including legacy fallback options. * chore: remove unused updater secrets from GitHub Actions workflow - Deleted UPDATER_GIST_URL and UPDATER_GIST_ID environment variables from the package-and-publish workflow, streamlining the configuration. * chore: comment out Vitest thresholds for clarity - Commented out the thresholds section in the Vitest configuration to improve clarity and maintainability, as it is currently not in use. * ran formatter * chore: update updater public key in tauri configuration - Replaced the existing public key in the updater plugin configuration with a new value to ensure proper functionality and security. * chore: update ESLint configuration and refactor components - Added `localStorage` and `sessionStorage` as readonly globals in ESLint configuration for better linting support. - Removed unused imports from `SkillsPanel.tsx` to clean up the code. - Changed the type of `watcherInterval` in `file-watcher.ts` for improved type safety. - Refactored toast management logic in `Intelligence.tsx` to enhance clarity and maintainability. - Simplified import statements in `IntelligenceProvider.tsx` for consistency. - Streamlined object property shorthand in `agentToolRegistry.ts` for cleaner code. * refactor: improve error handling and type safety in Intelligence component - Enhanced toast notification logic to defer state updates, preventing potential issues with setState in effects. - Updated the source filter dispatch to use a more specific type for improved type safety. * refactor: enhance type safety across various components and services - Updated type definitions from `any` to `unknown` in multiple files to improve type safety and prevent potential runtime errors. - Refactored state management in `TauriCommandsPanel` to use more specific types. - Adjusted context and parameters in several interfaces to ensure consistent typing. - Added ESLint directive to `polyfills.ts` for intentional global assignments. - Streamlined type handling in utility functions and API responses for better clarity and maintainability. * refactor: streamline import statements and improve code clarity - Consolidated import statements in `agentToolRegistry.ts` and `intelligenceSlice.ts` for better readability. - Simplified the `createTestStore` function in `test-utils.tsx` to enhance code conciseness. - Cleaned up the `isExecutionStepProgressEvent` function in `intelligence-chat-api.ts` for improved clarity and maintainability.
4.4 KiB
Privacy Policy
Last Updated: 02/02/2026
This Privacy Policy describes how we collect, use, process, store, and protect information when you use our system-level AI assistant (the “Service”). The Service is designed to operate as a general-purpose assistive agent on a user’s device, such as a laptop or desktop computer. We are committed to protecting user privacy and minimizing data collection and retention.
This Privacy Policy is intended to comply with applicable global data protection laws, including the EU General Data Protection Regulation (GDPR), India’s Digital Personal Data Protection Act (DPDP), the California Consumer Privacy Act and Privacy Rights Act (CCPA/CPRA), Brazil’s LGPD, and Canada’s PIPEDA. 
Information We Collect
We collect and process information only as necessary to provide the Service and only in response to explicit user actions.
1.1 User Content and System Data When you use the Service, it may process files, application data, system context, or other information on your device only when you explicitly instruct it to do so and only to the extent required to complete a requested task.
1.2 Minimal User Metadata We collect limited user metadata required for basic account or service functionality. This is restricted to: • First name • Last name • User-provided profile information (such as a bio, where applicable)
We do not collect phone numbers, contact lists, precise location data, device identifiers, browsing history, behavioral analytics, or background system activity unless explicitly required for and permitted by a user-requested task.
How We Use Information
We use information solely to operate, maintain, and provide the Service, including to: • Perform tasks explicitly requested by the user
• Provide contextual assistance across files, applications, or workflows
• Improve reliability and security of the Service
We do not use personal data for advertising, marketing, profiling, or behavioral tracking. We do not sell, rent, or trade personal data. User data is not used to train shared, public, or third-party AI models.
Data Retention and Deletion
The Service operates under a zero-retention-by-default design.
• System data and content are processed transiently
• No long-term logs of system activity, files, or actions are maintained
• Temporary data required to complete a task is deleted immediately after task completion or within a maximum of 30 days
Users may request deletion of their data at any time. Upon such request, all associated data is permanently deleted and cannot be recovered. Revoking permissions or uninstalling the Service immediately halts further processing.
Legal Bases for Processing
Where required by law, we process personal data based on one or more of the following legal bases:
• User consent
• Performance of a contract
• Legitimate interests, where applicable and balanced against user rights
Security Measures
We implement reasonable and appropriate technical and organizational measures designed to protect information from unauthorized access, loss, misuse, or alteration. These measures include encryption in transit and at rest, least-privilege access controls, isolated processing environments, and internal monitoring and audit mechanisms. Access to user data by personnel is restricted to operational, security, or legal necessity.
Service Providers
We may engage third-party service providers to support operation of the Service, such as infrastructure hosting or AI inference providers. These providers act only on our behalf, are subject to confidentiality obligations, and are restricted from using data for their own purposes.
International Data Transfers
Information may be processed in locations outside your country of residence. Where applicable, we implement appropriate safeguards to ensure adequate protection consistent with applicable data protection laws.
Your Rights
Depending on your location, you may have rights to access, correct, delete, restrict processing of, or withdraw consent for your personal data, as well as request data portability. Requests can be done on the dashboard at any time or may be submitted to privacy@[yourdomain].com.
Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be communicated as required by law. Changes will not apply retroactively in a manner that reduces existing privacy protections.