01 What this page is
A customer can ask us for an export of its data during its subscription. It can also ask for a full export when its agreement ends or when it moves to another provider. Paragraph 5 of the Exit and Portability Annex of our customer agreement lists the data.
This page is the register of the structures and formats of that data, which paragraph 7.2 of the Exit and Portability Annex promises. Article 26 of the EU Data Act (Regulation (EU) 2023/2854) asks for such a register.
A partner is a restaurant, hotel or other business that the customer supplies. The numbers in the table are the row numbers of paragraph 5.
02 The data that a customer can export
| Data | What it holds | Format | Standard |
|---|---|---|---|
| 1. Briefs (menu analyses) | For each partner: the dishes, the ingredients mapped to them, and the comparison with the product catalogue and with the deliveries. Each Brief names the menu version that it comes from. | JSON, as stored, and a summary table in CSV | JSON: RFC 8259. CSV: RFC 4180, in UTF-8 |
| 2. Menu files | The menu files that the customer's users uploaded. These include published versions, uploads and requests that we have not yet analysed, drafts, and uploads that were never submitted. Also the copies of such files that we keep for quality testing. Also the menu records: the name, the validity dates, the archive state and the uploader of each menu. | The original file format, and CSV for the menu records | The standard of each file's own format (section 04). CSV: RFC 4180, in UTF-8 |
| 3. Partner and product lists | The partner list and the product list as the customer supplied them, with the changes made in MenuMap | CSV | CSV: RFC 4180, in UTF-8 |
| 4. Product mapping | The mapping of each product to an ingredient, and the substitution rules that the customer approved | CSV | CSV: RFC 4180, in UTF-8 |
| 5. Delivery facts | The facts that MenuMap derives from the order and delivery records. For each partner and product: the order and delivery dates and the presence of the product. For each partner and ingredient: the first and the last delivery date and the status. | CSV | CSV: RFC 4180, in UTF-8 |
| 6. Order rhythm results | The order rhythm results for each partner and ingredient | CSV | CSV: RFC 4180, in UTF-8 |
| 7. Sales team work | Opportunity states, annotations, comments and replies, dish corrections, notes, tasks with their due dates, reminders with their dates, and partner profile entries. Each entry has its author, its time and its history. Also the activity log and the record of when each opportunity was first shown. | JSON, as stored, and CSV | JSON: RFC 8259. CSV: RFC 4180, in UTF-8 |
| 8. Reporting tables | The partner status and opportunity tables that MenuMap writes to the customer's database | CSV | CSV: RFC 4180, in UTF-8 |
| 9. Read markers | When each user last opened each partner | CSV | CSV: RFC 4180, in UTF-8 |
| 10. Users and access | The name, the email address and the role of each user, and the partners assigned to each. Also the access lists that the customer supplied, and the history of access changes. | CSV or JSON | CSV: RFC 4180, in UTF-8. JSON: RFC 8259 |
| 11. Settings | The group companies, the customer spaces, the modules switched on, the language and other settings of the customer, and the customer's look and logo | JSON, and the logo in its original format | JSON: RFC 8259. The logo: PNG (ISO/IEC 15948) or WebP (RFC 9649) |
| 12. Usage records | Only if usage recording was on. The active minutes of each user per partner and day, and the first and the last active time. Also the record of the confirmation that switched usage recording on. | CSV | CSV: RFC 4180, in UTF-8 |
| 13. Requests | The correction and re-analysis requests of the users, with their status | CSV | CSV: RFC 4180, in UTF-8 |
| 14. Request logs | The records of the sign-in codes that MenuMap sent, and of each attempt to use them, from the logs of our API. We keep these logs for 90 days. | CSV | CSV: RFC 4180, in UTF-8 |
| 15. Competitor data | The competitors that the customer named, and the matching of their products to the customer's products. The competitor prices that users recorded, with the competitors of each partner. | CSV | CSV: RFC 4180, in UTF-8 |
| 16. Lead lists | Each lead list that MenuMap delivered | CSV | CSV: RFC 4180, in UTF-8 |
| 17. Quote lists | Each price request that the customer sent and each file that MenuMap returned, while MenuMap keeps them | The original format, and CSV | The standard of each file's own format. CSV: RFC 4180, in UTF-8 |
Some rows exist only for a customer that uses the function, for example usage records, competitor data, lead lists and quote lists. If the customer's Order Form adds a module, the Order Form lists the exportable data of that module.
03 How we build the files
- CSV files use UTF-8 and a header row.
- We export JSON files as MenuMap stores them, with a description of their fields.
- Menu files keep their original format. The logo keeps its original format too.
- On the customer's written instruction, we give the exports to a provider that the customer names, in the same formats and free of charge.
04 Standards and specifications
| Format | Standard or specification |
|---|---|
| CSV | RFC 4180, Common Format and MIME Type for Comma-Separated Values (CSV) Files |
| JSON | RFC 8259, The JavaScript Object Notation (JSON) Data Interchange Format |
| UTF-8 (the character encoding of CSV files and of pasted menu text) | RFC 3629, UTF-8, a transformation format of ISO 10646 |
| PDF menu files | ISO 32000 |
| Word (.docx) and Excel (.xlsx) menu files | Office Open XML, ISO/IEC 29500 |
| Older Excel (.xls) menu files | Microsoft's open specification [MS-XLS] |
| JPEG photos | ISO/IEC 10918-1 |
| PNG photos and logos | ISO/IEC 15948, and the W3C PNG specification |
| WebP photos and logos | RFC 9649, WebP Image Format |
| Pasted menu text | Plain text in UTF-8 (RFC 3629) |
05 Data that we do not export
- The source code of MenuMap.
- The prompts, the model settings and the analysis method.
- MenuMap's ingredient list as a whole, with its aliases, its categories and its mapping rules. The ingredient names in rows 1, 4, 5 and 6 come with those rows.
- Password hashes and session identifiers, because their export would weaken the security of MenuMap.
This list is complete. It never covers data that the customer, its group companies or its users supplied, or that MenuMap produced only for them.
06 Questions
Write to hello@menumap.ai.