Jelly · Vulnerability Disclosure

Jelly Vulnerability Disclosure

Vulnerability disclosure

Jelly publishes a security policy page describing its security program and a security contact. No formal bug-bounty (HackerOne/Bugcrowd/Intigriti) or dedicated responsible-disclosure page was found; /.well-known/security.txt returns 404.

Jelly runs a coordinated vulnerability disclosure program on Hackerone. A dedicated security contact is published.

CompanyHospitalityRestaurantsKitchen ManagementFood CostingRecipe CostingInvoice ProcessingGraphQLSaaS
Program: Hackerone

Disclosure Policy

Policy
https://www.getjelly.co.uk/security

Security Contact

Contact
letscook@getjelly.co.uk

Source

Vulnerability Disclosure

jelly-vulnerability-disclosure.yml Raw ↑ 
generated: '2026-07-19'
method: searched
probe: true
source: https://www.getjelly.co.uk/security
description: >-
  Jelly publishes a security policy page describing its security program and a
  security contact. No formal bug-bounty (HackerOne/Bugcrowd/Intigriti) or
  dedicated responsible-disclosure page was found; /.well-known/security.txt
  returns 404.
policy: [https://www.getjelly.co.uk/security]
contact: [letscook@getjelly.co.uk]
program:
  bug_bounty: false
  security_txt: false
  soc2: in-progress
  controls: [role-based access control, vulnerability assessments, 24/7 monitoring, incident response]
  encryption_at_rest: AES-256
  encryption_in_transit: TLS 1.2/1.3
evidence:
  - { source: https://www.getjelly.co.uk/security, kind: security-policy-page, keywords: [security policy, vulnerability assessments, incident response, AES-256, TLS] }
probed_paths:
  - { path: /.well-known/security.txt, host: www.getjelly.co.uk, status: 404 }
  - { path: /.well-known/security.txt, host: kitchen.getjelly.co.uk, status: 404 }