Skip to main content

TendTag Privacy Policy

Effective date: August 5, 2026

TendTag is designed to work entirely on your Android device. The app processes care-card data on the device and stores its live database there; only you can explicitly create a local backup file. Lifestream Dynamics does not receive or collect that data, and the app does not transmit, sell, share, or use it for advertising or analytics.

For practical setup, tag, reminder, deletion, and troubleshooting instructions, see the TendTag User Guide.

Scope of this policy

This document is TendTag's privacy policy. It is published at https://lifestreamdynamics.com/tendtag/privacy, and that page is the published copy of this file rather than a summary of it.

Lifestream Dynamics' general website privacy policy does not govern the installed app. TendTag has no account, holds no Internet permission, and connects to no Lifestream Dynamics service, so the account records, web traffic, cookies, and analytics that policy describes have no counterpart in the app. It is also silent about what TendTag does keep: a local database on the device, an unencrypted backup file you export yourself, and an opaque identifier written to an NFC tag that anyone with an NFC-capable phone can read. Those are described below, and this document is the only policy that describes them.

TendTag's Google Play Data safety declaration reports no collection and no sharing, and this document is what supports that answer. A policy describing collection the app does not perform would contradict the declaration on its face and imply a data relationship that installing TendTag does not create. There is no such relationship to describe.

The general policy applies to one thing, and only outside the app: mail you choose to send to a support address. See Voluntary support communications.

What TendTag stores

TendTag stores the information you enter and the records needed to operate the app in a local SQLite database on your device. This can include:

  • Care-card names, rooms, icons, instructions or part notes.
  • Recurrence settings, reminder minute, and due dates.
  • Completion dates and times.
  • Random care-card identifiers and NFC tag-binding information.
  • Local app preferences and notification scheduling state.
  • Stable completion event identifiers and an immutable history of tendies earned and spent.
  • The optional Tender's nickname, hunger and happiness state, owned items, and equipped items.

This information remains on your device unless you explicitly export a local backup. An NFC sticker written by TendTag contains one opaque, versioned TendTag record with a random care-card identifier. It is not a web or app URI and does not contain the card's name, room, instructions, schedule, or completion history. Someone who scans the sticker may be able to see or copy that opaque identifier, but the linked care-card content is available only in the local TendTag database or a backup file you control.

What TendTag does not do

TendTag:

  • Does not connect to TendTag servers or any other internet service.
  • Does not require or offer an account.
  • Does not include analytics, advertising, tracking, telemetry, remote configuration, or third-party crash reporting.
  • Does not sync data between devices.
  • Does not provide cloud or operating-system backup, automatic restore or device migration (including device-to-device transfer), or a developer-operated recovery service.
  • Does not sell or share personal information.

The app is built without Android's Internet permission. TendTag is a paid download, so buying it is a transaction between you and Google Play rather than with the app: Google takes the payment, grants the entitlement at install, and keeps whatever purchase record its own terms describe. TendTag contains no billing or in-app purchase code, receives no payment details, and cannot read whether, when, or by whom it was bought; it behaves identically on every installation. Google Play may independently process purchase, download, refund, security, and diagnostic information under Google's own terms and privacy policy; that processing is performed by Google, not collected by TendTag through the app. Google’s privacy policy is available at https://policies.google.com/privacy.

Tendies are local points with no monetary value. They cannot be purchased, sold, transferred, or redeemed, and the Tender feature adds no billing or advertising service.

Permissions and device features

TendTag uses NFC to read and write compatible NDEF NFC stickers. Android treats NFC access as a device feature/normal permission; TendTag uses it only when you scan or write a tag for the app's care-card workflow.

On Android versions that require notification permission, TendTag asks contextually at the first reminder. If you allow it, TendTag schedules local reminders for all care cards from their stored due date and reminder minute. There is no per-card notification toggle. You can decline or disable notifications and continue to use the rest of the app. Exact-alarm and notification-policy access are optional and requested only from separate Help actions; denial keeps inexact/normal-channel behavior. TendTag does not request battery-optimization exemption, and Android may delay or suppress a notification.

TendTag may use Android system events needed to restore eligible local reminders after a device restart or relevant time change. This processing stays on your device.

Manual local backup and restore

On Android, you can start an export through the system document UI. TendTag passes Android a local-only provider hint and writes an archive containing schema-v3 data: all care cards, repeat and active-hours settings, their existing NFC identifiers and pairing state, completion history and event IDs, durable app settings, tendie transactions, the Tender nickname and its hunger and happiness state, owned items, and equipped items. Android controls which document destinations it offers. TendTag does not upload or send the file.

