Effective date: November 9, 2026
Who we are
The Buzz is operated by SIA PELE BELE, registration number 40203413465, VAT number LV40203413465, with its registered address at Liepājas iela 40 k-10 - 55, Rīga, LV-1002, Latvia. In this policy, “The Buzz,” “we,” and “us” refer to that operator.
For privacy requests, email support@thebuzz.events or write to our registered address above. You can also use our Contact us page.
This policy explains how we handle personal information when you visit our website, create or manage an organizer account, use an event page, or contact us.
Information from organizers
When you create and use an organizer account, we process your email address, account identifier, authentication information, and account activity. If you choose Google sign-in when available, we receive the identity and basic profile information needed to sign you in, such as your verified email address and display name. Google sign-in does not give The Buzz access to your Gmail, contacts, or calendar.
We also store the organization details, workspace ownership information, event information, page settings, design settings, and files you provide. These can include your organization name, event name and dates, page address, logo, banner, design artwork, and uploaded fonts.
Each workspace has one designated organizer account that manages all of its event pages, organization settings, purchases, and event activity reports. Team invitations and additional editor accounts are not available.
Authorized The Buzz staff may access saved workspace content to provide requested customer support, carry out agreed design services, or investigate technical problems. Administrator access is restricted, and support access and content changes are recorded. Support edits can include page settings, branding, and design templates. This access does not reveal your password or attendee files that stay in their browser.
Information from event attendees
You do not need an organizer account to personalize and download an image from an available public event page.
In the personalization tool, the photo or company logo you select and the text you enter are processed in your browser. The tool creates the downloadable image on your device. It does not upload those attendee files or text to The Buzz, add them to an attendee directory, or include them in the organizer’s download report.
The same browser-local handling applies to photos, logos and test text used by organizers in private previews. They are not saved as default attendee content. Organizer test downloads are excluded from attendee results.
This is different from organizer-uploaded logos, banners, and design artwork, which are stored so an event page can work. It is also different from information you choose to send us in a support message.
Your downloaded image remains on your device until you manage or delete it. If you share it on LinkedIn or another service, that service handles it under its own terms and privacy policy. The Buzz does not post it automatically.
Usage and technical information
We record event-page visits and image download requests to provide event statistics. Application records contain the event and design identifiers, the activity type, a request identifier, and the day of the activity. These reports count activity; they do not identify which attendee downloaded an image or prove that anyone shared it.
When you arrive at our website through a link we tagged for a campaign, such as an outreach email, we count the arrival as a daily total by campaign, source, medium and landing page. We do not use cookies or browser storage for this and do not store your IP address with it. If you then create an account, your account records which campaign link you used, so we can see how many sign-ups and published event pages each campaign produced.
Our servers and infrastructure providers receive technical information needed to deliver and protect the service, including network addresses, request information, and browser or device information. The application uses short-lived, hashed identifiers for rate limiting. A hashed identifier is not a guarantee that information is anonymous.
Infrastructure providers handle their own technical records under their applicable notices and retention arrangements. The application’s activity counts are separate from those records.
Payments and inquiries
When you buy an event page, extra template capacity, an extension or design services, Stripe processes the payment. We store the confirmed billing name, company details if supplied, billing email and address, country, tax ID and verification state, amount, currency, tax breakdown, product line items, payment status, invoice identifier and number, invoice PDF reference, transaction references, and receipt information. We also record the accepted terms version and timestamp, immediate-start request where relevant, and your separate marketing preference. Our application does not store your full payment card number. A finance recipient may receive an invoice payment link without receiving workspace access.
If you contact us, we process your name, email address, message, and related correspondence. If you request design services, this may also include your organization, event information, project brief, and supplied assets.
Why we use information
We use information to provide accounts and event pages, save your work, process purchases, deliver account messages, answer questions, provide requested design services, report event activity, prevent abuse, resolve disputes, and meet legal obligations.
Where the GDPR or similar laws require a legal basis, we rely on the following grounds as applicable:
- Performing or preparing a contract with you, including account services, purchases, and requested work.
- Our legitimate interests in operating and securing the service, communicating with business contacts, preventing fraud, and providing basic service statistics, balanced against your rights.
- Legal obligations, including required financial records and responses to lawful requests.
- Consent where required for optional marketing, nonessential storage or tracking, or another optional purpose. You can withdraw consent without affecting earlier lawful processing.
Creating an account or using an attendee page does not subscribe you to promotional emails.
Who receives information
We use providers to deliver the service. They receive the information needed for their functions, subject to their applicable roles and contracts:
| Provider or recipient | Purpose |
|---|---|
| OpenAI Sites and the underlying Cloudflare infrastructure | Website and application hosting, delivery, application data, uploaded organizer assets, and technical operations. |
| Supabase | Organizer authentication and account verification. |
| Stripe, when payments are enabled | Checkout, payments, receipts, refunds, and payment risk checks. |
| Resend, when configured | Delivery of account and contact messages. |
| Google, if you choose Google sign-in | Authentication and basic identity verification. |
| Google Fonts, if an organizer selects an externally hosted Google font | Delivery of the selected font to visitors’ browsers. |
| Our authorized support staff and configured business email provider | Handling requests, restricted access to saved workspace content for support and agreed design work, service administration, and related correspondence. |
| The organizer responsible for a workspace | That workspace’s organizer content and event activity reports, as described above. |
We use Google Workspace for business correspondence. Provider privacy information is available from OpenAI, Cloudflare, Supabase, Stripe, Resend, and Google.
The Buzz application does not sell personal information or share it for cross-context behavioral advertising. The providers listed above also describe their own processing in their privacy notices.
We may disclose necessary information to comply with law, address a security incident, protect legal rights, or support a business transfer with appropriate protections and required notices.
Published event-page content and the organizer assets used by it are accessible to people who can access the public page. Do not put confidential information in material intended for publication.
Cookies and browser storage
The Buzz uses cookies for organizer sign-in, secure account flows, and password recovery. The application’s sign-in cookies can last up to 30 days and may be renewed. Temporary sign-in verification cookies last up to one hour, and password recovery proof lasts up to 15 minutes.
During email verification, browser session storage can remember your pending email address, return page, and resend timing. It does not store your password there.
The pricing page can remember your selected currency in local storage until you clear it. When suggesting an initial currency, it can request country information from Cloudflare. This network request exposes normal connection information to Cloudflare; the currency feature does not save your raw IP address.
Pages using Google Fonts connect to Google to load the selected fonts. Other hosting or payment-provider technologies may operate when you use their features.
You can manage cookies and local storage in your browser. Blocking required authentication storage can prevent sign-in or recovery from working.
The hosting platform and sign-in or payment providers can use additional technologies for their own access, security, and service functions. Their notices explain those technologies. We will provide any consent choices required before introducing nonessential tracking into the public service.
Tracking preferences
Our application does not use cross-site advertising trackers and does not change its basic operation in response to a browser’s Do Not Track signal. This does not mean that essential service requests or security records stop when that signal is enabled.
Global Privacy Control is a separate browser signal. We will honor opt-out preference signals where applicable law requires them; our application does not enable advertising sale or sharing.
How long we keep information
We retain organizer and workspace information while it is needed for the account, saved event work, and the purposes described here. An event page’s initial availability lasts 365 days from publication. At expiry it goes offline and is archived; expired event content is normally retained for a further 365 days to allow restoration by extension, then removed under the retention process. Deleting an event does not necessarily delete workspace assets, the authentication account, or financial records.
During private setup, retention reviews and deletion are handled manually. The following periods guide those reviews; a documented legal obligation, active purchase, security incident, or unresolved dispute can require a longer period.
| Information | Retention and review criteria |
|---|---|
| Active accounts and workspaces | Retained while active and needed for the service. Dormant accounts are reviewed after 24 months without sign-in, an active paid event, or an unresolved order. We give 30 days’ notice before closure for inactivity. |
| Unpaid, unpublished drafts | Reviewed after 12 months without editing, with 30 days’ notice before deletion. A purchased but unpublished page is not treated as an unpaid draft. |
| Expired event data and analytics | Normally deleted 365 days after the event page’s availability period ends, unless extended or retained under a documented legal hold, unresolved payment or dispute. |
| Organizer assets | Retained while referenced by a retained event or workspace setting. Unreferenced files are targeted for removal within 30 days after confirming they are unused. |
| Closed support or design inquiries | Normally retained for up to 12 months after closure. Necessary contract, transaction, or dispute records follow the relevant longer period. |
| Application security records | Retained only for the relevant security purpose. Our target for ordinary diagnostic records is 30 days; infrastructure providers can have different retention arrangements. |
| Financial records | Invoices and supporting transaction records are retained for at least five years, and accounting registers for ten years, or longer where a specific legal obligation requires it. Required seller and buyer invoice details remain in restricted accounting records after account closure; ordinary account data is removed or pseudonymized where appropriate. The exact accounting retention schedule is confirmed before live payments open. |
For a verified account-closure request, we aim to remove unnecessary active-system data within 30 days, subject to applicable legal deadlines and exceptions. We will explain information that must remain and why.
Provider recovery copies, if any, follow the provider’s actual retention cycle. We do not promise immediate removal from every recovery copy or a guaranteed backup service. Information retained for a legal hold is restricted to that purpose and reviewed when the hold ends.
Your choices and rights
You can update available account and event settings in the dashboard. For account closure, access, correction, deletion, or another privacy request, contact us using the details above. We may need proportionate information to verify your identity and authority; please do not send passwords or full payment card details.
Depending on the law that applies, you may have rights to access, correct, delete, or receive a copy of information; restrict or object to certain uses; withdraw consent; and appeal a decision where an appeal right exists. These rights can have legal exceptions, such as required financial records. We will respond within the applicable legal deadline and will not unlawfully discriminate against you for exercising a right.
If your request concerns an organizer’s use of your information outside The Buzz, contact that organizer. Where we process information on its behalf, we will help route the request appropriately. We cannot remove copies already downloaded or shared to third-party services.
You may complain to Latvia’s Data State Inspectorate — Datu valsts inspekcija, Elijas iela 17, Rīga, LV-1050, Latvia; pasts@dvi.gov.lv. Follow the authority’s instructions for submitting a formal complaint. You may also contact another competent supervisory authority where applicable law permits.
International processing and security
We operate from Latvia. Our hosting and authentication providers may process information outside Latvia and the European Economic Area, including in the United States. The location depends on the provider and service used. Applicable law may require a transfer mechanism and additional safeguards.
Production transfer arrangements are being reviewed during private setup and must be confirmed before public customer processing begins. Contact us for the arrangements relevant to your information. This policy does not claim EU-only hosting or that every provider has the same role or safeguards.
We use access controls and other measures designed to protect information. No internet service can guarantee absolute security. Do not upload sensitive information that the service does not need.
Children
The Buzz is intended for adult organizers and professional event attendees. It is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Contact us if you believe a child has supplied information so we can investigate and take appropriate action.
Changes
We will publish an updated effective date when this policy changes and provide additional notice where required. A new purpose that requires consent will not be introduced solely by changing this policy.