Privacy Policy

JILCH inc. (株式会社JILCH) ("we") sets out below how personal information is handled in the WordPress plugin Affely and the hosted service Affely Worker (together, "the service"). This is a reference translation; the Japanese text at /ja/privacy/ is the governing version.

Last updated: 25 August 2026

1. Who this covers

Two groups:

1. users of the service — the people who run a site with the plugin installed
2. the readers of those sites

For a reader's personal data, the business handling it is the site owner. We act on their behalf, within the limits set out in section 5.

2. What we collect

1. Email address, and the record of licence purchases and renewals
2. The URL of the site a licence was activated on (to check the one-licence-one-site limit)
3. The content of requests to the service — product ASIN, search keyword, category, JAN code, site token — with their time and count
4. Payment details (the card number is handled by the payment processor; we never hold it)
5. The content of support correspondence

We collect nothing that identifies a reader. When click measurement (Pro) is on, the four things we receive are:

1. whether it was a click or a view (the link scrolling into sight)
2. the product's ASIN
3. which marketplace the link pointed at
4. the ID of the post the link was on

No IP address, no user agent, no cookie, no identifier of any kind. Batches are posted to the site's own server first, and that server relays them to us, so we never see the reader's connection either. A switch in the plugin's settings turns the whole thing off.

3. What we use it for

1. Providing the service, and issuing, renewing and validating licences
2. Billing and payment
3. Answering enquiries, verifying identity, and sending important notices
4. Maintaining and improving the service, and developing new features
5. Preventing abuse and unauthorised access, metering usage, and responding to breaches of the terms
6. Meeting legal obligations

4. Disclosure to third parties

We do not disclose personal information to third parties without prior consent, except where:

1. the law requires it
2. it is needed to protect someone's life, body or property and consent is hard to obtain
3. it passes with a business in a merger or similar succession

5. Processors

We may entrust all or part of the handling of personal information to outside parties, to the extent needed for the purposes above (running the platform, fetching product data, processing payments). We select them with care and supervise them by contract and otherwise as required.

6. Transfers outside Japan

Running the service involves companies located outside Japan, and personal data reaches them:

1. Cloudflare, Inc. (United States) — running the Affely Worker, storage and delivery
2. Amazon.com, Inc. and its affiliates (United States and elsewhere) — fetching product data (ASIN, search keyword, category)
3. Stripe, Inc. and Stripe group companies (United States and elsewhere) — payments

Within Japan, we send JAN codes and product names to Rakuten Group, Inc. and LY Corporation to match the same product for price comparison.

None of these recipients receives anything that identifies a reader.

We make these transfers either with prior consent, or to recipients maintaining arrangements that meet the standards of Japan's Act on the Protection of Personal Information and its enforcement rules. On request, the contact in section 11 will tell you the countries involved, what their data protection regimes provide, and what measures the recipient takes. Where personal data is handled abroad, we take account of that country's regime in the safeguards we apply.

7. Cookies

The plugin sets no cookie in a reader's browser, and click measurement uses none — as set out in section 2, it holds nothing that identifies a reader.

Where a site's theme or other plugins use cookies, that is for the site owner to describe.

8. Security measures

1. Organisational: a named person responsible for data handling; records and review of how data is handled
2. Technical: TLS for transport, access control, site-token authentication, per-licence usage records
3. External environment: where personal data is handled in the countries named in section 6, we take account of that country's data protection regime in the measures we apply

9. How long we keep it

Licence records are deleted or anonymised after the contract ends, once any period the law requires us to keep them has passed. Click measurement data is deleted as it ages past the longest reporting window (60 days).

10. Disclosure, correction and suspension of use

You, or your agent, may ask us to notify you of the purpose of use, to disclose, correct, add to or delete the content, to suspend the use of or erase, or to stop the third-party provision of, the retained personal data we hold about you. Write to the contact in section 11. We verify identity and respond without delay as the law requires. A fee may apply to notification of purpose and to disclosure.

11. Who we are, and how to reach us

12. What the plugin stores in your posts

The product's ASIN — ten characters — and the block's display choices. Nothing else. Titles, prices and images are fetched at render time and held in a cache you can clear from the settings screen; they are never written into your content or into wp_postmeta.

13. Changes to this policy

We change this policy on this page as needed. The new text applies from the moment it is posted.