BEEM Link is a digital namecard app built by kongmy.dev. This policy explains what the app does and doesn’t do with your data. The short answer: your cards stay on your phone.
The short version
- The cards you create are stored on your phone, not on our servers.
- We don’t run a backend. There’s nothing for us to look at.
- We collect anonymous crash reports (Firebase Crashlytics) and anonymous usage analytics (Firebase Analytics and PostHog) to improve the app. These never contain your card titles, URLs, or any content you typed.
- If you back up your Android device to Google, your card data is included in that backup — same as any other app’s settings.
- NFC broadcasts only happen when you turn the toggle on inside the app.
1. Who runs this app
BEEM Link is built and maintained by kongmy.dev, an independent developer. You can reach us at privacy@kongmy.dev .
2. What data we collect from you
2a. Card content (titles, URLs, colors)
When you add a card inside the app, the title, URL, and color you choose are saved to your
phone’s local storage (Android
SharedPreferences). We do not send this information to any server we operate. We can’t read it.
2b. Crash reports (Firebase Crashlytics)
If the app crashes, Crashlytics sends Google a stack trace, your device model, OS version, app version, and a randomly-generated installation ID. This data does not include the contents of your cards. We use it to find and fix bugs. See Firebase’s privacy page for details. You can opt out via Android Settings.
2c. Anonymous usage events (PostHog)
To understand which features are useful, the app sends a small number of anonymous events to PostHog, such as “a card was added” or “NFC was toggled on”. These events do not include card titles, URLs, hex colors, or any content you typed. They are tied to an anonymous device identifier that cannot be traced back to you. See PostHog’s privacy page .
2d. Usage analytics (Firebase Analytics)
The app also uses Google’s Firebase Analytics (Google Analytics for Firebase) to understand overall usage — for example how often the app is opened and which features are used. It automatically collects a randomly-generated app-instance identifier, your device model, OS version, app version, and coarse session and usage data. It does not collect your card titles, URLs, colors, or anything you typed, and it does not collect your advertising ID. We use it only in aggregate. See Firebase’s privacy page for details.
2e. Android cloud backup
If you have Google’s automatic backup turned on for your device, the file containing your cards is included in that backup. Google holds this backup on your account; we have no access to it. To opt out, turn off “Back up app data” in Android Settings or uninstall the app before backup runs.
3. What we don’t do
- No accounts. No login.
- No advertising trackers, and no advertising ID is collected. No third-party SDKs beyond Firebase (Crashlytics and Analytics) and PostHog.
- No selling, sharing, or licensing of your data.
- No reading the card content. Even if we wanted to, we couldn’t.
- No server-side storage of anything you typed inside the app.
4. How NFC works in the app
When you toggle NFC active and another phone touches the back of yours, the receiving phone reads your currently-selected card as a standard NDEF URI record — the same format used by the plastic NFC tags you can buy in a shop. The receiving phone’s operating system then opens that URL in its default browser.
The app does not identify the receiving device. We can’t see who tapped, when, or how often. That information never leaves the two phones involved.
For convenience, NFC broadcasting works even when the phone is locked — this is the intended behavior of a digital namecard. You can disable broadcasting at any time by toggling the indicator off.
5. Children
BEEM Link is not directed at children under 13. We do not knowingly collect data from children. The app contains no content rated above ESRB Everyone.
6. Your rights
Because we don’t store anything about you on our side, there is no account to delete or data export to request from us. To remove your data:
- Uninstall BEEM Link to clear local storage on your phone.
- Disable Android auto-backup or delete the backup from your Google account.
- Email privacy@kongmy.dev with a request to purge any anonymous analytics data tied to your installation, including the random installation ID from a recent app session.
7. Changes to this policy
If we change this policy, we’ll update the “Effective date” at the top. Material changes will also be announced in the app’s Play Store release notes.
8. Disclaimer of warranties
BEEM Link is provided “as is” and “as available”, without warranty of any kind. We make no guarantee that the app will work on every Android device — NFC Host Card Emulation (HCE) support, behavior with the screen locked, and compatibility with third-party NFC readers vary by device manufacturer, OS version, and carrier configuration and are outside our control. We expressly disclaim all implied warranties, including but not limited to merchantability, fitness for a particular purpose, and non-infringement.
9. Limitation of liability
To the fullest extent permitted by applicable law, kongmy.dev and its developers shall not be liable for any indirect, incidental, special, consequential, or punitive damages arising from your use of — or inability to use — BEEM Link. In no event shall our total liability to you exceed the amount you paid to purchase the app.
We are not responsible for the acts, omissions, or privacy practices of third-party services integrated into the app (Firebase Crashlytics, Firebase Analytics, PostHog). Their respective privacy policies govern your relationship with those services.
10. Governing law
This policy is governed by the laws of Malaysia. Any disputes shall be resolved in the courts of Malaysia.
11. Version history
May 30, 2026
Added disclosure of Firebase Analytics (Google Analytics for Firebase) as an anonymous usage-analytics service.
May 28, 2026
Initial publication of the BEEM Link privacy policy. Established the on-device storage model, anonymous analytics disclosure (Firebase Crashlytics and PostHog), and NFC broadcast behavior.
Contact us
For questions about this Privacy Policy or to exercise your data rights, contact:
KONGMY DIGITAL SOLUTIONS
privacy@kongmy.dev