Privacy Policy

1. Account and project data

Authentication is provided through Keycloak and Budgeter’s backend-for-frontend gateway. The interface receives your username, name and email, and may receive a phone number and session expiry from the account profile. The browser uses an opaque HttpOnly session cookie rather than storing access tokens in JavaScript.

Saved projects can contain a name, client, description, revenue, dividend, tax structure, folders, cost groups and cost lines, including names, performers, classifications and amounts. This information is sent to Budgeter’s backend to save projects and compute the results you request.

2. Why information is used

Account information establishes your session and associates projects with their owner. Project inputs support saving, reopening, calculations, comparisons, export and sharing features. Unsaved calculation drafts are also sent to the server for preview.

Device preferences make language selection, amount masking and analytics consent persist on the device. The language and amount-masking controls change presentation, not your underlying budget amounts.

3. Storage, access and sharing

Budgeter uses backend storage for accounts, sessions and saved project data. Keycloak handles identity and the gateway manages the browser session. The infrastructure providers, storage locations, operational logs and backup practices still require owner confirmation.

When you create a shared link, information can be made available to its recipients subject to the server’s access settings. Revoking a link prevents future access through that link but cannot retract copies already made. Avoid sharing more information than needed.

4. Cookies, device preferences and Google Analytics

The session cookie is used for authentication. Local browser storage remembers language (budgeter.lang), amount masking (budgeter.privacy) and analytics consent (budgeter.consent). Clearing browser storage removes those saved preferences.

When Google Analytics is configured, Budgeter loads Google’s tag to measure page use and named actions. The current consent-mode implementation starts with analytics storage denied: Google may receive cookieless pings before permission or after refusal. Allowing analytics permits analytics storage. Advertising storage and personalization are denied by the application.

The application’s named events use action types and categorical settings rather than budget amounts, project names or email addresses. Google’s tag can receive page URLs and technical device/network information. Owner review must confirm the Google property configuration, retention and transfer arrangements. Changing your choice is available from the analytics controls; see Google’s privacy information for its processing.

5. Deletion, retention and requests

You can edit and delete individual projects using the application’s controls and change device preferences. Account deletion and the removal of related backups have not been verified. No retention period is promised in this draft.

Depending on the applicable law and circumstances, privacy rights may include information about processing, access, correction, erasure, restriction, objection and withdrawal of consent. A verified request channel and the operator’s response procedure must be added before publication; use the working contact field below only once it has been confirmed.

6. Scope and updates

This notice describes the implementation reviewed for Budgeter. It does not claim a certification or guarantee complete security or legal compliance. The operator, lawful bases, recipients, retention and applicable legal requirements need owner and legal validation.

The final policy should be reviewed when authentication, analytics, hosting, sharing or commercial features change.