Privacy Notice

1. Information collected

We process account details such as name, email, password credential or social sign-in identifier, public profile fields, and your age and legal-version acceptance records. We also process listings, photos, direct messages, offers, comments, reports, moderation records, and notification activity you create. Authentication and security systems may record session cookies, IP address, browser or device user agent, and timestamps.

Optional trust workflows process a private phone number, linked social account details, mailing address, and identity-document extracts. Identity images are processed in memory and deleted after extraction. Email or phone team invitations process the recipient address supplied by a team manager, a one-time hashed invitation token, and delivery/audit status. Full phone numbers, invite contacts, legal names, and addresses are not shown on public profiles.

2. How information is used

We use information to create and secure accounts; publish member-selected profile and listing content; enable private messages, offers, and public discussions; enforce posting limits; send in-app notifications; investigate reports; moderate abuse; maintain reliability; deliver requested team invitations; verify control of a phone number; and comply with legal obligations. Public profile, listing, and discussion content is visible to other marketplace visitors as the interface indicates. Direct messages are visible to the two conversation participants and may be accessed by authorized personnel when reasonably necessary for safety, abuse review, support, or legal compliance.

3. Cookies

Signing in sets a session cookie from our authentication service; without it you cannot stay signed in. Before public launch, a pb_site_gate cookie records that a visitor entered the shared pre-launch password — it stores a digest of that password only, and identifies no one. Where analytics is enabled for a deployment, the analytics vendor stores its own identifier in the browser to keep a visitor consistent across page views.

There is no cookie-consent banner. You can block or clear cookies in your browser; blocking the session cookie will stop sign-in from working.

4. Analytics and error monitoring

When they are configured for a deployment, the web app loads PostHog for product analytics and Sentry for error and performance monitoring.

Analytics is limited in code to a fixed list of categorical events — viewing a kind of page, opening the listing composer, publishing a listing, completing an upload, starting a conversation, and opening a payment handoff. Those events carry no free text and no listing, message, or profile content. Automatic event capture, page-view capture, and session recording are disabled. Private pages are excluded from capture entirely: messages and conversations, offers, settings, admin, onboarding, email verification, team invitations, team management, and the sign-in and sign-up screens. If you are signed in, events are associated with your internal account identifier; signing out resets that association.

Sentry receives error and performance data with vendor-side personal information disabled, and each payload is reduced before it is sent: an error keeps its type, stack frames, and release and environment tags; route names and paths have identifiers replaced with placeholders; and the only account information attached is your internal account identifier. We do not control how long these vendors retain what they receive — their own policies govern that.

5. Social sign-in

You can create an account or sign in with a social provider. Google, Facebook, X, and Apple sign-in are each available only when that provider is configured for a deployment. When you use one, the provider gives us the account identifier and the basic profile details you approve — typically name, email address, and avatar — which become your sign-in identifier and initial profile. We never receive your password with that provider, and we do not post to your account there.

You can disconnect a provider from its own settings; on Facebook this is under Settings & privacy → Apps and websites. Disconnecting stops that sign-in method but does not delete your PAINTBALL BST account — see Data deletion.

6. Sharing and service providers

Information may be processed by infrastructure, database, object-storage, search, authentication, monitoring, analytics, transactional-email, SMS, and verification vendors used to run the service. Cloudflare Email Service delivers email invitations and Twilio delivers phone invitations and verifies one-time SMS codes when those integrations are enabled. Information may also be shared with other users when you publish or communicate, or when required for safety, legal process, or a business transfer.

We do not sell your personal information, we do not use it for targeted advertising, and we do not profile you to make automated decisions that produce legal effects. The product has no feature that does any of those things.

7. International transfers

PAINTBALL BST runs on infrastructure and vendors that operate in more than one country, including the United States. Information you give us may be stored and processed outside the country you live in, on systems subject to laws different from your own.

8. Retention and security

In-app notifications currently have configurable retention, initially 90 days. Invitation links expire after the configured period and only token hashes are stored; delivery attempts and phone-verification results remain in restricted audit records. Identity source images are not retained. Other information is kept while needed to operate accounts, maintain marketplace and moderation records, resolve disputes, secure the service, and meet legal obligations.

Moderation, audit, and marketplace activity records are written to be append-only, so they persist after the content or account they describe is gone. Copies also remain in routine backups until those backups age out of rotation, and each vendor keeps what it receives under its own schedule. We use reasonable safeguards, but no system is completely secure.

9. Security incidents

If a security incident affects your information, we will notify you where the law requires it, and describe what happened and what you can do about it.

10. Choices and requests

Members can edit supported public profile fields and control what they publish. To ask for a copy of your information, to correct it, or to have your account deleted, email support@paintballbst.com from the address on your account and include your handle so we can match the request. We aim to respond and complete the request within 30 days.

If we decline a request, you can appeal by replying to the same support thread. We will review the appeal and send you the decision and the reasons for it. Depending on where you live you may also be able to complain to a local data protection authority or attorney general.

Do not send identity documents or other sensitive attachments through ordinary support channels.

11. Deleting your account

Deletion is handled by email; there is no self-serve button. Data deletion sets out how to make the request, what is removed, what is kept for the reasons in section 8, and the same 30-day target described above.

12. Do Not Track and Global Privacy Control

Browsers can send Do Not Track or Global Privacy Control signals. PAINTBALL BST does not detect or act on either signal — nothing in the product reads them. The analytics limits in section 4 apply to every visitor regardless, and you can block analytics storage in your browser.

13. Age limit, changes, and contact

The marketplace is not offered to anyone under 16. If we learn that an underage person created an account, we will investigate and take appropriate action. Material notice changes will use a new version and may require acceptance. Privacy requests and questions go to support@paintballbst.com, which is the contact address for everything described in this notice.