Where Does TagWriter Store Profiles?
TagWriter writes datasets to NFC tags with saved profiles per tag type. Profiles stay local; tags carry the data physically.
Last updated
TagWriter programs NFC tags from local profiles only. Saved datasets with URIs, text, WiFi credentials, and vCards persist per install without accounts. Written tags carry data physically to any reader.
That makes tags the portable unit and profiles disposable. Exact behaviors may vary by version. Password-protect rewritable tags in public places; pranksters exist. Clone tags for spares quickly. NFC Tools imports datasets too. Password dictionaries fail hardened tags. Keep reader distance short.
Where TagWriter stores this, by platform
TagWriter app storage (private preferences)
Profiles per install with no account sync. Exact folder names may vary by version. Tags carry data physically.
Frequently asked questions
Do TagWriter profiles transfer phones?
No. Profiles stay per install without accounts by design. Recreate datasets on the new phone in minutes; tags themselves need no migration. Keep tag passwords documented separately.
How do I write an NFC tag?
Pick the dataset type matching the use case, fill the payload, and hold the tag steady until writing confirms. Lock tags against rewrites where permanence matters. Test reads on target phones immediately.
Notice an outdated path? Let us know.