{ "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "tool": { "slug": "tablecheck", "name": "TableCheck API", "vendor": "TableCheck Inc.", "vendorUrl": "https://www.tablecheck.com", "kind": "http-api", "category": "local-bookings", "summary": "TableCheck is a restaurant reservation and guest management platform used mainly in Japan and Asia. Its API components cover availability, booking, CRM, POS and distribution to booking sites, with an MCP server for merchants.", "url": "https://www.anchorterminal.com/tools/tablecheck", "markdownUrl": "https://www.anchorterminal.com/tools/tablecheck.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tablecheck.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tablecheck.json", "license": "Proprietary service under the TableCheck API Terms of Service", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.tablecheck.com/api/", "packages": [], "auth": "api-key", "authNotes": "Sales-led. Email api@tablecheck.com, complete the API Portal questionnaire and accept the API terms. Each approved request gets one `secret_key` per environment in the `Authorization` header, limited to the approved components and, for aggregators, approved venues. The API team rolls keys on request. The MCP server needs the `mcp_merchant` component added to a key (https://tablecheck.atlassian.net/wiki/spaces/API/pages/44630975).", "pricing": "paid", "pricingNotes": "No public price. The access page says \"Fees may vary\" and pricing is given during the application. No free tier. Test accounts and test data are prepared on request (https://tablecheck.atlassian.net/wiki/spaces/API/pages/43909423, checked 2026-10-14).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation or the OpenAPI files read (checked 2026-10-14).", "endpoints": [] }, "toolCount": 20, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://tablecheck.atlassian.net/wiki/spaces/API/overview", "openapi": "https://api.tablecheck.com/api/booking/v1/docs", "capabilities": [ "booking.availability", "booking.reservations", "booking.venue", "booking.orders" ], "tags": [ "hosted", "closed-source", "rest", "openapi", "mcp", "sales-led", "status-page", "diner-side", "venue-side" ], "graded": true, "anchor": { "graded": true, "score": 57.1, "grade": "C", "agentReady": false, "rank": 661, "ranked": true, "rankOf": 1076, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 35, "payments": 0, "reliability": 80, "schema": 77, "security": 46, "transparency": 66 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 80, "points": 16, "reason": "Graded on the hosted REST API and the MCP for Merchants endpoint. Statuspage site at tablecheck.statuspage.io with a \"TableCheck Third Party API\" component (20). No incident in the 90 days to 14 October 2026. The most recent posted incident is from 22 February 2023, so the page may be little used, which we note without deducting (30). 10,000 requests per 5 minutes for each API component (15). 429 is documented with an instruction to wait for the next 5-minute period, without Retry-After. The REST booking flow uses a 5-minute table blockage before a reservation, and MCP writes take an idempotency key, but REST POST /reservations has none (7). No SLA, and the rate-limit page says the limit is not a service level commitment (0). Availability and Booking v1 are live. MCP for Merchants is marked under development (8). Total 80." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 77, "points": 12.51, "reason": "Each component serves an OpenAPI 3.0 YAML at its /docs URL, for example Booking v1 at https://api.tablecheck.com/api/booking/v1/docs (25). No llms.txt or Markdown docs. The guides live on a Confluence site (0). Guide pages name the target audience, compare the three booking APIs and say what each is not for, and the MCP page lists what it should not be used for (17). The Booking spec has 27 enums and required fields (12). The Booking spec documents 51 4xx responses with examples, and the guides give request examples (13). Major versions in the path, a written change and deprecation policy and an announcements page, but no dated changelog (10). Total 77." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 72, "points": 11.7, "reason": "The MCP server has 20 tools, filtered to the components a key holds, and returns compact projections with personal data omitted unless asked (15 + 5). REST lists filter by date, venue and guest, and MCP results are capped (15). 401 and 403 are explained, and the MCP validates dates strictly so a model can correct the call (16). MCP write tools take `idempotency_key` and carry destructiveHint. REST booking has no idempotency key but a blockage hold (16). A JavaScript Booking Form SDK exists, with no server SDKs (5). Total 72." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 46, "points": 8.05, "reason": "One `secret_key` per environment issued by the API team and rolled on request, with access limited to the components and venues approved for the key. No self-serve rotation or OAuth (20). Keys can be set to read-only for the MCP, write tools are marked destructive, and guest names, phones and emails are omitted from MCP results unless requested (17). The MCP page states its trust assumptions (human in the loop, the key as the boundary, personal data redacted) but gives no prompt-injection guidance for guest-written notes (6). No audit log found (0). www.tablecheck.com/.well-known/security.txt returns an HTML page, not a security.txt. The trust centre at trust.tablecheck.com renders with JavaScript only and was not read (3). Total 46." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 0, "points": 0, "reason": "No x402, MPP or L402 (0). \"Fees may vary\", with pricing given during the application (0). No free tier. Test accounts and data are prepared on request (0). Access starts with an email to api@tablecheck.com and a case-by-case review (0). Total 0." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 35, "points": 3.06, "reason": "Read for a closed service. The MCP for Merchants page was last edited on 20 September 2026, and Messaging v1 and Custom Email Domain v1 in July 2026, which we count as the latest dated changes (30). No dated changelog with three entries in 90 days (0). Support by email (api@tablecheck.com, support@tablecheck.com), with no public issue tracker or forum (5). No server SDKs, and the MCP server is not in the official MCP registry (0). No package to judge (0). Total 35." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 66, "points": 5.78, "note": "editorial 45, provenance 86", "reason": "Closed service under published TableCheck API Terms of Service (enacted 10 December 2018) with TableCheck, Inc. (15). The privacy policy, revised 14 September 2026, says most information is retained indefinitely unless law or a deletion request requires otherwise (10). A written API change policy promises backwards compatibility within a major version and a deprecation process, and the tablesolution.com URL retirement was announced with dates (3 June and 2 October 2026) (18). Third-party processors are not named and no data locations are given (2). Total 45." } ], "assessment": { "date": "2026-10-14", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "The MCP server has 20 tools, filtered to the components a key holds, and returns compact projections with personal data omitted unless asked (15 + 5). REST lists filter by date, venue and guest, and MCP results are capped (15). 401 and 403 are explained, and the MCP validates dates strictly so a model can correct the call (16). MCP write tools take `idempotency_key` and carry destructiveHint. REST booking has no idempotency key but a blockage hold (16). A JavaScript Booking Form SDK exists, with no server SDKs (5). Total 72.", "maintenance": "Read for a closed service. The MCP for Merchants page was last edited on 20 September 2026, and Messaging v1 and Custom Email Domain v1 in July 2026, which we count as the latest dated changes (30). No dated changelog with three entries in 90 days (0). Support by email (api@tablecheck.com, support@tablecheck.com), with no public issue tracker or forum (5). No server SDKs, and the MCP server is not in the official MCP registry (0). No package to judge (0). Total 35.", "payments": "No x402, MPP or L402 (0). \"Fees may vary\", with pricing given during the application (0). No free tier. Test accounts and data are prepared on request (0). Access starts with an email to api@tablecheck.com and a case-by-case review (0). Total 0.", "reliability": "Graded on the hosted REST API and the MCP for Merchants endpoint. Statuspage site at tablecheck.statuspage.io with a \"TableCheck Third Party API\" component (20). No incident in the 90 days to 14 October 2026. The most recent posted incident is from 22 February 2023, so the page may be little used, which we note without deducting (30). 10,000 requests per 5 minutes for each API component (15). 429 is documented with an instruction to wait for the next 5-minute period, without Retry-After. The REST booking flow uses a 5-minute table blockage before a reservation, and MCP writes take an idempotency key, but REST POST /reservations has none (7). No SLA, and the rate-limit page says the limit is not a service level commitment (0). Availability and Booking v1 are live. MCP for Merchants is marked under development (8). Total 80.", "schema": "Each component serves an OpenAPI 3.0 YAML at its /docs URL, for example Booking v1 at https://api.tablecheck.com/api/booking/v1/docs (25). No llms.txt or Markdown docs. The guides live on a Confluence site (0). Guide pages name the target audience, compare the three booking APIs and say what each is not for, and the MCP page lists what it should not be used for (17). The Booking spec has 27 enums and required fields (12). The Booking spec documents 51 4xx responses with examples, and the guides give request examples (13). Major versions in the path, a written change and deprecation policy and an announcements page, but no dated changelog (10). Total 77.", "security": "One `secret_key` per environment issued by the API team and rolled on request, with access limited to the components and venues approved for the key. No self-serve rotation or OAuth (20). Keys can be set to read-only for the MCP, write tools are marked destructive, and guest names, phones and emails are omitted from MCP results unless requested (17). The MCP page states its trust assumptions (human in the loop, the key as the boundary, personal data redacted) but gives no prompt-injection guidance for guest-written notes (6). No audit log found (0). www.tablecheck.com/.well-known/security.txt returns an HTML page, not a security.txt. The trust centre at trust.tablecheck.com renders with JavaScript only and was not read (3). Total 46.", "transparency": "Closed service under published TableCheck API Terms of Service (enacted 10 December 2018) with TableCheck, Inc. (15). The privacy policy, revised 14 September 2026, says most information is retained indefinitely unless law or a deletion request requires otherwise (10). A written API change policy promises backwards compatibility within a major version and a deprecation process, and the tablesolution.com URL retirement was announced with dates (3 June and 2 October 2026) (18). Third-party processors are not named and no data locations are given (2). Total 45." }, "sources": [ { "what": "API documentation home", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/43909423", "seen": "2026-10-14" }, { "what": "Getting Started", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/44630975", "seen": "2026-10-14" }, { "what": "Booking APIs comparison", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/4687527943", "seen": "2026-10-14" }, { "what": "Booking v1", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/160334455", "seen": "2026-10-14" }, { "what": "Availability v1", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/46301274", "seen": "2026-10-14" }, { "what": "MCP for Merchants v1", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/4846682134", "seen": "2026-10-14" }, { "what": "Rate Limits \u0026 Cutoff", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/2060910685", "seen": "2026-10-14" }, { "what": "API Change Policy", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/44859552", "seen": "2026-10-14" }, { "what": "API Announcements", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/2603253889", "seen": "2026-10-14" }, { "what": "API Terms of Service", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/61571353", "seen": "2026-10-14" }, { "what": "Booking v1 OpenAPI", "url": "https://api.tablecheck.com/api/booking/v1/docs", "seen": "2026-10-14" }, { "what": "status components and incidents", "url": "https://tablecheck.statuspage.io/api/v2/incidents.json", "seen": "2026-10-14" }, { "what": "privacy policy", "url": "https://www.tablecheck.com/en/policy/privacy", "seen": "2026-10-14" }, { "what": "wiki page list", "url": "https://tablecheck.atlassian.net/wiki/rest/api/space/API/content", "seen": "2026-10-14" } ], "openQuestions": [ "unchecked: the trust centre at trust.tablecheck.com, which renders with JavaScript only", "The status page shows no incident since 22 February 2023, which may mean it is rarely updated", "The MCP page's stdio bridge example uses https://api.staging-qa.tablecheck.com/api/mcp/v1, while the endpoint given elsewhere on the page is /api/mcp_merchant/v1", "The MCP tool list was read from the docs page. No call was made to the live MCP server", "Only Booking v1's OpenAPI file was read in full. The other components' specs were not fetched", "Acts for both sides. Booking v1 is limited to first-party users (venue operators or their integration partners)" ] }, "negative": 0, "verdict": "TableCheck publishes OpenAPI specs for availability, booking, CRM and POS components and a merchant MCP server with read-only keys, idempotent writes and personal data hidden by default. Access is by email application with case-by-case approval and unpublished fees, the MCP server is still under development, and no audit log or dated changelog was found.", "bestFor": "Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.", "strengths": [ "OpenAPI 3.0 YAML served for each component, with a written change and deprecation policy", "Separate APIs for diner-side platforms (Availability, Distribution, Web Booking) and venue-side systems (Booking, CRM, POS)", "MCP for Merchants hides guest names, phones and emails unless asked and supports read-only keys", "MCP write tools take an idempotency key and are annotated destructive", "Rate limit stated as 10,000 requests per 5 minutes per component" ], "weaknesses": [ "Access needs an emailed application, case-by-case approval and fees quoted privately", "MCP for Merchants is under development and its tools may change without a version bump", "REST POST /reservations has no idempotency key", "Keys are issued and rolled only by the API team, with no audit log found", "Booking v1 needs per-venue approval for aggregators, and only a production environment exists by default" ], "agentNotes": [ "Decide which side you act for. Distribution and Web Booking serve diner-facing platforms, while Booking, CRM, POS and the MCP serve the venue", "Ask the operator for a read-only key before using the MCP, as TableCheck recommends, and avoid cancellations through it", "Call `hold_table` (MCP) or POST /blockages (REST) before booking, since availability is a snapshot and a blockage expires in 5 minutes", "Send dates as YYYY-MM-DD and convert the UTC times returned to the venue's time zone from `list_shops`", "Stay under 10,000 requests per 5 minutes per component and wait for the next window after a 429" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.1 } ], "editorialScores": { "ergonomics": 72, "maintenance": 35, "payments": 0, "reliability": 80, "schema": 77, "security": 46, "transparency": 45 }, "provenanceScore": 86 }, "connect": { "claudeCode": "claude mcp add --transport http tablecheck \\\n https://api.staging-qa.tablecheck.com/api/mcp_merchant/v1 \\\n --header \"Authorization: Bearer $TABLECHECK_API_KEY\"", "config": { "mcpServers": { "tablecheck": { "headers": { "Authorization": "Bearer ${TABLECHECK_API_KEY}" }, "type": "http", "url": "https://api.staging-qa.tablecheck.com/api/mcp_merchant/v1" } } } }, "letme": { "capability": "https://letme.dev/booking.availability", "tool": "https://letme.dev/tablecheck" }, "notable": [ "MCP for Merchants v1 is \"Under Development\", and TableCheck asks users not to build unattended integrations against it (https://tablecheck.atlassian.net/wiki/spaces/API/pages/4846682134)", "The MCP server exposes 20 tools across availability, booking, CRM and POS, from `check_availability` and `hold_table` to `cancel_reservation` and `set_table_status` (https://tablecheck.atlassian.net/wiki/spaces/API/pages/4846682134)", "Three booking APIs, Distribution v1 and Web Booking v1 for listing and travel sites and Booking v1 for merchant-owned sites (https://tablecheck.atlassian.net/wiki/spaces/API/pages/4687527943)", "A REST blockage locks a table for 5 minutes before POST /reservations and can be renewed (https://tablecheck.atlassian.net/wiki/spaces/API/pages/160334455)", "Rate limit of 10,000 requests per 5 minutes per component, with a hard cutoff (https://tablecheck.atlassian.net/wiki/spaces/API/pages/2060910685)", "Old api.tablesolution.com URLs returned 308 from 3 June 2026 and were to be shut off by 2 October 2026 (https://tablecheck.atlassian.net/wiki/spaces/API/pages/2603253889)" ], "area": "everyday", "details": [ { "label": "Surface graded", "value": "The REST API components at https://api.tablecheck.com/api/ and MCP for Merchants v1, read from the Confluence API space, the Booking v1 OpenAPI file and the status page on 14 October 2026" }, { "label": "Acts for", "value": "Both. Availability, Distribution and Web Booking serve diner-facing booking and listing sites. Booking, CRM, POS and the MCP serve the venue" }, { "label": "Booking cycle", "value": "Availability API for dates and times, a 5-minute blockage, POST /reservations, PUT to amend and PUT /reservations/{id}/cancel, with Sync webhooks for changes" }, { "label": "Payments and deposits", "value": "Booking v1 and Distribution v1 don't take payments. Web Booking v1 redirects to TableCheck's hosted page when payment is needed" }, { "label": "MCP server", "value": "Streamable HTTP at /api/mcp_merchant/v1, staging and production, bearer key. 20 tools, read-only keys recommended, personal data omitted by default. Under development" }, { "label": "Rate limits", "value": "10,000 requests per 5 minutes per component. 429 when exceeded, then wait for the next window" }, { "label": "Coverage", "value": "TableCheck says it is used in over 3,000 restaurants in over 20 countries" } ], "provenance": { "legalEntity": "TableCheck Inc.", "domain": "tablecheck.com", "domainRegistered": "1998-07-01", "endpointOnVendorDomain": true, "terms": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/61571353/TableCheck+API+Terms+of+Service", "privacy": "https://www.tablecheck.com/en/policy/privacy", "statusPage": "https://tablecheck.statuspage.io", "changelog": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/2603253889", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The API Terms of Service (enacted 10 December 2018) are with TableCheck, Inc. outside Mainland China and its designated entity inside it.", "The privacy policy (revised 14 September 2026) names TableCheck Inc., KR Ginza II 5F, 2-15-2 Ginza, Chuo-ku, Tokyo.", "The API documentation is hosted on tablecheck.atlassian.net. api.tablecheck.com redirects there.", "www.tablecheck.com/.well-known/security.txt returns an HTML page, read as no security.txt.", "RDAP gives a registration date of 1998-07-01 for tablecheck.com." ], "score": 86, "checks": [ { "check": "Legal entity named", "value": "TableCheck Inc.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "tablecheck.com, registered 1998-07-01 (28 years)", "points": 15, "max": 15, "state": "ok" }, { "check": "Endpoint on the vendor's domain", "value": "api.tablecheck.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 6 of the 7 things a reader expects, and has 1 clause that costs points", "points": 7.1, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 7 of the 8 things a reader expects", "points": 9.3, "max": 10, "state": "part" }, { "check": "Status page", "value": "tablecheck.statuspage.io", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" } ], "policies": [ { "kind": "terms", "url": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/61571353/TableCheck+API+Terms+of+Service", "state": "read", "readAt": "2026-10-14", "statedDate": "2022-10-11", "words": 3263, "points": 7.1, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": true, "quote": "Updated 2022-10-11", "says": "Last updated 2022-10-11" }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "If the need for legal proceedings should arise between the parties hereto in relation to this Agreement, the People’s Court of Beijing will have exclusive jurisdiction.", "says": "Disputes go to the courts of Beijing" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "9.1 IN NO EVENT WILL OUR AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THE AGREEMENT (WHETHER IN CONTRACT OR TORT OR UNDER ANY OTHER THEORY OF LIABILITY) EXCEED ONE HUNDRED U.S." }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "6.1 You may terminate the Agreement by discontinuing use of our APIs." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": true, "quote": "If we make a material change to the Agreement, we will provide you with reasonable notice prior to the change taking effect, either by emailing the email address associated with your account or by messaging you through the Services.", "says": "Says it gives notice of a change" }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "2.1 You will not access our APIs or documentation in violation of any law or regulation, including without limitation laws regarding the import or export of data or software, privacy, and local laws." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": false } ], "toKnow": [ { "key": "terms.benchmark", "label": "Restricts benchmarking or competitive use", "found": true, "quote": "…monitor the availability, performance, or functionality of any of the API or Services or for any similar benchmarking purposes.", "costsPoints": true }, { "key": "terms.cutoff", "label": "Says access can be ended without notice or for any reason", "found": true, "quote": "We may terminate the Agreement with or without cause and without notice to you." }, { "key": "old", "label": "Has not been updated for three years or more", "found": true, "quote": "Updated 2022-10-11" } ], "notes": [ { "date": "2026-10-14", "text": "Liability for all claims under the agreement is capped at 100 US dollars.", "quote": "IN NO EVENT WILL OUR AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THE AGREEMENT (WHETHER IN CONTRACT OR TORT OR UNDER ANY OTHER THEORY OF LIABILITY) EXCEED ONE HUNDRED U.S. DOLLARS ($100.00)." }, { "date": "2026-10-14", "text": "The developer grants TableCheck a licence to use its company name and logo in marketing and promotional communications.", "quote": "You grant us a non-exclusive, royalty-free, fully paid-up, worldwide right and license to use your company name and logo as a reference for marketing or promotional purposes on our website and in other public or private communications with our existing or potential developers and customers" } ] }, { "kind": "privacy", "url": "https://www.tablecheck.com/en/policy/privacy", "state": "read", "readAt": "2026-10-14", "statedDate": "2016-12-14", "words": 3373, "points": 9.3, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "Revised on December 14, 2016", "says": "Last updated 2016-12-14" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "The information we collect and its purpose of use is listed as follows:" }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "In order to achieve the purposes presented in Article 1, we retain most types of information indefinitely, except where otherwise limited by applicable laws, merchant-specific policies, or when deletion has been requested." }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "The Company may, within the scope of this policy and subject to applicable laws and regulations, consign all or part of your personal information to a third-party service, provided that such service has enacted adequate data protection measures." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": true, "quote": "We acquire and use personal information to the extent necessary for the development, sale, and operation of systems and services for reservation, customer management, business management, promotion, online sales, employee management, etc., intended for use in restaurants and other outlets." }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": false }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "Title: Data Protection Officer", "says": "Names a data protection officer" }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "When collecting or transferring your personal information, we employ data encryption technology and restrict access only to those persons who require it to fulfil their job responsibilities." } ], "toKnow": [ { "key": "old", "label": "Has not been updated for three years or more", "found": true, "quote": "Revised on December 14, 2016" } ], "notes": [ { "date": "2026-10-14", "text": "TableCheck may calculate Customer Scores reflecting a diner's reliability from reservation, cancellation, visit and payment history.", "quote": "We may also analyze reservation history, cancellation history, visit history, payment information, survey responses, account usage status, and other information held by us to calculate indicators, scores, or ranks that reflect a user’s reliability" } ] } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tablecheck.json", "live": { "slug": "tablecheck", "probe": { "target": "https://api.tablecheck.com/api/", "method": "get", "lastAt": "2026-10-14T09:42:09.492395571Z", "lastOk": true, "lastStatus": 200, "lastMs": 717, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 711, "p95ms24h": 871, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://tablecheck.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:43.550229393Z" }, "updatedAt": "2026-10-14T09:42:09.492395571Z" } } }