User Agreement
1. General provisions
1.1.This User Agreement governs the use of Smart Home Design between Mark Igorevich Kats, Moscow, Russian Federation, info@xyz.su (the “Operator”), and the user.
1.2.Clicking a login or registration button, using an account or continuing to use the Service after a new version is published constitutes acceptance.
1.3.A user may be an individual, sole proprietor or authorized representative of a legal entity or other organization. A representative confirms sufficient authority.
1.4.A minor may use the Service only within their legal capacity and with any consent required by law.
2. Purpose
2.1.Smart Home Design provides tools for design, storage and collaborative processing of data, documents, diagrams, tasks, financial and technical information, and for integration with controllers and external systems.
2.2.The Service does not replace professional review of design, electrical, engineering or operational decisions.
3. Registration and security
3.1.Users must provide accurate information and keep it current.
3.2.Users are responsible for passwords, access keys, tokens, authentication devices and all activity under their accounts.
3.3.Personal accounts must not be shared. Collaboration must use invitations, roles and permissions.
3.4.Suspected compromise must be reported immediately to info@xyz.su.
4. Organizations, roles and data
4.1.The organization owner manages members, roles, projects and organization deletion.
4.2.Owners and administrators must grant access only to authorized persons and revoke it promptly.
4.3.The organization is responsible for the lawful upload of customer, employee, contractor and facility data.
4.4.Organization deletion may result in permanent loss of projects after backup rotation periods expire.
5. Controllers, devices and remote commands
5.1.Users must verify wiring, addresses, channels, permissions, scenarios, limits and equipment safety.
5.2.Commands and automations may change real equipment operation. Users must provide hardware protection, manual control, emergency shutdown and safe modes.
5.3.Compatibility with every firmware, device, network or third-party service is not guaranteed.
5.4.The Service must not be used for systems where a failure or incorrect command may directly threaten life, health or cause major damage unless independent certified safety controls are in place.
5.5.Users are responsible for their configurations, commands, automations and access granted to third parties.
6. Support and technical access
6.1.The Operator may obtain necessary technical access to organizations, projects, files, logs, integrations and controllers for support, diagnostics, security, contract performance and project maintenance.
6.2.Access is limited to the relevant request or contract. Additional information and authority verification may be required.
6.3.Without a maintenance contract, the Operator is not required to continuously monitor equipment or independently remedy failures.
7. Integrations
7.1.Users enable external services and grant requested permissions themselves.
7.2.Yandex Alice, Asana, Seafile, Telegram, Zulip, Gitea, Grafana, Authentik/OIDC, WebAuthn, MCP/API, controllers and other integrations depend on third parties and network availability.
7.3.The Operator is not responsible for changes, suspension, data loss or unavailability caused by a third-party service, while taking reasonable measures to maintain its own integration code.
8. Acceptable use
Users must not:
- violate law, third-party rights or security requirements;
- access another person's organization, project, controller or data;
- upload malware, unlawful content or data without a lawful basis;
- interfere with the Service, bypass restrictions or scan vulnerabilities without written approval;
- create excessive load, scrape data or resell access without permission;
- use the Service for unlawful surveillance, control or other illegal purposes.
9. Availability and changes
9.1.The Service is provided “as is” in its current stage of development.
9.2.Maintenance, updates, restrictions and interruptions may occur. Continuous or error-free operation is not guaranteed.
9.3.Features may change or be discontinued. Material terms changes are published in a new document version.
10. Paid services
10.1.Prices, tariffs, scope, payment, refunds and maintenance are governed by separate contracts, invoices, commercial proposals or published tariffs.
10.2.This Agreement alone does not create a payment obligation unless a paid service and its price are separately agreed.
11. Intellectual property
11.1.Software and material use is governed by the License and Legal Notice.
11.2.Rights in user content remain with the relevant rights holders.
12. Limitation of liability
12.1.The Operator is liable only where required by law and only for documented direct loss.
12.2.The Operator is not liable for indirect loss, lost profit or data loss caused by user actions, equipment, network, third-party services, incorrect configuration or the user's failure to keep their own backup.
12.3.These limits do not apply where liability cannot lawfully be limited.
13. Restriction and termination
13.1.Access may be restricted for security threats, Agreement breaches, unlawful activity, debt under a separate contract or maintenance.
13.2.Accounts are deleted through support after request verification. Organizations are deleted by their owners.
13.3.Termination does not release obligations accrued earlier.
13.4.Before access ends, users should export required data where export is available and access is not restricted for security or legal reasons.
14. Confidentiality and public links
14.1.Users must protect non-public projects, commercial information, tokens, keys and third-party data.
14.2.A user creating a public link or invitation determines its recipients and is responsible for the disclosed materials.
14.3.The Operator may disable a public link following a complaint, security threat, legal violation or accidental disclosure.
15. Backups and exports
15.1.Backups are maintained for Service recovery and are not an individual archival service for users.
15.2.Users must independently export and retain critical documents, configurations and information where loss could cause significant harm.
15.3.Restoration of individual items from backup is not guaranteed and may be performed only where technically possible or under a separate contract.
16. Notices
16.1.Legal and technical notices may be sent by email, shown in the interface or published in the documents section.
16.2.Users must keep their contact address current and review notices.
17. Governing law and disputes
17.1.The laws of the Russian Federation apply.
17.2.Before court proceedings, a claim must be sent to info@xyz.su. The response period is 30 calendar days unless another period is required by law or contract.
17.3.Disputes are heard by the competent court under Russian jurisdiction rules.
18. Final provisions
18.1.Invalidity of one provision does not affect the remainder.
18.2.The current version is published under “Documents”.
18.3.Contact: info@xyz.su.