Public Site Privacy Notice

The privacy wall

The public web may describe BusyBi, but it must not expose the people inside. The current public site has no member profiles, posts, messages, media galleries, public member search, or indexable member routes.

Interest-list information

• Required: email address, an 18+ attestation, and a request for launch communications.
• The public form does not collect a name, location, profile, interests, free-text note, or marketing preference before email ownership is verified.
• Operational data: submission time, source, and privacy-preserving anti-abuse signals such as a keyed hash of the network address. The application does not retain the browser user-agent string.
• If anti-bot protection is enabled, its provider receives the limited request and device information needed to evaluate the challenge.

How public-site data is used

• To verify that the email owner wants BusyBi updates.
• To send requested launch notes and possible founding-member invitations.
• To prevent duplicate submissions, fraud, spam, harassment, and automated abuse.
• To meet legal duties and investigate credible threats to the service or another person.

Sensitive context

An association with BusyBi may reveal or suggest sensitive information. Email confirmation is therefore required before an address is enrolled. Each confirmation and unsubscribe secret is split between an incomplete request in the URL query and a 16-character private code carried in the URL fragment, which is not sent to the web server. The page combines them only in memory and removes both from the address bar immediately. If an email app drops the fragment, the owner can enter the code shown in the email; neither part works alone. Preference and profile questions are deliberately deferred until after ownership verification.

Sharing and advertising

BusyBi does not intend to sell interest-list information or share it for cross-context behavioral advertising. Limited processors may handle data only to provide hosting, email delivery, security, anti-abuse, and support functions under appropriate contracts. A production vendor register and retention schedule remain launch requirements.

Retention and your choices

You may use the unsubscribe link in a BusyBi email or contact the support address below to request access, correction, or deletion. Duplicate pending attempts are coalesced and do not extend retention. Unconfirmed readable request data is logically retired within the cleanup cycle after seven idle days and no later than 30 days in one active pending cycle. On unsubscribe, the readable address and optional legacy fields are removed from active records and replaced by a keyed suppression identifier; limited consent and security events may remain. Backup expiry, secure physical deletion, final timelines, and jurisdiction-specific rights still require counsel review before launch.