Terms of use

Hubflow service, published by SAS MEDUZA STUDIO. Version of 8 November 2026. These terms apply to anyone who uses the Service: team members of a workspace, contributors and recipients.

Publisher of the Service

The Hubflow service (the “Service”), available at hubflow.cloud and app.hubflow.cloud, is published and operated by MEDUZA STUDIO, a French simplified joint-stock company (société par actions simplifiée) with a share capital of 500 euros, registered with the Reims Trade and Companies Register under number 911 536 217, whose registered office is located at 126 boulevard Saint-Marceaux, 51100 Reims, France, intra-Community VAT number FR86911536217 (the “Publisher”). Publication director: Romain Duflot, President. Contact: support@hubflow.cloud. The Service is hosted in France by Scaleway SAS, 8 rue de la Ville-l’Évêque, 75008 Paris.

Article 1 — Definitions

• Customer: the business that has taken out a subscription to the Service with the Publisher under the terms of sale (the “Terms of Sale”), and on whose behalf a Workspace is opened.
• Workspace: the Customer’s environment within the Service, isolated from that of other customers, containing its Requests, Resources, Deliveries, templates, contacts and settings.
• Administrator: the Team Member appointed by the Customer to manage the Workspace, accounts, roles, API keys and settings.
• Team Member: any natural person holding a named account in the Customer’s Workspace.
• Contributor: any person invited by the Customer to submit documents to a Request, via a personal link, without an account.
• Recipient: any person who receives a Delivery or accesses a Resource, via a personal link or an access request, without an account.
• Participants: Contributors and Recipients.
• User: any person who accesses the Service, in whatever capacity: Team Member, Contributor, Recipient or mere visitor to the website.
• Request: a request for items created in the Collect product, made up of expected items and Participants.
• Resource: a set of files made available to Recipients by means of the Share product.
• Delivery: a transmission of documents to Recipients by means of the Send product, accompanied by usage rules and an undertaking.
• Content: all documents, files, data, messages and metadata submitted, shared, sent or generated in a Workspace.
• Credentials: username and password, single sign-on token (SSO), personal link, one-time code, API key, webhook secret.
• Documentation: the documentation of the Service published at hubflow.cloud/docs.

Article 2 — Purpose, acceptance and relationship with other documents

2.1. These terms of use (the “Terms of Use”) set out the rules governing access to and use of the Service by any User. Their purpose is to ensure fair, secure and lawful use of the Service, in the interest of all Users.

2.2. Accessing and using the Service, including merely viewing a Request, a Resource or a Delivery via a link received, constitutes full and unreserved acceptance of the Terms of Use. Team Members accept the Terms of Use when they first sign in to their account. Participants are informed of them on the access page to which their link leads. Any User who does not accept the Terms of Use must refrain from using the Service.

2.3. The contractual and financial relationship between the Publisher and the Customer is governed by the Terms of Sale; the processing of personal data on behalf of the Customer is governed by the data processing agreement; the processing carried out by the Publisher on its own behalf is described in the privacy policy. In the event of conflict, the Terms of Sale prevail over the Terms of Use in the relationship between the Publisher and the Customer. The rules specific to each Workspace (retention periods, access rules, undertakings) are defined by the Customer and supplement the Terms of Use without being able to derogate from them.

Article 3 — Categories of Users

3.1. Team Members. Team Members act in the name and on behalf of the Customer, in the course of their duties. Their account is created by the Administrator, who assigns them a role determining the actions they are permitted to perform (viewing, creating Requests, Resources and Deliveries, managing contacts, administration). A Team Member must be of legal age and authorised by the Customer.

3.2. Contributors. Contributors are invited by the Customer to submit documents. They act in their own name or on behalf of the person they represent. They have no account and no contractual relationship with the Publisher: their relationship is with the Customer, in connection with the engagement or service for which the items are requested.

3.3. Recipients. Recipients receive documents or access Resources made available by the Customer, under the access and usage conditions the Customer has defined. They have no account and no contractual relationship with the Publisher.

