Conflo Studio

Terms of Use and Sale

Draft. This text is a draft under review by a lawyer. It does not bind the publisher yet; the marked fields are still to be completed. The French version prevails.

Version: [TO BE COMPLETED: effective date]

1. Who we are

The Conflo Studio service (the "Service"), available at https://app.conflostudio.com, is published by Jean Carboni, sole proprietor (entrepreneur individuel), SIREN 917 410 979, whose place of business is [TO BE COMPLETED: business address], EU VAT number [TO BE COMPLETED], reachable at contact@conflostudio.com (the "Publisher").

2. Purpose and scope

These terms (the "Terms") govern access to and use of the Service by professionals (the "Customer"): companies, associations, freelancers, acting for the purposes of their business. The Service is not intended for consumers.

They apply to the Service hosted by the Publisher. An instance installed at the Customer's premises is governed by a separate agreement [TO BE COMPLETED if this offer exists].

By creating an organization, accepting an invitation or subscribing to a plan, the Customer and its users accept these Terms. The data processing agreement (GDPR annex) and the list of subprocessors form part of them.

3. The Service

Conflo Studio is a tool for designing application screens: the Customer assembles the components of its own code (its "kit"), turns them into clickable prototypes and flow sheets, exchanges comments, and can design the back end of its application (Back module). The Service is made of:

  • one organization per Customer, which groups its members and projects;
  • projects, which hold screens, sheets, data scenarios, kits and, when the module is on, the designed back end;
  • an MCP server through which an artificial intelligence agent that the Customer chooses to connect can read and change its projects (section 8).

The Publisher may change the Service. A change that removes an essential feature of a paid plan is announced [TO BE CONFIRMED: notice period] in advance.

4. Accounts and access

Entry. One enters an organization when one of its administrators invites them: an address nobody invited does not get in. When the Publisher opens free sign-up, a person may also ask for a trial for their own organization: the request is examined by hand by the Publisher, who accepts or refuses it, and nothing is opened before it is accepted. Once accepted, the person becomes the owner of the organization and gets in at their next sign-in (section 5).

Sign-in. Sign-in is through a Google account. Sign-in with a Microsoft account is planned and not available yet. The Service sends no e-mail: invitations are drafted by the Service and sent by the person inviting, from their own mailbox.

Roles. In an organization: owner, administrator, member, guest. On a project: editor (changes and publishes), reviewer (reads, comments, approves or rejects a draft), guest (reads the projects they are invited to). The Customer assigns these roles and answers for what its users do with them.

Access security. The Customer keeps its access and personal tokens confidential, and promptly closes the access of anyone who leaves its team. Each user can see their open sessions and close one remotely. After ten refused sign-ins in a row, the address and the account concerned are blocked for fifteen minutes.

5. Plans

There is no free plan. The Service offers a single offer, everything included (screens and back), preceded by a trial.

PlanTermProjectsEditorsBack moduleStorage (kit / total)Price
Trial14 days, on accepted requestunlimited2 (more on request to the Publisher)included50 MB / 1,000 MB [TO BE CONFIRMED]no charge
The offeras subscribedunlimitedpaid per editorincluded50 MB / 5,000 MB [TO BE CONFIRMED][TO BE COMPLETED: price, announced when online payment opens]
  • An editor, who therefore takes a paid seat, is: the owner, an administrator, or anyone who is an editor on at least one project. Reviewers and guests are free. The account of the organization's agent (section 8) and the support access (section 10) take no seat.
  • The demonstration project offered by the Service does not count against the project limit.
  • An action that would exceed the plan (one editor, project or kit too many, storage full) is refused with a message saying what to do; it is never billed automatically.
  • The trial is opened on request, from the sign-up page. The number of trials open at the same time is limited: when every place is taken, the page says so and takes no more requests. The Publisher accepts or refuses each request at its discretion, without having to give reasons for a refusal. The trial lasts 14 days from its acceptance; the Publisher may extend it. During the trial, a band says the days left.
  • At the end of the trial without a subscription, the organization becomes read only: its members may only look at its Content in the studio, from a browser, export it (section 7) and delete it (section 14). Nothing can be created or changed in it any more (screens, drafts, threads, kits, code checks), and no personal token nor artificial intelligence agent has access to it any more. The Content is kept [TO BE COMPLETED: how long after the end of the trial, then deletion].

6. Prices, invoicing, payment

[TO BE COMPLETED: billing period (monthly, yearly), invoicing date and method, payment method, VAT (the Publisher is liable for it), late-payment penalties and the €40 fixed recovery fee due between professionals, price revision and its notice.]

Online payment through a payment provider (Stripe) is planned and not in place yet. The number of editors billed is [TO BE COMPLETED: the number of seats subscribed, or the number of editors counted on a given date].

7. The Customer's content

Ownership. The screens, sheets, scenarios, kits, designed back end, comments and anything the Customer puts into the Service (the "Content") remain its property. The Customer grants the Publisher only the right to host, display and process them in order to provide the Service.

