Applies to: iOS App Store edition / Mac App Store edition / official BitFile website

This Privacy Policy applies to the iOS App Store edition, Mac App Store edition, and official BitFile website and explains the information handled by the apps and official website and how that information is stored and deleted. The official website consists of static informational and legal pages and is not a web edition of the app. This English version has the same provisions and effect as the Japanese version. The version published on this webpage is the controlling English version, and the app presents the same subjects and meaning relating to the apps. Features, permissions, and external communications may differ by platform. BitFile is developed and provided by Miyamoto Kazuhiro, trading as Ada Foundry (the “Provider”). The seller name displayed on the App Store is determined by Apple.

1. Core policy

BitFile is an encrypted file manager that performs its core processing on the user’s device. The Provider does not receive or automatically collect files stored in BitFile, file names, folder structures, tags, passwords, recovery information, or encryption keys.

BitFile does not track users, sell personal data, display third-party advertising, perform usage analytics, or automatically transmit crash reports to the Provider. In the iOS App Store and Mac App Store editions, no data is collected by the Provider through the app. Data processed only on the device, purchase information processed by Apple through StoreKit, and data sent to a destination chosen by the user are not collected by the Provider. If these practices change, the Provider will update this Policy and the App Store privacy disclosures before releasing the affected feature.

2. Information stored on the device

BitFile stores the following information on the user’s device to provide and secure its features.

InformationPurpose and storage location
Files and metadata stored in BitFileStored in encrypted form in the app’s data area
Application settings and records of reviewing or accepting legal documentsStored in the device settings area
iOS audit logUp to 10,000 entries, stored in encrypted form on the device
Mac App Store diagnostic logsStored on the device as .log files with file permissions 0600. Logs whose modification time is more than 14 days old are deleted when the app starts and are not sent automatically to the Provider
Device identifierThe iOS App Store and Mac App Store editions store a randomly generated identifier in Keychain

These device identifiers are not sent to the Provider and are not used for advertising.

3. Information not collected automatically by the Provider

During normal app use, the Provider does not automatically collect the following information:

  • Files stored in BitFile, file names, folder structures, or tags
  • Passwords, recovery information, encryption keys, or the results of on-device processing
  • Contacts, calendars, location, or a complete listing of the photo library
  • Advertising identifiers, in-application usage analytics, or crash information

4. External communications and permissions in the App Store editions

Apple StoreKit

The iOS App Store and Mac App Store editions communicate with Apple StoreKit to check purchase status and entitlements, make purchases, restore purchases, and manage subscriptions. Apple processes purchase information under its Privacy Policy, and the Provider does not obtain the user’s credit card number. StoreKit entitlement results are used on the device to determine whether paid features are available.

Sharing and export

When a user chooses to share or export data, BitFile transfers the selected data to the destination, app, or save location chosen by that user. This is a user-initiated transfer, not collection by the Provider. After the transfer, the terms and privacy policy of the selected third-party service apply.

Photos

BitFile uses the system photo picker to import photos and videos selected by the user. Only when the user chooses Save to Photos does BitFile request add-only permission to add the selected file to the photo library. Only when the user explicitly chooses to delete original photos or videos does BitFile request the read/write permission needed for that deletion. These are on-device operations chosen by the user, and granting either permission does not cause the Provider to collect the photo library or the selected media.

5. Mac App Store edition and the website

The Mac App Store edition processes BitFile data on the device.

Diagnostic logs for the Mac App Store edition are stored on the device as .log files with file permissions 0600. When the app starts, it deletes diagnostic logs whose modification time is more than 14 days old. These diagnostic logs are not encrypted and are not sent automatically to the Provider.

The Provider does not use web analytics or other access analytics, user tracking, third-party advertising, or analytics cookies on the official website. The official website uses Cloudflare Workers Static Assets as its publishing destination, and Cloudflare may handle the IP address, request headers, access time, and other connection information required for ordinary HTTPS communication to deliver and secure the website. This processing is distinct from access analytics or advertising tracking by the Provider. Cloudflare’s notices and policies apply to its handling, and information may be processed outside Japan. The official website does not itself sell or process payment for the app and does not provide a feature for sending vault data. When the App Store is used, Apple may handle connection information and other information under its notices and policies.

6. Inquiries outside the application

Signing in to a Google Account is required to open the Google Form. Google processes Google Account authentication information under Google’s terms and privacy policy. Information obtained by the Provider depends on the actual form settings and the items the user enters and submits in the form.

If the user submits an inquiry using Google Forms, the Provider may obtain the contact details and inquiry text that the user enters and submits in the form and information about the device, operating system, or BitFile version that the user voluntarily provides. Do not include passwords, recovery information, encryption keys, files stored in BitFile, or any other secret information in an inquiry.

The Provider uses this information to respond to inquiries, verify identity, investigate problems, respond to security events, confirm billing matters, prevent misuse, comply with legal obligations, and handle disputes. The Provider uses Google Forms, an external service, to receive and store inquiries. Google handles information associated with Google Forms under Google’s terms and privacy policy.

