Privacy policy and cookie notice · Global Girls Foundation

Last updated: 11 October 2026

We want you to feel confident about how Global Girls Foundation uses your personal information.

Global Girls Foundation is a Swiss foundation, and our use of personal data is governed first of all by Swiss data protection law, the Federal Act on Data Protection (FADP). This notice says, in plain words, what we collect on this site, why we use it, who else handles it and what choices you have. It is also written for donors in the EU and the UK: where a rule comes from EU or UK law rather than Swiss law, it says so.

In short

We do not sell your personal data.
You can read our website without creating an account or telling us who you are.
We use Google Analytics only if you switch it on in the cookie card.
Gifts by card or wallet are processed by Stripe. Your card details go to Stripe and never reach us.
If you write to us through the contact form, the website keeps your message for our team to answer, and deletes it within twelve months.
Our newsletter is sent through Mailchimp, and only to people who sign up and confirm.
We use service providers to host, secure and operate our website and communications. Each is listed below.
You can contact us at any time about how we use your personal data.
If you are in the EU or the UK, EU or UK law may give you further rights. This notice says where.

Questions about your privacy? Write to info@globalgirlsfoundation.org.

Who is responsible

Global Girls Foundation is a Swiss foundation (Stiftung) supporting girls' rights and gender equality worldwide. Its seat is in Zurich, and it is entered in the Commercial Register of the Canton of Zurich under UID CHE-347.920.926. Registered office: Badenerstrasse 580, 8048 Zurich, Switzerland. We are the controller for the data described here, which means we decide why and how it is used.

For anything about your data, write to info@globalgirlsfoundation.org, or by post to the address above, marked “Data protection”. We have not appointed a separate data protection adviser (Art. 10 FADP) or data protection officer (Art. 37 GDPR). Swiss law leaves that choice to us, and EU and UK law do not require one for what we do.

What this notice covers

This site, globalgirlsfoundation.org, and what it does with your data when you read it, give through it, write to us through it or sign up to our newsletter. It does not cover the pages that Stripe and Mailchimp run themselves, such as Stripe's payment page and Mailchimp's confirmation and unsubscribe pages, or Plan International's websites, or any other site we link to. Each of those has its own notice. We use your data only for the purposes this notice describes, or for purposes compatible with the reason we collected it.

If you only read the site

You can read every page without telling us who you are. While you read, our host's network sets two security cookies and the site keeps one small flag in your browser; all three are described under Cookies below. No analytics tool counts your visit unless you switch on Analytics in the cookie card, which is described below. No advertising or social-media tool runs on this site. Its fonts are served from the site itself, not from Google.

The site is hosted by WP Engine (WPEngine, Inc., Austin, Texas, USA) in a Google Cloud data centre in St. Ghislain, Belgium, where the site's files and its database are kept; WP Engine's daily backups are stored in the European Union. Like every web host, WP Engine receives your IP address, the page or file you asked for, the date and time, what your browser tells it about itself and your device, and technical details of the connection, and keeps this in its server logs to run and protect the service. Every request reaches WP Engine through the network of Cloudflare (Cloudflare, Inc., San Francisco, USA), which WP Engine uses to deliver the site quickly and to screen out attacks and automated abuse; Cloudflare sees the same connection details on the way through. We use those logs only to keep the site working, to find faults and to stop misuse. WP Engine's support and technical staff, who are in the United States, can reach the site's data when we ask them to; see Where your data goes below.

For readers in the EU and the UK: the legal basis for the server logs, and for our host's security cookies and the browser check described under Cookies, is our legitimate interest in running and protecting the site (Art. 6(1)(f) GDPR). The cookies and the check need no consent because they are strictly necessary to protect the site you asked to read (Art. 5(3) of the EU ePrivacy Directive, 2002/58/EC; in the UK, Schedule A1, paragraph 4, of the Privacy and Electronic Communications Regulations).

If you switch on Analytics