Responsibility. The Customer warrants that it has the right to put its Content into the Service, in particular its components' code and its scenarios' data. It avoids placing real personal data there when fictitious data will do.

Confidentiality. Nobody at the Publisher reads an organization's Content unless that organization has decided so (section 10). Content is encrypted with a key specific to each organization.

What is visible outside the organization. What the Customer chooses to show: a presentation link (a project's prototype, optionally protected by a password and an end date, revocable at any time), or an integration it connects (section 9). A kit's files are served by their address, without a session, to whoever knows it; only the project's readers learn it.

Export. An administrator may at any time export a project or the whole organization as a readable JSON file, which can be imported into another organization.

8. Artificial intelligence

  • Content trains no artificial intelligence model, and the Service itself sends none of it to a model.
  • Content reaches an AI only through an agent that the organization connects: an administrator allows or forbids agents and issues the tokens of the organization's agent. Everything that agent reads and writes is recorded in the organization's audit log. An agent has no publishing action: what it changes in an existing screen goes into a draft, which a person publishes or discards.
  • The agent's provider is chosen by the Customer and contracts with it; the Publisher is not liable for it.
  • A user may also use their own personal token with a tool of their choice; that token stands for the user themself, with their rights, and is the Customer's responsibility.

9. Integrations

The Customer may connect third-party services, project by project: Discord, Slack or Teams channels (announcement of opened threads, replies, resolved threads, publications — with an excerpt of the comment), Jira and GitHub (ticket creation). What the Service sends there leaves on the Customer's decision and is subject to those services' terms. The addresses and tokens of these integrations are stored encrypted.

10. Support

Support can enter an organization only if one of its administrators opens an access, for 1, 4, 24 or 72 hours, read-only or not. While it is open, a banner tells every member; the administrator may close it at any time. The opening, the closing, support's entry and every screen it reads are recorded in the organization's audit log.

Outside this access, the Publisher sees of organizations only numbers (plan, seats, number of members and projects, last activity), never the name of a project or a screen.

Support contact: [TO BE COMPLETED: address and response times].

11. Availability, backups

The Publisher uses its best efforts to keep the Service available, without an availability rate commitment [TO BE CONFIRMED: figure for the Enterprise plan]. Maintenance interruptions may occur [TO BE COMPLETED: notice].

The database is backed up every night and each backup is kept 14 days on the server. An encrypted copy of each backup is sent off the server and kept 30 days [planned: active once the external storage is opened]. A backup is test-restored every week.

12. Acceptable use

The Customer shall not, and shall ensure its users do not: circumvent its plan's limits or the Service's protections, test its security without written consent, deliberately overload it (a request limit applies), put unlawful content or content it has no rights to into it, or use it to send unsolicited messages.

13. Suspension

The Publisher may suspend an organization for a serious breach of these Terms, non-payment [TO BE COMPLETED: after a formal notice left without effect for … days] or a risk to the Service's security. Suspension closes the sessions and refuses any entry; Content is kept and the Customer is informed [TO BE COMPLETED: how and when].

14. Term, termination, fate of the data

  • The trial lasts 14 days, which the Publisher may extend; at its end without a subscription, the organization is read only (section 5). The offer is subscribed for [TO BE COMPLETED: term, renewal, termination notice].
  • Deletion: an administrator may delete a project, and the owner the whole organization. Deletion can be cancelled for 30 days; after that, everything is erased from the database. The backups that still contain it then expire on their own: at most 14 days later on the server, 30 days later for the off-server copies.
  • Before deleting, the Customer may export its Content (section 7). Deleting a project downloads its export just before.
  • A user may delete their own account; what they did in projects remains, signed "deleted account".
  • [TO BE COMPLETED: fate of the Content at the end of a paid subscription that is not renewed — read only as at the end of a trial, or deleted after a period.]

15. Liability

The Publisher is bound by an obligation of means (best efforts). [TO BE COMPLETED: liability cap, exclusion of indirect damages, force majeure.] The Customer remains responsible for its Content, its roles and access, and the third-party services it connects.

16. The Publisher's intellectual property

The Service, its code, the "Conflo" brand and its logos remain the Publisher's property [TO BE CONFIRMED: trademark filing status]. The conflo npm package, which the Customer installs in its own repository to build its kit, is distributed under its own licence [TO BE COMPLETED: package licence].

17. Personal data

The Publisher processes users' personal data in accordance with its privacy policy. For the personal data contained in the Content and that of the organization's members, it acts as the Customer's processor, under the attached data processing agreement.

18. Changes to the Terms

The Publisher may change these Terms. A change that affects the Customer's rights is notified [TO BE CONFIRMED: period] before it takes effect; a Customer who refuses it may terminate without charge before that date.

19. Governing law, disputes

These Terms are governed by French law. Failing an amicable settlement, any dispute is brought before [TO BE COMPLETED: competent court].