Inquiry information is retained only for the period necessary to handle the inquiry, comply with legal obligations, and handle disputes, and is deleted when no longer needed. Exceptions apply where retention is required by law, is necessary for a dispute, or deletion from backups reasonably requires additional time. Requests concerning access, correction, suspension of use, or deletion may be submitted through the contact point in Section 12.

Information submitted through an inquiry outside the app is handled separately from the app. It is not data collected through the iOS App Store or Mac App Store edition and does not change the App Privacy disclosures for those apps.

7. Retention and deletion

  1. Information on the device is retained until the user deletes it individually or runs BitFile’s complete-deletion feature.
  2. After deletion of the BitFile data has been confirmed, the complete-deletion feature deletes the iOS audit log, local Mac App Store diagnostic logs, application settings, records of reviewing or accepting legal documents, the device identifier, and any Keychain information for biometric authentication stored by an earlier version if such information exists.
  3. Operating-system backups, files exported by the user, data transferred to a sharing destination, and copies held by another application or service are not deleted by BitFile’s complete-deletion feature. The user must delete them at each storage location.
  4. Because of the way operating systems and storage devices work, BitFile cannot guarantee that deleted data is removed from physical storage immediately.
  5. After the last successful unlock, each failed unlock attempt is retained for 24 hours of time while BitFile is running and does not expire during time when the app is terminated or the device is off. When 30 retained failures accumulate, BitFile immediately and irreversibly destroys the wrapped key and recovery methods and then attempts to delete the remaining encrypted data. Even if physical deletion is not completed, the remaining BitFile data cannot be decrypted.

8. Consent, permissions, and data choices

In both the iOS App Store edition and the Mac App Store edition, normal use is available after the user accepts the Terms of Use and reviews the Privacy Policy. If acceptance or review of the current document versions cannot be recorded, the user is not treated as having accepted them. However, the revision to this Policy version 2.4.0 and Terms version 2.4.0 clarifies existing handling and strengthens user protections. Acceptance and review already recorded for the immediately preceding valid pair—this Policy version 2.4.0 and Terms version 2.3.0—are not invalidated solely because of this revision. Any new acceptance and review record uses the current version pair. A change in acceptance status does not automatically delete data on the device. To delete on-device data, use BitFile’s complete-deletion feature. If information handling that legally requires separate consent is added in the future, consent will be requested before that handling begins and a method for withdrawing consent will be displayed.

The user may change or withdraw permissions granted to BitFile, including photo permissions, at any time in iOS Settings. Withdrawing a permission may make all or part of the corresponding feature unavailable. Withdrawing a permission does not automatically delete copies of files that the user previously imported into BitFile. Delete unwanted copies within BitFile.

9. Handling by third parties

The Provider does not sell data stored in BitFile or disclose it to third parties for advertising. The Provider cannot access data that remains only on the user’s device. Apple’s Privacy Policy applies to StoreKit. When a user chooses to share or export data, the terms and privacy policy of the selected destination or save location apply.

If the Provider selects a third party in the future to process information or integrate with BitFile for the provision of a feature, the Provider will review public information or contractual terms and select a service provider capable of offering protection consistent with this Policy and applicable law. This does not guarantee that every incident or risk involving that third party will be prevented. The Provider may disclose information it actually possesses in response to a lawful request made under applicable law.

10. Security

BitFile takes measures to protect information, including encrypting BitFile data and the iOS audit log on the device. Diagnostic logs for the Mac App Store edition are not encrypted, but they are stored with file permissions 0600 and logs more than 14 days past their modification time are deleted when the app starts. These measures do not guarantee protection against every risk arising from a device, operating system, third-party software, or future technology.

11. Changes to this Policy

The Provider may change this Policy when reasonably necessary because of changes in law, changes in features, security needs, or other circumstances. The changes and their effective date will be announced before they take effect through the app, the published webpage, or another appropriate method. If a change materially affects user rights or data handling, the app will request another review, and separate consent will be requested for handling that legally requires consent.

12. Provider and contact

BitFile is developed and provided by Miyamoto Kazuhiro, trading as Ada Foundry. Privacy inquiries and requests concerning notice of purpose of use, disclosure, correction, addition, deletion, suspension of use, erasure, or suspension of third-party provision of inquiry information held by the Provider may be submitted through the Google Form (Google Account sign-in required; external site). A Google Account sign-in is required to open the Google Form. After confirming the request and performing any necessary identity verification, the Provider will explain the response method, response timing, and any applicable fee in accordance with applicable law. At the request of the person concerned, the Provider will without delay explain its business address, details of procedures for disclosure and related requests, and the security-control measures it implements, excluding portions whose disclosure would impair security. The Provider cannot disclose or restore on-device data that it does not possess.

日本語のプライバシーポリシー