Taply Privacy Policy

Taply handles only the information needed to provide NFC tools, local storage, billing, advertising, optional diagnostics, and support. The categories below distinguish information processed locally on your device from information that an integrated provider may receive.

Taply does not collect NFC payloads into a Taply server account. NFC records, contact fields, clipboard text, QR contents, Wi-Fi data, and other content may still contain personal information, so please review content before writing, sharing, or exporting it.

Taply uses information for the following purposes. If the purpose or the data flow materially changes, this policy will be updated before or when the change takes effect where required.

- Reading, decoding, writing, verifying, erasing, locking, dumping, and emulating standard NDEF tags at your request.

- Creating the local history, profiles, CSV imports, and automation sequences that you choose to keep on the device.

- Importing data from a QR code, clipboard, or selected contact so you can review it and use it in an NFC operation.

- Processing one-time Google Play purchases, restoring entitlements, and enabling Taply Pro or Remove ads.

- Showing and supporting banner advertising on the free tier through Google AdMob, where applicable.

- Detecting, investigating, and fixing crashes or reliability problems when the release is configured to send diagnostics to Jambo.team Sentry.

- Responding to support or privacy requests, protecting the service, preventing misuse, and complying with legal obligations.

Taply does not sell your personal information and does not send locally processed NFC content to a Taply backend. Information may be made available to a third party in the following limited situations.

- Google Play receives information needed to process purchases, restore entitlements, and maintain transaction records. Google controls its own processing under its terms and privacy policy.

- Google AdMob may receive advertising identifiers and device or app information when ads are served. AdMob controls its own processing under Google advertising policies.

- Jambo.team's self-hosted Sentry endpoint at ingest.jambo.team may receive crash and technical diagnostics when a release has diagnostics enabled. Taply configures diagnostics without default personal information and removes the user field before sending an event.

- A sharing, export, browser, dialer, messaging, email, calendar, or other action that you start can pass the selected content to the app or provider you choose. That recipient controls its subsequent processing.

- The public policy website and its hosting provider may process ordinary technical request data needed to deliver the page.

Information may also be disclosed when required by law, valid legal process, or an urgent need to protect the rights, safety, or security of users, Jambo.team, or the public.

For the limited external processing described in this policy, Jambo.team may use the following service providers or platform services.

- Google Play Billing: one-time purchase processing, purchase acknowledgement, and entitlement restoration.

- Google AdMob: banner advertising and related advertising-service processing when ads are enabled.

- Jambo.team's self-hosted Sentry service: crash and technical diagnostics only when diagnostics are enabled for the build.

- Cloudflare Pages or another static hosting provider: delivery of the public Taply privacy page.

These providers are instructed or configured to process information only for the relevant service purpose. Changes to the providers or the categories of information entrusted to them will be reflected in this policy where required.

Taply keeps information only for as long as it is needed for the purpose described in this policy, unless a longer period is required by law or needed to resolve a dispute or security issue.

Taply destroys or removes local information when you delete it through the app, clear Taply app data, or uninstall the app, subject to normal Android and device-storage behavior.

- You can clear recent history and delete saved profiles or automation sequences from the relevant Taply screens.

- Uninstalling Taply normally removes its local app storage. Taply is configured not to provide ordinary app backups, but device or operating-system behavior outside Taply can differ.

- Information held by Google Play, Google AdMob, Sentry, a share recipient, or a support mailbox must be deleted through the relevant provider or request process and is subject to that provider's retention rules.

Taply does not maintain paper files containing user NFC data. Electronic records under Taply's control are removed using the applicable storage or provider deletion mechanism.

You can review and manage the information that Taply stores locally by viewing, editing, or deleting saved profiles and automation sequences, clearing recent history, clearing app data, or uninstalling the app.

For advertising identifiers, you can reset the identifier or limit ad personalization through Android settings. For purchases, transaction records and account-level rights are managed through Google Play.

Because Taply does not operate a user-account backend and does not retain NFC payloads on its own server, Jambo.team cannot retrieve or delete local tag content on your behalf. If you have a privacy question or believe a provider is processing information incorrectly, contact [email protected] with enough detail to investigate; do not send NFC passwords or sensitive tag content unless it is necessary.

Taply is not directed to children under 13 and does not knowingly request personal information from children. A parent or legal representative who believes a child has provided personal information may contact [email protected].

Taply does not use cookies or a Taply account identifier in the Android app. It does not intentionally track the content of NFC tags across users.

Jambo.team uses reasonable technical and organizational measures appropriate to Taply's limited data flows.

If Taply's data practices, integrations, or purposes change, we will update this policy, the in-app legal notice, or both, and change the effective date. For material changes, we will provide notice through the app, store listing, public policy page, or another appropriate channel where required.

Jambo.team is responsible for operating Taply and handling privacy questions or complaints about the service.

[Taply privacy contact]

- Operator: Jambo.team

- Privacy email: [email protected]

- App support contact: the developer contact published in the Google Play listing (currently [email protected] in the Taply release documentation).

When contacting us, please avoid sending NFC passwords, payment-card details, or full tag contents unless we specifically request information that is necessary to resolve the issue.

This personal information processing policy comes into effect on 28 August, 2026.