HELIOS SOFTWORKS · YOUR INFORMATION

Privacy policy

What Helios accesses, why it needs it, and the choices you have.

Effective and last updated:

Website chat demonstration

The homepage demo sends your message and recent conversation context to Helios and its AI service provider to generate a reply. It has no access to your files, accounts, computer or browsing. Please avoid entering sensitive information.

Helios does not save demo prompts or replies on its demo server. The conversation stays in the open page and is cleared when you reload or leave. The AI provider processes the submitted content under its service terms; this is not a promise of zero retention by every provider.

A secure, essential cookie remembers your demo allowance for up to 90 days. We keep keyed, pseudonymous browser and network identifiers, request times, completion status and usage counts to enforce four successful replies and prevent abuse. These records are removed after 90 days by an hourly cleanup. People sharing a network may share the allowance. Clearing cookies does not necessarily reset it. Hosting infrastructure may also keep technical connection logs.

1. Who we are

Helios Softworks Limited operates Helios and this website and is responsible for the personal information it processes to provide these services. This policy covers the website, Helios desktop and mobile apps, the Helios AI service, and integrations you connect to your Helios account.

For privacy questions, access requests or deletion requests, email director@helios-softworks.com. Please identify your Helios account and the information concerned. Do not send passwords, access tokens or identity documents unless we specifically arrange a secure way to verify your request.

2. Information we handle

Connected providers supply information after you authorize access. People you communicate or collaborate with may also supply information about you, for example in an email or shared project. Avoid including another person's sensitive information unless it is necessary and you are entitled to share it.

3. Why we use information

We use information to authenticate you, answer requests, maintain the conversation and project context you use, carry out authorized tasks, provide optional notifications and synchronization, and keep Helios reliable and secure.

Where UK or European data-protection law applies, our bases are performing the service you request, your consent for optional access where required, legitimate interests in security and service administration, and compliance with legal obligations. You can withdraw optional permissions. Where a feature processes health or other special-category information, use it only with the required explicit permission or other applicable legal basis.

4. Gmail and iCloud Mail

What connecting Gmail allows

Google authorization identifies the connected account and lets you choose Inbox access, reviewed sending, or both. Helios requests only the permissions associated with those choices:

Account identity
openid and email identify the Google account you connect.
Read and search
gmail.readonly lets Helios search and read email for your requests. The current tools search the Inbox and retrieve message headers and selected message text. They do not mark messages as read, delete mail, or download remote images or attachments.
Reviewed sending
gmail.send lets Helios send the exact email you approve. Sending is optional. You review the sender, recipients, subject and full message before selecting Approve & send.

Email data can include sender and recipient addresses, subjects, dates, message identifiers and message text. Helios uses it to find mail, answer questions about it, summarize it, and help prepare messages. If you enable Inbox monitoring, Helios periodically checks recent message headers for notices; connecting email alone does not enable monitoring.

Relevant email excerpts, generated answers and drafts can remain in your Helios conversation or saved email records. These records can include the approved message, its recipients, sending status and provider receipt identifier. Connecting Gmail does not automatically create a complete mailbox backup in Helios.

How access is protected

Google sign-in happens with Google. Helios does not ask for your Google password. OAuth tokens are encrypted in Helios's private connection store, associated with your account, and kept out of AI tool responses. The service uses them to access the provider on your behalf.

For iCloud Mail, the current connection uses Apple's mail servers and an app-specific password, stored encrypted. Helios does not need your Apple Account password. Apple Mail can also contain Gmail or other providers; connect the service that actually hosts your mailbox.

Google data: limited use

Helios's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace user data and developer policy.

Google user data is used for the email and YouTube features you request or enable. We do not sell it, use it for advertising, or use it to train or improve generalized AI or machine-learning models. Processing a message to answer your request is different from training a model.

Transfers of Google data are limited to providing the features you consent to, necessary security purposes, legal requirements, or a business transfer with your prior explicit consent. Human access to Google data is limited to your documented permission to view specific information, necessary security investigation, legal obligations, or permitted aggregated and anonymized internal operations.

YouTube and Twitch connections