3.4. Visitors. Visitors to the hubflow.cloud website are subject to the Terms of Use as regards browsing the website, the documentation and the contact forms.

Article 4 — Access conditions

4.1. Prerequisites. Access to the Service requires an internet connection and the current or previous stable version of a mainstream browser. Users are responsible for their own equipment, software and connections, and for their security. The Service is designed to work on desktop computers, tablets and mobile phones.

4.2. Team Members. Team Members sign in with their username and password or, where the Customer has enabled it, by single sign-on (SAML or OIDC SSO) with the Customer’s identity provider.

4.3. Participants. Participants access the Service through the personal link received by e-mail or SMS, where applicable supplemented by a one-time code sent to the same address or number. The link may be time-limited, restricted to certain e-mail address domains or subject to the Customer’s approval (“on request” access). The Customer may also make a Resource public; access then takes place without identification.

4.4. Personal nature of links. The personal link and the one-time code are strictly personal. Actions performed by means of a link are attributed to its holder, whose name or address may be applied as a watermark to the documents viewed or downloaded. A Participant who receives a link not intended for them must refrain from using it and inform the sender or the Publisher.

Article 5 — Accounts, roles and accuracy of information

5.1. Team Member accounts are named accounts. An account may not be shared between several persons or transferred. The Administrator creates, modifies and removes accounts, assigns roles and revokes API keys. Removal of an account takes effect immediately; the Team Member’s past actions remain recorded in the audit log.

5.2. Users provide accurate information and keep it up to date. Participants ensure the accuracy of the e-mail address or number at which they wish to receive communications from the Service; the Customer is responsible for the accuracy of the contact details it enters for its Participants.

5.3. The Publisher may require verification of an e-mail address or telephone number before granting access, and may refuse or suspend any access it has serious grounds to believe is fraudulent.

Article 6 — Security of Credentials

6.1. Each User is responsible for the confidentiality of their Credentials and for the use made of them. Team Members choose a strong, unique password, disclose it to no one, including the Publisher’s support team, which will never ask for it, and sign out on shared devices.

6.2. API keys and webhook secrets are Credentials: they must be stored server-side, never appear in public source code, a web page or an e-mail, and be rotated in case of doubt. The Publisher retains only the fingerprint of API keys: a lost key cannot be recovered, only regenerated.

6.3. Any loss, theft, compromise or unauthorised use of Credentials must be reported without delay to the Administrator of the Workspace concerned and to the Publisher at security@hubflow.cloud. The Publisher revokes compromised Credentials as soon as possible.

6.4. The Publisher cannot be held liable for the consequences of access carried out using valid Credentials before it has been informed of their compromise.

Article 7 — Usage rules

7.1. The Service is intended for the collection, sharing and delivery of documents in the context of business relationships. Users use it fairly, in accordance with its intended purpose, the Documentation, these Terms of Use, applicable laws and regulations, and the rights of third parties.

7.2. In particular, all Users are prohibited from:

• submitting, sharing, sending or storing unlawful Content, including in particular Content that is contrary to public order or morality, defamatory, insulting or discriminatory, that infringes a third party’s privacy, image rights or intellectual property rights, or that constitutes a criminal offence;
• transmitting files containing malicious software, or attempting to introduce into the Service any code or device liable to impair its operation;
• accessing or attempting to access a Workspace, an account, a Request, a Resource or a Delivery without authorisation, fraudulently remaining within the Service, or impersonating another person;
• circumventing, disabling or testing the security measures, access restrictions, watermarks, expiry dates or usage rules defined by the Customer, except under the responsible disclosure policy set out in Article 20;
• collecting documents or personal data without the necessary right or legal basis, or using the Service for a purpose other than that stated to Participants;
• using the Service to send unsolicited commercial communications, bulk messages or communications unrelated to a Request, a Resource or a Delivery;
• automatically crawling the Service, extracting data from it by means other than the export functions and the documented API, or disrupting its operation through excessive load;
• submitting data whose hosting is subject to a certification, accreditation or localisation requirement that the Service does not hold, in particular health data subject to HDS (French health data hosting) certification, in the absence of a specific written agreement between the Customer and the Publisher;
• using the Service as a general-purpose backup space or to store files unrelated to an ongoing business relationship;
• reproducing, copying, selling, renting or exploiting all or part of the Service or its contents for purposes other than those intended.

