Privacy at Buzz.
Updated 10 November 2026. This notice covers Buzz at buzzbuzz.in, an adult community for finding people and making plans.
Your account and Google sign-in
Email signup stores your name, email address, private self-declared age, a securely hashed password and login sessions. If you choose Google sign-in, we receive your Google account identifier, name, email address, verification status and profile picture when provided. We use these details to create and authenticate your Buzz account. Sign-in records and session credentials are stored on our server. We do not request access to your Gmail messages, contacts or Drive files. Your email address is not shown on your public profile.
Your profile, photos and selfie
Your display name, bio, general area, activity, optional profile photo up to three interests and optional Instagram link can be shown to other members. Your signup selfie is used for the automated face-presence check and available to you, but not through the admin dashboard. Automated checks look for a face; they do not prove identity or liveness. You can replace or delete your private selfie in your profile. Removing it takes you offline until you submit another selfie.
Location and availability
Buzz asks for location when you activate availability or request nearby suggestions. You can choose an area instead. Coordinates are rounded to an approximately two-kilometre grid before storage. Other members see a broad area and approximate distance, not your coordinates or a map pin. Worldwide discovery can show an active public buzz to people in other cities. Other people may infer your approximate area from discovery results. Connections-only visibility limits nearby discovery; approved members of your communities can still see your introduction and use your hello request preferences. Buzzing out removes the stored presence record; expired availability is excluded from discovery.
Messages, communities and safety
We store connection requests, messages, community memberships, availability notifications, blocks, reports and moderation records to operate the community. Direct chat opens after a connection is accepted. Community messages and voice notes are visible to approved community members. Public communities appear in Explore; private communities appear only to their owner, members and pending applicants. An invitation lets its recipient preview community details and request access; it does not grant chat access. Owners can expire invitation links. Community names and optional community photos follow the community’s visibility. Join requests are visible to the community owner and appointed admins. New chat image uploads are disabled. Previously shared images remain visible to authorised conversation members. Microphone access starts only when you choose to record, with a preview before sending. Chats are not end-to-end encrypted. Authorised administrators can see member names and email addresses for support and review reports, including the details supplied in a report, any evidence already attached to it and relevant community metadata. Reports are made from a person’s profile or community details; individual messages do not have a Report button. The admin dashboard does not provide access to unrelated private conversations or signup selfies. Blocking stops contact and hides the two members from each other.
Optional device notifications
If you enable message notifications, we store your browser’s push subscription address and encryption keys, linked to your signed-in account and session. Your browser’s push service (such as Apple, Google, Mozilla or Microsoft) delivers encrypted notification payloads. Alerts contain a generic message notice and a conversation link, not message text or sender names. Notifications may appear on your lock screen. Turn them off in Buzz’s Message notifications settings or your device settings. Signing out or session expiry pauses delivery; signing back into the same account can resume a previously enabled device. Expired subscriptions are removed when detected or during later setup.
Services that help run Buzz
Buzz uses Vercel for hosting and private photo storage, Turso for account and community records, and Resend for account verification and password-reset emails and support email handling. Messages sent to query@buzzbuzz.in are processed by Resend and forwarded to the operator’s Gmail inbox, which Google processes. These providers process the information needed to deliver those services. Google processes sign-in when you choose that option. Hosting and security systems may process technical details such as IP addresses and request logs. Instagram links open Instagram, where its own privacy rules apply.
Your choices and deletion requests
You can edit your profile, stop buzzing, leave communities, manage blocked members and delete your private selfie. Unsent or deleted voice uploads become eligible for cleanup after 24 hours, except attachments preserved with reports. Cleanup is retried on later uploads. Account and community records remain stored until removed through the available controls or a deletion request is processed. Only share information needed for your support request. Hosting and storage providers process private content as necessary to operate the service; chat and selfie storage are not end-to-end encrypted. To request account deletion or ask a privacy question, email query@buzzbuzz.in from your account email. We may need to verify ownership before acting. Deletion from active storage may not immediately remove copies in provider backups or records that must be retained for security or legal obligations.
Use of Google information
We use Google account information for the sign-in and account features described here. We do not sell it or use it for advertising. Buzz’s use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements where applicable. You can remove Buzz’s access in your Google account settings; this does not by itself delete your Buzz account.
Changes and contact
We will update this notice when data practices change and seek consent where needed for a new use of Google information. Contact query@buzzbuzz.in with questions.