The cookie card has an “Analytics” switch. It is off until you turn it on. If you do, and only then, the site loads Google Analytics from googletagmanager.com. Google Analytics sets two cookies, _ga and _ga_ followed by our Analytics ID, which last up to two years; they hold a random number so that Google can tell one visit from another. It then receives which pages you read, with each page's address, and, as we have set it up, what you do on them: how far you scroll, links to other sites you follow, files you download, embedded videos you play, and forms you start or send (never what you type in them). If you take one of these steps, it also receives that you did: that a gift was completed, on this page or on Stripe's (and, for a gift completed on this page, its amount, currency, designation and whether it was one-time or monthly); that you sent a message (the topic only); and that you signed up to the newsletter. If you reach the contact page from the giving panel or from a link on another of our pages, the address of the contact page shows what you chose: the topic (for example, a gift in your will, or a gift from a foundation or trust) and, where you chose them, the designation, amount, currency and how often. Google receives that address too. It never receives your name, your email address or anything else that tells it who you are; it knows your browser only by the random number in its cookie. Google does not store your IP address: for visitors in Switzerland, the EU and the UK it uses the address only to work out roughly where you are, then discards it.

We tell Google, with every visit, that this data may be used for our visitor statistics and not for advertising, and no advertising runs on this site. Google keeps the individual records for no more than fourteen months; the totals in our reports are not tied to you. You can change your choice at any time: “Cookie settings”, at the foot of every page, opens the cookie card again. If you turn the switch off, the site tells Google at once, and from the next page you open Google Analytics does not load at all; delete the two cookies in your browser's settings to remove them. Our contract is with Google Ireland Limited, Dublin; Google processes analytics data on its servers, including in the United States (Google LLC). Google's privacy policy is at policies.google.com/privacy.

For readers in the EU and the UK: the legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time in the cookie card.

When you give

The giving panel asks for a currency, how often, a designation and an amount, and whether you are giving as an individual or as a foundation or corporate foundation. For a card gift it also asks for your email address, for your receipt.

For a one-time gift, nothing from Stripe loads until you press Give. When you press it, Stripe's payment script loads on this page from js.stripe.com and may set Stripe's fraud-prevention cookies (see Cookies below), and the card and wallet fields appear on our page. Those fields are Stripe's own, embedded in our page: what you type in them goes straight to Stripe and never reaches this site or our systems. For a monthly gift, pressing Give takes you to a payment page run by Stripe, at checkout.stripe.com, where you enter your card or wallet details.

Behind the scenes, our server passes Stripe the currency, how often, the designation, the amount and your email address, and asks Stripe to set up the payment: a single payment for a one-time gift or, for a monthly gift, Stripe's payment page, where Stripe sets up a customer record and a monthly plan when you confirm. Our server keeps none of it: this site's database holds no record of your card gift, your name or your email address. If you also write to us through the contact form, the website keeps that message (see When you write to us). Stripe confirms the payment and emails you a receipt in the Foundation's name, and you see our thank-you message.

For a monthly gift, Stripe keeps your payment method on file to take each month's gift until you stop it. You can change or stop it at any time by writing to us.

If the embedded fields cannot load, your browser goes instead to a payment page run by Stripe, at checkout.stripe.com, with the gift you chose. If JavaScript is off in your browser, the panel still takes your choices. When you press Give now, your browser sends the designation, how often, the currency, the amount and whether you are giving as an individual or as a foundation or corporate foundation to our server, in the web address it opens (not your email address). Our server then sends your browser on to Stripe's payment page for that gift or, for a gift that begins with a conversation (such as the Annual Giving Fund, the endowment or a gift larger than we take by card or wallet), to our contact page. Like the address of any page you open, that address can appear in the server logs our host keeps (see If you only read the site). Stripe shows the amount before you pay. Either way, Stripe's page asks for your email address itself. When you have paid, Stripe returns you to our thank-you page; if you stop, to a page that says the gift was not completed.