7.3. The Customer is responsible, towards the Publisher and third parties, for the use its Team Members make of the Service and for the rules it defines for its Participants (verification criteria, rejection reasons, reminder scenarios, usage rules, undertakings, retention periods).

Article 8 — Collect: Requests and submission of documents

8.1. How it works. A Request is made up of expected items, grouped by Participant. Each item may require one or more files, may be conditional, and may carry verification criteria (extension, size, name, number of files) and rejection reasons defined by the Customer. The Contributor receives a personal link to the Request page, where they see the requested items, their status and the Customer’s messages, and upload their files.

8.2. Verification and rejection. A file that does not meet the criteria is rejected with the reason written by the Customer; the Contributor may then upload a new file. An accepted file may subsequently be reviewed by a Team Member, who may approve or reject it, stating a reason. The status of each item is visible to the Contributor. The rejection of an item is a decision of the Customer; the Publisher plays no part in assessing the documents.

8.3. Reminders. The Customer may schedule reminders by e-mail and, optionally, by SMS, according to a scenario (for example D+3, D+7, D+14) that stops automatically for each item received. A Contributor who considers the reminders unjustified or excessive should contact the Customer; they may also inform the Publisher, which forwards the matter to the Customer.

8.4. Recurring Requests. The Customer may schedule the automatic creation and sending of a Request at regular intervals. Each occurrence gives rise to a new personal link sent to the Contributor.

8.5. Contributor obligations. The Contributor warrants that they are authorised to transmit the documents they submit, that these documents are authentic, accurate and complete, and that they do not infringe the rights of third parties. The Contributor retains the original of the documents transmitted. They are informed that each file is given a SHA-256 fingerprint and that their submission is timestamped and logged.

8.6. Submission receipt. The Contributor receives a confirmation of submission by e-mail or on screen. This confirmation attests to the technical receipt of the file by the Service; it does not constitute acceptance of the item by the Customer, nor completion of the formality for which the item is requested.

Article 9 — Automatic document verification

9.1. Where the Customer has enabled it for an item, an automatic verification is carried out at the time of submission or during review: extraction of information (type of document, dates, amounts, identity of the holder), consistency check against the expected item, and evaluation of the rejection reasons configured by the Customer. A reason evaluated at submission results in the immediate rejection of the file; a reason proposed at review is submitted to a Team Member, who decides.

9.2. This processing is carried out on the Publisher’s infrastructure, within the European Union. The documents are not used to train models and are not retained by the analysis component beyond the processing. The results are probabilistic indications and may contain errors.

9.3. Contributors are informed, on the Request page, of the existence of this verification where the Customer has enabled it. A Contributor whose file has been automatically rejected may upload a new file or contest the rejection with the Customer, which carries out a human review. No decision producing legal effects concerning a person is taken by the Service solely on the basis of this processing: the decision rests with the Customer.

Article 10 — Share: Resources and access

10.1. Access modes. A Resource may be public, accessible by link, restricted to an allow-list of addresses, or accessible on request approved by the Customer. The Customer assigns each Recipient a role: online viewing, download or contribution. It may restrict access requests to certain e-mail address domains and set an expiry date for the Resource or for each access.

10.2. Named watermark. Where the Customer enables it, the Recipient’s name and e-mail address are applied to each page viewed online and to downloaded PDFs. The Recipient is informed of this upon access. The watermark makes it possible to identify the source of an unauthorised distribution; removing or altering it is prohibited.

