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: 17 October 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 nine 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
5. which block in the post the link was in (an eight-character ID the plugin gives a block when it is placed, so two placements of the same product in one post can be counted apart; it says nothing about the reader)
6. what kind of link it was (a card, a ranking, a price comparison and so on)
7. its row in a ranking (rankings only)
8. whether the link went through an affiliate network's redirect (clicks only)
9. whether an ad blocker was running on that page (a single 0 or 1, once per page — not per reader and not per view)

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). Where the site owner has entered their own Creators API credentials these do not pass through the Affely Worker: they go from that site's own server to api.amazon.com or creatorsapi.auth.us-west-2.amazoncognito.com for a token, then to creatorsapi.amazon for the catalogue
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. Where the site owner has entered their own Rakuten Web Service application ID or Yahoo! Shopping client ID, search keywords and item codes for Rakuten and Yahoo! Shopping products do not pass through the Affely Worker: they go from that site's own server to openapi.rakuten.co.jp and shopping.yahooapis.jp.

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 12 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. Affiliate network beacons

When the site owner has entered a Moshimo or ValueCommerce ID, the plugin renders a 1x1 image on each card. This is the impression count those networks require in order to attribute a sale. The images load from:

• Moshimo Affiliate (moshimo, Inc.) — https://i.moshimo.com/af/i/impression
• ValueCommerce (ValueCommerce Co., Ltd.) — https://ad.jp.ap.valuecommerce.com/servlet/gifbanner

These load in the reader's own browser, directly from the network. The network therefore receives that reader's IP address and user agent, and may set a cookie of its own. What it does with them is governed by that network's privacy policy. We receive nothing from these requests.

With no ID entered for a network, or with that mall switched off in the settings, the image is not rendered.

When the site owner has also entered a ValueCommerce LinkSwitch ID (vc_pid), the plugin adds a tag to every page of the site that loads ValueCommerce's script https://aml.valuecommerce.com/vcdal.js. It is the same LinkSwitch tag ValueCommerce hands out, and it turns plain links to its participating advertisers into affiliate links in the reader's browser. This script also loads in the reader's own browser, directly from ValueCommerce, which therefore receives that reader's IP address and user agent and may set a cookie of its own. We receive nothing from these requests. With no ID entered, the tag is not output.

8. Cookies

We set 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. The beacons in section 7 are the networks' own, not ours.

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

9. 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

10. 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 is aggregated the moment it arrives, into one row per day holding the date, the post ID, the ASIN, the marketplace, the counts of views and clicks, and how many of those came from a browser running an ad blocker. No record of an individual view or click is kept, and nothing in a row identifies a reader. We put no upper limit on how long these daily counts are held, so that a site owner can compare periods going back as far as they have been measuring.

11. 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.

12. Who we are, and how to reach us

13. 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.

14. Changes to this policy

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