Privacy Policy - Iomlaid

1) Who we are

Iomlaid is provided by Saifullah Ahad ("we", "us", "our"). Iomlaid coordinates assigned multi-member exchanges of physical books and records each handoff.

2) Information Iomlaid handles

• Account and profile: an anonymous Firebase user ID, display name, country, broad postal zone, languages, maximum transit time, contribution mode, and adult confirmation.
• Shelf and reading needs: titles, authors, editions, ISBNs, languages, condition, subjects, syllabus keys, and the books or kinds of books you want to read.
• User-selected images: cover, title-page, or condition images you choose to capture. OCR and barcode recognition run on the device; selected condition media may be uploaded to private cloud storage for relay verification.
• Relay and custody: assigned member, copy, match, and leg identifiers; status and deadline data; tracking reference if supplied; signed dispatch and receipt events; public signing key; event hashes; signatures; and timestamps.
• Safety: reports, blocks, appeals, moderation status, and the target identifiers and explanation you submit.
• Notifications and diagnostics: Firebase notification token, synchronization state, and server security or delivery audit records needed to operate the service and investigate abuse.
• Postal address: recipient name, address lines, postal code, and country only when a recipient explicitly reveals an address for an open assigned postal leg.

Iomlaid does not collect contacts, microphone audio, precise location, payment information, advertising identifiers, or an analytics profile. It has no advertising SDK.

3) How information is used

We use the information above to authenticate the app, resolve book identities, find feasible directed cycles and donor-started chains, assign sending and receiving legs, synchronize offline changes, deliver notifications, verify signed custody, handle reports and blocks, prevent fraud, and support account deletion.

4) Sharing and assigned-address disclosure

Iomlaid has no public catalogue, seller profile, bargaining chat, or public member feed. Assigned copy and custody details are available only to members involved in that relay.

A postal address is disclosed only to the one authenticated sender assigned to post that copy, only while that leg is open. The address document is physically deleted when the parcel is marked dispatched, received, or as a problem. Do not place unrelated personal information in book, want, report, or tracking fields.

We use Google Firebase for anonymous authentication and notifications, and Google Cloud Run, Firestore, and Cloud Storage for the service. These providers process data for us under their service and security terms. We may disclose information when legally required or necessary to protect a person from harm. We do not sell personal data or share it with advertisers or data brokers.

5) Offline QR and NFC custody proof

Two assigned devices can exchange a signed custody event by QR or NFC without a network connection. The receiving device validates the event hash, P-256 signature, copy, assignment, role, and previous event before accepting it locally. When connectivity returns, authored events synchronize to the service. Conflicting same-parent events remain visible as evidence and create a dispute; they are not silently overwritten.

6) Android permissions

• Camera: optional cover/title-page capture and QR scanning.
• NFC: optional nearby custody-proof exchange.
• Notifications: optional relay assignment, deadline, and synchronization notices.
• Biometric or fingerprint: optional unlock for the independent app lock. Biometric templates stay with Android and are never available to Iomlaid.
• Internet and network state: authenticated synchronization and deferred-work scheduling.
• Wake lock, foreground service, boot completed, and FCM receive: reliable WorkManager and notification delivery.

7) Retention and deletion

Profile, shelf, want, token, and active relay records remain while needed to provide the account. Postal addresses follow the shorter purpose-bound deletion described above. Signed custody records, disputes, and safety audit records may be retained longer to preserve chain integrity, investigate abuse, resolve delivery disputes, and comply with law. When an account is deleted, retained safety records replace the user ID with a one-way deleted-member reference where appropriate.

Use Settings → Delete account to remove the Firebase identity and active account data. You may also contact us for a privacy request. Clearing app storage or uninstalling removes the local cache and independent app-lock settings but does not by itself delete the cloud account.

8) Security and international processing

Traffic is encrypted in transit. The service requires Firebase authentication, uses private cloud storage, validates assignment scope, and verifies custody signatures independently. Signing keys are created in Android Keystore and the private key does not leave the device. No method can guarantee absolute security.

Cloud providers may process information outside your country, including in the United States. Applicable provider safeguards and local law govern that processing.

9) Adults and child safety

Iomlaid is intended only for adults aged 18 and over and is not directed to children. Iomlaid prohibits child sexual abuse and exploitation. Read the separate Iomlaid Child Safety Standards for prohibited conduct, in-app safeguards, enforcement, and reporting routes.

10) Changes and contact

We may update this policy when Iomlaid's features, providers, or legal duties change. The current version and effective date will remain at https://privacy.saifullah.ai/iomlaid.html.

For a privacy question or request, contact [email protected].