Privacy Policy

The contact form asks for four things: your name, an email address, which of five subjects your message is about, and the message. There is nothing else on it: no phone number, no age, no address. There is no hidden field collecting anything you cannot see.

What you send is stored in our database and read by the Multiple District Council, who reply from the address you gave. It is not added to a mailing list, it is not used to send you anything you did not ask for, and it is not passed to anyone outside MD 306 except where your message is plainly a matter for your own district, in which case we forward it to that district's officers.

To stop the form being used to send the same message ten thousand times, we count recent submissions two ways: against a scrambled one-way fingerprint of your internet address, held in our cache for ten minutes and then gone, and against the email address you typed, counted over the last hour. The fingerprint cannot be turned back into your address, and your address is never written into our database.

If you would like a message you sent us deleted, ask, and it is deleted. You do not have to give a reason.

One kind, in one place. Signing in to the officers' area sets the session cookies that keep you signed in, and they are removed when you sign out. They are strictly necessary for that area to work and are not used to build a profile of anybody.

The names, portraits, districts and roles shown on this site were supplied by the officers they describe or by their district, for publication here. Photographs of projects and events are published by the same route.

If you appear on this site and would rather not, write to us and we will take the material down. You do not have to give a reason.

District and multiple district officers sign in to maintain their own district's page. That account holds an email address, a name and the district the account may edit, held in our database with the sign-in credential. Passkeys, where an officer uses one, are held as public keys: the private half never leaves that officer's device and we could not read it if we tried.

Every change made through that area is recorded with the account that made it, so a district can see who published what.

Three services, each doing one job: Supabase stores the database, the accounts, the uploaded images and the messages sent through the contact form; Upstash caches public district content so pages load quickly, and holds nothing personal beyond the ten-minute fingerprint described above; the site itself is hosted on Vercel. Nobody else receives anything, and none of it is sold, rented or shared for marketing.

Content stays published while it is current: a Council photograph comes down when the term ends. Officer accounts are removed when the officer leaves the role. Anything you ask us to remove is removed.

Messages sent through the contact form are kept while they are being dealt with and for as long as the correspondence is useful to answer. We have not yet set a fixed period for them, and when the Council sets one it will appear here.

Leo clubs include members under 18, in the Alpha programme. This site publishes no personal information about a member under 18 beyond what a club or district has been given permission to publish.

There is no sign-up on this site, no account for a visitor to create and no comment box. The contact form is the only way to send us anything, and it is a general enquiry box: it asks for a name, an email address and a message, and it asks nobody for their age, their school, their address or their date of birth. If you are under 18 and want to join a Leo club, the form points you to your district rather than taking your details. Your district speaks to your parent or guardian, and to your school or club, in the ordinary way.

When this policy changes, the date at the top of the page changes with it. The version you are reading is the one in force.