What Cumpà is, what it uses, and what it doesn’t do
What it does
Organising something with friends means chasing everybody, and it is always the same person doing it. Here the organiser drops a link in the group and whoever wants to joins on their own. The dates, the lifts, the beds, who brings what: Cumpà works out by itself what that occasion needs, it doesn’t ask for what the organiser has already put in, and what is missing it asks the people who are coming.
Who made it
It’s homemade, and part of a set of projects that all live on magistaf.com.
What gets stored
This is the part that matters, so it is written out in full. Two things only stay on the server:
The outing — the title, the proposed dates, what is needed, when it was created. The organiser writes it.
The answers — for each person: the name they came in with, what they answered, when they first joined and when they last changed their mind. The order of arrival is what decides who plays and who is a reserve, and that is why the joining date does not move if you correct your answer later.
What does NOT get stored
There is no table of people. No account exists, and there is no row holding your email, your address or a password: the columns to hold them are not there at all.
When you sign in with Google, Cumpà receives your identifier and your name from Google. The identifier is not kept: a code is computed from it, and only that code remains — twelve bytes that cannot be turned back into the account they came from. It is what lets you find your outings again from another phone. The name does stay, because it is needed: it is what the others read next to whatever you are bringing.
The visits to this site are counted with Cloudflare Web Analytics:
how many pages get opened and where they come from. We write it here
because you can see it: every visit makes a request to
cloudflareinsights.com, and a network request the page does
not name is a lie by omission.
One more thing has to be said, because it is true and it doesn’t show: the «continue with Google» button is Google’s code running inside the page. Google knows you opened Cumpà, the same way it knows every time you sign in somewhere with their button. We can’t claim otherwise and we are not going to talk around it.
Outings don’t end up on Google
The address of an outing is meant to be pasted into a chat between friends, not to be found by someone who wasn’t invited: the outing pages tell search engines not to index them, and the same refusal is repeated in robots.txt. Whoever has the link gets in: the address is the invitation, so it is worth not pasting it where it shouldn’t go.
What it uses
The typefaces are Aldrich (the mark and the labels) and Manrope (everything else), released under the SIL Open Font License. They sit on this same site and go through no outside service — the licence is here.
Signing in is Google Sign-In, and it is only there so you can find your outings again from another device.
The site and the database are on Cloudflare. The code running in this page is the code written here, plus the two things named above: Google's button and the visit counter. No third-party libraries, no framework.