Your lead sees that the team takes part, not who answered what.
No screen in the app shows what one person answered or pressed, and that is held in the database, not only on the screens: nobody at your employer can reach those records any other way. They are stored encrypted, in London.
The short version
- What your employer sees of what you do is a figure for a team, not a list of who did what.
- How your team split across the four names waits until 5 people have answered, and is only ever the team’s.
- Nothing you tap becomes a score with your name on it, and skipping a day is reported against nobody.
- Unsubscribe, at the foot of any email to your own address, opens a page where you vote to stop it: no account needed, and a reason only if you want to give one. That topic stops for you. Stopping everything is for your employer.
What we record
When the insight comes to your own address, we keep a record of that one email:
- Delivery. When it reached you, or that it bounced. If our email provider reports that it was opened or that a link in it was clicked, we keep that too.
- Your answer. Which name you picked, and whether it was right.
- Your feedback, if you give it: Useful or Not for me, and More on this theme or Less on this theme, one of each. The first tells your lead, pooled and once your team has given 4, how well the insights are landing; the second steers what is sent next.
- Whether you read to the end. Once the end of the explanation has been on your screen for three seconds, the page says so, once. Never how long.
- The occasional question, unless your employer has turned it off: one short question about your own experience of work, no more often than every 14 days. You can skip it, and skipping buys the same quiet as answering. We keep your answer as its place on the scale.
- A module’s closing question, if your team has one booked: did it change anything? We keep a count of each answer, and note that you answered so you are not counted twice. Not which answer you gave.
- A module delivered as a short course of daily lessons, if you say you are in: each lesson sent and opened, your answer to its check and whether you found it useful, and any note you write at a check-in. Your lead reads the notes with no name on them.
- A vote to stop, if you press Unsubscribe: which insight and topic it was on, the reason you chose and any note. The topic stops for you, and your employer sees only how many.
On a shared address or a team channel, it is different. If the email comes to a list your employer runs, or is posted in Slack or Microsoft Teams, what you tap is counted and nothing is recorded against you - unless you have claimed an account of your own and are signed in, when your answer is yours, as it would be from your own email.
What we do not record. The page you tap through to sets no cookie and runs no tracking script, and nothing you do there follows you anywhere else. Like any website, our host keeps a request log for a few days.
Who sees what
- You
Whether you were right, on the page you tap through to. If your email offers you an account of your own, claiming it shows you Your record: how often you answered and how many you got right. Nobody else in your organisation sees that page.
- Your colleagues
On the same page: how many of your team have answered today, and once 5 have, how the team split across the four names. Where the company has several teams, where yours stands this week, with the others unnamed. The next morning’s email can carry the same split.
- Your team lead
The team’s figures: how many took part and how often, how well the insights landed, and which themes the team asked for more of. Each is a number for the team. If they ask the whole team the occasional question at once, as a team check, they see its answers pooled once 5 have answered. They also see who is on the team’s list, because they look after it.
- Whoever runs the account
The account owner and anyone they share it with see the same for every team, plus the occasional question, pooled, once 5 people have answered it. They manage the list of who receives the email, so they see who is on it. If you vote to stop an email, they see how many people voted, on which topics and insights and why, for the whole company and not who. A team lead sees none of it.
- MeaningFuel
Our staff can open the records themselves, to run and repair the service, and owe your employer a duty of confidence (our data processing addendum, section 4). We do not sell them or use them for advertising.
Where the line gets thin
A minimum of 5 answers keeps a split from describing one person, and how well the insights landed waits for 4 Useful or Not for me presses on a team for the same reason. Neither can do the same for a very small team. How many took part and how often have no minimum, because a count names nobody - but on a team of two, “one of two answered” tells a lead a good deal. And a split is still a split: if everyone who answered picked the same name, it says so. Votes to stop have no minimum either, because a count of votes names nobody - but in a very small company, one vote may tell somebody a good deal.
The links in your email are yours. Forward it, and whoever taps answers as you.
Vote to stop it
These emails are a service your employer provides for its people, so you can vote to stop one and you cannot stop them all by yourself. Every email to your own address ends with Unsubscribe, and your mail app’s own unsubscribe button opens the same page. It asks why, in a few choices and a note, and neither is required.
Your vote is counted against the insight and the topic you were sent, and that topic stops being sent to you. The rest carry on. Your employer sees how many people voted, not who. Your note is read only by MeaningFuel staff, and no model ever reads it.
To stop everything, ask whoever runs MeaningFuel at your company. That is their decision, as the organisation responsible for your data, and they answer you.
If the email comes to a shared list, its foot says Vote to stop this list. That adds to the count and the list keeps coming. To leave on your own, ask whoever manages the list to take your address off it.
Two things still stop at once, with nobody deciding: marking an email as spam, and an address that bounces. They protect the address we send from. Your employer is not told who marked anything as spam.
Stopping deletes nothing: what you answered before stays in your team’s figures, and your vote stays on the record, because it is what keeps that topic stopped. Whoever manages the people on your account can see that your address stopped, if it does.
See it, correct it, or have it deleted
Write to privacy@meaningfuel.io. You can ask what is held about you, have it corrected, or have it deleted, and it costs nothing. Your employer decides what is held - we process it on their behalf - so we may need to route your request through them, and we will tell you if we do. We answer within a month.
Without a request, your records are kept while your employer’s account runs and deleted within 30 days of that account being deleted.
The privacy notice says all of this in full, with the legal basis for each part.