Legal

Privacy

Privacy Policy

We care about your personal data. This notice explains how we process data when you use this website and our licensed software delivered via Streamingzebra (for example ManifestGuard Python and AI Keep Clean CCC) (GDPR Art. 13).

Scope / regional applicability

This notice primarily targets users with habitual residence in the EU/EEA. For access from other jurisdictions, mandatory privacy/consumer rules of those jurisdictions prevail; no additional voluntary protections are promised beyond those. Where marketplace or third‑party services are used, their policies also apply.

Controller

Serap Kusu-Eryigit – Ready‑4‑IT (ready-4-it.com) Legal form: sole proprietor (entreprise individuelle) Technically responsible: Serap Kusu-Eryigit Serviceable address: 21, rue Basse, L-3813 Schifflange, Luxembourg No walk-in customers. Email: support [at] ready-4-it [dot] com Phone: +352 691 868 822

Purposes & legal bases

  • Provide website, stability, security (Art. 6(1)(f) GDPR)
  • Communication (Art. 6(1)(a)/(b) GDPR)
  • Contract performance, license provisioning, customer service (Art. 6(1)(b) GDPR)
  • Compliance with legal obligations (e.g., statutory retention obligations) (Art. 6(1)(c) GDPR)
  • Optional: analytics/statistics (Art. 6(1)(a) GDPR)
  • Optional: marketing (Art. 6(1)(a) GDPR)

See also our Cookies page.

Access data / server logs

When you access the site, technically necessary data are processed (e.g., IP address, date/time, URL, referrer, user agent). These serve secure operation and are deleted after a short time.

Cookies

Details: see Cookies. Necessary cookies rely on legitimate interests; additional cookies (analytics/marketing) only with consent.

Contact form / email

If you contact us, we process your details to handle the request. Legal basis is consent or pre‑contractual steps. Data are deleted once the purpose is fulfilled and no retention duties apply.

Web analytics (optional)

If analytics software is used, it happens only with consent. IP addresses are shortened; you can withdraw consent at any time.

Recipients / categories of recipients

IT service providers/hosting providers; within data processing agreements (Art. 28 GDPR) where applicable. Streamingzebra (api.streamingzebra.com) is our first-party delivery service: we use it to record installations and updates of our software packages (see below).

Third‑country transfers

Transfers to third countries occur only where an adequate level of protection exists (e.g., EU Standard Contractual Clauses) and where necessary.

Note: When marketplaces/payment providers (e.g., Payhip and their sub‑processors) are used, processing outside the EEA may occur. Where required, we rely on appropriate safeguards (in particular EU SCCs) and the respective contractual data protection arrangements.

Storage period

We process personal data only as long as needed for the stated purposes or where statutory retention periods apply.

Your rights

You have rights of access, rectification, erasure, restriction, portability, and objection. You can withdraw given consent. You may lodge a complaint with a supervisory authority.

If we process data based on legitimate interests (Art. 6(1)(f) GDPR), you may object for reasons arising from your particular situation.

Objection to direct marketing: If we process personal data for direct marketing, you have the right to object at any time (Art. 21(2) GDPR). In that case we will no longer process your data for that purpose.

In Luxembourg, the competent supervisory authority is the CNPD (Commission nationale pour la protection des données): https://cnpd.public.lu/

Security

We take technical and organizational measures to protect your data (e.g., TLS encryption, hardening, logging).

Updates

This privacy notice is updated as needed. Status: 2026‑09‑16.

Payhip – Payment Processing and Checkout

What is Payhip?

For the sale and checkout of digital products, we use the service provider Payhip Ltd. (UK). Payhip acts as "Merchant of Record" (reseller) – this means the purchase contract is concluded between you and Payhip.

Role allocation note: Payhip typically processes data for checkout processing as an independent controller under their terms. We process order/contact/license data insofar as this is required to provide the software, manage licenses, and provide support.

What data is transmitted?

When you click "Buy" and are redirected to Payhip, we transmit the following data:

  • Product information (name, price)
  • Your email address (for download link and invoice)
  • If applicable, your IP address (e.g., for fraud prevention and technical checkout processing)