Connecting YouTube lets Helios retrieve your channel information, subscriptions, liked videos, playlists and playlist items to answer your requests and help you find videos. The default connection requests youtube.readonly. If you separately enable playlist, subscription and rating changes, Helios requests youtube.force-ssl to perform those changes on your behalf. The broader permission is optional; review the permissions Google shows before connecting.

The YouTube API does not provide your Watch Later list or watch history to this integration. You may separately import your own Google Takeout watch-history.json. Imported history is stored for your Helios account and has a separate deletion control; disconnecting YouTube does not delete that import.

Connecting Twitch lets Helios retrieve your account identity and followed channels using user:read:follows, alongside public stream, video, clip and schedule information. This connection does not grant permission to send chat messages or change your Twitch account.

Connection tokens are encrypted in Helios's connection store and are not included in AI tool responses. Relevant video or channel information returned for your request may be included in your conversation and processed by the AI provider serving that conversation. Saved conversations and imported history remain until removed through their respective controls.

You can disconnect either provider in Settings → Plugins. Disconnecting removes the active Helios connection credentials. You can also revoke access through Google Account connections or Twitch connections. Revoking Helios's Google grant may affect both Gmail and YouTube when they use the same Google application. Previously saved Helios content must be deleted separately.

YouTube use is also subject to the YouTube Terms of Service and Google Privacy Policy. The Google data limited-use commitments above apply to Google API data used by these features.

5. AI processing and service providers

Helios's own AI service processes relevant context on service computers. Installing Helios on your device does not mean all processing stays on that device. Conversation encryption does not prevent the authorized AI processing endpoint from processing the content needed to respond.

Depending on the model and conversation settings, relevant conversation context, memories, tool results and images are processed by Helios or an external AI provider, including Together AI. This can include email excerpts or connected-account information used to answer your request. Standard conversations can use an external provider by default; installing the app does not make those requests local. Saved memory and conversation context are separate from training a generalized model.

Other recipients depend on the features you use: Hostinger hosts this public website; Google and Apple handle their account and mail services; Discord handles Discord login or conversations when used; and mail recipients receive the messages you approve. Optional cloud backup and sharing send the selected project or design material to the chosen service. Third-party services operate under their own privacy notices.

Information may be processed in countries where Helios's infrastructure, your devices or the services you select operate. Contact us for details relevant to your configuration. Where international-transfer safeguards are required by law, those requirements apply to the transfer. This policy does not claim that a particular cloud region or country is guaranteed for every feature.

6. Storage, security and retention

Data can be stored on Helios service computers, your linked devices, and an external service when you choose a feature that uses it. The website and mail connections use encrypted transport, and connection credentials are encrypted in the private credential store. Other content may be held in application databases, conversation records, files and recovery copies. We do not claim that all stored content is end-to-end encrypted or inaccessible to the service operator.

We retain account settings while your account is in use, connection credentials while the connection is enabled, and saved conversations, memories, projects and email records while needed to provide those saved features or until deleted. Operational records and recovery copies may remain for troubleshooting, security, recovery or legal obligations. Retention depends on the data's purpose and the copies involved; we do not promise an automatic fixed deletion period that the service does not currently enforce.

Disconnecting email removes the active connection credentials and clears the connection's recent-message monitoring data. It does not automatically erase previous conversations, saved memories, drafts, sending records, copies on your devices or the messages held by your email provider. For deletion across retained records or recovery copies, contact us using the address above. We will explain any information that must be retained and why.

7. Your choices and rights

Depending on the law that applies, you may have rights to access, correct, erase, restrict or object to processing, receive portable data, and withdraw consent without affecting earlier lawful processing. You may complain to your local supervisory authority; in the UK this is the Information Commissioner's Office.

8. Website storage and links

The website uses browser storage for preferences such as light or dark appearance and may use session information for authenticated features. Hosting infrastructure processes technical access logs to deliver and protect the website. This privacy page does not load advertising, analytics or third-party tracking scripts. Following a link to another provider takes you to that provider's own service and privacy terms.

9. Changes and contact

We will update this page when relevant features or data practices change and show the revision date above. Material changes to optional data access require the relevant notice or consent rather than being authorized simply by editing this page.

Questions about your information? Contact Helios Softworks Limited.