How IF uses data

Projects by IF is a limited company based in London, England. We run this website ( and its subdomains. We also use third party services to publish work, keep in touch with people and understand how we can do those things better. Many of those services collect some data about people who are interested in IF, come to our events or work with us.

Here you can find out what those services are, how we use them and how we store the information they collect. If you’ve got any questions, or want to know more about data we might have collected about you, email

This page was updated on 1 March 2018. You can see any revisions by visiting the repository on Github.


At IF, we take our approach to data very seriously, so we’ve set some guiding principles that all of our work follows:

Minimising the data we collect and record - We ask for as little information as possible. It reduces the risk of exposing sensitive data, and means people have more control over what they share with us.

Being clear about data use - We’re up front about what we’ll do with information: how we store it, who’ll have access to it and when we’ll delete it. If we won’t use it, we don’t keep it.

Making decisions as a team - No single person has all the answers. We talk about decisions we’re making about using data. Ideally, we write a blog post about it: public discussion is essential.

Storing data securely - No one should be able to access our data without permission, either by accident or design.

Keeping personally identifiable information confidential - Outside of the team working on a project, the information we share about people is a high-level synthesis.

Holding people to account - Someone should always be responsible for decisions made about our use of data. This person must be able to explain every decision made about the way a project’s data has been gathered, used and managed.

Services powering IF websites

We track visitors to IF’s website using analytics platform , which logs a visitor’s activity on our website: we then use this to work out how we can improve the site. We store the data collected indefinitely, so we can see how use of our website changes over time. We chose Matomo because we are able to run it on equipment we control, so no third parties have access to this data. You can read more about the information Matomo collects on their website here. You can also read about Matomo's approach to privacy, and which tools they recommend to anonymise your browsing, at, where you can also opt out of being tracked by Matomo.

We run our website on servers owned by We chose them because we control the server, and because that server is based in the UK. You can read about Digital Ocean’s approach to customer data, including their privacy policy and transparency report, here.

We use to release code related to our projects. Using Github allows people to scrutinise code changes, and we can easily open up our code to contributors from outside of the IF team. Read Github’s privacy policy here.

We host videos using , because its infrastructure is better suited to delivering video content than our own. Using Vimeo also allows us to edit to content of a video without breaking copies embedded on other websites. You can read Vimeo’s privacy policy here.

We host images using . We use AWS S3 because it’s reliable and integrates easily with our CMS, . It's not currently clear whether Amazon collects information about the use of content hosted on its platform. You can read more here.


We maintain our ‘Notes from IF’ and 'Trust & Design' mailing lists using a service called , which we run on IF’s servers. We use Sendy because it allows us to switch off the tracking features that are bundled into many email services. Besides storing subscribers' email addresses, Sendy tracks whether an email has bounced from a recipient or been marked as spam. We’ll keep this information indefinitely, unless a recipient unsubscribes from a mailing list. We do monthly audits to make sure information about unsubscribed email addresses is deleted, however some of this data may be stored in backups. We’re currently changing how we store this information so that it is processed during our monthly audits.

The newsletter is sent via , which we use because it improves the reliability of newsletter distribution. It’s not currently clear how Amazon SES handles personally identifiable information it processes. You can read more here.

Trust & Design meetup

We use to handle event signups and ticketing. We do this because it’s a ticketing service members of the team have experience of using, and because it allows us to promote each event to other people interested in similar events. When someone signs up to an event through Eventbrite, we’ll only use that information to get in touch about that specific event. We don’t keep copies of their information afterwards, and after an event has taken place we delete it from Eventbrite as part of our monthly audit. You can read Eventbrite’s privacy policy here.

We’ll check before each event whether attendees consent to being filmed or photographed by members of the IF team. If you’ve attended one of our events and have since changed your mind about whether you consent to being filmed or photographed, or if you find you’ve been filmed or photographed against your consent, email and we’ll take steps to meet your needs.

If a speaker consents, we film their talk so we can publish it after the event. This film is also transcribed to ensure that what the speaker says is accessible. This transcript will be published verbatim, unless a speaker wants to review and edit it. We won’t publish footage of Q&As if we haven’t asked for consent from all participants.

Our social media accounts

We use several social media accounts to share our work and the things we publish. At the moment, this includes;

We occasionally use the analytics tools provided by these platforms to understand how we can use them better. We may also feature public messages, comments or replies on If you’d like content removed from this site, please contact

Research participants

This content is currently being drafted. Please read Georgina’s blog post for our latest thinking on this.

People who work with IF

This content is currently being drafted.

Job Applicants

This content is currently being drafted.

Staff at IF

This content is currently being drafted.