An exported backup is outside TendTag's private app storage. It is portable, human-readable and is not encrypted by TendTag. Anyone or any app with access to the file may be able to read card details, notes, history, and identifiers. You are responsible for choosing a safe location, controlling access, moving the file if desired, and deleting copies you no longer need. If a document provider fails during export, it may leave a newly created incomplete file that you should delete.

Import also uses Android's system document UI. TendTag validates the complete file, including its size, structure, schema version, values, and relationships, before showing an explicit confirmation that importing will replace all current TendTag data. Cancellation or any validation/database failure leaves the current database unchanged. A successful import atomically replaces it. Existing written NFC tags continue to work because their identifiers are preserved. Device-specific reminder scheduling markers are rebuilt after import; Android notification permission and channel state come from the device and cannot be restored by a file.

TendTag can also import valid schema-v1 and schema-v2 backups. Because v1 predates Tender data, TendTag assigns event IDs and awards one historical tendie for every completion retained in that file. Schema v2 restores its Tender snapshot and defaults active hours to off. Import always replaces the entire current snapshot, including the current wallet and Tender state; it never merges tendies or restores one card into the existing database.

Data retention and deletion

The live database remains in app-private storage until you delete data, clear the app's storage, or uninstall the app. Deleting a care card from TendTag removes that card and its visible completion history, but previously awarded tendies and later Tender purchases remain as immutable local transactions. The award keeps only its stable completion event identifier, not a copy of the care-card name, instructions, part note, or completion note. Card deletion does not delete the Tender profile, its needs, inventory, or equipment, and it does not search for or alter older exported copies.

Clean up history in Help & privacy removes completion records older than a window you choose, or all of them, without deleting the care cards themselves. The same rule applies: the tendies those records earned remain as immutable local transactions, keeping only the stable completion event identifier. Care cards, tag bindings, settings, your Tender, and every next due date are kept. TendTag never removes history on its own; this only happens when you ask.

Clearing app storage or uninstalling removes the complete working database, including the tendie ledger and Tender state, subject to normal device-storage behavior, but does not delete backup files you previously exported through Android's document UI. TendTag has no account, cloud backup, or developer recovery service, so Lifestream Dynamics cannot recover either the database or a backup file you lose. TendTag has no persisted Tender journal at launch. It does not copy care-card names or task notes into bundled or generated-image metadata.

Deleting or reinstalling the app does not erase NFC stickers already written. A sticker can retain its opaque TendTag record until it is overwritten by compatible NFC software or physically destroyed. If the matching local card is gone, TendTag cannot recover the card content from that record.

Security

TendTag minimizes data exposure by keeping care-card content off NFC stickers and by not transmitting app data. Your information still depends on the physical and software security of your Android device and access to your NFC stickers. No storage system can be described as risk-free; use your device's screen lock and current security updates where available.

Do not put secrets, credentials, or highly sensitive personal information in a care card or part note.

Children

TendTag is a general household utility and is not directed to children. Information entered in the app is processed only on the user's device and is not transmitted to Lifestream Dynamics, including when the app is used by a child.

Voluntary support communications

TendTag does not send app data when you ask for help. If you separately email support@lifestreamdynamics.com, Lifestream Dynamics and its email provider will receive the address, message, and attachments you choose to send. That communication occurs outside the TendTag app, as ordinary mail rather than anything the app does, and is used to answer the request and maintain necessary support records. Because it is ordinary mail and not part of the app, Lifestream Dynamics' general website privacy policy at https://lifestreamdynamics.com/privacy governs how that correspondence is handled. It governs the correspondence and nothing else: it does not govern the installed app, which has no account, sends nothing, and is described only by this document. Do not include care-card content or other sensitive information. You may ask for a support message to be deleted, subject to legal or security retention needs.

Changes to this policy

If TendTag's data practices change, the policy and Google Play Data safety disclosure must be updated before the changed behavior is released. A change that introduces data transmission would also require an explicit product decision and clear notice; it is outside the scope described by this policy.

Because TendTag does not contact a server, the installed app cannot retrieve a policy update remotely. The policy included with each app release applies to that release.

The page at https://lifestreamdynamics.com/tendtag/privacy is the published copy of this file, so it follows the most recent release rather than an older installed one. Each copy carries the effective date at the top, which is how you can tell which text you are reading: where the hosted page and the copy shipped with your release differ, the hosted page is the newer text and the shipped copy is the one that applies to the release you installed. Updating the hosted page changes nothing about an app already on a device, because nothing in the app fetches it.

Contact

Questions about this policy can be sent voluntarily to privacy@lifestreamdynamics.com. The app never sends anything to that address; it receives only mail you write yourself, handled as described under Voluntary support communications.