Brio NFC

Privacy policy

Local data. Explicit choices.

App: Brio NFC.
Owner: Kelven Severo.
Privacy and support contact: learnflowbr@gmail.com.
Effective date: October 20, 2026.

How the app works

Brio NFC lets you read, prepare and write NDEF content on compatible NFC tags. Core operations run on the device, without account registration or an app server. The app is free, with no ads, in-app purchases or subscription. Usage metrics are optional and require permission.

Optional usage metrics

This section applies to app versions offering the optional metrics setting; earlier versions do not include the Analytics SDK.

If you opt in, Google Firebase Analytics receives feature selections, operation outcomes, an app installation identifier, device/app information and approximate region derived from the IP connection (not GPS). No field values, links, phone numbers, saved titles, tag identifiers, NFC payloads, credentials or session recordings are sent. We use metrics to understand adoption and improve usability. Advertising and personalized advertising are disabled. Google processes metrics on its infrastructure, which may be outside your country. You can withdraw permission in Settings: collection stops and the local analytics identifier is reset. This does not erase events already sent or existing aggregate reports. Contact learnflowbr@gmail.com for privacy requests. Google explains its handling at https://policies.google.com/privacy and https://firebase.google.com/support/privacy. Declining metrics does not limit NFC or the Library.

Content prepared with guides

The 20 guides and six manual types build text and link records locally. The app does not access social network accounts or check whether profiles exist. Phone numbers, optional WhatsApp messages, recipients, email subjects and addresses you enter may become part of the prepared record and its export.

The selected guide and original fields, including incomplete input, remain in the local draft; the guide selection is not an additional NFC JSON field. Displayed logos are local files, with no images loaded from the network.

Content on your device

Read content stays in memory until you choose to save it or use it in a draft. Templates, favorites, drafts and preferences are stored locally. Operational history contains minimal result and time metadata; it does not store read or written content, payloads, passwords or a persistent tag UID. Technical information may appear during inspection. The UID is not used for authentication.

Country and phone number

The picker uses a local table of 245 countries and territories and their calling codes. On Android, suggestions use your last explicit choice, SIM country, network country or system region, in that order. On iPhone, they use your last explicit choice or system region, without accessing the SIM. You can change the suggestion or enter an international number. This does not read your own phone number, contacts or location and needs no additional permission. The interface language does not determine the country. An explicit choice is stored in local preferences.

Backup and restore

Local data may be included in native iOS or Android backup, according to your settings and system services. This differs from app-managed synchronization. The system provider’s rules also apply. A pending write is not resumed automatically after a restore.

Uninstalling the app may remove local data. Backups and exported files follow the settings and storage locations you choose.

Files and sharing

Import and export use system file pickers and sharing mechanisms. Importing creates a new template without replacing existing templates using an identifier from the file. An exported document contains the selected records and may contain personal information you entered. Review the content before sharing. The chosen recipient or service handles the copy under its own terms.

Template exports do not include NFC tool credentials, UID, protected settings, the full database or internal logs. Sensitive content you type into a record may be part of the document; check what you have chosen to export.

On Android, choosing Export creates a private temporary copy excluded from backup, so the export can be recovered if the system restarts the app. The copy is removed when the export is completed or canceled. If removal fails, the app informs you and keeps the option to remove it.

NFC credentials

Specific password tools remain unavailable until qualified. Their forms and executors use credentials only in memory during the explicit operation; they do not include credentials in the database, backup, history, logs or export. There is no feature for storing NFC passwords.

A read does not automatically open links, make calls, send messages or execute commands. Test destination requires a tap from you and opens the same URI prepared for the record when a compatible app is available. On Android, phone opens the dialer; on iPhone, the system asks for confirmation before a call. SMS and email open the corresponding app for you to compose and review, without Brio NFC sending anything. The test does not read or write a tag and does not confirm that the destination exists. The corresponding app and destination may have their own data practices. Link previews are not fetched automatically. Opening a website, profile or file may require internet access, authorization and compatible apps.

Menus, files and PDFs

Menu and File or PDF store only the URL of content that is already hosted; Brio NFC does not receive, host, upload or embed the file in the tag. Later access may depend on the network, permissions and link validity in the selected service.

NFC and permissions

NFC is used for the operation you start. Typing contact or location information does not require access to your contacts or GPS. Files use system mechanisms. The app does not request camera, microphone, contacts or location access for its NFC core.

An interruption after a change begins may leave the result uncertain. The app does not retry mutations automatically or promise to undo them. Locking, password tools and Android formatting are unavailable in this version.

Delete data

You can delete templates and history through the interface and discard a draft in the editor. Clearing Library filters does not delete templates or favorites. Local removal does not delete previously exported files, content on tags or copies retained in system backup. Manage those copies with the corresponding tools.

Support and changes

Owner: Kelven Severo. Support and privacy contact: learnflowbr@gmail.com. Support receives only what you send and uses it to answer and resolve your request. Do not send sensitive content, NFC passwords or tag identifiers.

Local data remains until you delete it in the app, discard the draft/form or remove the app, subject to system behavior. Support messages are retained while needed to handle your request or meet legal obligations. You can request deletion of those messages through the same email. You manage exported files, tags and system backups separately.

Changes to this policy will update its effective date. See the support page.

This website

These support and privacy pages are hosted by Cloudflare. This website does not include advertising, analytics or forms. The hosting infrastructure may process technical connection data, such as your IP address and request information, to deliver and protect the pages, under Cloudflare’s privacy policy. Visiting this website does not send your app templates, drafts or NFC content.

Optional diagnostics

Optional diagnostics use Firebase Crashlytics and Performance Monitoring for technical crash reports, app/device versions, installation identifiers and timing of selected operations. Custom logs contain only fixed action/error codes, never field values or NFC contents. Automatic network instrumentation is not added to the Android build and is disabled on iPhone. Diagnostics has its own opt-in in Settings and starts off. Turning it off stops new app diagnostics and requests deletion of unsent crash reports; it does not erase data already sent. Firebase services have their own retention periods. Declining either option does not limit the app.