Numgigo

Privacy policy

Numgigo’s privacy policy for documents, reading records, customer support, and advertising.

Effective date: November 10, 2026.

1. Scope and contact

Numgigo is operated by WeeKL. WeeKL Customer Support handles privacy inquiries at weekl.support@gmail.com. This policy covers Numgigo and this support website, separately from the WeeKL letter app. Support is optional; reading does not require sign-in.

2. Documents and reading records (iPhone · iPad · Mac)

Imported documents, reading records, and preferences are stored on your device to display your library and resume reading. If you enable iCloud sync, originals and reading records needed for synchronization are transferred through Apple iCloud. Backups you export may include originals, library information, and selected background images. Deleting data in the app does not delete backup files you previously exported.

3. PDF text recognition (iPhone · iPad · Mac)

PDF text recognition uses Apple Vision on the device. Recognized text is stored separately in the app’s storage for search; it does not overwrite the original PDF. You can remove it using the search-text deletion feature.

4. Camera and text-to-speech (iPhone · iPad · Mac)

Head-gesture page turning uses camera permission to analyze face direction and movement. In the release app, this feature does not save video or face analysis results to files or upload them to support or advertising servers. Continuity Camera on Mac transfers video between iPhone and Mac using Apple’s functionality. Text-to-speech passes document text to Apple’s speech synthesis; it does not record your microphone or send the text to a separate external speech-generation server. Camera permission can be managed in your device settings.

5. Purchases (iPhone · iPad · Mac)

Payments and restoration of Pro lifetime purchases are handled through Apple App Store and StoreKit. The app uses verified purchase information to determine Pro access; it does not directly ask for Apple account passwords or card details.

6. Support inquiries (iPhone · iPad · Mac)

For support, the server verifies Apple's sign-in token and a one-time verification value. The token, original Apple account identifier, name, and email are not stored in the database. We store a derived account identifier to associate inquiries with their owner, subject, message, app language, retry identifier, receipt time, handling status, and support reply. Access and deletion require the verified account, not an entered email address. Book files and reading records are not attached automatically. Account identifiers, values derived from connection IP, and request counts are also used to prevent abuse; derived values are not necessarily anonymous. App drafts and sign-in tokens are handled in memory only.

7. Retention and deletion

Inquiries and support replies expire 30 days after the original submission. Expired content is excluded from user queries and processed for server deletion hourly; outages or backlogs may delay physical deletion. Account/IP abuse-prevention records remain for two days from initial creation and are not reset by inquiry deletion or sign-in. You can delete one or all of your inquiries in the app. No separate support membership profile is created. This does not delete your Apple account, iCloud library, or purchases. Support audit events contain administrator and inquiry identifiers and timestamps, not message bodies or sign-in tokens. Operational logs are separate: general log buckets currently retain logs for 30 days and required audit log buckets for 400 days. Inquiries and replies sent directly by email are also handled on a 30-day retention basis from initial receipt. The email provider’s trash and backup systems may have separate deletion cycles.

8. Providers and storage location

We use Google Firebase and Google Cloud for support servers, databases, operational logs, and web hosting. The inquiry Firestore database is in Seoul, South Korea (asia-northeast3); logs use the global location, so processing is not confined to Korea. Apple provides Apple sign-in, iCloud sync, and App Store payments. Google provides advertising and Gmail for email sent directly to us. Cloudflare manages DNS for weekl.app. Related information may be processed on providers’ systems abroad. See the provider policies below for processing scope and safeguards. We do not use support messages for advertising or sell them. We share personal data with these providers only as needed for the features described in this policy. Providers that receive user data from Numgigo protect it to the same or an equal standard as described in this policy, under their own privacy policies and data protection terms, which include security and confidentiality safeguards.

9. Advertising and privacy choices (iPhone · iPad · Mac)

The free iPhone/iPad experience includes Google Mobile Ads functionality. The SDK may process IP-based approximate location, device identifiers, advertising and usage information, and diagnostics for advertising, measurement, and operation. Processing depends on consent and settings. Where the app provides a privacy-options entry, you can manage your choices there. The macOS app does not include this Google advertising SDK.

10. This webpage

These pages contain no sign-in, advertising, analytics, inquiry forms, or third-party scripts. Visiting does not submit an inquiry. Firebase Hosting processes connection information such as IP for security and operation; its official notice states that IP data is retained for a few months. This is separate from the inquiry database’s 30-day retention. Clicking the email link opens your chosen email service; email you send contains your sender address and the content you write.

11. Your rights and choices (Shared rights · Apple settings)

You or your authorized representative may request access, correction, deletion, or restriction of processing at weekl.support@gmail.com. We verify ownership using the minimum necessary information and do not ask for passwords or verification codes. Delete one or all inquiries in the app; stopping optional features does not prevent basic reading. You can also manage Apple/Google processing and permissions through their services and device settings. To withdraw consent or stop processing: where advertising consent is required, change it at any time in Numgigo under Settings > General > Ad Privacy > Manage Ad Privacy Choices. To stop iCloud sync, turn off Settings > Library and Data > iCloud Library Sync > Sync on This Device. To stop camera use, turn off Chin and Head Page Turning in Reading Settings, or turn off camera access in the device Settings app. To remove support data, delete inquiries in Settings > Contact Support, or choose Delete inquiries and disconnect Apple. Withdrawing consent does not affect processing that took place before the withdrawal.

12. Protection and policy changes

We use HTTPS for inquiries and restrict access to the authenticated owner and authorized administrators. Replies cannot recreate a deleted inquiry; sign-in tokens and message bodies are not written to operational logs. Expired server records are deleted periodically without creating unnecessary new copies. No system can guarantee perfect security. When processing changes, we update this page and its effective date; important changes are announced in the app or on the website.

