繁體中文

NFC42 Privacy Policy

Last updated: 19 October 2026 · Okle42

NFC42 reads and writes NFC tags on your iPhone. We designed it so that almost nothing leaves your phone.

What stays on your iPhone

Everything you read from or write to a tag, the history of those actions, templates, your language setting, and your inventory (when you’re not in a company) are stored only on your iPhone. Tag passwords you set or choose to remember are kept in this iPhone's Keychain (this device only, not synced to iCloud) so the app can unlock those tags for you; you can delete them under Write → Password Protection. We have no server that receives them. The app has no analytics. The free version shows ads — see the next section.

Ads (free version) and purchases

The free version of NFC42 shows no ads for the first 7 days after you first install it; after that it shows banner ads on every screen and, now and then after a successful write, one full-screen ad, served by Google AdMob. To show ads, Google's SDK may collect your device's IP address, device and app information and how you interact with ads. We never send AdMob what you read or write on tags, your history, or your inventory. The app does not ask for permission to track you across other companies' apps and websites. Where required (for example in the EEA and UK) a consent form is shown first, and you can change your choice later in Settings → Plans → Ad Privacy Options.

If you buy Remove Ads (a one-time purchase) or subscribe to Business (an auto-renewing monthly or yearly subscription you can cancel in your Apple Account settings), you see no ads and the ad SDK is not started. To start the 7 ad-free days, the app reads the date you first downloaded it from Apple's App Store receipt on your device; this date is not sent anywhere. Payment is handled entirely by Apple; we never receive your payment details.

What goes to the cloud: company only

If — and only if — you create or join a company, the following is stored in Google Firebase (Cloud Firestore, region asia-east1, Taiwan) so that the people you invite see the same stock:

NFC42 signs in with a Firebase anonymous identity. There is no account, no email address and no phone number. The only name stored is one you choose to type in as “Your Name” or as a borrower. The anonymous ID is stored in your iPhone's Keychain, with a copy in the app's own storage so that it survives an app update.

Anyone who joins with the invitation code can see and change that inventory, until the owner removes them. Only members can read it, and only the owner can delete items and records. Share the code only with people you trust. Don't put personal or sensitive information in names or notes. CSV export only creates a file on your phone; where it goes next is up to you. CSV import reads the file you pick on your phone and adds its rows to your inventory; the file itself is not uploaded.

App integrity

To protect company data from abuse, the app uses Apple App Attest and Firebase App Check to prove that requests come from the genuine NFC42 app. This uses a key generated on your device; it contains no personal information.

Chip verification (Okle42 NFC chips)

When an Okle42 NFC chip is scanned — in the app or on our verification web page — the chip's serial number and scan counter are checked on our server to detect copied chips. For each chip we store only its serial number, batch, status, latest counter, and how many times and when it was verified. We do not record who verified it, and no personal information is collected.

Problem reports (Settings → Report a Problem)

Only when you send a report, we receive: the report type, which feature it is about, your description, your email address if you choose to enter one, and — if "Attach diagnostics" is on — the app version, iOS version, device model, language, plan, and whether you’re in a company. It never includes tag contents or inventory data. Reports are linked to the app's anonymous account so you can see their status under "My Reports". We use them only to fix problems and plan updates, and the email address only to ask you about that report. Reports are kept until the issue is closed and for at most 2 years.

Staff scheduling and attendance (Business, optional)

If your employer uses NFC42 for scheduling and attendance, the following is stored in Google Firebase for that company: your name and role as entered by the employer; a one-way keyed hash and the last 4 characters of your staff badge's chip ID; your hire date (used to calculate annual leave); shift types, schedules, availability and requested days off; leave, overtime and shift-swap requests, decisions and leave balances; company announcements and whether you have read them (managers see who has not read an announcement); and each clock-in/out with the server time, how it was made (company tag, your own phone, a colleague's phone with your badge, or the company's clock-in device), which member's phone was used, and — when the employer has set a clock-in area — the precise location at that moment (taken once, never in the background). Only the employer and managers can see everyone's records; each employee sees their own. Under Taiwan's Labor Standards Act (Article 30) attendance records must be kept for five years, so they are kept for at least five years and are not deleted when a staff member is removed; they are deleted when the owner deletes the company. Working-hour warnings in reports are reminders, not legal advice. For access or correction, contact your employer first.

