Privacy, explained for the current product stage.
Effective October 3, 2026. This is a plain-language notice for an early-stage proof of concept. It has not been reviewed by legal counsel and does not claim regulatory certification.
What Hotlution handles
When you register, the POC handles the name, email address and password credentials needed for account access. It also stores the organizations, teams, application requirements and planning choices you enter, together with generated architecture, cost and security planning records.
How that information is used
Information is used to authenticate users, provide the planning experience, preserve work between sessions, troubleshoot the service and protect it from misuse. Hotlution does not need real cloud credentials for the current POC.
Browser and operational data
The application stores an authentication token and basic user profile in browser local storage after sign-in. Hosting and application systems may also produce routine request, error and security logs. Do not use the POC on a shared or untrusted device.
Infrastructure and service providers
The public POC runs on Amazon Web Services. Necessary service data may be processed by infrastructure components used to deliver the application. Hotlution does not claim that the current POC is suitable for regulated or highly sensitive workloads.
What not to submit
Do not enter AWS access keys, cloud credentials, production secrets, private Terraform state, regulated data or confidential customer material. Repository and cloud connections shown in the POC are modeled planning records, not live integrations.
Retention and choices
Data may be retained while the POC is active and while it is reasonably needed for evaluation, security and troubleshooting. To request access, correction or deletion, email rvarvarych@gmail.com. Identity verification may be required.
Changes
This notice may change as the product and its data flows mature. The effective date above will be updated when material changes are published.