What we know about you, why, and how to remove it.

Controller

The ZooBC Foundation is the data controller for this website. The Foundation is in the process of incorporation in Switzerland; the registered controller entity, address, and — where required — data-protection representative will be published here once incorporation is filed. Until then the Foundation operates as an unincorporated body under founder stewardship, and Roberto Capodieci is the responsible person for the data on this site.

What we collect

If you only read the site

Your IP address and user agent appear in standard server logs, kept for at most 30 days for security and performance debugging. We do not run third-party analytics, advertising, or tracking scripts. Reading the site sets no cookie; the one exception is the ideas and projects pages, which set a vote cookie so that a vote can be counted once (see If you vote).

If you vote on an idea or a project

Anyone can vote, signed in or not. To count one vote per person per day without an account, the first visit to /ideas/ or /projects/ sets a random identifier in the zbcf_v cookie (one year, HttpOnly, sent only to this site). A vote is recorded against a keyed hash of your IP address together with that identifier; the hash is computed with a server-side secret and is not reversible by us or anyone else into your address. Votes are kept with the idea or project they belong to, for as long as it exists, because the ranking is computed from them. If you are signed in, the vote is recorded against your account instead. Clearing the cookie starts a new identifier; nothing links the old one to you.

If you sign in

Sign-in is delegated to Sippis. Sippis handles email, password, phone, 2FA, KYC and — if you add them — Web3 wallet addresses. This site never sees your Sippis password. When you sign in, this site receives from Sippis:

• Your Sippis user UUID.
• Your primary email address and full name (as you present them to Sippis).
• Whether Sippis considers this site's app "owned" by your account (used to bootstrap admin access).

We cache these locally so page renders don't require a network round-trip to Sippis on every hit. The cache is refreshed on every sign-in.

If you chose to share more with this site on Sippis (further email addresses, a phone number, a Web3 wallet address), we read what you shared at sign-in and when you press "Check again" on your account page, and we use it for one thing: to find the record the Foundation already holds about you (giveaways, allocations, grants, programme rewards, bug bounties). Only identifiers Sippis marked verified are used. We keep two flags (whether a verified email or phone was shared) and, when a verified wallet address matched, the address itself on your record. The identifiers themselves are read, not stored.

Your account page

Your account page holds a profile (handle, bio, links, country, a photo if you upload one, a ZooBC payout address) and, if you add them, private contact channels (Telegram, Signal, WhatsApp, X, GitHub). Handle, photo and bio are public only if you switch your profile to public; the contact channels are visible to you and to Foundation admins only, and are used to reach you about rewards. Tickets you open are visible to you and to admins only. An admin may mark your account as verified after checking a channel with you.

If you post an idea or a project

Ideas and showcase projects are public once an admin approves them. Your handle and photo are shown as the author only when your profile is public and you chose to be shown; otherwise the author reads "a member". Admins always see who posted. Edits after approval go back to the approval queue.

If you show a project with a download

A project's team may attach one file per version (a zip or a PDF). The file is public once an admin approves the version. Each download is counted once per day per visitor through the same keyed hash of your IP address that votes use, with no cookie; the count is shown on the project. Team membership (who is on a project) is public by handle, under the same rule as authorship above.

If you open a ticket without an account

The ticket form at /tickets/ stores the name and email address you type, your message, and the IP address the ticket came from, so an admin can answer and spot abuse. We email you a link to the ticket; whoever holds that link can read and reply to it, so keep it to yourself. The form uses a captcha whose answer is held in a short-lived session cookie (PHPSESSID) set only when you submit the form. Admins see the address as unverified: we do not check that it is yours. Nothing you type is quoted in the emails we send, only the ticket number.

If you apply for a grant

Your name, email, and application content (project name, category, proposal text, budget, milestones, team, links) are stored so the grants committee can review them and so you can return to a draft. Application content is visible to admins; it is not visible to other applicants. Approved grants publish the recipient's name, project title, category, amount, and milestone status — because they receive public funds — but not the internal proposal text unless you opt in.

Cookies we set

Only functional cookies. No trackers.

• sippis_session — the HttpOnly session bearer, set at sign-in, cleared at sign-out.
• sippis_lang — your language preference.
• sippis_oauth_state — a short-lived CSRF token during the sign-in redirect.
• zbcf_v — a random vote identifier for visitors who are not signed in, set on the ideas and projects pages (one year). See If you vote.
• PHPSESSID — a session for the captcha on the ticket form, set when you submit it (Secure, HttpOnly, session-length).
• zbcf-theme — your light/dark preference (client-side localStorage, not sent to the server).

Why we hold what we hold

• Access — knowing who is signed in and whether they are an admin or a grant applicant.
• Contract / legitimate interest — administering grant applications you submit to us.
• Legal obligation — post-incorporation, records the Foundation must keep for audit and regulatory purposes.

Who we share it with

We do not sell or rent personal data. Grant application content is visible to Foundation admins reviewing your submission. Approved grants publish recipient details as described above. Server-side operations use the Foundation's own infrastructure; email replies come from the addresses on the Contact page.

Your rights

You can:

• Access — a copy of what we hold on you.
• Correct — anything inaccurate.
• Delete — the local cache and any application content you own. Central Sippis identity deletion is handled by Sippis.
• Object — to any processing you consider unlawful.

Write to info@zoobc.foundation. Once incorporation completes, we'll publish a formal DPO contact address here.

Retention

• Server logs: 30 days.
• Local user cache: kept while your Sippis account is active; deleted when you delete your Sippis account (Sippis notifies us).
• Draft applications: kept indefinitely at your convenience; you can delete them from your account page (feature in the user backend).
• Submitted applications: kept as part of the grants record, subject to your access/deletion rights.
• Approved grant records: public, kept indefinitely for the Foundation's accountability record.
• Votes: kept with the idea or project for as long as it exists, as a keyed hash plus the vote's weight and time; never a plain IP address.
• Profile, contact channels, photo, tickets: kept while your account is active; removed on request, or when your Sippis account is deleted.
• Ideas and projects you posted: public for as long as they are listed; an idea with no votes can be deleted by you, otherwise by an admin on request.
• Project files: public while the version is live; the team can withdraw a version (hidden, kept), an admin can delete a hidden one. Download counts: a keyed hash and a day, kept with the version.
• Tickets opened without an account: the name, email and thread are kept while the ticket is open and after, as part of the support record; removed on request to the email on the ticket.

Changes to this policy

Material changes will be posted as news items on the news archive. The current version of this policy is always canonical at this URL.

Last updated: 1 October 2026. Contact info@zoobc.foundation if anything here is unclear.