Privacy policy
Last updated: October 2026
This privacy policy applies to the FeedblickSwarm web application.
This privacy policy describes what data FeedblickSwarm processes and how, drafted in good faith based on the features currently in use. It is not a substitute for legal review — please have it checked by a lawyer or data protection officer before relying on it.
Controller
The controller within the meaning of the GDPR is:
- Name:
- Dr. Sergio Vargas - biodatum.io
- Address:
- Nadistr. 06, Muenchen
- Email:
- info@feedblick.io
Full details (incl. VAT ID) are on the Impressum.
Hosting and server logs
FeedblickSwarm uses Supabase for its database, authentication, and realtime updates, and Vercel Inc. to host and serve the web application itself. Visiting the site automatically causes technical information (e.g. IP address, time of access, browser used, and request metadata in server logs) to be processed by these providers' infrastructure. This is technically necessary to deliver the website and ensure server stability (Art. 6(1)(f) GDPR). Vercel's Frankfurt region (eu-central-1) is used for hosting, and Supabase's EU region (AWS eu-central-1, Frankfurt) for the database, so this data stays within the EU — see the Sub-processors section below.
Your rights
Under the GDPR, you have the right to:
- Access the personal data we hold about you (Art. 15)
- Have inaccurate data corrected (Art. 16)
- Have your data deleted (Art. 17)
- Request restriction of processing (Art. 18)
- Receive your data in a portable format (Art. 20)
- Object to processing (Art. 21)
- Lodge a complaint with a supervisory authority (Art. 77)
Requesting access
Before you have an account, submitting the "Request access" form stores the name, email address, and team name you provide, so we can review and respond to your request (Art. 6(1)(b) GDPR, a pre-contractual measure). If approved, this becomes the basis for your account invite; if not, you may ask us to delete the record. The form also asks you to confirm that you act in a business capacity and accept the terms (AGB); we store the time of that confirmation and the version of the terms you accepted, as proof of the contract terms (Art. 6(1)(b) and (f) GDPR). The form is protected against automated abuse by Cloudflare Turnstile — see "Request form protection" below. When you submit the form we email you a confirmation that it was received, and later a message with our decision (an approval invitation, or a notice that we cannot offer access right now); we also email ourselves a notice of the request, containing the name, email address and team name you gave. These emails are sent through our email provider, Resend — see "Sub-processors" below.
Host accounts
A host account is created once an access request is approved — we send an invite email with a link to set your password. This stores your email address and an encrypted password (Art. 6(1)(b) GDPR, to perform the contract of use). Emails such as the invitation and password reset are created by our authentication provider (Supabase) and delivered through our email provider, Resend.
Event inquiries
If you ask for a price for an event, we process the name, email address and event details you type in the form, only to answer your inquiry (Art. 6(1)(b) GDPR, steps prior to entering into a contract). The inquiry is sent to us by email through our email provider, Resend, and is not stored anywhere else. The form is protected by Cloudflare Turnstile.
Participants joining a session
Anyone joining a session via a join code doesn't need an account and never signs in. The name they type is their own choice (a nickname works just as well); it's each participant's own responsibility not to type more personal data into it than they're comfortable sharing with the session.
The name, the chosen group and the avatar (one of a fixed set of animal pictures, picked at random and changeable; the host can switch avatars off for a session) are shared over a live, temporary realtime channel with the host and with the other participants in the same session, who see a list of who is present. While the session runs, each participant's device re-announces itself about once a minute so the host can see when it was last seen. The Done / Blocked / Need 2 min signal is sent to the host only; other participants don't receive it. The projector display receives neither names nor groups, and no avatars. If the host switches it on for a session, the projector display shows how many participants are currently signalling Blocked. That is a number only, without names or groups; it is kept with the session while it runs and can be read by anyone who has the join code. None of this is written to our database, and it is gone once the session ends or the participant disconnects (the host's screen keeps showing a participant for a few minutes after a disconnect, and while the session is paused).
When a participant signals Blocked, the host's screen answers that participant alone, with a one-word message: that the host has seen the signal and, once the host taps "On it", that help is on the way. It goes over a live channel that only that participant's browser listens to, so no other participant and not the projector receives it. It contains no name or other personal data, and it is not stored; it is sent again about once a minute while the signal stays on, and gone when the signal is cleared or the session ends.
At the start of each break, the projector display and the participants' pages show a short team celebration for about 25 seconds: how many tasks the host closed in the round that just ended, and how many Blocked signals ended in it. These are team counts, never a per-person count, and they show no names or groups. To work out the second number, the host's screen adds the time at which each Blocked signal ended to the session's record: a time only, with no name or other identifier of who was blocked. It can be read by anyone who has the join code while the session runs and is deleted with the session. The host can switch the celebration off, and then nothing is recorded. When the last round (or the single timer) has run out, the same card shows the totals for the whole session for about two minutes, using the time at which the timer finished, which is stored in the session's record and deleted with it.
One exception: when task claiming is switched on and a participant claims a task, the name they typed is stored with that task in our database, together with whether they have finished it, so everyone in the session can see who is working on what. It is visible to the host and to anyone in the session while it runs, and it is deleted as soon as the host ends the session. A scheduled session ends by itself ten minutes after its last round, with the same effect. A repeating session (a scheduled session that starts again every few days) clears the names and announcements at the end of every occurrence in the same way, and then waits for the next one. An open-ended session, which has no timer, ends by itself after 24 hours without activity (a change to a task, an announcement, or the host's open session page), so a forgotten session does not keep names.
When the host allows it, participants can add, edit and delete tasks in a session. The text a participant types is stored as a task of the session in our database, with no name or other identifier attached, and is visible to the host and to anyone with the join code. It stays with the session's task list, like a task the host wrote, until the host deletes it or the session. A task a participant deletes is kept for the host, who can restore it, and is removed for good when the session ends. The host can switch this off at any time, which locks the list again at once.
Completion badges. When the host has switched badges on (a paid feature), a participant can ask the host for a badge that shows they completed the session. The host approves each request, and our server signs a badge with the name the host sees for that participant (the name they typed when they joined), the session's name, the host's name, the date and how many tasks were finished. The badge is handed to the participant's own device: we do not keep the name, the badge or a list of badges issued. The request travels over a private live channel like the Blocked signal and contains no name; the approval goes back only to that participant, on a channel only their device listens to. The participant decides whether to show or share the badge. Whoever opens a badge's link or scans its QR code sends it to our server to be checked, and the answer is not stored either.
Announcements the host sends to a session (for example "Lunch at 12:30") are stored with the session in our database, so that a participant who joins later or whose device was asleep can still read them. They contain only the host's text and the time it was sent, nothing about participants. Anyone with the join code can read them while the session runs, and they are deleted from the session when it ends.
For accountability, we also keep a separate record of every announcement a host sends: the text, the time, the session's code and name, and the host's account and email address. It contains nothing about participants, can only be read by us, and is kept after the session ends, after the session is deleted and after the host's account is deleted.
Once a session has ended, the host can export its task list as a PDF or print it. The export contains no participant names: it is only available after the session has ended, when the claimed names have already been deleted, and it shows each task with the host's own sign-off only. It is created in the host's own browser and is not sent to or stored on our servers.
The join code is the access control, as with other join-code classroom tools: anyone who knows a session's code can join it and see who is present, for as long as the session runs. Hosts should share the code only with their group and end the session when it's over. When a host shows their own session screen to the room (for example on a projector), everyone can see the participant list and the signals shown there; the dedicated projector display shows neither (at most the number of participants who are blocked, if the host has switched that on).
To keep the host's progress chart complete even if the host's own screen was off for a while, each participant's browser briefly notes how many tasks were open and closed at the end of every focus round and, when the host's browser asks for them, sends those numbers to it over the same live channel. The numbers contain no names or other personal data and are not stored on our servers.
Paid plans and payments (Stripe)
If a host subscribes to the Pro plan, the payment is handled by Stripe on its own page: the name, email address, billing address and — if entered — company name and VAT ID the host provides there, and the payment method. We never see card numbers. On our side we store only a Stripe customer ID, the subscription ID and status, the plan, and the end date of a scheduled cancellation, linked to the host account (Art. 6(1)(b) GDPR, to perform the subscription contract; Art. 6(1)(c) GDPR for the accounting and tax records we are required to keep). Stripe also uses the billing address and VAT ID to calculate and show the value-added tax on the invoice. Invoices and payment records are kept, by Stripe and by us, for the statutory retention periods even after an account is deleted.
Request form protection (Cloudflare Turnstile)
The "Request access" form is protected against automated abuse by Cloudflare Turnstile. When you open that form, your browser loads a script from Cloudflare, and Cloudflare processes technical data (such as your IP address and browser information) to check that the request comes from a person (Art. 6(1)(f) GDPR, our legitimate interest in protecting the form against abuse). This happens only on that form, not elsewhere on the site.
Local storage (no tracking)
The following is stored only in your browser, not on our servers (except the session token, needed for authentication):
- feedblick-theme — Light/dark theme preference
- feedblick-pomodoro-participant-<session code> — Your typed name, your group, your avatar, your current signal and a random identifier, remembered per session you've joined so you can rejoin it as the same participant (this browser; deleted once the session has ended, or after 12 hours without use. If the host chooses, it is kept for up to 8 days instead, together with the ids of the tasks you finished, so that a session that is reopened can find you again: you are first asked "Hi! Name, right?" and can answer that it is not you, which wipes it)
- feedblick-pomodoro-badge-<session code> — A random secret made on your device when you ask for a completion badge and, once the host has approved you, the badge you were given (this browser; deleted with your other saved session data: when the session has ended, or after 12 hours without use)
- feedblick-pomodoro-name-<session code> — Your typed name, as stored by earlier versions; only read, no longer written (this browser tab only)
- feedblick-pomodoro-ticks-<session code> — The tasks you have ticked off on your own device in a session (this browser; deleted together with the entry above)
- feedblick-pomodoro-boundaries-<session code> — The numbers of open and closed tasks your browser noted when a focus round ended, so the host can complete its progress chart (no personal data; this browser tab only)
- feedblick-pomodoro-device-prefs — Whether this device plays sounds on the session page and keeps its screen awake (your own setting; no personal data)
- feedblick-pomodoro-burndown-open — Whether the progress chart on the host's session page is shown or folded away (hosts only; no personal data)
- sb-*-auth-token — Login session token (signed-in hosts only)
None of this is used for tracking or behavioral analysis. In our assessment, this storage is technically necessary to provide a feature the user explicitly requested and is therefore exempt from consent under §25(2) TTDSG — please have this assessment checked if in doubt.
Sub-processors
We use the following service providers as processors: Supabase, Inc. (hosting, database, authentication, realtime), Vercel Inc. (hosting and serving the web application itself), Stripe (payments for the Pro plan), Resend (sending our emails) and Cloudflare, Inc. (protection of the request form). A data processing agreement under Art. 28 GDPR is in place (or being put in place) with each of them.
Retention
Personal data is deleted once the purpose of processing no longer applies, or on request, unless a legal retention obligation applies. Hosts can delete their account and every session they own at any time via Account → Delete account (which also cancels a running Pro subscription), or request deletion by email. Payment and invoice records are kept for the statutory retention period.
Contact for privacy questions
For any privacy questions, please contact: info@feedblick.io
Changes to this policy
This privacy policy is updated as needed, e.g. for new features or changes in the law. The version currently published on this page always applies.