How CashflowWatch processes personal data

Depending on the feature used, CashflowWatch may process account identifiers, login credentials, watchlists, notification preferences, portfolio records, report-delivery metadata, device or browser session markers, and support correspondence.

Account, watchlist, notification, and portfolio processing is generally required to provide the requested service and maintain workspace security. Consent is used for non-essential cookie categories and can be changed at any time through the cookie settings UI.

Workspace data may be stored in application databases, cache layers, and operational logs within the configured hosting region. External providers may be involved where the user enables routed notifications such as email, SMS, or push delivery.

Retention depends on the account feature involved, operational logging needs, and any statutory obligations that apply to the operator. Cookie-consent records are stored so the site can remember your preference selection.

Subject to the applicable legal conditions, you may request access, rectification, erasure, restriction, objection handling, and data portability. The operator should respond to valid requests without undue delay and generally within one month.

Submit requests to privacy@cashflowwatch.local. If you believe your data was handled unlawfully, you may also contact the competent supervisory authority listed in the Impressum.

CashflowWatch uses authentication, access control, and operational monitoring to reduce unauthorized access. No internet-facing service can guarantee absolute security, so users should also protect their credentials and device sessions.