Privacy Policy

This page describes the current web application and the technical paths present in this repository. It is not a generic privacy-policy template.

The repository does not establish every operational fact required for a final privacy notice. In particular, it does not identify the hosting company or magic-link email provider, and it does not define server-log retention, account-data retention, deletion periods, or the final split between the local and cloud product variants.

The controller cannot be identified from the repository alone. The operator details above must be configured before this information is ready for publication.

Browser requests to /v1/* remain on the website origin and are relayed by the Next.js application to the configured BillGetter API. The relay forwards the request body, relevant headers, and cookies required for the requested function. The project documentation names api.billgetter.com as the production API.

The product documentation states that the online infrastructure required to operate BillGetter is hosted in Germany. It does not identify the hosting company.

The identity of the infrastructure provider, the contents of infrastructure access logs, and their retention are not defined in this repository. No statement about those details is made here.

• The language preference can be stored in the bg-locale cookie for up to one year with SameSite=Lax.
• Signed-in users can store the selected organization and workspace in the bg-org and bg-workspace cookies for up to one year with SameSite=Lax.
• The appearance setting is stored locally in the browser under the key theme. The application also follows the operating-system setting when system mode is selected.
• Authentication cookies can be issued by the BillGetter API and are relayed on the website origin. Their exact names and lifetimes are controlled by the API and are not defined in this repository.

Passwordless sign-in sends the entered email address and callback URLs to the BillGetter authentication API so that a magic link can be requested. The email delivery provider is not identified in this repository.

The retained waitlist endpoint accepts an email address and language. If an external API is configured, the request is relayed there. Without that configuration, the email address, language, and creation and update timestamps are stored in the configured MariaDB database. No deletion period is defined here.

When the corresponding account functions are used, the application can send the following data to the configured BillGetter API:

• account email address, display name, language, verification state, and authentication session data;
• organization, workspace, role, membership, and invitation information;
• contact names, email addresses, websites, and notes entered by the user;
• invoice PDFs and invoice metadata, including file name, provider, invoice number, date, amount, currency, source, and status;
• billing name, billing email address, postal address, country, VAT identification number, plan, and subscription status.

The application can redirect organization administrators to Stripe Checkout and the Stripe customer portal. The interface also states that an entered VAT identification number is sent to Stripe for EU countries.

The exact Stripe account configuration, contractual role, transferred checkout fields, retention, and possible international transfers are not defined by this repository and must be documented from the live Stripe configuration before this notice is treated as complete.

Provider icons are resolved server-side. The implementation first uses Google S2 Favicons and can use the configured InvoiceRadar favicon endpoint as a fallback. These requests concern provider domains; invoice files are not sent to the favicon services by this code path.

Page fonts are integrated through Next.js rather than loaded by the visitor's browser from a font CDN. The Open Graph image generator can retrieve font data server-side.

No analytics or marketing-tracking integration is visible in this repository. Infrastructure outside this repository may still create operational logs; their configuration must be checked separately.

Apart from the stated one-year preference-cookie lifetime, this repository does not define verified retention or deletion periods. None are invented on this page.

A verified privacy contact has not been configured. Use LEGAL_PRIVACY_EMAIL, or configure LEGAL_EMAIL as the operator contact.