How SiteBienfait handles your site, your data and your access

All code generation and edits happen in a sandbox against a git branch, and become a change set. The live site is not edited in place, and a sandbox build cannot publish itself.

• The sandbox works against the site's own source, on an isolated branch.
• The preview URL is private, and it is a build of that branch, not of production.
• The only path from the sandbox to production is an approved, deployed change set.

Nothing publishes without a person approving it on a preview. By default that person is the SiteBienfait reviewer; the owner reads every page once before launch and can ask to approve each change personally. Approval is given per change, on its preview; it is not a standing instruction to publish whatever comes next.

• A preview is shown before any write reaches the production site.
• A rejected change set does not ship under another title or inside another bundle.
• The owner can switch to approving every change personally at any time, by asking.

The approval boundary is drawn in the change-set diagram on /how-it-works.

The free audit collects the submitted URL, locale, goal, IP address and timestamp so a report can be reopened. Quote requests are kept to follow up a project. Paying customers' site data is kept for the life of the contract.

Free audit submissions

12 months

Project estimate requests

24 months

Account and site data

For the life of the contract, then deleted on request

Hosting, CDN, DNS and object storage

Cloudflare, Inc. (United States / global edge network)

Marketing site cookies

None; the language choice is stored in localStorage

Only providers that are actually activated are listed as subprocessors.

The domain stays with the owner, the content stays with the owner, and the output is a plain static Astro repository. Cancellation is never used as technical leverage over a site the owner paid to build.

• The domain and its DNS decisions stay under the owner's control.
• The content, URLs and page structure stay the owner's.
• The delivered site is a plain static Astro repository, not a proprietary runtime.

The repository and its assets can be exported and hosted anywhere. That is what static Astro output is for, and it means the exit path is tested rather than promised.

• The repository, content and assets export together.
• The output is static: no database on the request path, no plugin to patch.
• A migration away is a hosting change, not a rebuild of the site.

Account and site data can be deleted on request. A deletion request goes to the contact address published on /en/contact and in the legal notice, and the retention periods above say what is still held and why.

• A deletion request covers the account and site data still held.
• Audit submissions expire after 12 months; quote requests after 24 months.
• The request is acknowledged by a person, not a form that disappears.