10.3. Versions. Replacing a file creates a new version; subscribed Recipients are notified and earlier versions remain available to Administrators. The Recipient is invited to refer to the latest published version.

10.4. Log. Each view, download, access request, approval and modification is logged, together with the Recipient’s identity, the date and the time. The Recipient is informed that the Customer has access to this log.

10.5. Recipient obligations. The Recipient uses the documents within the limits of the role assigned to them and the conditions set by the Customer. Unless authorised by the Customer, the Recipient refrains from redistributing the documents, sharing their access link or circumventing download restrictions. A Recipient with a contribution role warrants that they hold the rights to the files they add.

Article 11 — Send: Deliveries, undertakings and evidence

11.1. Access to a Delivery. The Recipient of a Delivery receives a personal link. Before accessing the documents, they read the usage rules set by the Customer (for example: do not disclose, do not modify, do not copy, use limited to a specified purpose, deletion on the due date) and accept the undertaking generated from these rules, supplemented where applicable by the Customer’s own clauses.

11.2. Nature of the undertaking. The undertaking is entered into between the Customer and the Recipient; it may contain legally binding obligations for the Recipient, such as an obligation of confidentiality or of deletion by a given date. The Publisher is not a party to this undertaking, does not guarantee its validity and plays no part in its performance. A Recipient who does not accept the undertaking does not access the documents and informs the sender.

11.3. Signature. Acceptance is collected by simple electronic signature: identification of the Recipient by their e-mail address and, where applicable, a one-time code, timestamping and logging. The Customer may optionally require an advanced signature with identity verification. The Recipient is informed that the Service provides neither a qualified signature nor a qualified electronic registered delivery service within the meaning of Regulation (EU) No 910/2014, unless expressly stated.

11.4. Fingerprints and certificate. Each file sent is given a SHA-256 fingerprint. A delivery certificate in PDF format summarises the Delivery identifier, the sender, the Recipient, the fingerprints, the timestamps, the accepted undertaking and a verification code. Anyone may verify that a file corresponds to a Delivery by dropping it on the verification page: the fingerprint is computed locally in the browser, and the file is not transmitted to the Publisher.

11.5. Reminders and confirmation of deletion. Where the Delivery provides for deletion on a due date, the Recipient receives a reminder the day before and on the day of the due date, by e-mail and, optionally, by SMS. They are asked to confirm the deletion of the documents and of any copies; their confirmation, or the absence thereof, is recorded in the Delivery’s evidence vault. The Recipient undertakes to respond in good faith.

11.6. Recipient obligations. The Recipient complies with the usage rules and the accepted undertaking. They do not distribute the documents to unauthorised third parties, do not remove watermarks and do not keep any copy beyond the agreed period. The Customer may rely, against the Recipient, on the undertaking and on the contents of the evidence vault.

Article 12 — Electronic communications

12.1. The Service sends Users only those messages necessary for its operation: invitations, reminders configured by the Customer, one-time codes, submission receipts, notifications of a new version or of an access request, certificates, and security and service information. These messages are sent on behalf of the Customer, who is identified in them, from the domains and numbers of the Publisher or its providers.

12.2. The Publisher sends no commercial prospecting messages to Participants. Participants who no longer wish to receive reminders for a given Request should contact the Customer, which alone is able to stop them; they may also write to support@hubflow.cloud, in which case the Publisher forwards the request to the Customer.

12.3. Users are invited to verify the origin of the messages they receive: links from the Service point exclusively to the hubflow.cloud domains and their subdomains, or to the Customer’s custom domain where one has been configured. The Publisher never asks for passwords, bank details or payment by e-mail or SMS. Any suspicious message may be reported to security@hubflow.cloud.

Article 13 — Content: ownership, technical licence and liability

13.1. Content remains the property of the User who submits it or of the person on whose behalf the User acts. The Publisher acquires no intellectual property rights over Content.

