FOLDLOG / PRIVACY POLICY

Privacy Policy

How local records, voluntary sharing, and website visits are handled.

This page is a reference translation of the Simplified Chinese original. Chinese original

On this page

FoldLog respects your privacy. Movement records and daily goals are processed and stored on your device. The app does not automatically send these records to the developer. You can view, export, or clear your records.

01 Scope and contact

This policy covers the FoldLog iOS app, its widgets, and the support website. “We” means the individual developer of FoldLog. For questions about this policy, data processing, or your rights, contact chenwxiong@gmail.com.

Local app data, support emails you choose to send, and website visits are handled separately as described below.

02 Data processed locally

The following data supports movement records, personal goals, history, and widgets. It is stored on your device by default.

CategoryDataPurpose
Movement events and historyFold and opening events, internal compatibility records, timestamps, random event identifiers, archive creation date, and statistics time zoneDaily, lifetime, and historical totals grouped by statistics day
Daily goalsLimits for fold and opening goals and internal compatibility goals, enabled status, effective dates, and random goal identifiersGoals, remaining allowance, and effective-date rules
PreferencesAppearance settingsRemember your display choices
Compatibility and live stateModel identifier, system version, device category, system-provided hinge state, and a monotonic clock for short intervalsCheck compatibility locally, detect changes, and perform internal timing
Widget summaryStatistics date and time zone, folds and openings today, total saved folds, fold goal, update time and recording statusShow goal progress, today’s counts and fold totals on the same device
Shortcuts and local setupEvent source; close/open action, receipt time, result, random receipt ID and linked event ID; deduplication boundary, onboarding completion and pending return pageSave automated counts locally, process local receipt logs, avoid duplicate counts for the same opening or closing and resume setup

Random event and goal identifiers distinguish local entries. They are not advertising identifiers and do not identify or track your real identity. A model identifier describes a device model, not its serial number.

Live hinge state and timing data are used during observation and calculation. The app does not save raw hinge-angle sequences or raw monotonic-clock values in exported archives.

Only for iPhone Duo with iOS 27.1 or later. After setting up both presets and their run options, Shortcuts can deliver closing and opening events while the app is in the background. Fold and opening counts reflect events actually received and saved; an opening event does not confirm full unfolding. The app may also record valid hinge transitions it receives. System scheduling, permissions, interruptions, delayed actions or missing events may cause gaps or mismatches. Complete all-day coverage is not guaranteed, and missing events are not reconstructed.

Shortcuts actions use the same local archive as the app and send no data to a developer server. The receipt log retains up to 256 entries; older receipts are removed without deleting saved count events. Actions may also be run manually or through Siri. JSON exports may include event sources, receipts, deduplication and setup state. Clearing records also clears receipts and deduplication state, while keeping appearance and shortcut-onboarding preferences. It does not disable system automations.

The app supports iOS 27.1 or later. Duo open/close automations require the matching system trigger, which Apple lists as new in iOS 27.2. If your older system lacks it, update to iOS 27.2 or later. Without it, counting relies on valid posture input the app actually receives; these automations cannot provide ongoing background or non-running-app recording.

03 Storage and use

Record archives are kept in the app’s local storage. Preferences use the system’s app settings storage.

Widgets read a summary through system-managed shared storage on the same device. They do not request records from a developer server or independently collect movements. The summary is not the full event history.

People who can see your screen may see Home Screen or Lock Screen widgets. You can remove them in system widget settings or adjust the Lock Screen options the system provides.

The app currently has no developer-operated account system, cloud synchronization, advertising, or third-party analytics SDK. We do not automatically receive your local records, perform cross-app or cross-site advertising tracking, or sell your personal information.

04 Permissions and platform services

The app does not request your location, contacts, photos, camera, or microphone. Hinge state, compatibility checks, and widgets use system capabilities.

When downloading, updating, or using TestFlight, Apple may process purchase, distribution, crash-diagnostic, or testing information according to your settings and its policies. Feedback you submit through those services, and diagnostic or aggregate information Apple makes available to developers, may be used to resolve problems and maintain the app. The scope depends on Apple’s services, settings, and policies; it does not mean the app includes a third-party analytics SDK.

