coetio

A club is small. Its software should be too.

Every club picks a colour, and the whole app wears it.

Small in reach

There is no way to find an organization from outside it. The link a leader shares does one thing: it lets someone ask to join. Everything else needs an account and a place on the roster.

Small in what it keeps

Leaders see the roster. The owner alone sees phone numbers. A date of birth is checked once at sign-up and shown to nobody at a club. A volunteer program never records a resident's name.

Smaller over time

A feature nobody uses gets removed, and the changelog says which.

Changelog

The name

Coetio is a coined word. The nearest real one is Latin coetus, a gathering, from coīre, to go together. It appears in no dictionary. Neither does your club.

Who is behind it

I'm Kevin, a high-school student. I run clubs at my school and built Coetio to run them. Real clubs use it while it is being built, and a message to support@coetio.com reaches me. Get in touch.

Why it is built this way

One person writes Coetio and one person answers the email. There is no security team to catch a mistake, so where it can, Coetio keeps a protection in the shape of the records themselves, where nobody has to remember it.

A student's date of birth sits on their account. The roster screens and every export a leader can download read the membership record, and the membership record has no date-of-birth column. Nobody has to remember to keep it out of a roster. Phone numbers are protected differently. They sit on the membership record, and every screen and export that could show one checks on the server whether the reader is the owner. An officer's roster and exports leave them out.

Coetio holds no certification, and no outside firm has been paid to test it. There is no two-factor sign-in yet. The security page lists what is protected and says where the protection stops.

Start a club or a volunteer program.