13.2. The User grants the Publisher, for the period during which the Content is retained in the Service, only the technical, non-exclusive and royalty-free authorisation necessary to host it, back it up, display it, convert it for online viewing, transmit it to the persons designated by the Customer, compute its fingerprints, apply watermarks to it, automatically read its contents where the Customer has enabled this function, and delete it on the due date.

13.3. The Publisher exercises no prior control over Content and guarantees neither its lawfulness, nor its accuracy, nor its quality. Each User is solely responsible for the Content they submit, share or send. The Publisher acts as a hosting provider within the meaning of article 6 of French law no. 2004-575 of 21 June 2004 on confidence in the digital economy (LCEN) and of Regulation (EU) 2022/2065 (Digital Services Act); it promptly removes any manifestly unlawful Content notified to it under the conditions of Article 20.

13.4. The Customer alone decides who has access to its Content and how long it is retained. On the date set by the Customer, the Content is deleted; the deletion is logged together with the fingerprint of the deleted file.

Article 14 — Publisher’s intellectual property

14.1. The Service, its software, architecture, databases, interfaces, graphic elements, texts, Documentation, library of templates for Requests, items, reminders and undertakings, as well as the name “Hubflow”, its logos and domain names, are the exclusive property of the Publisher or its licensors and are protected by the French Intellectual Property Code and international conventions.

14.2. The User enjoys a mere right to use the Service, which is personal, non-exclusive and non-transferable, for the period and purposes provided for in the Terms of Use and, for Team Members, in the Customer’s contract. Any reproduction, representation, adaptation, extraction, decompilation or exploitation not expressly authorised, of all or part of the Service or its components, is prohibited and constitutes infringement.

14.3. The templates made available in the library are generic examples, provided as an aid to configuration and without any guarantee of suitability for a particular situation; they do not constitute legal advice. The Customer adapts them under its own responsibility.

14.4. Suggestions and feedback sent to the Publisher by Users may be freely used by the Publisher to improve the Service, without consideration.

Article 15 — API and webhooks

15.1. The public API and webhooks allow authorised Team Members to automate use of the Service from the Customer’s applications, in accordance with the Documentation. An API key gives access to a single Workspace, with the rights of the Team Member who created it; actions performed by means of a key are attributed to the Customer.

15.2. API Users comply with the Documentation and with the rate and volume limits the Publisher may apply to preserve the quality of the Service; they design their processing so as to ignore unknown fields and to handle events idempotently; they verify the signature of webhooks before processing them; they keep secrets server-side. “Test” environment keys read and write the same data as “live” keys in the absence of an isolated sandbox, as stated in the Documentation.

15.3. It is prohibited to use the API to circumvent the rules of the Service, to extract data in bulk unrelated to the Customer’s activity, or to access the data of another Workspace. The Publisher may revoke a key or disable a webhook in the event of abusive use or a security risk, after informing the Customer except in an emergency.

Article 16 — Third-party integrations

The Customer may connect third-party services to its Workspace: online storage (Google Drive, Microsoft SharePoint and OneDrive, Dropbox), automation platforms (Zapier, Make), identity providers (Google Workspace, Microsoft Entra, Okta) and business software via the API. These connections are enabled by an Administrator, who authorises the corresponding data exchanges and accepts the terms of the third-party providers. Content exported to a third-party service is subject to the terms and security of that service; the Publisher is not responsible for it. An Administrator may disconnect an integration at any time from the Workspace settings.

Article 17 — Personal data, cookies and local storage

17.1. Participants. Participants’ personal data (identity, contact details, content of documents, access logs) are processed on behalf of the Customer, which is the controller within the meaning of Regulation (EU) 2016/679 (GDPR), for the purposes it determines: compiling a file, performing an engagement, sharing or sending documents in the context of its relationship with the Participant. The Publisher acts as processor, on the Customer’s instructions, under the conditions of the data processing agreement. For any question about this processing and to exercise their rights of access, rectification, erasure, restriction, objection and portability, Participants should contact the Customer, who is identified on the access page and in the messages received. The Publisher forwards to the Customer any request it receives directly and assists the Customer in responding.

