SuguMemo

SuguMemo Privacy Policy

Operator and scope

This policy applies to SuguMemo, an iOS app with Bundle ID com.k7m42.sugumemo, provided by NANAE MIURA. Its effective date is November 4, 2026. For privacy inquiries, contact k7m42.support@proton.me.

Data in the app

Memo titles and text, categories, checklist items, pin and completion state, creation/update/deletion state, and reminder dates are stored on the device using SwiftData. SuguMemo does not implement its own accounts, cloud synchronization, or automatic iCloud Drive storage. Depending on device settings and Apple's behavior, iOS iCloud Backup may include data from downloaded apps. Apple and device settings control whether backups are made and how long they are retained; the app does not control this system service (Apple's explanation).

When permission is granted, reminders are scheduled as local notifications on the device. Their body uses fixed text and does not contain memo text. Deleted memos move to Trash. Memos deleted at least 30 days earlier are permanently purged by maintenance when the app starts. You can also permanently delete individual or all trashed memos immediately.

JSON backup export and import are initiated by you. A backup contains memo, category, and related data. Its destination and subsequent handling depend on the location you choose and iOS. The app does not automatically send backup files.

When you open “More Apps” in Settings, the app retrieves a public app catalog over HTTPS from a static catalog host. This request does not include memos, feedback, account data, device identifiers, or usage history. The hosting provider may process connection metadata under its terms and operations; the app does not configure or guarantee its logs or retention period.

Feedback

If you provide consent, choose a category, enter a message, and submit feedback, the app sends the following to the feedback service over HTTPS:

The submitted request payload does not contain memo titles, text, or categories assigned to memos; checklists; reminders; backups; your name, email address, or account ID; device model; locale; or app logs. The category selected on the feedback screen is sent. The form does not ask for your name, email address, or an account. This does not mean that network services or platforms process no connection metadata.

Feedback is used as input for planning, developing, improving, providing, and operating the app and service. App, OS, and build information is also used to investigate technical issues, as well as to plan feature improvements and new features. The service contract documented in the repository stores the submitted content and the app ID/name, app version/build, OS version, category, terms version and consent timestamp, status, reply/reward information, and creation/update timestamps in a database. It stores a SHA-256 hash of the access token, not the token itself. The application has no automatic expiry or user-facing server deletion feature. The existing administrator runbook provides a manual deletion procedure that matches the inquiry number and app identifier before deleting one D1 row. When handling a deletion request, the operator temporarily matches the sender's inquiry number to the corresponding row; no continuing mapping between the sender's email address and the D1 row is retained. There is no control to delete local feedback history. Removing history or a token from the device does not delete the server record.

UserDefaults stores on-device feedback history: feedback ID, category, message, submission time, status, reply/reward information, and update time. A per-submission access token used to check replies is stored in Keychain. Checking a reply sends the relevant submission ID, access token, and app ID to the service. Keychain item handling after uninstall has not been verified, so uninstalling should not be assumed to remove those items.

The API runs on Cloudflare Workers, and feedback records are stored in Cloudflare D1. For rate limiting, the Worker hashes CF-Connecting-IP with SHA-256 and passes the result to Cloudflare Rate Limiting. The Worker application code does not write the raw IP address or its hash to D1 or application logs. Cloudflare receives connection metadata. Any platform-side information, logs, retention, and deletion are subject to Cloudflare's terms and operations; this app does not configure or guarantee those periods or details. See Cloudflare's Privacy Policy for more information.

Submitted feedback is not treated as confidential. No reply, adoption, implementation, or reward is promised. Do not include personal or confidential information. The feedback terms displayed before submission govern the use of submitted content.

Analytics, advertising, and tracking

Feedback text and category are also used for analytics, specifically feature improvement and planning new features. No dedicated analytics SDK, advertising SDK, or advertising-tracking feature was found in the inspected source. Account-wide Cloudflare logging settings could not be confirmed. This is not a complete audit of all dependencies and the distributed binary.

Privacy inquiries

Contact: k7m42.support@proton.me

Feedback records do not automatically expire in the application. To request deletion, copy the relevant “Inquiry number” from Submission History / Thanks and email the contact above. The operator verifies the number together with the app identifier and manually deletes only the matching SuguMemo row from Cloudflare D1. The message, reply/reward fields, and reply-check token hash are stored on that same row and are deleted with it. Cloudflare D1 recovery features may allow records to be restored from an earlier database state after deletion. Whether such a feature is enabled for SuguMemo, its retention period, and the post-deletion recoverability window have not been confirmed. Reply checks for the deleted record will no longer work. Cloudflare may separately process connection or operational logs to run its services; SuguMemo does not set or guarantee their retention or deletion period, which is subject to Cloudflare's terms and operations. To remove memo data from the device, use the app's deletion controls. Deleting on-device feedback history and deleting a server record are separate operations.