Privacy Policy

How JILCH inc. ("we", "us") handles personal information in connection with HostPush, the HostPush Pro add-on, and this website.

Last updated: 13 October 2026

1. Who this covers

This policy covers three groups: people who visit this website, people who buy a HostPush Pro licence, and site owners who install the plugin. It does not cover the readers of your site. Their data stays on your server and you are the controller of it — section 2 explains why we could not reach it even if we wanted to.

2. What the plugin keeps, and why none of it reaches us

HostPush is self-hosted. Everything it records about a reader lives in your own WordPress database:

• the push endpoint URL the browser issued, and the two keys the browser generated so the payload can be encrypted
• the date the subscription was created and the date it was last seen
• whether the browser is on a phone or a computer: one of two words, decided in the reader's browser. The user agent string is not stored
• where the reader chose categories, which ones
• how many times each broadcast was opened, and how many times each of its buttons was pressed: a counter on the broadcast, not a record of who opened it

A subscription identifies a browser, not a person: there is no name, no email address and no column that joins one to a user account. IP addresses are not stored. To turn away floods of requests, the plugin keeps a counter for one minute under a keyed hash of the requesting address, never the address itself, and then lets it expire.

Opens are counted the same way. When a reader opens a notification or presses one of its buttons, their browser reports it to your own site at the /click route of HostPush's REST API, with a token that is the same for every recipient of that broadcast. The token shows the report came from somebody the broadcast was sent to, and nothing narrower, so the only thing written is the counter.

Your site sends notifications by talking directly to the browser vendors' push services — Google, Mozilla, Apple, Microsoft — using the keys generated on your own server. There is no server of ours in that path, and no copy of your subscriber list anywhere but your database. We do not receive it, cannot request it, and have nothing to hand over if somebody asks us for it.

3. What the plugin and the add-on contact

The free plugin contacts no server of ours, and no service on its own initiative. Activating it makes no outgoing request. The requests it does make are these:

• to the push service of each reader's browser, to deliver a notification. Which service that is (Google, Mozilla, Apple or Microsoft) is decided by the reader's browser, not by the plugin
• to your own site's front page, to check whether a web app manifest is already there

The paid add-on, HostPush Pro, contacts one external service, and it is not ours:

Nothing about your readers is in any of those requests.

4. What we hold when you buy a licence

Using the free plugin gives us nothing: there is no registration, and section 3 is the whole of what it sends anywhere.

Freemius is the merchant of record for HostPush Pro: it takes the payment and holds the buyer record. What reaches us from it is the licence administration data — the name and email address given at purchase, the licence key and its state, the sites it is activated on, and the purchase and renewal dates — together with what the add-on sends when it is activated, as section 3 lists.

We use it to issue and renew licences, to answer support, to notify you of security fixes and other changes that affect an active licence, and to decide which WordPress and PHP versions to keep supporting. We never see or hold card numbers. You can deactivate the licence on a site at any time from the Account screen under HostPush's menu.

5. This website

These pages carry no analytics, no advertising tags and no cookies of our own. They are static files served from Cloudflare Pages, whose logs record the usual request metadata. Web fonts are loaded from Google Fonts, which sees the request for the font file.

6. Sharing with third parties

We do not sell personal information and do not provide it to third parties except as permitted under Article 27 of the Act on the Protection of Personal Information — with your consent, where the law requires it, or to a contractor acting for us within the scope of the purposes above. Freemius is the contractor in that sense for payment, licensing and updates.

7. Transfers outside Japan

Freemius, Inc. is established in the United States, and Cloudflare, Inc. serves this site from infrastructure outside Japan. Where we provide personal information to them, we do so under Article 28 of the Act on the Protection of Personal Information, having taken the steps that article requires. Information about the data-protection regimes of those countries and the measures those companies take is available on request at the address in section 11.

8. How we keep it safe

The steps we take to protect what we hold, as Article 32(1)(iv) of the Act on the Protection of Personal Information and Article 10(i) of its Enforcement Order require us to state:

• Organisational. One named person is responsible for handling it, and access is limited to those who need it to issue licences, answer support or send the notices in section 4.
• Technical. Everything is reached over TLS, through accounts protected by two-factor authentication, on services we do not administer ourselves.
• By holding less. The strongest measure here is the shape of the product rather than anything we operate: your readers' data is not in our custody at all, so there is no store of it to breach. What we hold is licence administration, and nothing more.
• Conditions abroad. Where data is handled outside Japan (section 7), we inform ourselves of the data-protection regime of that country before relying on the service.

9. How long we keep it

Licence administration data, including what the add-on sent on activation, is kept for the life of the licence and then for the period required by tax and accounting law in Japan. Support correspondence is kept for two years. Anything we no longer need for the purposes above is deleted.

10. Your rights

Under Articles 32 and 33 of the Act on the Protection of Personal Information you may ask us to disclose, correct, add to, delete, stop using or stop providing your retained personal data, and you may ask about the purposes for which we hold it. Write to the address in section 11. We will verify that the request comes from you or your authorised representative before acting on it, and we do not charge for it.

For data your own site holds about your readers, the request goes to you, not to us. The plugin does not register a personal-data exporter or eraser with WordPress, because those tools find data by email address and a subscription holds nothing an email address can be matched to. A reader withdraws from their browser or from the subscribe control on your site; no further notifications are sent, and the subscription is deleted within 30 days.

11. Who we are, and how to reach us

12. Changes to this policy

We may update this policy. The current version is always the one on this page, and the date at the top says when it last changed. A change that materially affects how we handle information already collected will be announced by email to active licence holders.