Who this is for: Organisations that switch on HUBAL's social media integration. These Terms supplement the Terms of Service, the B2B Annex, the Privacy Policy and the Data Processing Agreement (DPA), which otherwise apply unchanged. In matters concerning the integration, these Terms prevail. They do not apply to Organisations that have not switched the integration on. In case of discrepancies, the Polish version prevails.
Who accepts: the owner or an administrator of the Organisation, on its behalf, before the first Account is connected. We record the acceptance with the document version, the person and the date.
§1. What the integration is
- The social media integration lets the Organisation connect its social network accounts to the Platform and, from the Platform, prepare posts (also with the help of an AI assistant), approve, schedule and publish them, and check their publication status. The integration may also cover post and account statistics and comments under posts — to the extent we make them available.
- The integration works through an external provider — Zernio (ZERNIO SOFTWARE SL, Spain; the "Intermediary"), which connects to the Services on the Organisation's behalf (§4, §6). We may add, change, restrict and withdraw integration features and supported Services at any time; this is not a change to these Terms. A change of Intermediary is governed by §8(2).
- Terms used here: Service — a social network supported by the integration (currently Facebook, Instagram and LinkedIn); Account — a page, account or profile in a Service connected to the Platform (on Facebook — a Page, on Instagram — a business or creator account, on LinkedIn — a company page or a personal profile); Post — content (text, images, videos) prepared in the Platform for publication on an Account. Other terms have the meaning given in the Terms of Service.
§2. Availability, switching on and connecting Accounts
- The integration is available on the Plans that include it according to the Pricing or information in the Platform, with the Account limit applicable to the Plan (shown in Settings → Integrations). The integration is not a separately paid Add-on — its use is covered by the Plan fee.
- The integration is switched on by the owner or an administrator of the Organisation, who accepts these Terms before the first Account is connected. Accounts are connected and disconnected by administrators and by people to whom an administrator has granted the "Social media" permission.
- When connecting an Account, the person signs in to the Service and grants consents in the window of the Service or the Intermediary; that window may show the Intermediary's name. The person connecting represents that they hold the rights to the Account required by the Service (e.g. the Page administrator role) and the authority to make it available to the Organisation.
- Connecting a personal profile (e.g. on LinkedIn) requires its owner's consent to publishing on their behalf by authorised people in the Organisation. The Organisation is responsible for obtaining that consent, its scope and the consequences of its withdrawal (disconnecting the profile).
- If the Organisation moves to a Plan that does not include the integration, new Accounts cannot be connected and Posts cannot be published, and we may disconnect the connected Accounts.
§3. Human approval and responsibility for content
- A Post is passed on for publication only after an authorised person in the Organisation (an administrator or someone with the "Social media" permission) approves it in the Platform. AI assistants and connected external tools can only prepare a draft. Approval covers the version of the Post, the selected Accounts and the publication time chosen by the approver; changing a Post after approval requires approving it again.
- Approval is the Organisation's decision. The Organisation is responsible for the content of Posts — including those prepared by an AI assistant — for the materials, the choice of Accounts and time, and for the consequences of publication, in particular for compliance with the law (including copyright, image and personal rights, data protection, advertising and consumer protection rules), with the terms and policies of the Services, and for labelling content where required (e.g. advertising, or content generated or manipulated by AI).
- We have no obligation to review Posts before publication. We may, however, apply automated safeguards and, in the event of a breach of these Terms or the law or a reasonable suspicion of one, stop publication, withdraw a scheduled Post, or suspend or switch off the integration for the Organisation; §13 of the Terms of Service applies accordingly.
- Paragraphs 1–3 apply accordingly to replies to comments, if the integration allows publishing them on the Organisation's behalf.
§4. Services and the Intermediary
- Access to Accounts (authorisations granted by the Services) is obtained and stored by the Intermediary. HUBAL does not know Account passwords and does not store the Services' access tokens; in the Platform we store the Account identifiers at the Intermediary, Account names and avatars, and their status.
- The Organisation uses the Services under its own agreements with their operators (the Services' terms) and is responsible for complying with them. Service operators are not our subcontractors or sub-processors — they receive Posts as separate entities under their agreements with the Organisation.
- The Services and the Intermediary operate under their own rules, which we do not control. A Service may change or restrict access at any time (e.g. expire an authorisation — the Account then needs to be reconnected), reject a Post, limit its reach, remove it or block the Account. The Intermediary may change, restrict, suspend or stop providing its services.
- We show the publication status based on information from the Intermediary and the Services. We do not guarantee the availability of the Services or the Intermediary, the publication of a Post at the chosen time or at all, how it is displayed in the Service, its reach or the availability of statistics.
§5. Liability
- Nature of the integration. The integration is provided as is. Publication depends on the Services and the Intermediary, and the content of Posts on the Organisation. The Organisation uses the integration at its own risk.
- Exclusions. To the fullest extent permitted by law, we are not liable for:
- the content of Posts, materials and replies published through the integration and the consequences of their publication, including third-party claims and actions of authorities;
- the operation, interruptions, delays, changes, errors, restrictions or unavailability of the Services and the Intermediary — including a Post not being published, being delayed, duplicated, removed or displayed incorrectly, and an Account authorisation expiring;
- decisions of Service operators concerning the Organisation, its Accounts and Posts (e.g. reduced reach, content removal, Account blocking);
- the consequences of a publication approved by an authorised person in the Organisation, including at the time they chose;
- acts or omissions of people to whom the Organisation has granted permissions, and connecting an Account or a personal profile without the required rights or consents;
- lost profits, indirect and consequential damage, loss of reputation, reach, followers, data or business opportunities.
- No SLA. The availability levels, response times and refunds of the B2B Annex (§7) do not apply to the integration. Switching off, restricting or unavailability of the integration does not entitle the Organisation to a reduction of the Plan fee.
- Cap. Our total liability in connection with the social media integration, whatever its basis, is limited to the amount of Plan fees paid by the Organisation in the 3 months preceding the event giving rise to the damage.
- Indemnity. The Organisation shall indemnify us and cover damages and reasonable costs (including legal costs, compensation and penalties) if a third party, a Service operator or an authority brings a claim, demand or proceedings against us arising from Posts, materials or replies published through the integration, or from an Account being connected by the Organisation or by people it has granted permissions to — in particular from infringement of copyright, image or personal rights, data protection, advertising or consumer protection rules, or the terms of the Services. We will notify the Organisation of such a claim and allow it to take part in the defence.
- The limitations and exclusions in this section do not apply to damage caused intentionally or where mandatory law does not permit the exclusion or limitation of liability — in particular towards Consumers and ETCs and towards data subjects. Paragraph 5 does not apply to Consumers and ETCs.
§6. Data, the Intermediary and locations
- Our role. With respect to Posts and Account data, we act as a processor on the Organisation's instructions (Data Processing Agreement, §8). The Organisation is the controller of this data and is responsible for the legal basis for its processing and for information duties towards data subjects (e.g. people shown in images and videos).
- What we pass to the Intermediary. After a Post is approved: its content (text and versions for the Services), the attached images and videos, the publication time, the identifiers of the Accounts and of the Organisation's space at the Intermediary, and the identifiers of the Organisation and the Post in the Platform (to match the publication status). When an Account is connected — the return address to the Platform and the HUBAL name and logo shown in the connection window. Drafts, notes and rejection reasons stay in the Platform. Approval of a Post by an authorised person is the Organisation's documented instruction to pass this data to the Intermediary and on to the Services.
- What we receive from the Intermediary: the list of Accounts (identifier, Service, name, username, avatar, status), the publication status and addresses of published Posts and, once the integration covers them, statistics and comments.
- The Intermediary and locations:
- The Intermediary processes data under its terms and its data processing agreement, which — according to the Intermediary — applies together with its terms. The Intermediary publishes the current list of its sub-processors and locations; we have no direct influence over its further sub-processors.
- We store the content of Posts, versions for the Services, notes and rejection reasons in the Platform encrypted with the Organisation's key (Privacy Policy, Section 8).
§7. Retention periods
§8. Data processing (DPA supplement)
- This section supplements the Data Processing Agreement (DPA) with respect to the integration. By accepting these Terms, the Organisation as Controller gives its consent to the use of the Intermediary listed in §6(4) (and its further sub-processors) as a further processor — solely within the scope of the social media integration.
- We give the administrators of Organisations that have switched the integration on notice of an intended change of Intermediary, as a rule 14 days in advance (by e-mail or a message in the Platform). During that time the Organisation may raise a reasoned objection — the only consequence of an objection is the option to switch the integration off before the change takes effect. In urgent situations (e.g. the Intermediary ceasing operations, security reasons) we may change the Intermediary immediately and notify without delay after the change.
- Types of data in the integration: the content of Posts (which may contain personal data, including the likeness of people in images and videos), Account identifiers, names and avatars, the publication status and, once the integration covers them, statistics and comments. Categories of data subjects: Users, owners of connected personal profiles, people whose data the Organisation includes in Posts and — for comments — their authors.
- §5 applies to liability in connection with data processing, to the extent permitted by law.
§9. Switching the integration off
- The Organisation may switch the integration off at any time by disconnecting all Accounts in Settings → Integrations → Social media. After an Account is disconnected, we do not pass new Posts to it; scheduled Posts that should not appear must be withdrawn before disconnecting. Access can also be revoked in the Service's settings.
- We may suspend or switch off the integration — for the Organisation or entirely — in particular where the Organisation breaches these Terms, a Service or the Intermediary restricts or ends access, security or the law requires it, or the Organisation does not have a Plan that includes the integration. Where we stop offering the integration for reasons other than a breach by the Organisation, we notify administrators in advance where possible.
§10. Changes to the Terms
- We may change these Terms for the important reasons listed in §17 of the Terms of Service. We notify the administrators of Organisations that have switched the integration on at least 14 days in advance. If the Organisation does not accept the change, it may switch the integration off before the change takes effect; until then, the previous version applies. Continued use of the integration after that date means acceptance of the change. A new version of the Terms may require renewed acceptance in the Platform before another Account is connected or a Post is published.
- Changes required by law or decisions of authorities, changes for security reasons or resulting from decisions of the Services or the Intermediary, and changes in the Organisation's favour may take effect immediately.
§11. Contact
Formal matters: legal@hubal-project.com · personal data: privacy@hubal-project.com · support: support@hubal-project.com. Service Provider details — Terms of Service.