Skip to content
Fluw
Create a project

Data and access

How Fluw handles your data

Before a connection is enabled, its source, required fields, and permitted actions are agreed. This page separates safeguards already implemented in Fluw from decisions that depend on your project.

Ask a question about data

Four questions to settle before work starts

Which data can the project use?
The scope depends on the connection configuration: list the source, fields, documents, and statuses the website or service needs.
Who gets access?
Project APIs check the user and their permission to access the project. Roles for website visitors, customers, or staff are defined separately for the service itself.
What is already implemented?
HTTPS, project access checks, hashed refresh tokens, private repositories, and safeguards for the working environment.
What depends on configuration?
Data scope, update frequency, roles, permitted actions, source outages, and retention rules after deletion.

Where responsibilities meet

Company system
Catalog, prices, documents, or other selected data You define the source and required fields.
Fluw project
Fluw checks the user and their permission to work with the specific project Access is checked for the specific project.
Website or service
Uses the data and actions included in the agreed connection Visitor roles are defined separately.

Integration credentials are encrypted in the connection service. The specific fields, roles, and actions are defined for each connection.

Safeguards we can confirm

This describes current Fluw mechanisms. It is not a universal security assessment for every future project.

Data transfer and sessions

  • HTTP redirects to HTTPS.
  • Tokens used to renew a session (refresh tokens) are stored server-side as hashes, not in their original form.

Project access

  • Project APIs verify authentication and the user’s permission to work with a specific project.
  • A new project is created in a private Git repository.

Working environment

  • Containers in active environments run without root, privilege escalation, or additional capabilities.
  • Network rules (NetworkPolicy) constrain traffic, but the environment can make HTTP/HTTPS requests.

Connection credentials

  • Integration credentials are encrypted with AES-256-GCM in the connection service (Connector Hub).
  • This does not mean a separate KMS manages the keys or that they rotate automatically.

What to record with the requirements

These answers define the project boundary. Without them, the connection, roles, and deletion process are not agreed.

  1. 01

    Data

    Which system is authoritative? Which fields, documents, and statuses are actually required?

    The source and exact data scope

  2. 02

    People and actions

    Who works with the project, and what can visitors, customers, or staff do?

    Users, roles, and sensitive actions

  3. 03

    Updates

    How often is fresh data needed, and what should the site show if the source is unavailable?

    Frequency and failure behavior

  4. 04

    Network

    Which external addresses does the connection need? Network rules do not mean complete internet isolation.

    Permitted connection destinations

  5. 05

    Retention

    Does the scope include personal, financial, or regulated data, and what retention periods apply?

    A separate assessment and retention policy

Send requirements

Project retention and deletion

The project is retained indefinitely. The published website stops when the subscription ends. Cancelling renewal does not delete the project and keeps the paid period intact.

Deletion has a defined scope

A documented process should not be replaced with a blanket promise to remove every copy immediately.

What is removed
The project’s Git repository and the project record in the database.
What needs separate confirmation
The timing and process for removing data from backups, logs, and object storage.
What to agree in advance
Disconnecting the source, any project materials you need to retain, and who confirms that access has ended.

Claims Fluw does not make without a separate review

What happens when the subscription ends?

The project is retained indefinitely. The published website stops when the subscription ends. Cancelling renewal does not delete the project and keeps the paid period intact.

Is all data protected with end-to-end encryption?

We make no such claim. AES-256-GCM encryption is confirmed for credentials in the connection service. This cannot be generalized to every Fluw data type.

Is the working environment completely isolated from the internet?

No. NetworkPolicy defines network constraints, but an active environment may have outbound HTTP/HTTPS access.

Can regulated data be connected?

Only after a separate review of sources, roles, retention, deletion, and applicable requirements. This page is not a certification or legal assessment.

Describe the data, users, and actions you need

We can then separate what is ready from what requires configuration or a separate assessment—before anything is connected or published.

Send requirementsCreate a website