What we then hold, in our Stripe account: your name as entered, your email, the amount, currency, designation and date, whether the payment went through, the type of payment method, the last four digits of a card, and any billing detail Stripe asked you for, together with three labels we attach to every payment: the designation, whether the gift is one-time or monthly, and that it came from this website. For a monthly gift, we also hold the monthly plan. Never the full card number. We use this to receipt and account for your gift, to honour your designation, to thank you, to answer your questions, and to keep the records Swiss accounting law requires.

For readers in the EU and the UK: the legal bases are the gift itself, which is a contract under Swiss law (Art. 6(1)(b) GDPR), and our legitimate interests in keeping the accounting records Swiss law requires of us and in thanking you (Art. 6(1)(f)). You can tell us at any time not to write to you, and we will stop.

Stripe processes your payment as our payment processor. Stripe also uses payment data on its own account, for fraud prevention, for its own legal duties and, if you choose to use it, for its Link service. Stripe explains this in its privacy policy at stripe.com/privacy. For an account in Switzerland, Stripe's contracting company is Stripe Payments Europe, Limited, Dublin, Ireland; the regulated payment service itself is provided by Stripe Payments UK, Ltd. in the United Kingdom; and Stripe's US company, Stripe, LLC, is part of the group that handles the data.

If you ask the giving panel for our bank details, or your gift is larger than we take by card or wallet, the panel shows our bank details instead of card fields, and you make the gift from your own bank. The panel sends us nothing: the copy buttons use your own device, and the email link opens your own mail program. From our bank we receive the name, address and account number of whoever sends the transfer (usually you), the amount, the date and the reference you entered. If you email us about your transfer, we also have your email address and what you wrote (see When you write to us). We use this to receipt and account for your gift, to honour your designation, to thank you, to answer your questions, and to keep the records Swiss accounting law requires. We keep it for ten years (Art. 958f of the Code of Obligations).

For readers in the EU and the UK: the legal bases are the gift itself, which is a contract under Swiss law (Art. 6(1)(b) GDPR), and our legitimate interests in keeping the accounting records Swiss law requires of us, in honouring your designation and in thanking you (Art. 6(1)(f)). You can tell us at any time not to write to you, and we will stop.

When you write to us

When you send the contact form, the website keeps what you typed: your name, your email address, the topic you chose and your message, if you wrote one. If the giving panel sent you to the form, it also keeps what you chose there: the designation and, where you chose them, the amount and currency, whether the gift is one-time or monthly, and that you are giving as a foundation or corporate foundation. With your message it keeps the date it arrived, our own record of who on our team opened and answered it and when, and, if our checks put it aside as possible junk, the reasons (see Stopping abuse of the forms). It keeps nothing else with your message: not your IP address, and nothing about your browser or device.

Your message is stored in the website's own database, at our host, WP Engine, in Belgium (see If you only read the site); on its way there it passes through Cloudflare's network, like every visit to this site. Sending the form sends no email, to us or to you, and you receive no automatic reply: the first email you get from us is from a person. Your message waits on the website until a member of our team signs in to read it (see Security for who can open it). We answer you by email, from a globalgirlsfoundation.org address, and the conversation then carries on in our mailbox.

If JavaScript is off in your browser, the form's button opens your own email program instead, with a message addressed to info@globalgirlsfoundation.org. What you send that way reaches our mailbox as an ordinary email; the website keeps nothing.

We delete your message from the website twelve months after it arrives at the latest, or sooner if you ask us to. A message put aside as possible junk is deleted 30 days after it was put aside, unless we move it back to our inbox. A copy stays in our host's backups until they are replaced, at most 60 days later (see How long we keep it).

When your message arrives, our server checks it for signs that a program sent it, as described under Stopping abuse of the forms. Our forms never ask you to solve a puzzle, and no spam-checking service sees what you typed. The only other bot check on this page is the one our host's network runs on every page, described under Cookies.

We use your message to answer you and to carry on the conversation you started. We do not use what you send through the contact form to send you marketing, unless you have separately agreed to receive it.

Emails sent straight to the addresses on this site go to our mailbox only. Our mailbox runs on Microsoft 365, and incoming mail passes through Mimecast's filtering service in the European Union.

