Privacy Policy

Effective June 18, 2026 · whoosin, LLC (“whoosin,” “we,” “us”)

1. Who we are

whoosin is operated by whoosin, LLC, a Connecticut limited liability company, USA. Questions about this policy or your data: hello@whoosin.app.

2. The information we access from Google

When you connect your Google account, you authorize whoosin through Google OAuth. You sign in on Google’s own page, and we never receive your password. whoosin requests two permissions:

• View your email messages and settings (gmail.readonly) — used only to find the group invites you sent and read the replies to them, so we can build your attendance list.
• “Manage drafts and send emails” (gmail.compose) — this is Google’s name for the drafts permission. whoosin uses it only to create draft follow-up emails for you. whoosin never sends email and never deletes or modifies your existing messages; you always press Send yourself.

Your Gmail is read in your browser, communicating directly with Google’s API. Through this automatic reading, full message bodies and the subjects of replies are not transmitted to or stored on our servers. The one exception is a message you choose to paste yourself when reporting a misclassification (a reply, or your own invitation — see section 5) — nothing is ever captured from your mail without that deliberate action.

Google Limited Use disclosure

whoosin’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, we:

• only use Google user data to provide and improve the user-facing features described here;
• do not transfer it to others except as necessary to provide those features, comply with law, or as part of a merger or acquisition with continued protection;
• do not use it for advertising; and
• do not allow humans to read it, except with your explicit consent, where necessary for security, to comply with law, or where the data has been aggregated and anonymized.

3. How AI classification works

To turn replies into a tally, a short snippet of each reply (up to roughly 800 characters) is sent transiently to our classification service and our AI provider (Anthropic) to determine whether it means yes, no, maybe, or no clear answer. These snippets are processed in the moment and then discarded — they are not stored, not logged, and not used to train any model. Only the resulting verdict (a status plus a short generated note, e.g. “in unless it rains”) is saved, so your list stays consistent. If the AI reads a reply wrong, you can report it — and optionally paste that reply — to help us improve accuracy; see section 5.

4. What we store — and what we don’t

We store only the metadata needed to run your dashboard:

• your account email address (from Google sign-in);
• classification verdicts and their short generated notes;
• the subject line and an AI-generated one-line summary of your own sent invitation;
• event metadata (dates you set, display order, activity timestamps);
• any manual entries or status overrides you create;
• your settings and subscription status;
• if your access was sponsored: the sponsorship’s name, type, end date, and a short group label (used to answer questions like “how many of this group signed up” — no personal details beyond your own account).

We do not store the content of invitees’ replies, full message bodies, or attachments — with one exception you control: a message you choose to paste (a reply, or your own invitation) when reporting a misclassification (see section 5). Your Google OAuth access token is held only in your browser’s memory and is never written to our database or logs.

5. Other information we collect

• Usage & diagnostics: basic, non-content operational data (such as error logs) to keep the service working — not behavioral analytics or tracking.
• Cookies & tracking: whoosin uses no advertising trackers, no third-party analytics, and no tracking cookies. We use only the browser storage strictly necessary to keep you signed in (Firebase Authentication, kept on your own device — not a cookie that follows you across the web). Because we set no non-essential cookies, whoosin shows no cookie-consent banner. Beyond the anonymous aggregate counts described below, the only data we collect to improve our AI is the optional accuracy feedback you choose to give when you correct a reading (see “Accuracy feedback” below) — you decide what to share, and you can switch the prompts off anytime in Settings.
• Aggregate counts: anonymous totals (e.g. number of organizers, events, replies classified) with no personal information, used for product statistics.
• Payments: if you subscribe, payment is processed by Stripe. We do not receive or store your full card details; we store only your subscription status.
• Sponsored access: if an organization sponsors whoosin for a group (for example, a league covering its team captains), the sponsor gives us the group members’ email addresses. We use these addresses for two things only: applying the sponsored plan when that person signs in themselves, and keeping the sponsor’s own grant record straight (a private list of who was granted what, visible only to us and never shown to other users). We never send email to these addresses, never use them for marketing, and automatically delete any that go unclaimed when the sponsorship offer expires. Once someone signs in, the sponsorship’s name and end date become part of their account and are deleted with it — including the grant record — when they delete their account.
• Feedback you send: if you submit a rating or comment from Settings, we store it (with your account ID) to improve whoosin. It is deleted along with everything else when you delete your account.
• Accuracy feedback: if you tell us whoosin misread something — a reply’s status or note, or an event date it estimated — we record the original and corrected reading. You may additionally choose to paste the original text (a reply, or your own invitation) so we can review it and improve accuracy — this is the one piece of message content we store, kept only because you explicitly chose to share it, used solely to improve classification, and deleted along with everything else when you delete your account.

6. How we use information

To provide and operate whoosin, classify replies into your attendance list, create follow-up drafts at your request, process billing, send you a welcome message and service reminders about your own events (these are on by default — every email has a one-click unsubscribe, and you can turn them off in Settings; for EEA/UK users this rests on our legitimate interest in helping you run the events you set up), maintain security, and comply with law. Genuinely promotional email, if we ever send it, is separate and opt-in where local law requires. We do not sell personal information and do not use Google user data for advertising or marketing.

7. Service providers (subprocessors)

We share data only with providers who help us run the service, under their own terms:

• Google (Firebase hosting, database, authentication; Gmail API) — infrastructure and your Google account access.
• Anthropic — AI classification of reply snippets (transient, not retained for training).
• Stripe — payment processing for subscriptions.
• Brevo (Sendinblue) — sends organizer-facing account and service emails about your own events (a welcome message, and service reminders that are on by default and which you can turn off); organizer-facing only, never sent to your invitees. You can unsubscribe from any email, or turn reminders off in Settings.

8. Data retention & deletion

• Untracking an event deletes that event’s data immediately.
• An event you stop using becomes read-only after its keep-until date (shown on each event, and extendable with one tap). We may also periodically remove long-archived events; either way, you can delete any event right away by untracking it.
• Deleting your account removes your data from our active systems right away; any copies in routine system backups are overwritten on a rolling basis shortly after.
• One narrow exception: when you delete your account, we keep a single anonymized, irreversible token derived from your email address (an HMAC hash — it contains no personal information and no message data). Its only purpose is to prevent the one-time “first event free” credit from being farmed by repeatedly deleting and recreating accounts.

Because we store only metadata — never message content, aside from a message you explicitly choose to paste (a reply or your invitation) when reporting a misread — the most sensitive information stays out of our hands by default.

9. Your choices & rights

You can disconnect whoosin at any time from your Google Account permissions, and you can delete your account and all associated data from within the app.

We do not sell or “share” your personal information for advertising, and we never use Google data for marketing. Depending on where you live — for example, California, or the EEA/UK — you may have rights to access, correct, delete, or port your personal information, or to object to certain processing. You can do most of this yourself in the app; to make any other request, email hello@whoosin.app and we’ll respond within the time your local law requires. We won’t discriminate against you for exercising these rights.

10. Security

We rely on Google’s infrastructure, transport encryption (HTTPS), and a design that minimizes message content on our servers. No method of transmission or storage is 100% secure, but minimizing what we hold is our primary safeguard.

11. Children

whoosin is not directed to children under 13 and is intended for adults organizing events. We do not knowingly collect personal information from children under 13.

12. Changes to this policy

We may update this policy as the product evolves. Material changes will be reflected by a new effective date, and where appropriate we will notify you.

13. Contact

Questions or requests: hello@whoosin.app.