Privacy policy (prototype)

Preliminary content: this page will be reviewed for content and legality before publication.

1) What this is about

This page describes how the current benefy prototype handles data. It is a factual description of the current state, not a legally reviewed privacy statement. A full statement under the applicable requirements will be created once the offering is completed.

2) Telling local checks and submitted requests apart

Personal and household details for checks are stored locally in the browser and can pre-fill other forms. When the mandate dialog is submitted, the person entered is created or updated as the primary profile; place of residence and postcode belong to the shared household. The profile is retained for checks even if the submission fails. Other check results are not sent automatically. Files are not stored in the local profile.

3) Direct mandate requests

For a mandate request, BeneFy processes your name, date of birth, email address, optional phone number, postcode, place of residence, goals, insurance areas, advisory arrangement so far and language. Voluntarily uploaded policies or certificates are placed in non-public storage; they may contain sensitive information. Also included are the request number, document metadata, consent version and server-side timestamps. The data serves processing and contacting you, not automatic AI document analysis in this step. The request does not grant a mandate. Information about the responsible party, retention and data protection rights must be legally completed before public launch.

4) Server requests

Accessing public pages and content involves standard requests to a server, as with any website. We make no statement about whether or which network or server logs are generated; details will follow in the final technical documentation.

5) Language setting

A cookie may be set to remember your language choice. Public articles may be cached in the browser via the content service; this is separate from transient form entries. Storage locations, retention periods and the final list of technical services must be reviewed and documented before publication.

6) File selection

When you select a policy file, the browser only holds a file reference (File object) with metadata such as name, size and type. The file itself is not uploaded. There is no text recognition (OCR), no evaluation by language models (LLM) and no live booking.

7) What we expressly do not assure

We claim neither that connections are encrypted nor that the offering complies with data protection legislation (such as the Swiss FADP). Such assurances can only be made after technical and legal review; they will then be added here.

No assurance of encryption
No claim of FADP compliance
No statement about server or network logs