Studio, the website-building service Liva uses, had its cloud environment accessed without authorization, leaving data retrievable from outside; Studio’s findings put the access at September 30 to October 1, 2026. On October 20 Liva announced that 428 submissions to the inquiry form on its Google Ads landing page, sent between August 20, 2024 and August 7, 2026, may have leaked, including names and their readings, email addresses, phone numbers, cities and the message text. Unauthorized access to Liva’s own services has not been confirmed. Liva plans to notify affected people individually and asks them not to open links or attachments in suspicious messages.
Liva Inc.Google Ads landing page inquiry form
1MinorPossibleAnnounced Checked against sources (2026-10-31)
Studio, the website builder Liva uses, was breached, and 428 inquiry form submissions from August 2024 to August 2026 may have leaked: names, email, phone, city and message. Liva's own services were not accessed.
- Cause
- Via a vendor or service
- Occurred
- 2026-09-30 – 2026-10-01
- Operational impact
- None
Data involved
| Data | Status | Count | Group | Evidence |
|---|---|---|---|---|
| Name | Possible leak | Not disclosed | お問い合わせフォームに入力した人 | Source(opens in a new tab) |
| Email address | Possible leak | Not disclosed | お問い合わせフォームに入力した人 | Source(opens in a new tab) |
| Phone number | Possible leak | Not disclosed | お問い合わせフォームに入力した人 | Source(opens in a new tab) |
| Postal address | Possible leak | Not disclosed | お問い合わせフォームに入力した人 | Source(opens in a new tab) |
| Other | Possible leak | Not disclosed | お問い合わせフォームに入力した人 | Source(opens in a new tab) |
| Other | Possible leak | 428 records | 全対象のフォーム送信の合計(2024年8月20日から2026年8月7日) | Source(opens in a new tab) |
Counts are the figures the organization announced. Because the same person may be counted more than once, we do not add the rows together.
What users should do
- Watch for emails and texts pretending to be the company
General steps based on the type of data involved. Check the organization’s notice or help line to see whether you are affected.
Other incidents naming the same service
- Incidents naming Studio (152 incidents)