See Apple’s Privacy Policy.

Both signed presets are bundled local files; no iCloud sharing link is required. You confirm import, automatic execution and locked-device execution in system Shortcuts. FoldLog cannot change or read the system automation switches. You can disable or delete them in Shortcuts; Apple’s rules govern that system processing.

05 Export and sharing

The interface and JSON export include only fold and opening records and goals. Internal compatibility records and goals are not displayed or exported. Existing records are retained when hidden. You can export JSON records under Settings → Data. An export may include event types and times, random entry identifiers, goals and effective dates, the archive creation date, and its statistics time zone.

You initiate an export and choose its location, app, or recipient through the system share interface. A cloud drive, email provider, or other service you choose handles that file under its own rules. Check its contents and recipients before sharing.

The current version cannot import JSON to restore app data. Exports support keeping or examining a copy; restoration is not guaranteed. Clearing app records does not recall copies already shared.

06 Retention, clearing, and system backups

Local records remain on your device until you clear them, remove the relevant app data, or they are lost through app deletion, device failure, or another cause. History filters of 7 or 30 days do not automatically delete older records.

  • Confirming Clear under Settings → Data resets counts, history, and goals within the scope shown in the confirmation and updates the widget summary. The app cannot undo this action.
  • Clearing records does not reset all preferences, such as appearance, or remove exported or shared copies.
  • Removing a widget removes its display entry, not the app’s records.
  • Deleting the app generally removes its local data. Offloading may retain documents and data. Shared containers and restored backups can be handled differently; follow the system’s actual descriptions.

Whether local files enter iCloud device backups, computer backups, or device transfers depends on system behavior and your settings. The absence of developer-operated cloud sync does not guarantee exclusion from system backups you enable. Manage backups and exported copies in their respective locations.

We have no remote copy of your local archive and cannot remotely access, delete, or restore it for you.

07 Contacting support

If you email chenwxiong@gmail.com, we receive your email address, message, and any screenshots, diagnostic details, or files you voluntarily attach. We use these to respond, investigate issues, handle rights requests, and keep necessary correspondence, not for advertising profiles.

Start with the app version, system version, device model, and steps to reproduce the issue. Conceal unrelated personal information. You do not need to submit your full movement archive, passwords, or other sensitive material. The in-app contact entry does not automatically attach your archive.

Gmail and other mail services participate in transmission and storage; processing may involve other countries or regions. We retain support information only as needed to handle requests, keep necessary correspondence, and meet legal obligations, then delete or anonymize it. You may request deletion at the same address. Mail providers also follow their own policies; see Google’s Privacy Policy.

08 Website access and external links

The public website is prepared for GitHub Pages hosting. When you visit a page deployed there, GitHub may process IP addresses and access logs for security and service operation, including in countries or regions where it provides services. See the GitHub Privacy Statement.

The pages contain no ads, analytics scripts, third-party fonts, or social tracking components. They do not intentionally set advertising or analytics cookies or read your device’s local FoldLog records. They offer no archive-upload interface.

External sites and email providers apply their own rules when you follow their links. Visiting support pages does not transmit the app’s movement archive to the host. Reading the bundled policy in the app works offline.

09 Choices and rights

You can view records, change or disable goals, export files, clear records, stop using the app, or remove it through the system. There is no account to close.

Where applicable law grants rights to access, correction, deletion, restriction, withdrawal of consent, or complaints, contact us about information we actually hold. We verify requests only as necessary and handle them under applicable law; you do not need to send a full local archive. Use local controls for data held only on your device.

10 Minors

The app supports personal device habits. It is not designed specifically for children and does not request an age or birth date. Minors should use it with guardian guidance and obtain consent where local law requires it.

Contact us if you believe support correspondence contains information about a minor that we should not hold, so we can investigate and address it.

11 Security and updates

We rely on iOS storage isolation and system security for local files and take reasonable steps to protect support information we receive. Protect your device access, system account, and exported files. No storage or transmission method is absolutely secure.

Updates to this policy will show a new version and date. If future account, synchronization, analytics, paid, or other features change data processing, we will update the policy and provide additional notice or obtain consent where the law requires it.