At a glance
- Browsing, requesting information or sending an activation enquiry from the website does not start a subscription or prove contract acceptance.
- Plan, environment, included services and trial/free-tier conditions must be identified before joining. A licence key is not itself contractual evidence.
- Customer and provider are responsible for activities within their remit. Automations, AI and third-party services do not remove provider obligations.
1. Provider, scope and definitions
The Provider is BizCom.IT S.r.l., registered office Via Palombarino 8, Osimo (AN), Italy, VAT number 02621920426, REA AN202301. Operating office: Via Primo Maggio 20, 60131 Ancona (AN). Contractual communications: amministrazione@bizcom.it or certified email (PEC) BIZCOMITSRL@PEC.IT.
The Customer is the party joining the service through a person with the necessary authority. An Authorised User is a person enabled to use the platform for the Customer. Organisation or tenant means a logical environment: it is not automatically a separate contracting party, and technical administrator status does not itself confer authority to legally bind the Customer.
SaaS service means access to software in the hosted environment supplied by the Provider; installation in the Customer's environment means software running on infrastructure within its remit. Plan and specific conditions identify the functions, limits, duration and services actually included.
FlowSharp primarily serves organisations and professional users. This page does not introduce an absolute exclusion of consumers: all applicable mandatory protections remain unaffected.
2. Joining, trials and free tiers
In an offer or order process, the agreement is formed under the communicated proposal and acceptance by the authorised party, through the arrangements set out in the relationship's documents. Browsing and demo, information or activation enquiries do not start a subscription.
This website's process collects enquiries for the team: it does not automatically create an account, trial or contract. In self-service, trial or free-tier activation processes, applicable conditions must be made available and accepted before joining in the system managing that process; a separately signed offer is not presumed always to exist.
Identifiable process conditions include at least the terms version, plan, hosted or installed environment, limits, duration and consequences of trial or licence expiry. Requesting a key and technical activation do not themselves prove terms acceptance. Contract acceptance remains distinct from reading the privacy notice and optional marketing consent.
A generic checkbox is not treated as specific approval of every clause: provisions requiring such approval follow legally appropriate methods and checks. You can save and print these terms from this page before deciding.
3. Agreement documents and precedence
The relationship includes documents actually referenced and accepted: these terms, any offer or order, the identified plan's conditions, any SLA, special conditions and DPA. Trials and free tiers also depend on identifiable conditions in their respective process, not solely an offer that may not exist.
Specifically agreed conditions prevail in a conflict; the DPA prevails within its scope for processing on the Customer's behalf. Mandatory rules remain applicable. This page does not declare a DPA signed or an SLA included where agreements do not establish this.
Updated website prices, roadmaps, demos and changelogs do not retrospectively amend an agreement or automatically add functions or rights to a purchased plan.
4. Usage rights, features and licences
Within the agreed scope the Customer may access and use the service or install the software without acquiring ownership. Partners, resellers and multi-organisation environments follow expressly authorised rights: usage limits do not exclude these agreed models.
Official builds require activation. Online and offline licences are supported; functions and limits may differ between installation and individual tenants. Online licensing depends on communications with the portal for licensing operations; offline mode applies where offered under service conditions and does not automatically synchronise.
The product technically returns to Free entitlements on licence expiry. This is distinct from suspension and does not promise perpetual free SaaS hosting, indefinite environment access or unlimited data retention. Temporary feature availability does not automatically confer additional contractual rights.
Included features, volumes, users, AI usage, environments and support follow the identified plan. A trial's duration or plan is not presumed from technical documentation alone: the conditions presented and accepted in the actual process apply.
5. SaaS and Customer environment: operational activities
Each party is responsible for the components and activities it manages. The table distinguishes scope without attesting undocumented procedures, backup frequencies or recovery times. The Provider remains responsible for its own activities and defects within its remit, including where the Customer configures processes or uses external services.
| Component / activity | Provider | Customer | Specific agreement |
|---|---|---|---|
| Infrastructure | SaaS: manages the hosting components it supplies. Customer environment: supplies the software and any agreed installation work. | SaaS: manages its own devices, connectivity and access. Customer environment: manages infrastructure under its control. | Identification of the environment and managed scope. |
| Updates | SaaS: maintains updates to managed components. Customer environment: makes updates and work available under the agreed usage rights and support. | Assesses its configurations and integrations; in its managed environment coordinates installation, testing and dependencies within its remit. | Supported versions, release arrangements and commissioned work. |
| Backups | For managed components, performs the backup activities it has undertaken; no specific frequency or complete backup of every connected system is presumed. | Manages copies of components within its remit and data in external systems under its control. | Scope, frequency, retention, access and backup checks. |
| Recovery | Performs recovery activities within the service or engagement; no unagreed recovery time is presumed. | Supplies request context and coordinates recovery of its components and integrations. | Procedure, scope, priorities and any SLA recovery commitments. |
| Monitoring and security | Protects and monitors managed components within applicable duties and undertaken activities. | Manages its credentials, users, permissions, processes and systems; cooperates on relevant reports. | Channels, access, event management and agreed interventions. |
| Support access | Limits work to the authorised scope and processes data under applicable roles, instructions and agreements. | Authorises necessary access to its environment and does not share secrets through public forms. | Authorisation, access methods, logging and DPA where relevant. |
| Integrations and automations | Is responsible for integrations it develops or manages within the engagement and its own obligations, including defects within its responsibility. | Configures destinations, permissions, data and controls for integrations within its remit; manages its own external contracts. | Connected systems, commissioned activities, retries, duplicate controls and agreed charges. |
6. Users, permissions and configuration
The Customer identifies authorised users, keeps roles and permissions current and protects credentials, API keys and secrets for its integrations. Users act within their assignments and promptly report suspicious access or compromised credentials.
The Customer manages its configurations and the suitability of its processes; the Provider meets proper service-delivery, access and support obligations for managed components. Tenant separation, audits and roles do not authorise access to other environments or replace organisational procedures.
7. Permitted use and security
The service must not be used for unlawful activities, infringement of third-party rights, malware, unauthorised access, compromising availability or security, or circumventing agreed limits. Resale and third-party provision follow authorised rights without preventing agreed partner or multi-organisation models.
Mandatory legal rights, including relevant interoperability rights, remain unaffected. Potentially invasive security tests require prior coordination; responsible vulnerability reports may be sent to info@bizcom.it without transmitting credentials or other people's data in public forms. Arbitrary revocation of usage rights without cause is not provided for.
8. Content, ownership and confidentiality
The Customer retains its rights to its data, documents and the configurations or processes it creates. This does not transfer rights to Provider software, documentation, templates or components incorporated in configurations, or to licensed third-party materials and components. The Customer holds the necessary permissions for submitted content.
The Provider uses content only for activities necessary to deliver, maintain and support the service under applicable agreements. These terms grant no general rights to commercial exploitation, publication, use of the Customer's logo or AI training. External provider conditions remain distinct, and exclusivity or protectability of every AI output is not guaranteed.
The parties mutually protect confidential information and restrict access to those needing it for the relationship under suitable obligations. Exceptions remain for legitimately public information, lawfully obtained or independently developed information and legally required disclosures. Confidentiality and protection-of-rights duties survive termination according to their nature and applicable agreements.
9. AI, automations and proportionate controls
The Customer configures the level of automation and controls appropriate to the process. AI outputs may be inaccurate or incomplete and require checks proportionate to purpose, risks and applicable duties. Where human approvals are necessary, they must be included in configuration and operating procedures.
Data Shield applies shielding and pseudonymisation in supported paths according to classification and configuration; pseudonymisation is reversible and does not mean total anonymisation. Data Gate checks availability of data needed for the process. Neither guarantees correct outputs or that no personal data is sent to external systems.
Automations may change data and perform actions on external systems. Approvals depend on function, permissions and configuration; retries and repetitions require controls and duplicate handling. Exactly-once execution is not promised for every integration, nor does this exclude responsibility for defects.
Purchase does not automatically produce GDPR, AI Act or sectoral compliance. The Customer assesses its processes, legal bases and safeguards; Provider duties are not transferred to the Customer. Enabling a feature or document for agent context is not the individual's GDPR consent.
10. Integrations and third-party services
Services chosen and contracted by the Customer, providers used by BizCom.IT to deliver the service and integrations developed or managed under an engagement are distinct. Using its own providers does not release BizCom.IT from obligations to the Customer.
APIs, webhooks, connectors and automation tools may transmit data and actions to external systems. Within their roles, parties check destinations, access rights, permissions, legal bases and applicable conditions. A technology name does not necessarily identify the service operator or data recipient.
External charges, essential dependencies and limits are communicated in the plan, order or agreed integration before the relevant commitment. No automatic charges or unagreed additional services are introduced.
11. Metrics and Saving Challenge
Time, cost, KPIs, baselines, estimates, simulations and measured results are distinct. Indicators depend on data quality, configuration and assumptions; this does not remove the Provider's responsibility to apply the product's stated methods correctly.
Demos and simulations do not guarantee a particular saving or economic result. Saving Challenge is a separate engagement with agreement on baseline, scope, duration, result verification, fees and success fees. Using Saving or analytics functions does not itself activate that engagement.
12. Personal data and roles
The privacy notice describes BizCom.IT's controller processing, including website, contacts, licensing and support in their respective context. For data entrusted to the Provider as processor, instructions, measures, subprocessors, transfers, rights assistance and deletion follow the applicable DPA. Access, licensing and case content do not automatically share one privacy role.
The Customer determines its processes' purposes, provides required notices and ensures necessary legal bases. The Provider meets its own role's obligations. Special-category, criminal-offence or restricted data requires checks of lawfulness, scope and measures before entry. Do not send passwords or unrequested confidential information through public forms.
13. Prices, duration, renewal and cancellation
Before joining, the plan, any fees and taxes, duration and conditions are identified, including for trials and free tiers. No automatic renewals, penalties, usage charges or purchase obligations not communicated and accepted are introduced.
Trial completion, licence expiry, commercial renewal, cancellation notice, withdrawal, hosting termination and data deletion are separate events. Technical return to Free entitlements does not itself determine the others. Prices and plans subsequently shown on the website do not replace accepted conditions.
For cancellation, withdrawal and contractual communications, email amministrazione@bizcom.it or certified email BIZCOMITSRL@PEC.IT, identifying the relationship and request. Statutory and accepted conditions' methods and periods apply: this page adds no invented commercial notice period. Switching to another provider is distinct and described in its own section.
14. Maintenance, changes and suspension
Scheduled maintenance, urgent work and functional changes are distinct from commercial changes. Guaranteed frequencies and timings depend on actual commitments; no numerical SLA does not mean no proper-delivery obligations. Beta status is not a general liability exemption.
Material changes require communications and remedies consistent with law and agreements. Continued browsing is not automatic acceptance of new conditions, and website updates do not retrospectively amend the contract.
Security, abuse, legal obligations and material breach may require proportionate measures, including suspension where permitted. Except for urgency or legal restrictions, the Customer receives notice with reasons and information to resolve the issue; restoration follows removal of causes and necessary checks. Indiscriminate suspension without cause is not provided for.
Technical licence suspension limits new writes and certain starts, but queued work and callbacks may continue. It does not immediately stop every automation or reverse effects on external systems. It differs from licence expiry and grants no additional contractual suspension right.
15. Exit, export and deletion
To initiate exit or request data return, email amministrazione@bizcom.it identifying the Customer, environment, authorised person, requested categories and destination. Do not include keys or passwords. Flow, map and Solution definitions, case data, history and logs, documents and attachments are separate categories.
Exporting a definition is not a complete tenant backup and does not automatically include operational data, attachments or integration secrets. Parties identify available functions and necessary return/support activities for uncovered elements. Switching also requires reconfiguration of connections and credentials, without presuming a full-export button.
Available format for each category, secure delivery method, authorisation checks, applicable timing and support are specified in request handling and agreements, subject to mandatory rights and the switching procedure below. Operation confirmation distinguishes what was returned or erased, remaining copies and applicable reasons or deadlines.
Closure coordinates database, storage, backups and external systems: immediate simultaneous erasure of every copy is not promised. Technical storage-cleanup intervals after tenant deletion are not a contractual retrieval period or recovery guarantee. Legal duties, legal holds and applicable DPA instructions remain.
16. Switching providers and the Data Act
For SaaS services falling within Chapter VI data processing services of Regulation (EU) 2023/2854, its switching provisions apply to another provider or the Customer's own infrastructure, including free-tier offerings. Ordinary termination does not replace that procedure. Article 31 special regimes depend on actual conditions: beta, trial or customised labels alone do not establish them.
Where applicable, switching notice does not exceed two months; transition takes place without undue delay and normally within thirty calendar days after notice. The Provider provides reasonable assistance, supports the exit strategy and maintains continuity and security under the Regulation. A data-retrieval period of at least thirty calendar days follows transition.
If the maximum transition is technically unfeasible, within fourteen working days of the request the Provider gives reasons and an alternative period no longer than seven months, maintaining required continuity. The Customer's right to extend transition once and other Article 25 conditions remain. Erasure of exportable data and assets follows completion of switching and retrieval, or a later agreed period, under applicable duties.
During the transitional charging regime any permitted switching charges do not exceed costs directly linked to the process and must be disclosed before contracting. From 12 January 2027, switching charges prohibited by Article 29 are not imposed. Obligations cannot be evaded by treating every necessary activity as extra consultancy; other lawful agreed fees remain distinct.
For the actual procedure, requests can use the contractual channel above. Exportable categories, any permitted exclusions, available methods and formats, technical limits and support conditions must be identifiable for the service without reducing applicable rights. This page does not itself attest completeness of technical switching tools.
17. Liability and warranties
The Provider's proper-delivery obligations and responsibility for its activities and persons it uses remain. The Customer is responsible for configurations and activities within its remit. Nothing excludes liability for wilful misconduct or gross negligence, limits mandatory rights or transfers Provider duties to the Customer.
No promise of an economic result does not remove responsibility for service defects or correct application of stated methods. AI, third-party services, beta status and absence of an SLA are not general exemptions. No financial caps, blanket exclusions of damages or unlimited indemnities are introduced.
Governance and security descriptions do not attest ISO certifications or automatic regulatory compliance. Specific warranties, special conditions and any necessary approvals follow law and actually accepted agreements.
18. Law, language and communications
Italian law applies, subject to mandatory rules and other validly agreed conditions. Jurisdiction follows law and agreements: this page introduces no unagreed exclusive forum.
Italian and English texts are available for transparency; Italian prevails for interpretation, subject to mandatory rights and any agreed contractual language. Date and version identify the text: changes to the relationship require applicable communication and acceptance procedures, not merely browsing.
Information: info@bizcom.it. Contracts, cancellation and switching: amministrazione@bizcom.it and certified email BIZCOMITSRL@PEC.IT. Personal data: privacy@bizcom.it. The registered office and other company contacts below remain available.
Company details and contacts
- Company name
- BizCom.IT S.r.l.
- Registered office
- Via Palombarino 8, Osimo (AN), Italia
- Operating office
- Via Primo Maggio 20, 60131 Ancona (AN), Italia
- VAT number
- 02621920426
- REA
- AN202301
- SDI code
- SZLUBAI
- info@bizcom.it
- Privacy email
- privacy@bizcom.it
- Administration and contracts email
- amministrazione@bizcom.it
- Certified email (PEC)
- BIZCOMITSRL@PEC.IT
- Phone
- 0712861468
- Website
- http://www.bizcom.it
