How Facteur processes the data of your messages for you

Facteur is not in production yet. A passage in square brackets holds a piece of information the publisher has not declared yet: it will be filled in before launch, and we do not make it up.

What is processed

Facteur receives, keeps and hands back to your organization the messages your tests send it: emails (sender and recipient addresses, subject, body, attachments, raw file) and SMS (sender number, recipient number, text; receiving them is not yet in service). It extracts the one-time codes and links to show them. It also processes the data of the organization: its members, workspaces, addresses and API keys.

For whom, and for what

The people concerned are those whose data appears in the messages of your tests. You decide what your tests send. Facteur processes this data for one purpose only: to provide the service you opened.

For how long

A message is deleted when the retention period of your plan ends, with its raw file and its attachments. The deletion runs every hour. The other data of the organization is kept as long as the organization exists, and are deleted when an owner deletes the organization from the application.

The protections in place

• Each organization sees only its own data: a resource of another organization answers as if it did not exist.
• Sign-in goes through a Logto instance reserved for Facteur, with a second factor and passkeys available, and the sessions of a user can be revoked.
• A support session lasts one hour at most, requires a reason, is announced by a banner, and every action is recorded in the journal. Writing is refused unless an owner or an administrator allows it.
• The deletion of messages at the end of their retention is automatic and cannot be turned off.

Sub-processors

The list of sub-processors says who else processes this data, and what is not chosen yet.

Rights of the people concerned

Facteur helps you answer requests for access, rectification, erasure and portability that concern your test messages. Write to hello@facteur.eu or use the support of the application.

Contract, incident notification and audit

The parties, the clauses of article 28 of the GDPR (notification of a data breach, audit, return and deletion at the end of the contract, notice before a sub-processor is added) and the signing procedure: [To be declared before production]

Annex 1: description of the processing

Purpose

Receive, keep and hand back to your organization the messages your tests send, and extract the one-time codes and the links from them.

Categories of people

Those whose data appears in the messages of your tests, which you choose; the members of your organization.

Categories of data

Addresses of the sender and recipient, subject, body, attachments and raw file of emails; numbers and text of SMS, whose reception is not yet in service; email addresses of the members, workspaces, addresses and API keys of the organization.

Duration

A message is deleted when the retention period of your plan ends. The data of the organization is kept as long as it exists.

Place of processing

France

Annex 2: technical and organizational measures

In place today:

• Data is partitioned by organization: a resource of another organization answers as if it did not exist.
• Sign-in through a Logto instance reserved for Facteur, with a second factor and passkeys available; the sessions of a user can be revoked.
• API keys revocable from the application.
• Journal of support sessions: every action of the team is recorded in it.
• Automatic deletion of messages when their retention ends, every hour.

Encryption in transit and at rest, backups and their restoration, vulnerability and update management: [To be declared before production]