Legal & Privacy.

Through this site and the demonstration instance, Bonfleur handles personal data as described below. What a component listed in § 06 records while serving a request is governed by that component's own policy. No data is sold or shared for marketing purposes.

Data controller.

Bonfleur s.r.o., a company registered in the Czech Republic. Company-identification details are provided on request through the contact form.

Contact form.

Name, email, role, the key of the page that linked to the form, and message, used to respond and to act on what is raised. Submissions are not stored in an application database; they are delivered by email through the transactional-email component listed in § 06, whose own policy governs what it retains. If a message cannot be delivered and the form says it has been recorded, it is kept instead in the hosting provider's runtime logs and answered from there. That copy lasts for as long as the provider keeps runtime logs, whether or not a reply has been sent.

Rate limiting.

To protect the site from abuse, the network address of a request is the key of a request counter over a one-minute window, held by the coordination store listed in § 06. That counter is not used for anything else, and the store's rate-limit analytics feature, which would otherwise keep a count of every check with no expiry, is turned off.

Specimen binder requests.

When the specimen binder is available, each download the file route serves is logged with the time, the file, the terms version carried by the link, whether the download was partial, the country and referring site of the request, a browser user-agent string shortened to 120 characters, and a digest of the requesting network address keyed with a secret held only on the server; where that secret is not configured, no digest is recorded. The address itself, a name or an email address is never written to this log, which is kept only as long as the hosting provider retains runtime logs. Acknowledgements of the terms are logged as § 05 states.

Demonstration accounts.

Accounts on the demonstration instance are issued by invitation to evaluate the platform, and may be used only with synthetic data, under the condition of use in § 01. Authentication is handled by the identity component listed in § 06. The platform's database holds the account's name and email address, including in its append-only audit trail, whose records the platform refuses to alter or delete. Actions taken in an account are recorded in the audit trail with the account and with the network address and browser user-agent string of the request, and security events, such as a refused request, may be recorded with the same two details. Accepting the demonstration terms records the account's email address and identity-component id, the version of the terms, the time, and a SHA-256 fingerprint of the text shown; that record cannot be altered or deleted, and it is kept after the account or its organization is removed, so that what was agreed can be shown.

Retrieval index.

The platform uses no vector index or retrieval store.

Retention.

Contact-form messages are kept in the recipient mailbox only as long as needed to reply. The demonstration instance and its accounts may be reset at any time. Bonfleur assumes no retention obligation on anyone's behalf; a licensee's retention duties run against its own deployment, which Bonfleur does not operate.

Access and erasure.

You may contact us about the message you sent us, and we will action access or erasure within the timeframes applicable law provides. Erasure does not reach a copy kept in the hosting provider's runtime logs, which lasts until those logs expire. Rate-limit counts and the specimen request log carry no name or email address; they, and the append-only audit trail and the record of terms accepted, are kept as described above.

Cookies.

Strictly necessary cookies only:

• theme: the light or dark preference, kept for up to one year.
• the cookies the identity component listed in § 06 sets to keep a demonstration account signed in, such as __session, __client_uat and __refresh_* (including variants of these names with a suffix).

Usage analytics, through the hosting provider, are cookieless and do not identify individual visitors. There is no third-party or cross-site tracking, no advertising or marketing-analytics cookie and no marketing mailing list. On this basis the site shows no cookie-consent banner.

The site's own code also keeps, in the browser's local storage, the theme preference, the sidebar's collapsed state, an unsaved new-engagement draft and the command palette's recently opened pages; and, for the open tab only, the outcome of a re-scope and a count of sign-in retries. They are read in the browser; storing them sends nothing to a server.

The specimen binder is a workpaper exported from a fictional engagement, and its terms are shown, with the statements a reader confirms, before download. The terms that describe an edition are published with it.

A fictional engagement.

The company in the file is invented. The engagement, its people, its systems and every figure in the file are fictional, and any resemblance to a real company or person is coincidental.

Synthetic data.

Every population, evidence file, test result and exception was generated to demonstrate the software. No real company’s data, controls or personnel were examined, and no client information of any kind is in the file.

Nothing about any real vendor.

Where a kind of technology or a product is mentioned, it describes what the fictional company is imagined to use. Nothing in the file tests, evaluates or states anything about the controls, services or security of any real vendor or service provider.

Not an audit, an opinion or assurance.

The file is not an audit report, an opinion, an attestation, or an assessment of the internal control of any entity, and it was not prepared by or for a CPA firm.

Not professional guidance.

References to auditing standards are printed as the software prints them; they are not professional guidance.

No reliance, no warranty.

The file is provided as-is, solely so the software can be evaluated, and must not be relied on for any audit, compliance, regulatory, investment or other decision. To the fullest extent permitted by applicable law, Bonfleur s.r.o. accepts no liability arising from its use.

Not to be presented as real work.

You may not present the file, or any part of it, as a real audit file or as work performed for a real entity.

What the reader confirms

• a.I understand that the file is a fictional engagement on synthetic data — not an audit, an opinion or an assessment of any real company, person or vendor.
• b.I accept these terms, including that the file is provided as-is and must not be relied on.

Each acknowledgement is logged with its time, the terms version, the statements confirmed, the country and referring site of the request, and a digest of the requesting network address keyed with a secret held only on the server (none is recorded where that secret is not configured) — never the address itself, a name or an e-mail address. No edition is published at present: accepting the terms issues no link, a link to the file opens the platform page in a browser, and any other request for it is refused.