Privacy Policy

Helios is operated by Brompton Holdings Ltd, Griva Digeni, Paphos, Cyprus. Contact info@brompton-holdings.com with questions about this policy or requests relating to your personal information.

If you use Helios through a business workspace, that business also controls the information it chooses to upload or connect. The applicable roles and business customer arrangements must be confirmed below.

• Account and workspace information: sign-in details, profile information, workspace memberships, roles, brand settings and preferences.
• Content you provide: uploaded images and videos, captions, drafts, articles, website addresses, instructions, chat prompts and saved reports or recommendations. Content may contain information about other people.
• Connected accounts: account identifiers, names, granted permissions and authorisation tokens, together with content metadata and performance metrics made available through the APIs you authorise.
• Publishing records: selected accounts, approved content, scheduling choices, privacy and disclosure settings, publication identifiers, status and errors.
• Technical and support information: device/browser and request information, service diagnostics, usage information made available by hosting services, and information you provide when requesting help.

Some information comes directly from you. Other information comes from your workspace members, authorised platforms, public website pages you ask Helios to review, or infrastructure providers that operate the service.

Helios uses relevant information to operate accounts and workspaces, store and prepare content, carry out approved publishing, retrieve authorised analytics, produce reports and suggestions, respond to support requests, and protect the service against misuse.

Brand information, saved reports and available performance evidence can inform later suggestions for that workspace. This is context used to generate recommendations; it is not a claim that Helios trains its own AI model on your posts.

Account information is needed for signed-in features. Connecting external accounts is optional; features requiring their permissions will not work without that connection. Optional marketing communications, if introduced, require their own appropriate handling.

When you connect a supported platform, its authorisation screen explains the permissions requested. Helios uses those permissions for the features you enable. It does not need your social account password.

For TikTok, an authorised connection can retrieve your account identifier and display information, public video metadata, and available counts such as views, likes, comments and shares. These can support performance reports and content suggestions. Metrics the API does not provide are not treated as known.

Where TikTok Direct Post is enabled and separately authorised, Helios sends the media, caption and posting choices you approve to TikTok, and checks processing status. A read-only connection does not itself authorise publishing. Published content is handled under the receiving platform's own terms and privacy policy.

Owners and admins can disconnect an account in Settings. You can also revoke access through the platform's app-permission controls. Disconnecting stops future use of the connection and removes stored credentials through the disconnect flow; it does not by itself delete existing posts from that platform or erase previously imported reports and metrics. Use the deletion process below for information retained by Helios.

Relevant instructions, text, selected images and contextual information can be sent to AI service providers to generate the assistance you request. The current direct AI integration uses OpenAI. Avoid submitting personal information that is unnecessary for the task.

The current application uses Supabase for account/data services and storage, and Lovable for application hosting. Other providers may support email, diagnostics or connected features. The complete provider list and processing arrangements must be confirmed below.

Information is also shared with the destinations you select for publishing and with workspace members according to their access. Information may need to be disclosed where required by applicable law or to address security incidents or legal claims.

Helios uses authenticated workspace access and encrypted storage of connected-account credentials in its integration flows. No online service can guarantee absolute security. Keep your sign-in details secure and give workspace access only to people you trust.

Manager conversation history is stored on the device/browser and is cleared by the sign-out flow. Saved content, media, reports and publishing records can be stored separately on the service. Clearing browser history does not delete those server records.

Helios uses browser storage for sign-in/session functionality and preferences such as the selected workspace and local conversation history. Hosting and security services may also set cookies or collect request information.

Depending on the law that applies, you may have rights to access, correct, delete, restrict or object to processing of your information, receive a portable copy, and withdraw consent where consent is the basis for processing. These rights can be subject to legal conditions and exceptions.

Contact the privacy contact above to make a request. Helios may need to verify your identity and your authority over a workspace. If a business controls the information, the request may need to be coordinated with that business.

You may also complain to the relevant data protection authority.

Helios is intended for adult users managing marketing activities. Do not provide children's personal information unless you have the necessary authority and a lawful reason. Uploaded media and content remain subject to the rights of the people they depict.

AI suggestions and performance patterns assist marketing decisions. They can be inaccurate and should be reviewed. They are not intended to make legal or similarly significant decisions about individuals.

The effective date above identifies the current version. Material changes to how personal information is used should be brought to users' attention through an appropriate notice.