Privacy Policy
Last updated: November 2, 2026
LiveCommerce, the trade name of an individual sole proprietor ("we"), provides the Shopify app "JustFlow for LINE" (the "App"). This policy describes the information the App handles.
1. Roles
- The App lets merchants who run a Shopify store (the "Merchant") send LINE messages to their own customers, for example from Shopify Flow, as campaigns or as back in stock alerts.
- We act as the controller of Merchant information.
- For information about the Merchant's customers, we act as a processor on the Merchant's instructions. The Merchant decides why and how that information is used. If you are a customer and want to access or delete your data, please contact the Merchant.
2. Information we handle
Merchant information:
- The store domain, the access token and granted scopes received from Shopify, the display language and the plan.
- The LINE channel IDs and channel secrets the Merchant registers (stored encrypted with AWS KMS), and the display name and Basic ID of the LINE Official Account.
- Test send recipients: the LINE user ID and display name of the Merchant's staff who register through LINE Login, whether they have added the LINE Official Account as a friend, and when they registered (up to 10 per store).
- Messages the Merchant creates: templates, the message of each Shopify Flow step, and campaigns (name, message, type of recipients, the ID and name of the chosen LINE audience, scheduled time, send status, the number of recipients handed to LINE, and LINE's request ID). These are the Merchant's own texts and contain no customer information unless the Merchant writes it into them.
- Performance measurement: the measurement settings (the parameter values to add, the store domains), the names of measurement units, and the number of sends per unit and day.
- Quota warnings: when back in stock alerts could not be sent because the monthly LINE message quota ran out, the time and the number of people who were not sent the alert.
Information about the Merchant's customers:
- When a customer links their LINE account with LINE Login: the Shopify customer ID, the LINE user ID, the time of linking, and whether the customer has added the LINE Official Account as a friend.
- Importing existing links: when the Merchant asks for it, the App reads from Shopify the LINE user IDs that the Merchant had already stored in a customer metafield (
my_fields.line_userid) and creates link records from them. - Send logs (Shopify Flow and test sends): the result, an error code, the Shopify Flow run ID, the customer ID and the time. We do not store the text of the messages we send or the LINE user ID in send logs.
- We pass the text of sent messages to LINE and do not store it. Whether the text contains names or other personal data depends on how the Merchant configures it. However, when the Merchant selects the "深夜は朝まで待って送る" (wait until morning during quiet hours) option on a Shopify Flow step and a send request arrives during the quiet hours the Merchant set, we store the message to be sent (its text, which may include the customer's name or order information depending on the Merchant's settings), the customer ID, the Shopify Flow run ID and the scheduled send time until the quiet hours end, and delete them once the message is sent.
- Campaigns: when a campaign goes to linked customers, the App reads their LINE user IDs from the link records and hands them to LINE. We keep no per-customer record of the send. While a campaign is being sent, we store one customer ID to remember how far the send has got, and delete it when the send ends. When a campaign goes to a LINE audience, LINE decides the recipients and the App handles no customer information.
- Back in stock alert sign-ups: when a shopper signs up from a product page through LINE Login (a linked customer who is logged in to the store can skip LINE Login), the LINE user ID, whether the shopper has added the LINE Official Account as a friend, the IDs and names of the product and variant, and the time of sign-up. For a linked customer, we also store the Shopify customer ID. Each person can sign up for up to 50 items. We delete a sign-up once the alert for it has been sent.
- When a customer links or unlinks, the App passes that customer's ID to Shopify Flow so that the Merchant's workflows can run.
What we retrieve from Shopify on demand (not stored):
- So that the Merchant can tell linked customers apart in the admin, the App retrieves the customer's name (first and last name) from Shopify APIs and shows it on the screen. It is fetched each time the screen opens. We do not store it, write it to logs or send it to LINE.
- Order and shipping notifications: when the Merchant sets up an order notification in Shopify Flow, the App retrieves, for the order that Shopify Flow sends, the order number, date and total, the items (name, quantity, price and image), the order status page URL, the tracking number and carrier, the names of the customer and the recipient, and the shipping address and phone number, and puts them into the LINE message to that order's customer. When the Merchant sends a test message with an existing order, the App sends the same content to the LINE account of the Merchant's staff registered as a test send recipient. In addition, when the Merchant turns on "Receive copies of messages sent by Flow" in the settings, the App sends a copy of each message successfully sent to a customer from Shopify Flow (including this content) to the LINE account of the Merchant's staff registered as a test send recipient. We do not store any of this, including the copies, or write it to logs.
- Back in stock alerts: for the sign-up page and the alert message, the App retrieves the product name, variant name, price, image and product page URL. We store the product and variant names with the sign-up, to show them in the list of sign-ups and in the admin.
- Performance measurement: the App retrieves order IDs, creation times, totals and the measurement parameters of the last visit, and temporarily stores only the number of orders and the total sales per measurement unit. We do not store order IDs or customer information.
Performance measurement:
- The App adds measurement parameters (
utm_source,utm_medium,utm_campaign,utm_content) to links in sent messages that point to the store. The Merchant can turn this off in the settings. - The App attaches a measurement unit to LINE sends and retrieves from LINE the number of people who opened or clicked per unit (LINE does not report numbers below 20). We do not handle the behavior of individual customers.
What we do not collect:
- The App does not retrieve customers' email addresses from Shopify APIs. It retrieves addresses and phone numbers only for the order and shipping notifications above.
- We do not use tracking for third-party advertising, and we do not sell data.
Technical records:
- Access logs (request ID, status, response size) and error records. We do not record personal data, secrets or tokens in them.
- Audit logs of AWS operations (CloudTrail), including access to the database.
3. Purposes
- To send LINE messages to linked customers according to the Shopify Flow workflows the Merchant configures.
- To send the campaigns the Merchant creates to the recipients and at the time the Merchant chooses.
- To include the order details and the shipping destination in order and shipping notifications.
- To tell shoppers on LINE when a product they signed up for is back in stock.
- To link a customer to a LINE account and to unlink it.
- To let the Merchant check the messages they create on their own LINE (test send).
- To let the Merchant check, as copies on their own LINE, the messages sent to customers from Shopify Flow (only when the Merchant turns this on).
- To show the customer's name in the Merchant's admin so that linked customers can be told apart.
- To show the Merchant the results of their messages (sends, opens, clicks, orders and sales).
- To show send results to the Merchant and to investigate failures and abuse.
- To comply with the law.
4. Where data is stored and who processes it
- Data is stored in the AWS Tokyo region (ap-northeast-1). Campaign sending and scheduling use an AWS queue (SQS) and the scheduling service (EventBridge Scheduler) in the same region; for campaigns they hold only the store domain and the campaign ID. Back in stock alerts use the same queue, which holds the store domain, the variant ID and the alert message containing product information (no customer information). To send messages held during quiet hours, the queue and the scheduling service hold only the store domain and the scheduled send time (the messages themselves stay in the storage above).
- To send messages, to run LINE Login, to list audiences and check send status, and to retrieve open and click counts, we send the necessary information to the LINE (LY Corporation) APIs.
- We receive from Shopify the information the App needs to work. We pass customer IDs to Shopify Flow as described above.
- We do not share information with anyone else.
5. Retention
| Information | Retention |
|---|---|
| Link records (customer ID, LINE user ID, time) | Until the customer or the Merchant unlinks. After uninstall, deleted when Shopify sends the deletion request (normally after 48 hours) |
| Send logs | 90 days |
| Templates, Flow step messages, campaigns, measurement settings and unit names | Until the Merchant deletes them. After uninstall, deleted when Shopify sends the deletion request |
| The customer ID kept while a campaign is being sent | Until the send ends |
| Back in stock alert sign-ups | Until the alert is sent or the person cancels (at most 365 days). After uninstall, deleted when Shopify sends the deletion request |
| Back in stock alert messages waiting to be sent (no customer information) | Until sent (normally within 24 hours; messages that could not be processed are kept for up to 14 days to investigate the cause) |
| Messages held during quiet hours (may include customer information) | Until sent (at most 2 days after the scheduled send time) |
| Quota warnings | Until the Merchant dismisses them (at most 31 days) |
| Test send recipients (staff LINE user ID and display name) | Until the Merchant deletes them in settings. After uninstall, deleted when Shopify sends the deletion request |
| Sends per unit and day | 100 days |
| Open and click counts retrieved from LINE | 6 hours |
| Order counts and sales totals | 1 hour |
| Link failure diagnostics | 7 days |
| Duplicate-send protection records | 48 hours |
| Temporary records while linking or signing up for back in stock alerts | 15 minutes |
| Access logs and error records | 30 days |
| AWS audit logs | 365 days |
6. Deletion
- When the Merchant uninstalls the App, we delete the Shopify access token and the LINE channel secrets right away. Scheduled campaigns are then not sent, because the LINE channel is gone.
- On Shopify's
shop/redactrequest, we delete all of that store's data (link records, send logs, LINE channel information, test send recipients, templates, campaigns, measurement records, back in stock alert sign-ups, messages held during quiet hours and quota warnings). - On a
customers/redactrequest, we delete that customer's link record, send logs, the back in stock alert sign-ups that carry that customer's ID and the messages to that customer held during quiet hours. - On a
customers/data_requestrequest, we check the data we hold (whether the customer is linked, when, the number of send logs and the number of back in stock alert sign-ups). - Customers can unlink at any time from the linking page. Unlinking does not change the friend relationship on LINE.
- Shoppers can cancel a back in stock alert sign-up at any time from the sign-up page.
7. Security
- Traffic is encrypted with TLS. Stored data is encrypted; LINE channel secrets are encrypted with a dedicated key (AWS KMS). Backups (point-in-time recovery) are encrypted too.
- Development and production data, keys and permissions are separate. Production data is not copied into development.
- Access to production data is limited to the minimum and is logged. Administrative accounts use strong passwords and multi-factor authentication.
- We have a procedure for security incidents (detection, containment, notification).
8. Changes
We will announce changes to this policy on this page.
9. Contact
- Operator: LiveCommerce (trade name of an individual)
- Email: info.spector.fitness@gmail.com
- Address: not published. We disclose it without delay on request.