Business card pages (optional)

If you create a business card page, the details you enter (name, title, company, department, phone numbers, email, website, address, short bio, social links, photo and theme) are stored in Google Firebase and shown publicly at its link, so anyone with the link or the tag can see them. The page is not listed in search engines. We keep which anonymous app identity owns the card and when it was changed; the edit code is stored on your iPhone only (we keep a one-way hash). You can edit or delete the page in the app at any time; deleting removes it from our servers. Anyone can report a card page; reports (reason, optional contact, and a one-way hash of the reporter's IP address) are used only to handle abuse.

Event invitations and tickets (Business, optional)

An organizer can publish an event page (title, time, place, description, cover image, organizer contact) and write its link to NFC tags. Anyone with the tag or link can see the page. If you RSVP on an event page, we receive the name you type, the number of guests and an optional note; only the organizer can see them in the app. For ticket cards we also store the guest name the organizer entered, the tag's serial number (to stop copied links), and the check-in time. To limit abuse we store a one-way hash of your IP address with each RSVP. RSVP names, notes and guest names are deleted automatically 90 days after the event ends; the organizer can delete the event (and all its RSVPs and tickets) at any time. To remove your RSVP earlier, ask the organizer or email us the event link.

Voice tags (optional)

Only when you record a voice message under Write → Voice and tap Upload, we receive: the recording (up to 30 seconds, compressed audio), an optional title, its length, your app's anonymous ID, and a proof of purchase or of the App Store installation signed by Apple (used only to check your daily or trial allowance). Anyone with the tag or its link can play the recording on a public page, so do not record anything private. We keep a recording while your subscription is active and for 90 days after it ends; recordings made with the one-time "Remove Ads" purchase are kept until you delete them; the free trial recording is kept for 90 days. You can delete a recording at any time in the app (Write → Voice → My Voice Messages). Reported recordings are hidden until we review them, and recordings that break the content rules are deleted. We do not use recordings for any other purpose and do not share them.

Card messages and AI Guild (optional)

Card messages: people who both have an NFC42 business card can message each other in the app. We store the conversation (the two card IDs and anonymous app IDs, message text, time, read and hidden state, and blocks) so both phones can show it, plus this phone's push token to notify you. Messages stay until either side deletes their cloud data (Settings → Delete My Cloud Data removes the whole conversation for both sides). You can block a person, delete a conversation, or report a message or conversation; a report (reason, the reported text and the IDs involved) is reviewed by Okle42 within 24 hours.

AI usage level and AI Guild: if you turn on the AI level on your card and install the reporting script on your computer, the script sends only numbers: monthly AI token totals, counts by tool and file type (used for the “class” shown on the card) and a device code — never your prompts, files or file names. If you join your company's AI Guild, other members of that company can see your card name, level and the posts, screenshots and reactions you leave on the guild board. You can set a guild nickname yourself (up to 20 characters); members of the same company see it instead of your card name on the guild board, in @mentions, notifications, the weekly digest and the dashboard. A screenshot you attach to a post is stored with that post (JPEG, up to 400 KB) and is deleted together with it. The owner and managers can delete, pin or feature posts, and anyone can report or block a member; a reported post and its screenshot are hidden from the person who reported it. On a #Charity post, other members can tap “Endorse” (only the count is shown, not who endorsed). After three other members endorse it and the owner or a manager approves it, the author earns the “Charity” badge and the post's title (the first 30 characters of its first line) is shown publicly on the author's business card page; an approval cannot be withdrawn. Each week the app records the author and card of the most popular post, which counts toward the “Creative” badge. Your guild contribution counts — how many of your replies helped others and how many were chosen as the best answer — are shown on your public business card page; they are counts only and do not affect your AI level. Posts written in another language can be translated automatically; translation runs on your iPhone with Apple's built-in Translation feature, so the text is not sent to us or to any other translation service.

Room info pages and door locks (Business, optional)

A hotel or B&B can publish a room info page (property name, Wi-Fi, check-out time, breakfast, house rules, contact) for each room; anyone with the room's tag or link can see it. If the business connects TTLock door locks, we store the TTLock access token encrypted (AES-256-GCM; we never store the TTLock password) and each stay's room, lock, start and end time and an optional guest name, so the card or passcode can be issued and expire on time.

API & MCP (Business, optional)

A company can create API keys so its AI assistant or ERP can read and update the company's data. We store only a one-way hash of each key, its name, permission, creator and last-used time; the key itself is shown once on your iPhone. Requests made with a key can access only that company's data, and the owner can revoke a key at any time.

Medical cards and NFC tags

Data you write to a tag lives on the tag, not with us. Anything on a tag can be read by anyone with an NFC phone (a tag password only prevents others from changing it). Write only what you are comfortable sharing. A medical card is not a substitute for medical diagnosis. Medical card details are never uploaded: they are written only to the tag, and the app keeps your last entries on this phone so you don't have to retype them. One tag can hold your business card link, staff badge and medical card together; writing one keeps the others. When a tag holds both your business card and a medical card, the medical card text is also added after the “#” in the business card link, so someone without NFC42 (such as a paramedic) sees a red cross button for the emergency medical info at the bottom of your business card page with a single tap. Browsers never send the part after “#” to our servers, and the page removes it from the address bar once read, so reloading the page or opening the card link again later does not show it; it may still remain in the browsing history of the phone that tapped the tag.

Deleting your data

• Data on your iPhone: delete the app, or use Settings → Clear All History and delete items in Inventory.
• Shared inventory: the owner can delete items (which also deletes their records). Leaving a company stops syncing on your phone but does not delete the inventory from the cloud. The owner can delete the entire company in the app (Company → Delete Company), which removes its items, records, members and notification settings from the cloud; you can also email us the invitation code and we will delete it.
• Problem reports: email us the report number shown in the app and we will delete it.
• Voice tags: delete them in the app (Write → Voice → My Voice Messages, swipe to delete). They stop playing at once, and cached copies disappear within a day.
• Everything in the cloud at once: Settings → Delete My Cloud Data. This deletes, right away and permanently, the anonymous cloud account of this app and everything tied to it: your business card pages, voice tags, events (with their RSVPs and tickets), room info pages, card messages (each conversation is deleted for both people), your AI Guild posts (with their screenshots), nickname, reactions and endorsements, your entries in the weekly popular-post records, problem reports, push-notification registrations and daily-limit counters. You leave every company you are a member of; a company where you are the only member is deleted entirely (items, records, staff and attendance data, dashboard and guild links, smart-lock connection and stays). If you own a company that still has other members, the app asks you to remove them or delete the company first. Afterwards the app is signed out of the cloud; using a cloud feature again creates a new, unrelated account.

What is kept after Delete My Cloud Data: records you made in a company you were a member of (stock movements, check-ins, attendance, stays, ticket check-ins, including the name shown on them) belong to that company and stay with it — attendance records must be kept for five years under Taiwan's Labor Standards Act (Article 30); the owner can delete them by deleting the company. To stop abuse we also keep the daily allowance counter for voice recordings, which is tied to your Apple purchase or App Store installation (not to your account), and a content-rule ban list if your account was banned. Reports that other people sent about your content (the reason and a copy of the reported post or message) are kept for abuse handling; reports you sent about others are kept without your identity. Apple subscriptions are not cancelled; cancel them in your Apple account. Content already written to NFC tags, and data stored only on your iPhone, are not affected — tags that link to deleted cloud pages will simply stop opening.

Sharing

We do not sell or share data. Google Firebase acts as our infrastructure provider and processes the data described above on our behalf. Apple delivers push notifications and App Attest. Okle42 staff can technically access the data stored in the cloud (companies, business card pages, problem reports). We only look at it when needed to answer a support request you sent, to handle a report of abuse, to keep the service secure, or when required by law, and only as much as needed. Data that stays on your iPhone, tag passwords, card edit codes, API keys and payment details are not available to us.

Children

NFC42 is a general utility app and does not knowingly collect personal information from children.

Contact

okle42.ai@gmail.com