Where Burg's information comes from

Your Burg experience starts with what happens on Burg

What you do on Burg helps Burg understand what is useful to show you on Burg. Features like Feed relevance, nearby content, and suggestions are built primarily from activity that happens inside the app itself — things like:

• posts you create and react to
• events you create, open, or RSVP to
• Groups you join or participate in
• people and organizers you follow
• places and events you save
• searches you run inside Burg
• the nearby radius you choose
• your account settings and preferences
• who you block and what you report or hide

Not every action feeds every feature. Today this mostly works as a light touch: Burg derives simple, coarse interests from your recent activity — like "goes to a lot of live music" or "opens nightlife spots" — and uses them to gently rank content that you could already see. Personalization never overrides privacy, safety, age, blocking, or audience rules, and blocking and reporting are used to protect your experience, not to advertise to you.

What you create and what Burg keeps

Most of the information Burg holds is information you intentionally create or provide: your account and profile, posts and photos, Community Events and Group Events, Groups, chats and messages, RSVPs, follows and friend connections, settings and preferences, support requests, and reports or other safety activity.

Burg keeps this information for reasons you would expect: running your account, showing your content to the audience you chose, making app features work, keeping safety and moderation systems effective, preventing abuse, helping you when something goes wrong, and meeting the obligations that apply to us.

The full details — including how long different kinds of information are kept and how deletion works — live in our Privacy Policy. This page is the plain-language version, not a replacement for it.

We don't buy social-media profiles to build your experience

Burg does not buy behavioral data from other social-media companies to construct your Feed, interests, connections, or suggestions. What you see on Burg is not decided by a purchased profile of who you are somewhere else — it's decided by what you actually do here.

Burg also does not build your experience from third-party advertising identifiers or cross-app advertising profiles, and does not use third-party analytics SDKs or device fingerprinting for personalization. If you're new to Burg, Burg simply knows very little about you — and that's by design.

We don't sell your personal data

Burg does not sell your personal information to third-party advertisers or data brokers, and we do not currently serve third-party targeted advertising in the app. We also do not hand your personal information to advertisers so they can build behavioral advertising profiles of you.

That position is written into our Privacy Policy, which is the document that controls how your information is collected, used, and shared.

Events: made on Burg, submitted to Burg, or from event services

Events you see in Burg can come from a few different places:

• Community Events — created by people on Burg.
• Group Events — created through Burg Groups.
• Venue-requested events — sent to Burg by businesses, venues, organizers, or their authorized representatives from publicly verifiable business or venue email addresses, and reviewed before listing.
• Events from supported event services — public event information, such as concerts and ticketed shows, from sources like Ticketmaster and Eventbrite where those sources are enabled and the information is current. Not every event from those services appears in Burg.

Using an outside source to show public event information is very different from buying personal information to figure out what you like. Ticketmaster and Eventbrite are where some event listings come from — they are not a source of information about you. When Burg looks up nearby public events, limited information like a search area may be shared with a service to return relevant results, as described in the Privacy Policy.

Venues and businesses

Burg's venue and business information is built from a few direct sources:

• requests sent directly by businesses, venues, organizers, or their authorized representatives from publicly verifiable business or venue email addresses
• publicly available business and venue information
• basic location and contact details

Burg treats direct venue and business requests as a first-party source for venue and event information. Burg may review, confirm, correct, reject, format, or supplement submitted information before it appears in the app, and may use appropriate publicly available venue, place, business, or event information to verify, supplement, format, or maintain place information. Once Burg has reviewed venue information, that reviewed version is treated as the trusted record — outside sources don't silently overwrite it.

Businesses and venues can help keep their information accurate by emailing requests directly to Burg from a publicly associated address — use the venue and event request templates, or start from the Business & venues page. Burg aims to keep venue and event information accurate, useful, and as directly sourced as reasonably possible.

Places and local reference information

A local app needs a foundation of basic place information before every business has talked to us. Burg may use publicly available information to establish or supplement the basics: place and venue names, addresses, categories, coordinates, and public business details.

That public foundation makes nearby browsing useful from day one, and direct updates from businesses make it more accurate over time. A place appearing in Burg doesn't necessarily mean that place gave Burg its information directly — but any business can claim the accuracy of its own listing by sending us an update.

Identity verification through Didit

Burg uses Didit as its identity verification service provider. Verification helps confirm that a real person is behind an account, which is what makes verified-only audiences and other trust-sensitive features meaningful. Didit handles the verification process itself. During identity verification, our identity-verification provider, Didit, may provide Burg with verification results and associated information, including gender information. Burg receives and stores only limited resulting fields — first name, last name, full name, date of birth, age, gender information, and verification status or result metadata — and does not store your identity documents, selfie images, or biometric data.

Didit's job is verification — it does not provide Feed recommendations, local content, venue data, or advertising information. Verification is optional for basic use of Burg. It is not required to browse eligible public Groups or Events. And verification is a trust signal, not a safety guarantee.

For what verification does and doesn't mean, what data is involved, and how long it's kept, see the Verification FAQ.

Maps and location

Burg's location features run on simple inputs: the nearby radius you select, your current or approximate location when you grant permission, and the coordinates of places and events. Burg does not broadcast your live location to other users in real time — sharing a location always takes an explicit action, like tagging a post at a specific place.

As Burg's map experience develops, Burg plans to use the native mapping service available on your device — the platform-provided mapping experience on iPhone or Android. Map services like these can supply the map display, geographic context, place positioning, and directions or related functionality where supported. Burg doesn't own the underlying map data; mapping services are a source of geography, not a source of information about what you like.

Outside services have specific jobs

Like any app, Burg uses service providers for defined functions: Didit for identity verification, supported event services like Ticketmaster and Eventbrite for public event information, and providers for hosting, storage, email delivery, maps, and error monitoring. Each one has a specific job.

The distinction we care about: using a service to operate a specific Burg feature is not the same as buying a behavioral profile to build someone's Feed. The Privacy Policy describes how information is shared with service providers; the Cookie and Website Notice covers this website, which currently has no Google Analytics web implementation, no cookies, and no browser storage. Planned Firebase Hosting is website delivery, not the same thing as website analytics.

Keeping Burg's data clean and useful

We try to keep Burg's information direct, understandable, and connected to the people and places it represents. In practice that means preferring information created on Burg when practical, reviewing what businesses and venues send, using public information carefully for local context, keeping Burg-created content distinct from externally sourced information, and correcting or removing inaccurate information when we find it or when someone tells us about it.

We won't claim perfection — event times, hours, and business details can change without notice, so confirm anything important with the venue or organizer directly. If something looks wrong, businesses can use the venue and event request templates, and anyone can reach us through Support or at support@burgsocial.com. Privacy questions go to privacy@burgsocial.com.