For readers in the EU and the UK: the legal basis is the steps you asked us to take before a possible gift (Art. 6(1)(b) GDPR) and our legitimate interest in answering you and in keeping a record of what you asked for twelve months (Art. 6(1)(f)).

The form in the footer asks only for your email address. When you send it, our server passes the address to Mailchimp, the service that sends our newsletter, with a label saying that it came from this website, and nothing else: not your name, and not your IP address. Mailchimp then emails you, in our name, a link to confirm. Nothing is added to our list until you press that link; if you do not, you will hear nothing more from us. When you press it, Mailchimp records when you confirmed and the internet (IP) address you confirmed from. That is our record that you agreed.

This site does not keep your address. So that no address receives more than one confirmation email a week, it keeps a scrambled form of the address for seven days (see Stopping abuse of the forms).

Mailchimp can report to us whether you open an issue and which of its links you click, using a tiny image in the email and links that pass through its own servers. Even with those reports switched off, Mailchimp may pass the links through its servers, to protect readers from harmful links and its service from abuse, and uses that for its own checks.

Every issue has a link to leave, and you can also write to us. When you leave, Mailchimp marks your address as unsubscribed and sends nothing more to it. We keep that mark so that you are not added again by mistake; if you would rather we deleted your address altogether, tell us and we will.

Mailchimp is run by The Rocket Science Group LLC, an Intuit company, in Atlanta, USA, and keeps its data on servers in the United States (see Where your data goes). It handles your address for us, as our service provider, and also uses some of it on its own account, for example to prevent abuse of its service. Intuit, which owns Mailchimp, explains this in its privacy statement at intuit.com/privacy/statement.

Swiss law (Art. 3(1)(o) of the Unfair Competition Act) requires your consent before we send you a newsletter, our name as the sender, and an easy way to say no in every issue. The confirmation link, the sender line and the link to leave are how we meet it. For readers in the EU and the UK: the legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time by leaving. Keeping the record that you agreed, and the mark that you left, rests on our legitimate interest in being able to show that we respect your choice (Art. 6(1)(f)).

Stopping abuse of the forms

Programs send junk through forms all over the internet. We stop them on our own server. Our forms never ask you to solve a puzzle, nothing you type is sent to a spam-checking service, and none of these checks uses a cookie or stores anything on your device.

Limits. On the contact form, once five messages have come from one connection in ten minutes, or three from one email address in an hour, further messages are put aside for a person on our team to look at (see Checks on a message); after twenty from one connection in ten minutes, the form pauses for up to ten minutes. On the newsletter form, sign-ups are limited to five from one connection in ten minutes, and each email address gets at most one confirmation email in seven days: a second sign-up for the same address within that week sends nothing. Starting a gift, on this page or on Stripe's, is limited to twenty attempts from one connection in ten minutes.

What we keep to count. Our server keeps a scrambled form of your IP address and, on the contact and newsletter forms, of your email address, made with a secret key kept on our server. For the newer kind of IP address (IPv6) it uses only the first half, which identifies your network rather than your device. Each is kept in a temporary record: ten minutes for an IP address, one hour for an email address on the contact form, seven days for a newsletter sign-up. To notice the same text sent by several people, it also keeps, for 24 hours, a scrambled form of the words of a message, with a scrambled form of the email address that first sent them. Each record stops counting when its time is up and is deleted soon after. These records are kept apart from your message, and used for nothing else.

Checks on a message. When you send the contact form, our server looks for signs that a program sent it: a hidden field that people never see but programs fill in; a message sent from another website, or one that does not say which website it came from; more messages than a person usually writes; and the same words from several people. If a message looks automated, we do not throw it away: we put it aside, with the reasons, for a person on our team to look at. If it is real, we move it back to our inbox, delete the reasons and answer it like any other. Anything put aside is deleted 30 days after it was put aside, unless we move it back; if more than 5,000 are ever waiting, the oldest are deleted first. A member of our team can also put a message aside as junk, and it is then deleted 30 days later too. The newsletter form has the same hidden field; a sign-up that fills it is ignored.

