Security and incident response

How Hailbell protects the data your apps and stores send us, and exactly what we do if that data is ever exposed, lost or reached by someone who shouldn't have it. Last updated 15 November 2026.

How we protect data

If something goes wrong

A security incident is anything that exposes, changes, deletes or gives someone access to data they shouldn't have. That includes a leaked key or token, someone reaching another account's data, data lost beyond what a backup restores, or a bug that shows one customer's data to another. Vidur Saini, Hailbell's founder, is responsible for handling every incident.

What we do, step by step

  1. Look into it right away. Every report and alert gets a first look within 24 hours. We decide whether it's an incident and how serious it is.
  2. Stop it. We cut off the access: rotate or revoke the leaked key, token or secret, end the affected sessions, turn off the broken feature, or pause the affected account if we have to.
  3. Work out what happened. We find out which data was involved, which accounts, apps and stores were affected, when it started, and how.
  4. Tell the people affected. See below.
  5. Fix the cause. We fix the bug or gap that allowed it, check the fix, and restore any lost data from backup where we can.
  6. Learn from it. Within 14 days we write down what happened, what we changed and what we'll do differently, and we share that with the affected account owners.

Who we tell, and when

If we learn more after the first email, we send an update.

Report a security problem

If you think you've found a security problem in Hailbell, email hello@hailbell.com with what you found and how to reproduce it. A person reads every message, and we reply within 2 business days. Please don't access or change other people's data while testing, and give us a reasonable time to fix the problem before you share it publicly.

We review this policy at least once a year and whenever Hailbell changes in a way that affects it.