17.2. Team Members and visitors. The data necessary for managing Team Member accounts, for the security of the Service, for support and for the website forms are processed by the Publisher as controller, under the conditions of the privacy policy. Data subjects exercise their rights with the Publisher at support@hubflow.cloud, for the attention of the data protection officer, and may lodge a complaint with the CNIL (the French data protection authority).

17.3. Hosting. Data are hosted in France, in the Paris region of Scaleway SAS, including backups. No data are transferred outside the European Union.

17.4. Cookies and local storage. The website and the Service use only strictly necessary cookies and local storage items: maintaining the sign-in session, protection against fraudulent requests, remembering language and display preferences. These items are exempt from consent within the meaning of article 82 of the French Data Protection Act (loi Informatique et Libertés). No advertising tracker or third-party audience measurement tool is set without the User’s prior consent.

Article 18 — Audit log, timestamping and evidence

18.1. Actions performed in the Service (sign-ins, creations, submissions, views, downloads, approvals, rejections, modifications, deletions, acceptances of undertakings, sending of messages) are recorded in a timestamped audit log, together with the identity of their author and their IP address. The log may be viewed and exported by the Customer; it is retained for three (3) years from each event, then deleted or anonymised.

18.2. Users acknowledge that the Service’s records, SHA-256 fingerprints, timestamps and delivery certificates may be produced by the Customer or the Publisher as evidence of the operations carried out in the Service, in accordance with articles 1366 et seq. of the French Civil Code, their evidential value being assessed by the competent courts.

Article 19 — Availability, maintenance and changes

19.1. The Publisher endeavours to keep the Service accessible at all times. It may nevertheless temporarily interrupt access for maintenance operations, announced in advance where possible and preferably carried out outside business hours in France, or in the event of an emergency relating to security or the integrity of Content. The service level commitments owed to the Customer are set out in the Terms of Sale; no availability commitment is made to Participants.

19.2. The Publisher develops the Service on an ongoing basis: adding, modifying or removing features, changing interfaces. Users are informed of significant changes within the Service or through the Documentation.

19.3. The availability of a Request, a Resource or a Delivery to a Participant also depends on the Customer’s choices: expiry dates, revocation of access, deletion on the due date, end of the Customer’s subscription. The Publisher does not guarantee Participants continued access beyond these limits.

Article 20 — Reporting, suspension and removal of content

20.1. Reporting. Anyone may report to the Publisher Content or a use they consider unlawful or contrary to the Terms of Use, at support@hubflow.cloud, stating their identity and contact details, the precise location of the Content (link), the grounds for the report and, where applicable, a copy of the correspondence sent to the author. The Publisher acknowledges receipt, examines the report diligently and informs the person who made the report of the action taken. An abusive report engages the liability of its author.

20.2. Responsible disclosure. Security vulnerabilities are reported to security@hubflow.cloud; the Publisher acknowledges receipt within 72 hours. The Publisher undertakes not to bring proceedings against any person who, in good faith, reports a vulnerability to it without exploiting it, without accessing Content beyond what is strictly necessary for the demonstration, without disrupting the Service and without disclosing the vulnerability before it has been fixed.

20.3. Measures. In the event of a breach of the Terms of Use, a risk to the security of the Service or of Users, manifestly unlawful Content or an order from a competent authority, the Publisher may, in a proportionate manner: warn the User or the Customer; suspend a link, an account, an API key or an access; make Content inaccessible or remove it; inform the authorities. Except in an emergency or where prohibited by law, the User or Customer concerned is informed of the measure and its grounds and may submit observations to support@hubflow.cloud. Measures are lifted as soon as their cause ceases to exist.

Article 21 — Liability and warranties

21.1. The Publisher implements the means necessary to provide a secure Service that conforms to its Documentation. It does not guarantee that the Service will be free from any defect or interruption, nor that it will meet the particular needs of each User.

