Privacy Policy
Last updated: 18 November 2026
This is a translation provided for convenience. The German version is legally binding; in case of any discrepancy, the German version prevails.
FLIORE is built for confidentiality. This policy explains what personal data we process, why, where it is hosted, who may access it, and the rights available to individuals. It is provided for transparency and does not replace the Data Processing Agreement (DPA) entered into with each organisation, which prevails in case of conflict.
1. Who is responsible (controller / processor)
FLIORE is operated by Innopulse Consulting GmbH, Gotthardstrasse 30, 6300 Zug, Switzerland (UID CHE-219.727.921). For personal data that an organisation uploads or processes through FLIORE (its mandates, beneficial owners, documents and transactions), the organisation is the controller and FLIORE acts as its processor, processing that data only on the organisation's documented instructions. For data we process about our own account holders (name, email address, authentication and billing data), FLIORE is the controller. FLIORE is organised in workspaces: each workspace is a separate data space with its own members, settings and subscription. The controller for a workspace's data is the organisation for which it is run; its owner manages members, roles and the subscription. Data is not linked across workspaces. Members of several workspaces see in the “My day – all workspaces” overview only the tasks assigned to them in those workspaces.
2. What data we process
As processor, on behalf of an organisation: mandate and entity records; details of persons in mandates and in the people register, such as beneficial owners, beneficiaries and officers (name, title, dates of birth and death, place of birth, nationalities, tax residency, marital status, occupation, PEP status) and identity-document data (type, number, issuing country, issue and expiry date); documents stored in the vault; transactions and bank-statement data; screening and risk-assessment results; messages. As controller, for account holders: name, email address, optionally a profile picture (resized by the server, without location or other metadata, visible only in shared workspaces), hashed authentication factors, language, role, logs and billing information. We do not intentionally collect sensitive personal data unless an organisation chooses to store it within its own documents. If account holders change their sign-in email, the new address only takes effect after confirmation via a link; the change is logged.
3. Purposes and legal bases
To provide the service under our contract with the organisation; to secure the platform and prevent abuse (overriding legitimate interest); to meet legal and regulatory obligations; and, for account data, to administer billing. Where required, processing of personal data from the EU relies on the corresponding GDPR legal bases (contract, legal obligation, legitimate interest). FLIORE does not sell personal data and does not use client data for advertising.
4. Where data is hosted
FLIORE stores application data and documents on Swiss cloud infrastructure (Supabase, data centre in Zurich, Switzerland); Swiss data-protection law applies. Where a subprocessor processes limited data outside Switzerland (see the Subprocessors page), that disclosure is covered by appropriate safeguards such as the EU Standard Contractual Clauses with the Swiss addendum.
5. Subprocessors
FLIORE uses a small number of vetted subprocessors to run the service (hosting, email delivery, payments and the AI provider). Each is bound by data-protection terms and processes only the data needed for its function. The current list, with the purpose and location of each, is maintained on the Subprocessors page.
6. How data is protected
Two-factor authentication for every account, which each organisation can make mandatory for all of its members; row-level security enforcing strict separation of organisations at the database layer, so no organisation can access another's data; encryption of documents and particularly sensitive details (identity document and tax identification numbers, account numbers, access credentials, message content, source-of-funds details) within the application using a separate key per organisation (AES-256-GCM), with documents delivered only after a permission check; and an immutable audit trail of security-relevant actions whose entries are cryptographically chained (hash chain with a daily checksum). Access by our personnel is restricted, logged and used only to operate and support the service. Two-factor authentication is voluntary; if an organisation requires it, we additionally enforce the requirement at database level. When you sign in with Google or Microsoft, we receive your name and e-mail address from the provider, never your password; we accept Microsoft accounts only with an e-mail domain verified by the organisation. To protect your account we store, for each sign-in, the device (browser and operating system), a shortened IP address and the time, show this list under Settings › Security and inform you by e-mail about sign-ins from new devices; entries of ended sessions are deleted after 180 days. For passkeys we store only the public key – biometric data never leaves your device. You confirm security-critical actions (such as exports, payment approvals or new keys) with a code from your authenticator app, a passkey or a code sent by e-mail. We store security-relevant events of your account (sign-ins and failed attempts, new devices, changes to your password, two-factor sign-in and passkeys, exports, new keys, access by platform staff) with a shortened IP address and the device name for 400 days, show them to you under Settings › Security › Security activity and warn you by email if something looks unusual; the owners of your organisation are informed about events that affect the whole organisation (for example exports shortly after a sign-in from a new device). To protect against payment fraud, new payees and changed bank details require approval by a second person and can only be used 24 hours later; the owners receive an email in which the account number (IBAN) appears only masked. To detect data leaks, we place invisible canaries in every organisation (an unusable access key, a link and a control document, none containing personal data); if one of them is used, we notify the owners and our operations team immediately. The legal basis is our legitimate interest in the security of the service; where the organisation’s data is concerned, we act on its behalf.
7. AI and your data
FLIORE AI answers only from the data of the respective mandate within the organisation and cites the data it draws on. When you ask the assistant a question, the relevant mandate context – which may include names and PEP flags of beneficial owners, asset and liability figures, KYC status and document titles – is sent to the configured AI provider (by default Anthropic; optionally OpenAI or Azure OpenAI) solely to generate that answer. Client data is never used to train models and is not retained by the provider for any other purpose. Each provider is listed on the Subprocessors page. Organisations can disable AI entirely or bring their own AI key (BYOK) so that requests run under their own provider agreement. AI output is decision support: it supports, but does not replace, the judgement of the responsible person.
8. Retention
As processor, we retain an organisation's data for the life of the account and delete or return it after termination in line with the DPA, subject to any retention the organisation must observe (for example statutory record-keeping periods under anti-money-laundering law). Account and billing data we hold as controller is retained for as long as the law requires. Logs are retained to meet security and regulatory requirements. When an organisation is deleted, we remove all of its data completely once the 30-day restoration period has passed – including stored files and the sign-in accounts of its members; the audit trail is kept as evidence where a retention duty applies. Deleted documents stay in the trash for 30 days, longer while a statutory retention period is running; only owners and admins can see them, after which file and record are deleted permanently. Owners and compliance officers can create a full export of all workspace data at any time (ZIP with tables, original documents and checksums). The owner can restore a deleted workspace for 30 days; after that its data is deleted permanently. When the business relationship with a mandate ends, FLIORE calculates the retention period from that day; once it has expired, the affected documents are automatically moved to the trash and identity data is deleted – both are recorded in the audit trail, and owners and compliance see upcoming deletions 90 days in advance. We store error logs without personal data (email addresses, account numbers, phone numbers and credentials are removed before storage) and delete them after 90 days.
9. Rights of individuals
Depending on applicable law (the Swiss Federal Act on Data Protection, FADP, and, for individuals in the EU, the GDPR), individuals may request access, correction, deletion, restriction and data portability, or object to certain processing. Because most personal data in FLIORE is under the responsibility of the organisation that uploaded it, requests about that data should be directed to that organisation; FLIORE assists it as processor. For data for which we are the controller, contact us directly. We record requests concerning your FLIORE account in a register and answer them within 30 days. On request you receive all personal data of your account in a machine-readable format (JSON). On erasure we anonymise your name and e-mail address and remove your sign-in; entries subject to statutory retention (such as logs under anti-money-laundering or commercial law) remain until the end of the retention period but then only refer to an anonymised identifier. Every action taken on a request is logged immutably.
10. International transfers
Where personal data is disclosed to a subprocessor outside Switzerland or the EEA, we rely on recognised transfer mechanisms (adequacy decision, EU Standard Contractual Clauses with the Swiss addendum) and apply additional technical measures such as encryption in transit.
11. Changes to this policy
We may update this policy to reflect changes in the service or the law. Material changes will be communicated to account holders. The date shown above always identifies the current version.
12. Website, contact form and support
FLIORE is the controller for this processing. When you visit the website, our hosting provider processes technically necessary data (IP address, time, requested address, browser identifier) to deliver the pages and defend against attacks; these logs are kept for a short period. We also measure in the browser how quickly the website and the application load and respond (main content load time, input response, layout shifts, duration of page changes). Only the page path without identifiers, the measured values and the device class (mobile or desktop) are transmitted – without cookies and without any link to an account. The IP address is used only briefly to limit the number of requests and is not stored with the measurements; we delete the measurements after 90 days. If «Global Privacy Control» or «Do Not Track» is enabled in your browser, no measurement takes place. The legal basis is our legitimate interest in stable and fast operation. If you request a demo through the form or write to us, we process your name, your email address, your company and role, the type of your organisation, the language of the website and your message to answer your request, and keep them for as long as this and any follow-up questions require. You receive a confirmation of receipt by email; it is sent through our email service provider (see the Subprocessors page). Your IP address is used only briefly to limit the number of requests and is not stored with your request. Support requests from the application are stored with your account and handled by our team. You may ask us to delete this data at any time.
13. Demo workspace
You can try FLIORE without registering in your own demo workspace with fictitious sample data. For this we create a technical account with a random address that is not linked to you; we ask for no email address and no payment details and send no emails from the demo. We process the data you enter in the demo yourself and your IP address, which is stored briefly to prevent abuse (limiting the number of demos) and then removed automatically. Access ends after 24 hours. We then delete the demo workspace completely – data, files and the technical account – at the latest 48 hours after it was created. You can end the demo yourself at any time; it is then deleted immediately. Please do not enter real personal or client data in the demo. The legal basis is our legitimate interest in demonstrating the software to interested parties, or pre-contractual measures.
14. Guest access per mandate
Customers can give external parties (e.g. tax advisers, auditors, law firms, banks) time-limited access to individual mandates. For this we process on the customer's behalf: the guest's e-mail address and name, the permissions granted, expiry and note, and a log of every access (invitation, acceptance, view, download, upload, extension, revocation, expiry). Guests see only the shared mandates; they receive master data with fixed fields (name, structure, roles), without ID numbers or comparable details. On download, PDFs and images are marked with the guest's name, the workspace, date and time; the marked copy is kept in non-public storage, is retrievable via a link valid for 60 seconds and is deleted after one day at the latest. We keep the access logs like the rest of the customer's audit log. The inviting organisation is responsible towards guests; guests address requests for access, rectification or erasure to it.
15. Contact
Innopulse Consulting GmbH, Gotthardstrasse 30, 6300 Zug, Switzerland – hello@fliore.com.
This page is provided for transparency and general information. It is not legal advice. The Data Processing Agreement and applicable law govern the actual rights and obligations of the parties.