If a member of our team asks the website to always, or never, put aside messages from one email address, the website keeps a scrambled form of that address for that purpose, for twelve months at most.

These checks apply only to the forms on this site. You can always write to us at info@globalgirlsfoundation.org instead.

For readers in the EU and the UK: the legal basis is our legitimate interest in keeping the site, our inbox and our donors' payments secure (Art. 6(1)(f) GDPR).

Cookies and your browser's storage

Cookies and similar technologies help us run this site and, if you allow it, understand how people use it. Our host's network sets two cookies, for security; they are described below. The site also keeps up to three small things in your browser's storage, a store on your device that is not sent to a server:

Your choice in the cookie card, in local storage under the name ggf_cookie_consent. It does not identify you, and it stays until you delete it.
A page-transition flag, set on every page, in session storage under the name ggfH. Its value is 1, and it makes the header's opening animation play on the first page you open and not again on every page after it. It says nothing about you, the switches in the cookie card do not change it, and closing the tab deletes it.
Only if the giving panel sends you on to the contact page: the email address you typed, in session storage under the name ggf_gift_email, so that you do not have to type it again. The contact page reads it once and deletes it, and closing the tab deletes it too. It reaches us only if you send the form.

You can delete or block all three in your browser's settings; the cookie card will then simply ask you again.

The cookie card has three switches:

“Essentials”, always on: your saved choice, our host's two security cookies and, when you give, Stripe's fraud-prevention cookies, all described in this section. The site and the payment you ask for need them.
“Analytics”, off until you switch it on: Google Analytics and its two cookies, as described under If you switch on Analytics. It runs only with your consent.
“Marketing”, off: it turns nothing on. There is no advertising, marketing or social-media tool on this site, and no advertising cookie. If we ever add one, we will name it here first and ask before it runs.

You can change your choice at any time with “Cookie settings” at the foot of every page.

Our host's two security cookies come from Cloudflare, the network WP Engine uses to deliver the site and to screen out attacks and automated abuse. Both are set before you make any choice in the cookie card, and we can neither read them nor use them. As our host has them set up today:

__cf_bm is set on every visit. It holds encrypted information that Cloudflare uses to tell people from bots, and it expires 30 minutes after you last open a page. Cloudflare says it makes a separate one for each site and does not use it to follow you from site to site or from one visit to the next.
cf_clearance is set by a small Cloudflare script that runs in your browser when you open a page without this cookie. Without showing you anything, the script checks that your browser behaves like a person's and not like a bot, and the cookie keeps the result so that the check does not run on every page. Your browser keeps it for a year from when it was last set.

Our host decides which security cookies its network sets and how long they last, and can change this. We check them from time to time and will update this section when they change. You can block both cookies in your browser's settings, and turning off JavaScript stops the check; at present the pages still load without them.

When you press Give for a one-time gift, Stripe's script may set Stripe's fraud-prevention cookies on this site: __stripe_mid, which lasts one year, and __stripe_sid, which lasts 30 minutes. If you are sent to Stripe's own payment page, as you always are for a monthly gift, Stripe sets its cookies there under its cookie policy. They exist to process the payment you asked for and to stop fraud. The way to refuse them is not to give by card; bank transfer is on the Give page.

Swiss law (Art. 45c of the Telecommunications Act) asks us to tell you what is stored on or read from your device, why, and that you can refuse it. That is what this section does.

Who else sees your data

We share personal data only with the service providers and others below, and only for what this notice describes.

