GrowerHub Privacy Policy
Operator: GrowerHub. Contact: https://t.me/growerhub_info.
Data we process
Email address and the identifier of the selected sign-in method, technical connection and device data, security events, zone and automation settings.
Why we use it
To provide sign-in and platform functions, protect each user space, diagnose issues and respond to support requests.
Connection secrets
A one-time MQTT password is shown when credentials are created or rotated and is not stored as plain text in the GrowerHub database. Local Home Assistant credentials are entered only in the browser for the downloaded file.
Web analytics
Yandex Metrica and Google Analytics 4 help us understand visits and platform setup progress. Events include the page address, interface language and non-personal scenario parameters. We do not send email addresses, internal identifiers, IEEE addresses or MQTT credentials to analytics.
Requests
Use the operator contact for data or account deletion requests.
Pilot connection requests
At your request, we store your preferred contact method, contact details, optional equipment description and request date in your account. You and GrowerHub administrators can access this information to discuss the pilot and help with setup; it is not sent in web analytics events. In connection settings, open “PushOk help and my request”, then “Withdraw request” to remove the request and contact details. They are also removed when your account is deleted.
PushOk cloud connection
After your confirmation and physical pairing, GrowerHub uses the PushOk cloud to receive the hub's device list, names, readings and states, and can send commands. A separate access key is created; this key and the server MQTT bridge password are stored encrypted in the database and are not sent to web analytics. GrowerHub does not request your home Wi-Fi password or an access export from Upravlyator. Archiving the connection stops communication and deletes the saved server keys; collected history remains in your account. You can remove the separate hub user in Upravlyator. Communication depends on internet access and PushOk cloud availability.
Kit orders and help choosing
When you submit a request, we store your name, phone number, selected kits and their prices, and the city, code and address of your chosen CDEK pickup point. Telegram and comments are stored only if provided. GrowerHub administrators use these details to respond, check the kit and agree the order and delivery with you. Requests are handled in the protected site administration area; automatic email and Telegram notifications are not sent at this stage. Contacts, addresses and form text are excluded from analytics and Webvisor form recording. A request key and a hash of the network address help prevent duplicates and abuse. Submitting a request does not subscribe you to marketing messages. Contact the operator to correct or delete your information.
Assistant conversations, photos and Telegram
When you use the assistant, GrowerHub stores your messages, attached photos, results of queries about your farm and proposed changes. To generate a reply, the text, prepared images and relevant information about your plants, devices and care are sent to the DeepSeek API. The project owner separately uses their personal Codex/OpenAI connection; other users’ conversations are not routed to it. EXIF metadata is removed from photos. Account names, contacts and connection secrets are not included in the domain tools. Do not include passwords or other people’s private information in messages. Conversations and photos are retained for up to 90 days; proposals and usage records also prevent duplicate commands and enforce limits. Text and photos are excluded from web analytics and form recording. A signed session and a hash of the network address help protect the service. If you separately enable chat in Telegram, your selected conversation is shared with the bot and its messages and replies pass through Telegram. You can disable that channel and scheduled summaries in assistant settings; ordinary care reminders have separate settings. Contact the operator to request data deletion. A confirmed feature request is stored separately from the conversation: title, task, expected benefit, account number and the team’s decision. Administrators can review it, and a notification is sent to the project owner through Telegram. Conversation history and photos are not included automatically. The request is retained until account deletion or a deletion request.
Demo farm and sessions
A guest demo farm stores virtual devices, settings and history for 24 hours. Access uses a separate protected session cookie; a hash of the network address limits how often farms can be created. Simulation pauses after 10 minutes of inactivity. A demo saved to an account remains until reset, replacement or account deletion. Demo access does not grant access to the account's real devices.