FridgedoorSecurity
The questions your IT person asks before your operations lead signs.
Fridgedoor holds your customers' names, phone numbers and email addresses, and the history of what you have said to them. This page is what we can tell you about how that is handled, written plainly and limited to what is true today.
Your records reach only your organisation
Locations, users, permissions, customer records and message history are each scoped to the organisation that owns them, on every route that reaches them. A caller with no organisation is refused rather than shown a partial view.
This was reviewed route by route rather than fixed where it was noticed, and the work is recorded in the changelog. We describe the outcome rather than the shape of what was corrected, deliberately.
Roles, and a trail of who did what
Admin, owner, manager, office and view roles. Each person's permissions are visible on their own page and editable from the same screen, so the answer to "why can this person see that" is one screen rather than a support request.
An activity log records sign-ins and changes to your email and SMS templates. It never records a password — it records that an authentication happened, not what was typed. Retention is measured per organisation from your own last activity.
Your own sending domains
Outbound and inbound mail run through domains you verify and control, and suppression lists are kept per domain. Replies come back to an address you own rather than to a shared one.
When verification fails, the screen names the record that is wrong rather than showing a generic error. Deliverability is your reputation, not ours, which is the reason it works this way.
Mail from outside is treated as untrusted
Anyone can email you, and an email is a document written by someone neither of us controls. Inbound content is cleaned before it is displayed, so a message from outside cannot carry anything active into your queue.
Scoped tokens, and support access you can see
API tokens carry scopes you can read at a glance, so a token that can do more than it needs to is visible rather than assumed. When someone from Fridgedoor signs in as you to look at a problem, a banner says so for as long as it lasts.
Accounts are configured before anyone logs in
There is no self-serve signup. Branches, sending domains and templates are set up with you, and an approved owner sets their own password through a link — we do not generate one and email it to you.
Reporting a problem
If you believe you have found a security problem in Fridgedoor, tell us before you tell anyone else and we will work it through with you. We publish a security.txt at the address below, which is the machine-readable version of this paragraph.
- [email protected]
We will not pursue anyone who reports a genuine issue in good faith and gives us reasonable time to fix it.
Something not answered here?
If your procurement checklist asks something this page does not cover, send it to us and we will answer it directly rather than guess at it in public. An honest "not yet" is worth more to you than a page that implies otherwise.