Google authentication for Android support

Android support uses Google to verify your identity. The server verifies Google's ID token and a request verification value. Names, email addresses, profile photos, tokens and original account identifiers are not stored in the inquiry database. A derived, Google-specific identifier, inquiry content, replies, processing information and abuse-prevention records are handled for the purposes described above. Google processes sign-in information under its own policies. Support does not request access to Drive files.

Android documents and external clouds

Book originals, reading positions, notes and markings, library information and settings are stored on the device. Enabling external-cloud sync transfers the originals and reading information needed for sync to the Google Drive, Microsoft OneDrive or Dropbox account you choose. Each provider processes data under its policies; processing is not confined to Korea. Account identifiers and display names, the email address for a Google connection, and required authentication information are used to identify and maintain the connection and are encrypted on the device. Manage connections in Settings under Library and Data. Disconnecting does not erase existing cloud files or exported backups. Deleting support data does not delete these files either. Disconnecting Google Drive on Android also requests revocation of the Google access granted to this app. It does not delete your Google account or files already stored.

Android PDF recognition, camera and speech

Android uses Google ML Kit on the device for PDF recognition, head-gesture face analysis and speech-language detection. ML Kit does not send inputs or results to Google servers, but may send performance and usage metrics. Recognized PDF search text is stored separately and can be deleted in the app. Head gestures require camera permission; the app does not save video or face-analysis results to files. Reading aloud passes text to an offline device speech engine without recording the microphone. Manage camera permission and speech data in Android settings.

Android Google Play, advertising and choices

Google Play handles Pro payments and restoration; the app checks purchase status for access without directly receiving Google passwords or card details. The free Android app includes Google Mobile Ads and consent controls. The ad SDK may process IP-based approximate location, device/account identifiers, usage, advertising and diagnostic information, depending on consent and settings. Manage choices under Settings → General → Advertising and privacy → Ad privacy options. Delete inquiries or sign out under Settings → Contact Support.

External-cloud processing in Apple version 1.1

When external-cloud sync is enabled in Apple version 1.1, the app transfers book originals, reading positions, notes and markings, library organization and order, deletion records and other sync information to the Google Drive, Microsoft OneDrive or Dropbox account you choose. Account identifiers and display names are stored on the device; authentication credentials are kept in the device-only Keychain and do not sync to other devices. Providers process data under their own policies, and processing is not confined to Korea. Disconnecting removes this device’s connection and stored credentials; it does not delete the provider account, local books, remote files or exported backups. Deleting support data is separate. See the earlier paragraphs for Apple version 1.0 iCloud and reading-data handling.

Turning pages with a remote in Apple version 1.1 and Android

Turning pages with a remote connects devices on the same Wi-Fi directly over an encrypted link, without passing through WeeKL servers. Only previous and next page commands and their results, current and total page numbers, whether pages can be turned, connection checks, temporary session identifiers and reconnection key-exchange values, and a fixed remote name set by the app (not your device name) travel between devices. Book text, titles and files are not sent. For pairing and reconnection, the reading device announces a random service name starting with “Numgigo-” that is visible on the same network. Apple devices use Local Network permission for this connection. QR scanning on iPhone, iPad and Android uses camera permission and is processed on the device; video and photos are not saved or transmitted. Even with Chin and Head Page Turning turned off, the QR scanning screen uses the camera. You can instead copy and paste the connection info, which places it on the device clipboard. It can no longer be used after 5 minutes, but it is not automatically removed from the clipboard. The app handles connection info and reconnection keys in memory only and does not save them to files or backups. Automatic reconnection after a drop is possible only within 15 minutes, and ending the connection erases the key. Manage camera and Local Network permissions in device settings.

Linked Folders in Apple version 1.1 and Android

Linked Folders (Pro) imports TXT, EPUB and PDF files from a folder you choose into your library. The app stores on the device the access information needed to reopen the folder (a folder bookmark on Apple devices; on Android, the folder address and read permission granted by the system), the folder name, file locations, change-check values such as SHA-256, and linked book identifiers. The folder is read only when you link it and when you ask to check it again; the app does not monitor it continuously. New and changed files are copied into the app’s storage, and originals are not modified or deleted. The app does not send folder information or files externally during this check. Imported books are treated like any other book, however, so if iCloud on Apple devices or external-cloud sync is on, they are transferred as described in those paragraphs. Unlinking removes the folder from the list and stops checks, and Android also gives back the granted read permission. Books already imported and the folder’s originals remain.

Sync after closing the app in Apple version 1.1, and Android

If a Pro user has connected an external-cloud account and has not stopped sync, iPhone and iPad continue external-cloud sync after the app is closed when iOS allows. The operating system decides when it runs, and Mac does not work this way. The information exchanged and its destination are the same as in the external-cloud paragraphs above; this sync does not send books or reading information to any other server. It waits when there is no network, in low-power mode, or when the device is overheating. In this automatic sync run by the operating system, book originals move only on Wi-Fi without data limits; on cellular or data-saving connections, only reading information such as positions may move. Long tasks may wait until the device is charging. On iPhone and iPad, sync that began while you were using the app, or that you started yourself, may continue after you leave the app while the operating system allows, and in that case book originals may also move over cellular. Stopping all sync in the app or disconnecting the last account cancels scheduled runs. On iPhone and iPad, turning off Background App Refresh in device settings also prevents it. On iPhone and iPad with iCloud sync on, the “Background file sync” setting (on by default) also lets iCloud sync run when iOS allows. The Android app currently does not run automatic sync scheduled by the operating system after the app is closed; it syncs automatically or when you start it only while the app is open. If this feature is turned back on, this policy will be updated first.

Google Firebase · Apple · Google · Cloudflare · Google ML Kit · Google Mobile Ads · Android · Microsoft · Dropbox