Cookies

1. What a cookie is

A cookie is a small file a website leaves on your device so it can recognise your browser the next time it hears from it.

Without them a website cannot tell one visitor from another, which means it cannot keep you signed in — every page would ask for your password again.

Some are ours and some belong to the companies whose tools this site uses. Both kinds are named below.

2. What this site sets

Three cookies, and every one of them is doing a job you would notice the loss of.

2.1. breadfundme-session

Keeps you signed in as you move from page to page, and remembers a half-finished form. It holds a random reference and nothing about you. It goes when you close your browser, or after two hours of doing nothing.

2.2. XSRF-TOKEN

A one-off code that proves a form was really submitted from this site, so another site cannot make your browser donate, post or change your details behind your back. It goes when you close your browser.

2.3. The sign-in cookie

Only set if you tick "Keep me signed in on this device". It is what lets you come back tomorrow without signing in again. Leave the box unticked and it is never set; sign out and it is deleted.

3. Two things that are not cookies

Your browser has other places to store things, and this site uses one of them for a single purpose worth naming.

3.1. Unfinished work

A half-written fund, or a sign-up you are partway through, is kept in your browser’s own session storage so a refresh does not lose it. It never reaches us, it is only readable by this site, and it is gone when you close the tab. Your password is deliberately never kept this way.

3.2. Nothing that follows you

There is no pixel, tag or beacon on this site reporting your visit to anybody else. If that changes, this page changes with it, before it does.

4. Cookies from our payment provider

When you donate, the card form is Flutterwave’s, not ours — that is what keeps your card number away from our servers entirely.

Their script sets its own cookies to run that form, keep the payment secure and spot fraud. They are Flutterwave’s, governed by Flutterwave’s privacy policy, and they are only loaded on the donate page.

5. What we may add

We may start measuring how the site is used — which pages people reach, where they give up — so we can fix what is not working. That needs a cookie.

Where your consent is needed for that, we will ask before setting anything, and saying no will not stop you using the site. When it happens, this page will name each one as it names the three above.

We do not use your information to advertise to you on other sites.

6. What you can do

Every browser lets you see the cookies a site has set, delete them, or block them — usually under Settings, then Privacy.

Be warned about the three above: block them and this site stops working in ways that look like faults rather than choices. You will not be able to sign in, and donating will fail.

Blocking cookies on one browser does nothing on another, or on your phone. Each one is separate.

7. Changes, and how to reach us

If we add a cookie, this page gets it before the cookie gets you.

Questions? Write to hello@breadfund.me and a person will answer.