Effective date: 30 July 2026
Provider (launch entity): Buzzz Creations LLC, a Texas limited liability company ("Buzzz", "we", "us") and the data controller for the Buzzz app.
Privacy contact: buzzzcreationsllc@gmail.com
Publisher verification required: The age-eligibility statements below describe required US-launch behavior. They must not be published as live behavior until the client, backend, rules, minimum-version cutover, and legacy-data migration have been deployed and verified.
Buzzz is operated by Buzzz Creations LLC and launches in the United States. India availability is deferred until local legal, payments, privacy-contact, and deployment requirements are complete.
Buzzz is a chat and local-commerce app ("Chat. Shop. Sell."). Specifically:
Depending on the feature and jurisdiction: performance of a contract, consent, legitimate interests such as safety and product improvement, and legal obligations.
Current personal text-message bodies sent by supported Buzzz clients are encrypted on the sender's device separately for participant devices using Matrix Olm, and the service stores ciphertext for those bodies. The service still processes account, device, participant, timing, delivery, and other routing metadata needed to operate the chat. The message-content guarantee does not cover that metadata, service/system content, public content, commerce records, call signalling, or media. Personal-chat media sending is paused while client-side file encryption is completed.
Historical messages that used the retired Signal implementation are not decrypted by current clients. A historical body may still appear when a previously decrypted copy remains in that participant's local encrypted cache; otherwise it is unavailable. After any message is decrypted, its plaintext may also remain on participant devices, in operating-system backups where allowed, or in a Buzzz client-encrypted chat backup if the user enables that feature. Recipients can also copy, export, photograph, or otherwise retain content.
Calls use WebRTC DTLS-SRTP to encrypt media in transit between participants or a relay. Buzzz does not currently claim a separate, independently authenticated app-level end-to-end encryption layer for calls.
If enabled, cached chat history is encrypted on the client with AES-256-GCM and an account-bound recovery key before upload. The key may be kept in platform secure storage or chosen by you. Buzzz cloud storage receives the encrypted blob. Losing every available copy of the key can make the backup unrecoverable.
We share data only with:
We do not share your content with advertisers or data brokers.
Content you post publicly is visible to others and may be served through public links. Content marked private is intended only for the audience you select. Visibility controls are not end-to-end encryption. Current personal text-message bodies have the additional protection described in §5.
Depending on your region you may access, correct, delete, export, or object to processing of your data, and withdraw consent. Contact buzzzcreationsllc@gmail.com.
Buzzz's United States service is for adults who are at least 18. Every new and existing account must complete the current, versioned 18-or-older declaration before entering the service. The check fails closed: a person who says they are under 18, declines the declaration, or has not completed its current version is not allowed into the service. The app provides a sign-out path and, where an account already exists, an account-deletion path.
We do not ask for a date of birth. The declaration is not identity or document-based age verification. It reduces data collection but cannot guarantee that a person states their age truthfully. These controls do not by themselves establish compliance with every law or eliminate the risk of underage access.
Safeguards include Matrix Olm encryption for current personal text-message bodies, client-encrypted backups, access-control rules, platform attestation where configured, and transport encryption. Metadata and decrypted copies on participant devices remain outside the message-content encryption boundary. No system is perfectly secure, and these controls do not make the app immune to compromise. We work to protect your data and will notify you of breaches as required.
Buzzz launches in the United States and is not currently offered to users in India. Before an India launch, we will complete local legal review, appoint and publish required contacts, and update this policy.
Buzzz and its providers may process data in the United States, India, and other regions where configured cloud, payment, delivery, or support services operate. We will use required contractual or other transfer safeguards and obtain consent where applicable. Exact production regions must be verified before launch.
We'll post updates here and, for material changes, notify you in-app.
Buzzz Creations LLC: buzzzcreationsllc@gmail.com.
The publisher separately maintains its verified public business/service address in app-store, payments, tax, and regulatory profiles where required. A founder's home address is not published merely to fill a template.
Buzzz Creations LLC · Chat. Shop. Sell.