NFCare — Privacy Policy

Effective date: October 19, 2026

This application (“NFCare”, the “app”) is developed and published by Yusuf Tunc. This policy explains what data the app and its companion service process, why, and with whom. For questions or deletion requests, contact yusuf.tnc@gmail.com.

Summary. NFCare is a workplace tool for care-home staff. It is not a consumer social app, not a medical device, and does not diagnose or treat anyone. There are no ads and no advertising or analytics tracking SDKs. Staff sign in with an account created by their organization. The care-home organization is the controller of resident records; the developer hosts the service and processes that data only to run the product the organization subscribed to.

1. How the app works

Care-home administrators create staff accounts on the NFCare service (web panel). Staff then sign in to the mobile app with their work email and password. They record scheduled room, resident, cleaning, care, and medication checks by scanning NFC tags, see their assigned tasks, and receive alerts when a check is missed. The public cannot create an account in the app.

2. Data we process and why

Staff (app users)

Data	Content	Purpose
Account	Name, work email, optional phone number, role/permissions, organization and branch	Sign-in, authorization, and showing the right workplace
Credentials	Password (stored only as a hash on the server). Session tokens on the device in iOS Keychain / Android Keystore	Authentication
Remembered email	Work email, only if “Remember me” is enabled — stored on the device only	Faster sign-in after sign-out. The password is never remembered
Device token	Firebase Cloud Messaging token for this phone	To deliver missed-check / on-call push notifications
Scan / task records	Which staff member scanned which NFC tag, when, and the resulting task status (done / missed)	To prove that a scheduled check was performed
On-call acknowledgements	Whether the staff member opened and acknowledged an alert call	Escalation and shift handover
Preferences	Theme and language	App appearance — stored on the device

Residents and workplace records (entered by the organization)

Administrators enter these records in the web panel. Staff see and scan them in the app only as needed for their assigned work. This can include:

Data	Content	Purpose
Resident	Name, optional date of birth, optional notes, room	To identify who a check belongs to
Medication / clothing items	Item name, optional dose, linked NFC tag	To record that a specific medication or item check was done
Rooms, branches, NFC tags	Names, addresses, tag UIDs	To map a scan to the correct place or person
On-call phone numbers	Staff phone numbers on the branch duty list, plus a branch fallback number	To call the on-duty person when a check is missed

Resident name, date of birth, notes, and medication information can be health-related. It is processed only to operate the care home’s scheduled checks. It is not used for advertising, profiling, or sale.

3. Data that stays only on the device

Session tokens — iOS Keychain / Android Keystore.
Remembered work email, if enabled.
Theme and language.
A local offline queue of scans that have not yet reached the server (deleted after they are sent, or when the app is uninstalled).

4. Who data is shared with

Data is not sold. As part of running the service it reaches these parties:

Party	Data received	Reason
The care-home organization that created the account	Staff activity, scan results, and the resident/workplace records they entered	They operate the workplace; they are the controller of that data
Yusuf Tunc (service host)	The records stored on the NFCare backend	To operate, secure, and support the service
Google Firebase Cloud Messaging	Device token, and technical data such as IP address on Google’s side	To deliver push notifications. No advertising or Analytics SDK is included
Telephony / IVR provider (Telsam)	The on-duty phone number and a short announcement that may include a resident or room name	To place the missed-check voice call

5. Permissions the app asks for

NFC — to read workplace tags. Required for recording a check.
Notifications — to show missed-check alerts. The app remains usable if this is declined; the organization’s voice-call escalation does not depend on push.

The app does not access the camera, photos, contacts, precise location, microphone, or HealthKit / Google Fit.

6. Retention and deletion

Uninstalling the app deletes on-device tokens, the offline queue, and remembered email.
Signing out removes the session and unregisters the device token so this phone stops receiving push.
Staff accounts are created and deactivated by the organization. A staff member who wants their account removed should ask their administrator, or email yusuf.tnc@gmail.com.
The organization can deactivate or delete its tenant records (soft-delete, then permanent removal on request).
Deletion requests sent to the contact email are handled within a reasonable time.

7. Children’s privacy

The app is for adult staff. It is not directed to children. A care home may keep records about residents who are minors; those records are entered and controlled by the organization, not collected from a child in the app.

8. Changes

This policy may be updated from time to time. The effective date on this page is updated when that happens. Please review the current version periodically.

9. Contact

Developer / publisher: Yusuf Tunc
Email: yusuf.tnc@gmail.com