Privacy Policy

Effective October 19, 2026

This policy covers ReleaseFlow, the release, update and licensing service at releaseflow.net: the website, the dashboard, the download pages, update feeds, checkout and license portal it serves for apps, and its REST, MCP and licensing APIs. Questions? Email hi@kitze.io.

1. Who we are

ReleaseFlow is made by George Kitanov (“Kitze”), a sole proprietor based in Skopje, North Macedonia. “We”, “us” and “our” mean Kitze. Privacy contact: hi@kitze.io.

2. Two kinds of people

Developers sign up for ReleaseFlow to distribute, update and sell their apps. For developer accounts we decide how the data is used.
Customers download, update, buy or activate an app that a developer distributes through ReleaseFlow. The developer who publishes that app decides how its customer data is used, and we process it on their behalf to run downloads, checkout and licensing. For questions about a specific app, contact its developer. Some apps on ReleaseFlow (for example Sotto, Supermac and Sizzy) are Kitze’s own, so for those we are both.

3. Developer accounts

Account. Your name, email, username, password (stored hashed) or GitHub sign-in, optional profile details, timezone and preferences. For each signed-in session we store the IP address and browser user agent.
GitHub connection. If you sign in with GitHub we store your GitHub account ID, username and access token. The token has the user:email, read:user and repo scopes so we can read releases from the repositories you connect, including private ones, download their release files, and create a release webhook on each connected repository.
Your apps and releases. App settings, the connected repository, release versions, release notes, channels and file metadata. Files you upload manually are stored on our servers. Files from private repositories are fetched from GitHub with your token when a customer downloads them.
Payment integrations. If you connect Polar, Stripe or Lemon Squeezy to sell your app, we store the API keys and webhook secrets you give us, encrypted, and use them only to create checkouts, read orders and issue license keys for your apps.
API access. API keys you create and the OAuth clients, tokens and consents used to connect tools such as MCP clients to your account.
Paid plans. ReleaseFlow’s own plans are sold through Polar, our merchant of record. Polar collects your name, email, billing address and payment details and handles taxes, invoices and refunds. We never see your full card number. We receive your name, email and subscription or order details.

4. Customers of apps on ReleaseFlow

Downloads and updates. When you open a download page, download a file or your app checks for updates, we process your IP address, user agent, the platform and architecture requested, the app version and release channel. Download and page-view events are recorded in our analytics (section 5). Files from public repositories are delivered directly by GitHub, which also receives your IP address.
Checkout. Buying an app sends you to the developer’s own checkout provider (Polar, Stripe or Lemon Squeezy), which collects your payment and billing details under its own privacy policy. We attach the anonymous analytics ID, campaign parameters (UTM tags) and any affiliate referral code to the checkout. After payment the provider sends us your name, email, order ID, product, price and currency.
License keys. We create a license key tied to your email and name and send it to you by email. When the app activates or validates a license we store a device ID and a hardware fingerprint, the device name and model, operating system and version, app version, IP address, user agent, trial dates and a log of activation events. This enforces device limits and trials and lets you manage your devices.
License portal. To manage your licenses you enter your email and we email you a one-time code or link. A cookie keeps you signed in to that app’s portal.
Purchase records and lifecycle email. We record the purchase in our analytics with your email. For Kitze’s own apps, we also add your email, name and plan to our lifecycle email tool to send onboarding and product emails. You can unsubscribe from non-essential email from the link in any of those emails.

5. The website, analytics and cookies

Analytics. We use a self-hosted PostHog instance at posthog.server.kitze.io on our own server in Germany. We do not use PostHog Cloud. It records page views, clicks, scroll and heatmap data, errors, page load timing and session recordings. Session recordings mask what you type into form fields. PostHog receives your IP address and the approximate location derived from it. Events about an app can also be recorded in that app’s own project on the same instance.
Cookies and local storage. First-party only:
- a sign-in session cookie when you are logged in to the dashboard;
- rf_did (anonymous visitor ID, 1 year) and rf_exp (which version of the home page you see, 30 days);
- PostHog’s ph_* cookie and localStorage entries to connect visits;
- rf_portal_session when you sign in to a license portal;
- ph_affiliate_ref and affonso_referral when you arrive through an affiliate link, so the affiliate gets credit if you buy. Our affiliate program runs on Affonso, which sets its own cookie (60 days) when it is enabled.
No ad pixels. ReleaseFlow does not load advertising or social media tracking pixels.
Third-party content. The API documentation at /api/docs loads its viewer from unpkg.com, and a dashboard confirmation page loads images from media.giphy.com. Those services receive your IP address like any web request.
Server logs. Our servers log IP addresses, user agents and request paths for delivery, rate limiting and security.

6. Services we use

Hetzner: servers in Germany that run ReleaseFlow, its database and stored release files.
GitHub: sign-in, reading releases from connected repositories, release webhooks and file delivery.
Polar: merchant of record for ReleaseFlow plans, and checkout for apps whose developers use Polar.
Stripe and Lemon Squeezy: checkout for apps whose developers connect them.
Plunk: transactional email (sign-in and password emails, license keys, license portal codes).
PostHog, self-hosted on our own server: analytics.
Dittofeed, self-hosted on our own server: lifecycle email to buyers of Kitze’s apps.
Affonso: affiliate referral tracking, when enabled.

We do not sell your data.

7. Why we use it

To provide the service you signed up for or the app you bought: accounts, downloads, updates, checkout, license keys and email (performance of a contract).
To keep ReleaseFlow secure, prevent abuse and fraud, and understand how it is used so we can improve it (legitimate interests).
To keep payment and tax records (legal obligation).

8. How long we keep it

Account, app and release data are kept while your account exists. License keys, activations and order records are kept while the license is valid and afterwards as long as the developer or tax law requires. When you ask us to delete your account, we delete its data except records we have to keep.

9. Your rights

Wherever you live, you can email hi@kitze.io and ask us to confirm what we have on you, send you a copy, correct it, or delete it. If your request is about an app you bought from another developer, we will pass it to that developer or help them handle it. We have to keep payment records as long as tax law requires. We reply within 30 days.

10. International transfers

Our servers are in Germany. Some of the services above are based outside the EU (for example Polar, Stripe, Lemon Squeezy and GitHub in the United States). They provide their own safeguards for international transfers, such as Standard Contractual Clauses, and we rely on those.

11. Children

ReleaseFlow is not directed at children under 16, and we do not knowingly collect their data. If you think a child has sent us data, email us and we will delete it.

12. Changes

We update this page when what we collect or the services we use change. The date at the top shows the latest change.