Payhip processes your payment data (credit card, PayPal, etc.) directly – we do not receive this data.

In addition (depending on checkout/product), we typically receive:

  • Contact and order data (e.g., name, email, billing information)
  • Product/license data (e.g., product, license type, term)
  • Transaction metadata (e.g., timestamp, status)

Legal basis: Contract performance (Art. 6(1)(b) GDPR)

Where Payhip acts as Merchant of Record, Payhip may also process data based on legal obligations (Art. 6(1)(c) GDPR) under its own responsibility.

Storage period: Payhip stores your data according to their own policies. Details: see Payhip Privacy Policy and Payhip Terms (EN).

Your rights: You can request information, deletion, or correction of your data from Payhip via their support channels.

Streamingzebra — recording package installations

Ready‑4‑IT operates Streamingzebra (https://api.streamingzebra.com, site https://streamingzebra.com) as a first-party delivery service for licensed software packages. It is not a marketplace like Payhip. This applies to Ready‑4‑IT products that use Zebra, not to one product only.

Via Zebra we record which of our packages were installed, updated, or (where the client reports it) uninstalled on an entitled device. Purpose: licensed delivery, update entitlement, and aggregate install/update counts — not analysis of your source code or projects.

When a product fetches an entitled package or runs an update check, the client may send a delivery lifecycle event (POST /api/v2/lifecycle/event or the product-specific update endpoint).

Typical data

  • License/activation token (Zebra stores an activation hash, not the raw key)
  • Module/product id (as stored for that product, e.g. akc_ccc, manifestguard_py)
  • Event type (install, update, uninstall) or update check
  • Software version (semver)
  • for bound licenses, a device hash used to check activation (product-dependent)

Not included: source code, file paths, project names, chat contents, Cursor/IDE passwords, CLI command names, dependency lists. Failed installs are not counted as successful delivery. Public GitHub Free releases usually do not call Zebra. Some public bootstraps (for example PyPI) may send a token-less first-run ping after you agree in that product; that series is not mixed into entitled counts.

Legal basis: contract performance (Art. 6(1)(b) GDPR) for licensed delivery and update-check. Aggregate install/update counts typically use legitimate interests (Art. 6(1)(f) GDPR). Some products ask for consent (Art. 6(1)(a) GDPR) before a count is sent; you can refuse without losing the install or the licensed update. How to agree or withdraw is shown in that product (CLI, in-app, or installer).

Examples (same service, different clients)

  • AI Keep Clean CCC (akc_ccc): purchase/checkout on this site (Payhip). In-app updates (e.g. “Check for updates”) may send the token, installed version, and module id to Zebra so an entitled VSIX/package can be delivered. Free updates may use public GitHub release assets (no license token).
  • ManifestGuard Python: entitled module manifestguard_py; optional public bootstrap ping mgpy_pypi. The CLI asks yes/no (default no) before counting. Withdraw: manifestguard license lifecycle --off. Uninstall count is best-effort (license report-uninstall before pip uninstall; pip has no hook). The entitled ZIP is a PyArmor-protected wheel plus encrypted marker JSON — that is product IP protection, not extra personal data.
  • Other Ready‑4‑IT modules with Zebra delivery in the product record (where the client uses the same service), e.g. AI Keep Clean or Code Spots.

Product pages: Products. Additional Zebra operator notes: streamingzebra.com/privacy.

Support, bug reports, log files

If you contact us for support requests, bug reports, or Early Bird/Early Access feedback, we process the content you provide (e.g., email address, messages, and potentially log files or screenshots). We process these data to handle the request and to improve/stabilize the software.

Legal basis is typically contract performance/pre‑contractual steps (Art. 6(1)(b) GDPR) and—for technical analysis/abuse prevention—legitimate interests (Art. 6(1)(f) GDPR). Where possible, please remove personal data from log files before sending them.

Storage period: Support communications are stored as long as needed to handle the case and for reasonable traceability, and longer where statutory retention duties apply.

External links

External links are indicated (🔗). We do not assume liability for third‑party content and do not adopt such content as our own.

Third‑party services (examples)

Further cookie/consent details: Cookies.