[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f19hcefczo64cu":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"modifiedDate":13,"contentUpdatedAt":13,"source":14,"sourceUrl":15,"sourceUrls":16,"pwnCount":17,"affectedCount":17,"affectedCountStatus":18,"affectedCountLowerBound":19,"affectedCountUnit":20,"hasEnglishDescription":4,"severity":21,"dataClasses":22,"description":28,"seoTitle":29,"seoTitleEn":30,"seoDescription":29,"seoDescriptionEn":31,"logoUrl":32,"isVerified":4,"isSensitive":4,"isSpamList":33,"isMalware":33,"company":34},"68e3266eda11adda4882523b","iMenu360","iMenu360 Data Breach","imenu360","imenu360.com","2022-08-11T00:00:00.000Z","2023-08-17T20:55:07.000Z","2026-07-29T14:12:58.498Z","Verified breach records; no first-party response located","https:\u002F\u002Fbreaches.sencode.co.uk\u002Fbreaches\u002Fimenu360",[15],3425860,"known",null,"records","Critical",[23,24,25,26,27],"Email addresses","Latitude and longitude pairs","Names","Phone numbers","Physical addresses","\u003Cp>\u003Cstrong>The iMenu360 2022 data breach\u003C\u002Fstrong> involved the exposure of 3,425,860 customer records believed to have come from online ordering systems used by restaurants. The verified breach record stores 11 August 2022 in its date field while its description places the data in approximately late 2022. Public evidence does not establish an exact access or publication day, so those entries are not converted into a more precise technical timeline.\u003C\u002Fp>\n\n\u003Cp>The source record says multiple attempts were made to contact iMenu360 between April and August 2023 without a response. The event is therefore supported by the verified dataset and breach records; it is not presented as though the company publicly confirmed the event, entry method, actor, or response.\u003C\u002Fp>\n\n\u003Ch2>What information was present?\u003C\u002Fh2>\n\u003Cp>Confirmed fields are email addresses, names, phone numbers, physical addresses, and latitude-longitude pairs. The sources do not list passwords, usernames, payment cards, bank accounts, or products ordered. They also do not establish that every field appeared in every record. Because an address combined with coordinates can identify a home, workplace, or another delivery point more precisely, the event is sensitive from a location-privacy perspective.\u003C\u002Fp>\n\n\u003Ch2>Privacy boundary and safe next steps\u003C\u002Fh2>\n\u003Cp>An email match does not establish that a person ordered from a particular restaurant, which products were purchased, that a payment occurred, or that the person still lives at a listed address. Those inferences should not be shared or used against anyone. Unexpected delivery, refund, coupon, address-verification, or payment-update messages should be checked through a known restaurant or ordering-service channel rather than a link in the message. Because password and card data are not confirmed for this event, this record alone should not be treated as proof that either was exposed.\u003C\u002Fp>","","iMenu360 2022 Data Breach (3.4 Million Records)","The iMenu360 breach exposed 3,425,860 customer records. Review the email, phone, address, and coordinate data scope.","\u002Fuploads\u002Flogo\u002Fimenu360_com.webp",false,{"name":7,"sector":35,"country":36,"website":10,"websiteArchiveUrl":29,"websiteStatus":29,"websiteCheckedAt":19},"Restaurant Online Ordering","United States"]