What we hold, and why

The short version

We hold what is needed to carry a message and bill for it, and nothing we were not given. We do not sell anything about you or your recipients, and we do not use the content of your messages for any purpose other than delivering them and showing them back to you.

Two kinds of people are involved, and only one of them is our customer

You hold an account. You gave us an email address and chose a password, and we know what you have bought and sent.

Your recipients did not. They are the people whose phone numbers you send us, and they have never heard of us. We process their numbers only to deliver what you asked us to deliver, on your instruction, and we do not contact them for our own purposes, ever.

That division decides who is answerable for what. You are responsible for having a lawful reason to message them — consent, an existing relationship, or whatever your own obligations require — and for honouring their requests to stop. We are responsible for keeping what you send us safe, for using it only as described here, and for deleting it when we say we will.

What we hold

About your account

• Your email address, and a one-way hash of your password. We cannot read your password.
• Your organisation's name, and the names and roles of colleagues you invite.
• A one-way hash of each API key, plus its first characters so you can recognise it in a list. We cannot show you a key again after it is issued.
• Which sender IDs you have asked for, and any business licence you uploaded to support the request.

About the messages you send

• The recipient's number, the sender name that was used, and the network it was routed to.
• The text of the message. It is stored, and it is visible to anyone who can sign in to your account and to our staff when investigating a fault you have reported. Do not put anything in an SMS that you would not put in an email.
• Its size in segments, what it cost, and its delivery status including any receipt the carrier returned.

About money

• Every top-up, refund and invoice, and the reference the payment gateway gave us.
• We never see your card. Card details are entered on the payment provider's own page and are never sent to us or stored here.

Automatically

• A session cookie so you stay signed in. There is no advertising or analytics tracking on this site, and no third-party script of any kind — the content security policy forbids it.
• Server logs, including IP addresses, kept for security and fault-finding.

How long we keep it

Message records — including the text and the recipient's number — are kept for the retention period of your plan and then removed. Daily totals used for your usage charts and invoices are kept longer, because they are what your billing history is made of, and they do not contain message text or recipient numbers.

Invoices and ledger entries are kept for as long as we are required to keep accounting records. Closing your account does not delete them, and we would be breaking the law if it did.

Who else sees it

We pass on the minimum each of these needs to do its job, and nothing more.

• The mobile networks. To deliver a message we must give the carrier the recipient's number, the sender name and the message text. There is no way to send an SMS without this.
• The payment provider. Handles your card or bank transaction and tells us whether it succeeded.
• Our email provider. Carries account emails such as verification and password resets.

We do not sell, rent or share your data or your recipients' numbers with anybody else. We will hand over records if we are legally compelled to, and we will tell you when we are allowed to tell you.

What you can ask for

• A copy of what we hold about you. Most of it you can already export yourself from the message log and the billing page.
• Correction of anything wrong.
• Deletion of your account and its message records, subject to the accounting records we must keep.

Requests from your recipients should go to you, not to us — they are your contacts, we hold them on your instruction, and we have no way to know who they are or whether a request is genuine. Ask us and we will help you action it.

Security

Traffic is encrypted in transit. Passwords are hashed and checked against known-breached password lists when you set them. API keys are stored hashed and shown once. Repeated failed sign-ins lock an account temporarily. Access to your data inside the product is decided by rules on the data itself rather than by which page you are on.

No system is perfect. If something happens that puts your data at risk, we will tell you what happened, what it affected, and what we did about it.

Talk to us

Email hello@wons.bt with anything on this page.