Privacy Policy

Information we handle

• Sign-in identifiers: When you use a third-party sign-in, we receive the identifier supplied by that identity provider. When Meta/Facebook sign-in is enabled, BOMB01 requests only public_profile and uses the Facebook app-scoped ID to identify the account. We do not request or read your Meta email. A Meta access token is used on the server for the exchange and immediate verification and is not retained. Member identity is based on the verified issuer and subject; matching email addresses do not automatically merge accounts.
• Member details: The display name and bio you choose. If you choose email sign-in or native member sign-in, we also handle the related email address, username and sign-in credential data.
• Journey information: Saved trips and plans, private workspace drafts, contributions and images, Likes, and your consent choices for contribution or content use.
• Essential cookies: Your browser stores guest or member session and sign-in security cookies. Disabling cookies may prevent sign-in and member features from working.
• Technical and security logs: Website requests may produce records such as IP address, browser information, request time and errors. We use these to operate the website, troubleshoot issues, protect the service and prevent abuse.

Public browsing and voluntary information

You can browse public content without signing in. Journey account features require the identifiers needed by the sign-in method you choose; without them, that account feature is unavailable. Providing a display name, bio or contribution is voluntary. You can still browse public content without providing them, but the related member or contribution feature may be unavailable.

How information is used and shared

We use information to provide sign-in, saved trips across devices, workspaces, contributions and community features, protect accounts, and respond to support or security issues. Private trips and workspace drafts are private by default. Information is made public or selected for use only through the relevant feature, such as when you enable sharing, submit a contribution that is reviewed, or choose to consent to content use.

Meta Platform Data

FOODY TECHNOLOGY LIMITED is the responsible entity for Meta Platform Data. For questions about Meta Platform Data, contact info@bomb01.com.

Service providers and retention

Website hosting, database and email-delivery providers may handle information as needed to operate the service. When you choose third-party sign-in, the authentication request is sent to that identity provider. We retain information while needed to provide accounts and saved content, operate the service and protect security. A deletion request may not immediately remove information from existing backups; backups are handled according to operational cycles.

Access, correction and deletion requests

To access, correct or request deletion of information, contact the BOMB01 privacy contact at info@bomb01.com. We first verify control of the account, then review the request against related records and retention needs. See our data deletion instructions. Do not include passwords, sign-in codes or session tokens in your email.

Last updated: 9 November 2026.