Look before you send us anything.

Clean an export of your support conversations on your own computer. Nothing on this page is uploaded: names, addresses and numbers are removed in this browser tab, and you read what is left before deciding whether FunctioningHQ sees it.

1

Export from your helpdesk

A CSV of conversations: one row each, with the messages, a date and, if you have them, the customer’s name and email. Fifty you would be comfortable showing a contractor is enough to start.

2

Clean it here

Names, email addresses, phone numbers, card and account numbers, keys and street addresses come out in this tab. Each customer becomes a stand-in. Columns we do not read are dropped.

3

Read it, then decide

You see what was removed, column by column, and rows before and after. Download the cleaned file and look through it. Send it to us only if you are happy with what is in it.

Everything below happens in this tab. To check, load this page, go offline, and clean a file: it still works, because nothing is sent.

What comes out

The same rules our servers run on everything that arrives, plus two only a file on your side can have: each customer’s own name, matched in their own messages, and any words you list.

  • Names and addresses we were told. The contact’s own name, email and phone as your helpdesk holds them, removed by exact match wherever they appear in the text. This is the strongest thing here: it is your record, not a guess at what looks like a name.
  • Email addresses. Anything shaped like an address, in any alphabet, wherever it appears in a message — including one split by an invisible character or written in full-width letters.
  • Phone numbers. Seven to fifteen digits in any grouping, international prefixes included. A date and an IP address are left alone.
  • Card numbers. Thirteen to nineteen digits, grouped or not, full-width digits included; grouped by dots only when the number passes the card checksum.
  • Bank account numbers. An IBAN in any country’s length, printed in groups of four or not at all, in capitals or not; one in lower case or grouped by dashes must pass the IBAN checksum.
  • Social security numbers. The US three-two-four shape.
  • National Insurance numbers. The UK shape: two letters, six digits and a letter A to D, spaced or not.
  • API keys. The prefixes GitHub, GitLab, Slack, Stripe, npm, Google and AWS give their tokens, the common sk_ and api_ shapes, and an AWS secret key where the text says it is one.
  • Bearer tokens. An Authorization header pasted into a message.
  • Passwords in headers and links. A Basic authorization header, a header named for a key, token or secret, and a username and password written into a link.
  • Signed tokens. A JSON Web Token: the three dotted parts a sign-in session is carried in.
  • Private keys. A private key pasted whole, from its BEGIN line to its END line.
  • Sign-in codes. Four to eight digits where the sentence says they are a code: “your verification code is”, OTP, PIN. A number on its own is left alone.
  • Links carrying a token. A link whose query or fragment holds a token, key, secret, password, session, signature or sign-in code, or whose path is a magic link, a reset or an invitation. Only the token is removed and the rest of the link is kept, because which page somebody was on is what the conversation is about.
  • Street addresses. A number and a street name with a street word after it, in capitals or not, with the flat or suite number in front of it.
  • Postcodes and ZIP codes. Only where the text says it is one — after “postcode” or “zip”, or beside a street address. A five-digit number on its own is left alone.

What stays, and why

What your customers asked, what they were told and how it ended. That is what we check an answer against your help center with, so it has to stay. Product names, error messages and prices stay for the same reason.

A name the file does not give, such as a teammate’s signing off a reply, stays unless you list it. Read the rows before and after, and list anything you would rather keep to yourself.

If you do send it, it is redacted again on arrival, kept in a database of its own, and deleted when you ask. How your data is handled.