rondea

Security and sovereignty

Your answers hold site photos, employee names and sometimes positions. Here is what we do so they stay yours.

Where your data lives

Hosted in France, with a European provider, with encrypted backups kept in the same region.

  • Servers and backups in France
  • No transfer outside the European Union for production data
  • Sub-processors listed and kept up to date in a public register

Separation between customers

Each organization is isolated at the database level, not only in application code.

  • Isolation enforced by PostgreSQL (row level security) and checked by automated tests on every release
  • A query without an organization returns nothing: the database refuses, rather than a forgotten condition
  • API keys and webhooks are bound to one organization and to explicit scopes

Access by our team

We do not open your console to have a look. When support needs to, the access is short, justified and read-only.

  • Thirty minutes by default, two hours at most, on a single organization
  • Read-only: no write is possible through a support access
  • The reason and the opening appear in your own audit log, the second they happen

Traceability and recovery

What is done is visible, and what is lost can be recovered.

  • Readable, append-only audit log
  • Correction history per answer, with author and date
  • Backups with point-in-time restore
  • Two-factor authentication, device management, immediate revocation

Compliance

We act as a processor under the GDPR for the data you entrust to us.

  • Data processing agreement (Article 28) available on request
  • Register of sub-processors kept up to date
  • Organization export and deletion on request, with a grace period
  • Employee geolocation: explicit opt-in and a reminder of the French regulator's rules in the app

What is not done

A security officer looks for the gaps first. Here they are, named, rather than discovered during the audit.

  • No external penetration test has been carried out to date. It is planned and budgeted; we will publish the date and the summary.
  • No certification is held: not ISO 27001, not HDS, not SecNumCloud. We claim none and imply none.
  • The RGAA accessibility audit has not been carried out. The site and the console are written aiming at AA, without a third party having verified it.
  • Single sign-on works over OpenID Connect against a test provider; it has not been validated against a real corporate directory.
  • No production load evidence: the product runs in preproduction, not yet at customers.

Reporting a vulnerability

If you find a flaw, write to us: we answer, we fix, and we tell you when it is fixed.

  • Write to the site's contact address with "security" in the subject.
  • We acknowledge within two working days and give a remediation timeframe.
  • We will not pursue research conducted in good faith and without degrading the service.
  • No bug bounty programme exists today: saying so avoids implying otherwise.

Ask the questions that are missing

Data processing agreement, subprocessor register, hosting detail, penetration test schedule: write to us and we answer in writing.

Start free