Stripe, for payments, as described above.
WP Engine, our host, for the site, its database (including the messages you send through the contact form and the records described under Stopping abuse of the forms), its server logs and its backups, in a Google Cloud data centre in Belgium, as described above.
Cloudflare, Inc., which runs the network WP Engine uses to deliver the site and screen out attacks, and which sets the security cookies and runs the browser check described under Cookies.
The web studio that builds and maintains this website for us, which can reach the site and its database, including messages sent through the contact form, to keep them working.
Google Ireland Limited, for analytics, only if you switch it on.
Mailchimp (The Rocket Science Group LLC, an Intuit company), which sends our newsletter, only if you sign up.
Microsoft (Microsoft 365), which hosts our mailbox and the office software we work in; Mimecast, which filters incoming mail for security; and the IT service provider that administers our mailbox for us.
Our bank, UBS Switzerland AG, for gifts by transfer, as described under When you give.
Our auditor; our lawyers and the courts, if we need to establish, exercise or defend a legal claim; and, where the law requires it, the authorities.

Nobody else. Your data is not passed to Plan International, Inc. or any Plan International office for their own use. We never sell your data and never pass it to anyone for their own marketing.

Where your data goes

Switzerland, where we are. Belgium, where the site and its database are kept, including the messages you send through the contact form, and the European Union more widely, where WP Engine keeps its backups: EU countries are recognised by the Swiss Federal Council as giving adequate protection (Art. 16(1) FADP). Ireland, home of Stripe Payments Europe, Limited and Google Ireland Limited, on the same footing. The United Kingdom, where Stripe Payments UK, Ltd. provides the regulated payment service for Swiss accounts; the UK is on the same list. The United States: Stripe, LLC; WPEngine, Inc., whose support staff can reach the site's data when we ask them to; Cloudflare, Inc., which runs WP Engine's network and handles each visit in whichever of its data centres around the world your connection reaches; Google LLC, which processes analytics data; The Rocket Science Group LLC (Mailchimp), which keeps the newsletter list there; and Microsoft, which may hold our mailbox in the European Union or the United States. Stripe, WP Engine, Cloudflare, Google and Mailchimp are certified under the Swiss-US Data Privacy Framework, which the Federal Council recognises as giving adequate protection; for Microsoft, and wherever a transfer is not covered by a certification, we rely on standard contractual clauses recognised by the Federal Data Protection and Information Commissioner (Art. 16(2) FADP).

For readers in the EU and the UK: Switzerland is recognised by the EU and the UK as providing adequate protection, so your data coming to us is covered, and data kept in Belgium and Ireland does not leave the EU; onward transfers to the United States rest on the EU-US Data Privacy Framework and its UK extension, or on standard contractual clauses (Art. 44 to 46 GDPR).

How long we keep it

We keep personal data only as long as we need it for the purposes in this notice. We keep it longer only where the law requires it, or where we need it to establish, exercise or defend a legal claim.

Records of gifts, in our Stripe account and our accounts: ten years, as Swiss accounting law requires (Art. 958f of the Code of Obligations).
A card saved for a monthly gift: while the gift runs, and after it stops until it is removed from our Stripe account; you can ask us to remove it.
Emails and conversations with you: for as long as we need them to answer you and keep our records; emails about a gift are kept with the gift records for ten years.
Messages sent through the contact form, on the website: twelve months from when they arrive at the latest, then deleted automatically; sooner if you ask.
Messages put aside as possible junk: 30 days from when they were put aside, then deleted automatically, unless we move one back to our inbox because it is real.
Newsletter: while you are subscribed. After you leave, your address stays in Mailchimp marked as unsubscribed, so that nothing is sent to it again, until you ask us to delete it. A sign-up you never confirm: Mailchimp says it deletes it after 60 days.
Analytics records at Google, if you switched Analytics on: no more than fourteen months; its two cookies, up to two years unless you delete them.
Server logs: kept by WP Engine for as long as it needs them to run and secure the service; we can see the last 72 hours of edge logs and the most recent 1,500 requests to the server.
Site backups: WP Engine keeps its daily backups for at least 30 and at most 60 days. A backup holds the site's files and database as they were that day, including the contact-form messages then on the website (those put aside as possible junk too) and the scrambled records then current; it holds no record of a card gift. A message or record we delete from the website stays in the backups until they are replaced.
The scrambled records that count form use: ten minutes for an IP address; one hour for an email address on the contact form; 24 hours for the words of a message and the address that first sent them; seven days for a newsletter sign-up. Then deleted soon after.
The scrambled record of an email address our team asked the website to always or never put aside: twelve months at most.
Our host's security cookies, in your browser, as our host has them set up today: __cf_bm, 30 minutes after you last open a page; cf_clearance, a year from when it was last set.
What the site keeps in your browser's storage: your cookie choice until you delete it; the page-transition flag and the gift email until you close the tab, or sooner.