21.2. The Publisher does not control Content and guarantees neither its lawfulness, nor its accuracy, nor its authenticity, nor the decisions Users take on the basis of it. It is not a party to the relationship between the Customer and its Participants: requests for items, rejection of documents, undertakings, deadlines, reminders and the consequences of an incomplete file fall exclusively within that relationship.

21.3. The Publisher cannot be held liable for damage resulting from: use of the Service that does not comply with the Terms of Use or the Documentation; the disclosure or loss of Credentials by a User; a failure of the User’s equipment, software or connections; third-party services connected by the Customer; a decision taken on the basis of the results of the automatic verification; a Recipient’s failure to comply with an accepted undertaking; a case of force majeure.

21.4. Towards the Customer, the Publisher’s liability is limited under the conditions of the Terms of Sale. Towards other Users, the Publisher may be held liable only for direct damage resulting from a proven fault in the provision of the Service, to the extent permitted by law. Nothing in the Terms of Use limits the Publisher’s liability in the event of gross negligence or wilful misconduct, personal injury, or in cases where the law prohibits such limitation.

21.5. Users are liable for damage caused to the Publisher or to third parties by their breach of the Terms of Use, and indemnify the Publisher against any third-party claim based on the Content they have submitted or on their use of the Service.

Article 22 — Term, end of use and deletion

22.1. The Terms of Use apply throughout the period during which the User uses the Service and, for those provisions which by their nature so provide (intellectual property, liability, evidence, confidentiality of accepted undertakings), beyond that period.

22.2. A Team Member’s account ends upon its removal by the Administrator or at the end of the Customer’s subscription. A Participant’s access ends upon the expiry of their link, the revocation of their access by the Customer, the deletion of the Request, Resource or Delivery concerned, or the end of the Customer’s subscription. Participants are invited to keep, during the access period, a copy of the documents they may need, in compliance with the usage rules set by the Customer.

22.3. At the end of the Customer’s subscription, the Content of its Workspace is returned to the Customer and then deleted under the conditions set out in the Terms of Sale.

Article 23 — Amendment of the Terms of Use

The Publisher may amend the Terms of Use to reflect changes in the Service, in regulations or in case law. The current, dated version is permanently published on this page. In the event of a substantial amendment, Team Members are informed within the Service or by e-mail at least thirty (30) days before it comes into force, and Participants through the access page to which their link leads. Continued use of the Service after the amendment comes into force constitutes acceptance of the new version. Amendments required by law apply immediately.

Article 24 — General provisions

24.1. If any provision of the Terms of Use is declared null and void or unenforceable, the other provisions shall remain in full force and effect.

24.2. The Publisher’s failure to rely on a breach of the Terms of Use does not constitute a waiver of its right to rely on it subsequently.

24.3. The Terms of Use are drawn up in French. Any translation is provided for convenience only; in the event of discrepancy, the French version prevails.

24.4. The Terms of Use may be consulted at any time at hubflow.cloud/en/cgu/ and printed or saved by any User. The Publisher archives successive versions and provides them on request.

Article 25 — Governing law and jurisdiction

25.1. The Terms of Use are governed by French law.

25.2. Any dispute relating to their interpretation or performance shall first be the subject of an attempt to reach an amicable solution. Failing this, and for Users acting in a professional capacity, the dispute shall be submitted to the exclusive jurisdiction of the Reims commercial court (tribunal des activités économiques), notwithstanding multiple defendants or third-party proceedings. For Users who are natural persons not acting for professional purposes, the statutory rules of jurisdiction apply; they may have free recourse to a consumer mediator under the conditions of articles L611-1 et seq. of the French Consumer Code, or to the European online dispute resolution platform.

Contact

SAS MEDUZA STUDIO — Hubflow — 126 boulevard Saint-Marceaux, 51100 Reims, France. Questions and reports: support@hubflow.cloud. Vulnerabilities and security incidents: security@hubflow.cloud.