Fluent Commerce Logo
Docs

RFP Essential Knowledge: Data Management and Privacy

Essential knowledgeCore knowledge to understand Fluent Commerce

Author:

Michael Wholohan

Changed on:

29 May 2026

Overview

Fluent Commerce acts as a data processor for client data within the Fluent OMS. This article covers database security practices, data ownership and portability, data destruction procedures, third-party data access controls, and data retention and archiving policies.

Key points

  • Intended Audience: Security Team, Legal, IT Leadership, Data Protection Officer  
  • Classification: Data Management and Privacy

Database Security

  • All client data is stored on isolated databases — client data is fully segregated. Access is always performed via a tenant identifier.
  • Data at rest is encrypted using AES-256 across all database infrastructure.
  • Data in transit is protected using TLS 1.3 or higher for all API interactions and communication channels.
  • Direct database access from external tools is not available. Fluent provides secured access to data exclusively via authenticated API.
  • Dedicated and segregated production and sandbox environments are provided for all clients. Development and test environments are kept separate from production.
  • Multi-tenant components are modelled on tenant identity in the software layer — all shared infrastructure access is via tenant-specific identifiers and encryption.

Data Ownership and Portability

  • All data input by the client is owned by the client.** Fluent does not claim ownership of any client data.
  • Client application user data (username, role, first name, last name, email address) can be queried via the Admin Console UI or API.
  • Customer data (name, address, contact details, order history) can be accessed via the Admin Console UI and queried via API.
  • Data import and export can be scheduled and implemented via the integration layer as part of the project configuration.
  • Data can be extracted via JSON-based GraphQL endpoints. Mass data extraction for migration or portability can be supported by the Fluent SRE team on request.
  • Data formats supported for extraction: JSON (primary); CSV and XML via configurable export settings.

Data anonymisation: Fluent does not anonymise or pseudonymise data by default. Clients can implement anonymisation using data masking and encryption capabilities available at the application and database layers. Methods such as tokenisation, generalisation, or pseudonymisation can be implemented by the client if required.

Data Destruction and Erasure

At the end of a contract, Fluent follows a comprehensive data deletion process:
  • All customer-related data — including database entries, files, backups, and logs containing sensitive or identifiable information — is permanently deleted.
  • Logs that contain sensitive or identifiable information are purged as part of the erasure process.
  • Storage media is securely erased following defined data disposal procedures before decommissioning.
  • Full data destruction procedures are covered in Fluent's standard terms and conditions.

Third-party Data Access

  • All third-party providers and subprocessors are subject to NDA agreements and contracts covering data access obligations.
  • Third-party sub-processors handling personal data are governed by written agreements with terms aligned to Fluent's Data Processing Agreement (DPA), as required under applicable data protection law.
  • Fluent does not transmit client data to third-party AI systems (e.g. OpenAI, Anthropic) for standard platform operations. Any AI features made available as part of the Fluent OMS use foundation models deployed and run as managed services within AWS or GCP cloud infrastructure.
Sandbox environments:
  • Fluent provides 1 production and 2 sandbox accounts as standard per license.
  • Within each sandbox account, clients can create multiple Retailers, each with siloed users, workflows, products, inventory, orders, settings, and data/business logic.
  • Replication between environments is typically managed via a third-party CI/CD tool.

Data Retention and Archiving

  • Fluent makes all historical data (e.g. orders) available through the same API mechanisms as current in-flight datasets — there is no separate archive query interface.
  • Data can be archived and purged on client request. By default, Fluent does not automatically purge data.
  • Automated database snapshots are retained for 7 days for short-term recovery purposes.
  • Audit trail data is retained for 7 years to meet compliance requirements.
  • Personal data processed by Fluent as a data processor is retained only for the duration of the client agreement, unless a different retention requirement is configured.
  • The Fluent OMS can be customised to enforce specific data retention policies for different data types using APIs and workflow configuration.

> Note: Fluent does not store document attachments directly. Documents (invoices, proforma, customs docs) are referenced via URL or encoded PDF stored as order attributes. AWS S3 is a common solution for document storage in Fluent implementations.