The form builder was the file

Each site mailed its own enquiry box. The box still sat on one cloud.

Studio said today that a third party reached its cloud and that data inside that environment could be taken. It is telling customers through a portal and at login. The rooms then counted. Link-U: 7,663 corporate-site enquiries. Raksul: 6,412 on a guide site, not the print-shop member file. Luup: 21,368 old web-form sends, not the scooter app. Saitama’s museum: 162 event sign-ups. Fuller, Fukuoka Growth Next, Kyoto, and a stack of others issued the same shape of letter. Those numbers are rooms. They are not a second incident.

The fields repeat: name, email, phone, whatever the form asked. A password-protected page and an API hook are in the vendor’s own list of things to check. Cards are not the default on a contact form. Do not invent them.

What a 21,368-row letter will be asked to mean

It will be briefed as “Luup lost twenty thousand riders.” The app registration is out of this file. It will be briefed as Raksul’s print customers. The print account is out. Adding a city museum does not empty the next tenant, and it does not make the next tenant this room.

If a company mailed you, the fields on that form are the incident. If a company has not written, you are in the vendor’s ceiling until that letter arrives. A Studio login reset is not a finding that the tenant’s product was reached. A mail that already knows the enquiry text is the next page of the same form.

The tenants will keep issuing their own counts. Add them only after you have subtracted the overlap. The builder does not issue a new copy each time a logo speaks.