Your logo, your theme's header, and spam kept off the contact form
v0.14.2
If you have a logo you can now choose between the big logo header and your theme's own header with your logo in it — which is what an event page usually wants. Both the sign-up and contact forms quietly check your browser before they accept anything, because spam had started coming through, and that check runs on Collr's own machines rather than sending you to anybody else. The privacy policy has been corrected on two counts and now says plainly what happens to a banned account's data.
Your page
A logo no longer decides your header. Uploading one used to put your page into the big logo-over-banner layout and leave it there, with your theme's own header replaced and no way back except deleting the logo. There is a switch in the Design editor now, in the theme section, and it only appears if you have a logo. It starts on, so nothing changes unless you turn it off.
With it off, your theme's header draws with your logo in place of your name. That is usually what an event page wants, and it is the only way to see the header a theme was actually designed around. Your logo is sized against each theme's own title, so it looks right on all of them rather than on one.
Signing up and writing in
The sign-up and contact forms check your browser before they accept anything. You will see one line saying so while it happens, it takes a fraction of a second, and there is no puzzle to solve and no boxes to click. Spam had started arriving through the contact form, which had almost nothing standing in its way.
That check runs on Collr's own machines. Nothing about you is sent to anybody else and no fingerprint of your browser is taken — which was the whole reason for building it this way rather than using one of the usual services. It does need JavaScript, and says so if yours is off.
Your data
The privacy policy now says what happens to a suspended or banned account: we keep its record indefinitely, and it cannot be deleted. That has always been how Collr works — a ban somebody can erase by deleting their account and signing up again is not a ban — and you were entitled to be told before it could apply to you. The policy names the law that allows it and points you at the regulator if you disagree.
It also stops naming a bot-protection company we never actually used. It was described in detail in our policy and in our list of companies that handle your data, and the code never once called it. That is now gone, and the section explains what we do instead.
And it finally mentions that you can delete your own account from Account & settings, with 30 days to change your mind, which has been true for a while and was missing from the page that should have said so.
