chibichange Privacy Policy

:::info TL;DR We don't sell your data and don't train AI on it. The changelog widget records only three things — which project, which version, and a hashed origin. It never sees your users' IP addresses, never sets a cookie on their browsers, and never fingerprints them. If you self-host, no data reaches us at all. :::

This policy applies to the chibichange service we operate at chibichange.com and my.chibichange.com. If you run your own instance, nothing reaches us and you are the sole controller of everything it processes.

1. Controller​

ZeitFlow UG (haftungsbeschränkt) — Kolonnenstraße 8, 10827 Berlin, Germany. Managing Director: Evgenii Burmakin. Email: hi@dawarich.app. Full company details: Impressum.

2. Two kinds of people​

chibichange sits between two groups, and it treats them very differently.

• Authors — people with an account here, who write changelogs. We hold an account for them.
• Readers — the users of an author's software, who see the "What's New" widget inside an app we do not operate. We create no account, no profile and no identifier for readers. See Section 4.

3. Author data​

No automated decision-making with legal effect (Art. 22). Providing this data is voluntary but necessary to have an account.

We are not currently charging for chibichange. When we do, billing data (name, email, address, tax ID, payment metadata) will be processed under (1)(b) contract and (1)(c) legal obligation, and the payment provider will be added to Section 5 before that happens.

4. Reader data — what the widget actually sends​

When the widget loads inside an author's application, it requests the changelog and that request records exactly three fields:

The origin is hashed with a keyed hash the moment the request is received; the plaintext domain is never written to our database. Hashing is one-way and keyed, so it cannot be reversed by guessing.

We do not store IP addresses from widget requests, set cookies on readers' browsers, fingerprint devices or browsers, or build profiles. The widget keeps a "which versions have I already seen" marker in the reader's own localStorage; that never leaves their browser and we never receive it.

Our legal basis for this minimal record is Art. 6(1)(f) — our and the author's legitimate interest in knowing how many instances run which version. Given that no identifier for a person is stored, the impact on readers is minimal.

The feedback board is different: if a reader chooses to submit an idea, they may optionally supply an email address, and we store a hashed form of their IP address for spam control. That is voluntary and based on Art. 6(1)(f).

Raw beacon records are pruned automatically (Section 6).

5. Recipients / Processors​

All listed processors are bound by DPAs under Art. 28 GDPR. We do not sell data or share it for advertising.

Our waitlist form and our own usage analytics run on software we host ourselves on the Hetzner infrastructure above; no third-party analytics or email-marketing vendor receives your data through them.

International transfers: hosting and transactional email stay within the EU. US transfers (Cloudflare) rely on the EU-US Data Privacy Framework where the provider is certified, and on Standard Contractual Clauses (Art. 46 GDPR) otherwise.

6. Retention​

• Account, project and changelog data: while your account is active; deleted on request or on account deletion.
• Beacon records: pruned on a rolling basis by a scheduled job; the dashboard only ever reports aggregates.
• Feedback-board submissions: for as long as the author keeps them.
• Error and server logs: up to 30 days.
• Support correspondence: up to 3 years after last contact.

Deleting a project releases its content but keeps its slug reserved, so that instances still requesting it cannot be served someone else's changelog. The reservation stores the slug and the owning account, nothing else. See the abuse and slug policy.

7. Your Rights​

You have the right to access (Art. 15), rectify (16), erase (17), restrict (18), port (20), object to processing based on legitimate interest (21), and withdraw consent at any time (7(3)) without affecting prior processing. To exercise any right, email hi@dawarich.app.

You may also lodge a complaint with a supervisory authority (Art. 77). Our competent authority is the Berliner Beauftragte für Datenschutz und Informationsfreiheit (datenschutz-berlin.de); you may instead complain in your country of residence or workplace.

8. Cookies​

We set no advertising or cross-site tracking cookies, and there is no consent banner because nothing here requires consent.

9. Security​

HTTPS for all transfers, an enforced Content Security Policy, rate limiting on authentication endpoints, encrypted database storage and backups, and all application data stored in the EU. Beacon origins are hashed at ingest so the plaintext is never persisted.

10. Children​

chibichange is a tool for people who publish software. You must be at least 16 years old to hold an account. We do not knowingly collect data from children under 16.

11. Self-hosting​

If you run your own chibichange instance, we receive nothing: no beacons, no account data, no telemetry. You become the controller for everything your instance processes, including the reader data described in Section 4, and you are responsible for your own Impressum and privacy notice.

12. Changes​

We will notify account holders of material changes (new purposes, new processors, changed retention) by email and/or in-app notice at least 30 days before they take effect. Non-material edits are published here with an updated date below.

Last updated​

Effective 2026-08-10. Contact for all privacy matters: hi@dawarich.app.