Last updated: 2026-11-06 · 日本語版
This is an English translation of the Japanese policy. If the two versions differ, the Japanese version is the one that applies.
memoro ("the extension") is a Chrome extension designed with your privacy as the first priority. It never collects or transmits the flashcards you create or your study data. The only time it communicates with an outside service is when you buy or restore the one-time unlock, and then only with ExtensionPay / Stripe to process the payment.
The purchase feature (including regional pricing), the review timer, and the links to the feedback form are features of version 0.3.0 and later.
We do not collect study data. The extension does not collect the flashcards you create, your review progress, your browsing history, or usage analytics. It uses no cookies and no tracking technology.
Exception (only if you buy the unlock):
If you buy the paid version (a one-time purchase; ¥600 in Japan, shown in your local currency elsewhere), the
extension communicates with the payment service ExtensionPay (which uses Stripe) to check your purchase status and
to restore a purchase on another device. In that case,
the ExtensionPay library stores your purchase status, including the email address you entered at checkout, in
chrome.storage.sync (or chrome.storage.local when sync is not available).
If Chrome Sync is turned on, this information is synced to your other devices through your Google
account
(your flashcards themselves stay in chrome.storage.local only and are never synced). The extension
never shows or exports this information in its screens, card manager, or export files. See "Operations that
communicate with a server" below.
How the regional price is chosen: The price shown on the purchase button is chosen on your device from your device's time zone and language settings. The time zone and language settings themselves are never sent anywhere. Only when you press the purchase button does the name of the chosen price plan (for example, the US dollar plan) go to ExtensionPay so that the checkout page can show the right price.
The flashcards you create (front and back text, tags, the URL and title of the source page, and review progress)
and your settings are stored
only in your browser's local storage (chrome.storage.local).
http and https source URLs are stored; URLs in any other scheme are discarded when
the card is saved.
The extension can communicate with ExtensionPay (Stripe handles the payment itself) to process a purchase. This happens only during the operations listed below. Everything else, including installing the extension, creating cards, reviewing, managing cards, and export/import (JSON and CSV), involves no network communication at all.
| Operation | Network |
|---|---|
| Installing the extension, creating, reviewing, editing, or deleting cards, export/import (JSON and CSV) | None |
| Pressing the purchase button on the settings page (in the Japanese UI the label is "600円で無制限にする（買い切り）", which means "Unlock unlimited cards for ¥600 (one-time)") | Yes (fetching plan information, opening the checkout page, checking purchase status) |
| Pressing "Already purchased?" on the settings page (to restore a purchase made on another device) | Yes |
| Pressing "Recheck purchase status" on the settings page | Yes |
| Anything else (including normal use after a purchase) | None |
The extension does not check your license in the background. Unless you perform one of the operations above, it never contacts ExtensionPay.
When you press "Send feedback", "Share your thoughts", or "Write a review on the store" on the settings page or in the popup, a Google Form or the Chrome Web Store review page opens in a new browser tab. The extension itself sends nothing to these pages. The feedback form URL carries only the extension's version number (for example, 0.3.0) so that we can read your answer in context; it never includes card content or personal information. Anything you type and submit on those pages is handled under the privacy policy of the page's operator (Google).
We do not share or sell study data (such as card content) with anyone. Only during a purchase does the extension communicate with the following payment processors.
| Processor | Purpose | Privacy policy |
|---|---|---|
| ExtensionPay LLC | Payment platform for browser extensions | extensionpay.com/privacy.html |
| Stripe, Inc. | Credit card processing (through ExtensionPay) | stripe.com/privacy |
| Permission | Purpose |
|---|---|
storage |
To store your flashcards and settings (including purchase status) in your browser |
contextMenus |
To show the right-click menu item "Add a card to memoro" |
activeTab / scripting |
To show the save dialog temporarily in the current tab when you use the right-click menu, the keyboard shortcut, or the popup button |
alarms |
To refresh the "due today" count periodically (at most once an hour) and to schedule the review timer notification |
notifications (optional) |
Only if you turn on the review timer's notifications, to show "You have N cards to review today" once a day at the time you set. No notification appears on days with no due cards, and notifications never include card content (front or back) |
The extension requests no host_permissions. Communication with the payment server for the purchase
feature works without any additional permanent site access. None of the permissions is used to send study data
anywhere.
notifications is an optional permission. It is not requested at install time; Chrome asks for it only
when you turn on the review timer's notifications. Notifications are shown on your device by Chrome, and no
network communication is involved. Turn notifications off and no further notifications appear.
chrome.storage.sync, Chrome Sync has also copied it to your other synced devices, so to remove it
completely you must uninstall the extension on every device or delete the data from Chrome's sync settings.
Because the extension collects no study data, it can be used safely at any age. Buying the paid version requires a payment method such as a credit card, with a parent's or guardian's consent.
When this policy changes, we update the "Last updated" date on this page and describe the change in the revision history below.
alarms permission to match its actual behavior.
chrome.storage.local to the
actual chrome.storage.sync (falling back to local when sync is unavailable). Added that
it is copied to other devices when Chrome Sync is on, and what that means for deletion.
notifications
permission, the use of alarms to schedule the notification, and the storage of review timer
settings.
Questions about this policy:
Email: meer076th@gmail.com