Your rights

Under Swiss law (Art. 25, 28, 30 and 32 FADP) you can ask what data we hold about you and get a copy; have it corrected; have it deleted; object to a particular use or a particular disclosure; and, where we process it automatically on the basis of your consent or a contract, receive it in a common electronic format. You can withdraw a consent you have given at any time: in the cookie card for analytics, and with the link in any issue for the newsletter. Swiss law allows a few exceptions (Art. 26 FADP); if one applies, we will tell you which and why. Asking is free, and we answer within 30 days. Write to info@globalgirlsfoundation.org. We may ask you to confirm who you are first.

For readers in the EU and the UK, the GDPR and UK GDPR give you the same rights (Art. 15 to 21), plus the right to restrict processing, and to complain to the data protection authority where you live (Art. 77).

Security

We protect personal data with technical and organisational measures suited to the risk (Art. 8 FADP). The site is served over HTTPS. Card data never touches our systems, and the site stores no record of your card gift; of a newsletter sign-up it keeps only the scrambled seven-day record described under Stopping abuse of the forms. Messages sent through the contact form are stored in the site's database. They can be opened only by people who sign in to the site's administration, which means our team and the web studio that maintains the site, each with their own account and password, and by our host's support staff if we ask them to fix a fault. Our Stripe account requires two-factor authentication for every login. No system on the internet can be guaranteed to be completely secure. If a breach ever put you at high risk, we would tell you and the Federal Data Protection and Information Commissioner (Art. 24 FADP).

People shown on this site

The photographs of girls and young women come from Plan International or its partners. We rely on the permissions and consent arrangements made available to us for those photographs and use each one only as those permissions allow; we add no names, ages or stories that Plan did not publish. The members of our Board are named with their roles and nothing more: we do not rely on their agreement for a photograph or a biography, because we publish neither. The members of our team and Philanthropy Council, our ambassador and our youth delegate appear with their own agreement, using names, photographs and biographies they gave us or approved for publication. We aim to keep what we publish about anyone accurate and appropriate. Anyone shown on this site can ask us to correct or remove what we publish about them, or to take a photograph down, at info@globalgirlsfoundation.org (Art. 30 and 32 FADP).

For readers in the EU and the UK: the legal basis is the consent of the person shown (Art. 6(1)(a) GDPR), which can be withdrawn at any time, and, for the names of our Board, our legitimate interest in saying who governs the Foundation (Art. 6(1)(f)).

Children

Our work is for girls and young people, so we take particular care with any information about children. This site is for adults: its contact, giving and newsletter forms are not designed for children, and we do not knowingly collect data from anyone under 18 through them. If you think a child has given us data, write to info@globalgirlsfoundation.org and we will delete it. For the photographs of girls on this site, see People shown on this site.

Complaints

Tell us first, at info@globalgirlsfoundation.org or by post to Global Girls Foundation, Badenerstrasse 580, 8048 Zurich, Switzerland, and we will try to put it right. In Switzerland you can also contact the Federal Data Protection and Information Commissioner (FDPIC), Feldeggweg 1, 3003 Bern, edoeb.admin.ch, who can investigate, and you can bring a claim in court (Art. 32 FADP). In the EU or the UK you can complain to your own data protection authority; in the UK that is the Information Commissioner's Office.

Changes

We will post changes here with a new date. If a change matters to you, for example if we add a new tool or change who sends the newsletter, we will say so plainly, and where we need your consent we will ask for it.

Questions about your data? Start a conversation.

Privacy policy and cookie notice.