privacy policy

1. Core Privacy Principles

• No Constant GPS Tracking: We do not maintain a travel history, record your exact locations, or track you on a live map.
• Local-First Handshakes: Proximity matches are recorded using local Bluetooth Low Energy (BLE) signals. Your proximity handshake history is stored directly on your device, not on our servers.
• Gradual & Controlled Reveal: You decide exactly what parts of your profile are shared with users you bump into before adding them as friends.
• Under-18 Protection: To protect minors, profile age and school sharing are permanently disabled for non-friends if you are under 18.
• No Address Book Uploads: weBump does not scan, access, or upload your device's contacts or address book.

2. Information We Collect and How We Use It

A. Account & Installation Data

weBump does not require passwords, email registration, or third-party OAuth sign-ins.

• Installation Credentials: When you open the App, it generates a unique, anonymous Installation ID, a cryptographically signed secret token, and a Public Tag. These are securely stored in your device's Keychain.
• Friend Code: The server generates a unique, randomized Friend Code (e.g., WB-ABCD-EFGH) linked to your installation, allowing you to invite or add trusted friends.
• Metadata: We store your platform (iOS), application version, and the timestamp of when you were last seen.

B. Profile Information

You have control over your profile details. You can choose to provide and publish:

• Display Name, Age, State/Region, and School.
• Bio / Blurb (up to 250 characters).
• Theme Colors & Badge Titles.
• Social Media handles (Instagram, TikTok, X, Snapchat, YouTube, Threads).
• Gaming Platform handles (Nintendo Switch, Steam, PlayStation Network, Xbox).
• Apple Music Metadata: If you choose to link your Apple Music account, we store metadata about your designated favorite song, album, or playlist (title, artist, artwork URL, catalog ID, and web URL).

C. Proximity Discoverability & Rolling IDs

To discover nearby devices without transmitting your persistent identity:

• The App generates a rotating, anonymous local identifier called a Rolling ID which is broadcast via Bluetooth Low Energy (BLE).
• This Rolling ID rotates every 10 to 15 minutes to prevent replay attacks or continuous tracking of your device in public areas.
• We store active Rolling IDs on our server for up to 48 hours to resolve handshakes, after which they are permanently deleted.

D. Coarse Location Density

If you opt to check local activity density:

• The App sends your current coordinates to our server.
• The server immediately rounds your location to a coarse grid (approximately an 11km x 11km area bucket).
• We do not save your precise latitude and longitude. We save only the coarse grid ID and the time of the query to calculate general street density levels (e.g. "growing" or "active") and return them to nearby users.

E. Safety, Moderation, & Abuse Prevention

To enforce our EULA and protect the community:

• If you report a user or are reported, we collect the report details (reason, text details, and a snapshot of the reported profile at the time of the incident).
• We store user blocks (the blocker and blocked installation IDs) on our server to prevent blocked users from interacting with you.

3. On-Device Storage (Local Data)

Your proximity handshake history is stored locally on your device (in the App's private UserDefaults database). This history contains:

• Scanned Rolling IDs of nearby peers.
• The date/time of the encounter.
• An estimated proximity indicator (e.g., immediate, near, around, far) based on Bluetooth signal strength (RSSI).
• A cache of profiles resolved from those encounters.

We cache up to 200 of your most recent handshakes on your device, overwriting older logs automatically.

4. Third-Party Services & Data Collection

To support our operations, we integrate the following third-party services:

A. Google AdMob (Advertising)

Unless you have acquired a "Supporter Badge" or reached the referral threshold, weBump shows rewarded advertisements.

• Google AdMob collects and processes tracking identifiers (such as the IDFA on iOS), IP addresses (to infer coarse location for ad targeting), and performance/crash metrics.
• You can manage ad tracking preferences using iOS system settings (under Settings > Privacy & Security > Tracking).

B. Apple Push Notifications (APNs)

• We collect and store APNs push tokens on our servers to deliver friend request alerts and proximity notifications.
• If a push token is inactive for 90 days, it is deactivated, and it is permanently deleted from our servers 30 days later.

5. Data Retention & Account Deletion

• Account Deletion: You can purge all your data at any time by navigating to Settings in the App and tapping "Start Over".
• What is Deleted: Tapping "Start Over" instantly erases all local handshake logs and Keychain credentials on your device. The App also calls our server to delete your Installation record, secrets, active rolling IDs, profile settings, friendships, friend requests, blocks, and push tokens.
• What is Retained for Safety: To prevent ban evasion and maintain platform safety, moderation reports (snapshots of profiles reported for EULA violations) are not deleted when an account is removed.

6. Children's Privacy

weBump does not permit registration or use by anyone under the age of 13. If we discover that we have collected information from a child under 13, we will immediately delete that installation and all associated data.

7. Contact Us

If you have any questions or concerns about this Privacy Policy or our data practices, please contact us at:

• Email: support@webump.app