Skip to content

Privacy Policy

Last Updated: October 19, 2026

TOMOSHIBI LLC ("we," "our," or "us") has established this Privacy Policy as follows regarding the handling of user information in Cravault (the "App").

1. Information We Handle

The App handles the following information.

1.1 Information Entered or Added by Users

  • Information entered by users within the App, such as collection titles, tags, and notes
  • YouTube URLs and YouTube playlist URLs
  • PDF, ZIP, image, video, and audio files selected and imported by users

1.2 Information Generated by the App

  • Content settings such as viewing and playback order, start positions, end positions, and timer settings
  • Usage history, including date and time, usage duration, completion status, and notes

1.3 Analytics and Diagnostics Information

After the initial onboarding, the App presents choices regarding analytics and diagnostics. When the user agrees, the App may send information to the following third-party services. The scope of information sent may vary depending on SDK settings and the nature of the event that occurred.

  • Firebase Analytics (Google LLC): used to understand usage and improve features. Examples of data that may be collected include screen view information, interaction data, general usage data, device information, OS, app version, language or region, and Firebase-assigned identifiers.
  • Sentry (Functional Software, Inc.): used to investigate issues and improve quality. Examples of data that may be collected include crash logs, error logs, stack traces, device information at the time of the event, OS, app version, and other technical diagnostic data.

Firebase Analytics measures events such as purchases/restores, sync, and collection-package imports/exports. Purchase measurement may include product and transaction information. Data may be associated with an SDK-assigned app instance identifier; the fact that the App does not set a name or custom user ID does not mean the data is fully anonymized. Firebase Analytics may derive a broad geographic region from network information.

These data may include technical identifiers generated by the SDKs and timestamps related to events. Analytics events are designed so that collection titles, YouTube URLs, imported file names, and note contents are not intentionally included.

1.4 Information the App Does Not Collect

The App does not collect user information for the following purposes:

  • Ad delivery
  • Tracking
  • Sending analytics or diagnostics data when the user has turned the relevant setting off
  • Sending collection titles, YouTube URLs, imported file names, or note contents as analytics event parameters

1.5 User-Submitted Feedback

Only when you submit the in-app feedback form, we handle its message, type, submission time, app version/build, language, plan status, and any name and email address you provide to request a reply, for support purposes. The form is sent through our relay hosted on Cloudflare and forwarded to and stored in Discord for support handling. Do not include secrets or unnecessary personal information. For the website's shared contact form, also refer to the information provided on that site.

2. Purposes of Use

We use the information handled in the App for the following purposes:

  • To allow users to create, edit, save, and view content
  • To retain settings such as viewing and playback order, timers, and start positions
  • To save usage history and notes so that they can be reviewed later
  • To sync collection structures and usage history across multiple devices when the Pro plan is used
  • To display metadata such as titles and durations of YouTube videos and playlists
  • To understand app usage and improve features based on the user's choice
  • To detect crashes and errors and investigate issues based on the user's choice
  • To respond to feedback submitted by users

3. Storage Locations

3.1 Local Storage

Including on the Free plan, collection data created in the App and imported files may be stored in the App's local storage area on the device.

3.2 iCloud / CloudKit / iCloud Drive

When using the sync feature on the Pro plan, the App uses Apple's iCloud, CloudKit, and iCloud Drive to sync or store the following information:

  • Collection structure
  • Usage history
  • Content files that users choose to save as sync targets

These data are associated with the user's own Apple account and are managed through Apple's systems.

4. Access to Photo Library and Files

The App requests access to the Photo Library or files only at the following times:

  • When the user chooses to add images or videos as content
  • When the user chooses to import PDF, image, video, or audio files

The App does not automatically obtain photos or files without the user's explicit action.

5. Use of YouTube API Services

The App uses URLs entered by users and may use YouTube API Services in order to handle YouTube videos or playlists as content.

5.1 Embedded Playback

YouTube playback is provided through an embedded player.
The App does not download, extract, or background-play YouTube videos or audio.

5.2 Metadata Retrieval

To obtain metadata such as video titles, playlist names, and durations, the App may use a proxy service operated by us as well as Google's YouTube Data API.

During this process, service providers involved in the communications, such as Cloudflare and Google, may process IP addresses and other communication-related information in accordance with their respective privacy policies.

The App does not obtain users' YouTube login information or Google account credentials.

5.3 Google's Policies and Settings

In connection with the use of YouTube API Services, Google may handle information. For details, please refer to the following:

At this time, the App does not require Google Account sign-in or OAuth authorization and does not retain authentication tokens linked to Google Accounts. If such functionality is added in the future, this policy will be updated.

6. User Controls for Analytics and Diagnostics

  • Usage Analytics and Crash Diagnostics can be selected separately; both are initially off
  • Save Settings applies your choices; Not Now discards unsaved choices
  • You can change these choices later in Settings > Analytics & Diagnostics
  • Turning Usage Analytics off disables Firebase Analytics collection
  • Turning Crash Diagnostics off stops the Sentry diagnostics runtime
  • Normal library features remain available with both off. Turning a setting off does not immediately delete information already sent

7. Provision to Third Parties

Except where required by law, we do not sell or provide user information to third parties.

However, the following external services may be involved in providing the App's functionality:

  • Apple (iCloud, CloudKit, iCloud Drive)
  • Google LLC / Firebase Analytics (usage analytics)
  • Functional Software, Inc. / Sentry (crash and error monitoring)
  • Google (YouTube embedded playback, YouTube Data API)
  • Cloudflare (YouTube metadata proxy and relay for user-submitted in-app feedback)
  • Discord (receipt and storage of user-submitted in-app feedback)

The handling of data by these external services is governed by the privacy policies and terms of the respective providers.

8. Data Retention and Deletion

Sentry diagnostic data is processed in the United States region. Under the current Developer plan, event data is generally retained for 30 days. We enable prevention of IP address storage and default server-side scrubbing for new diagnostic events. Scrubbing does not guarantee removal of all personal information. Turning diagnostics off does not immediately delete information already sent.

Users can delete content and logs within the App.
Deleted data will be removed in sequence from the device and any sync destination.

However, it may take some time for changes to be reflected on external services such as iCloud.

Users can also delete related information stored in the App by removing YouTube URLs. Permissions for Photo Library access can be changed in device settings as needed.

9. Children's Privacy

The App is not designed primarily for children.

10. Security

We strive to take reasonable security measures to protect the information handled in the App.
Local files are stored inside the App sandbox.
Data related to iCloud is processed in accordance with Apple's systems.

For original-file references, connection bookmarks remain on the device. Synced reference metadata can include relative paths containing filenames and library identifiers.

Biometric Vault locking

On supported devices, biometric authentication such as Face ID or Touch ID can restrict access when opening a Vault. This is an in-app access control, not file encryption using a Vault-specific key.

11. Changes to This Policy

We may revise this policy as necessary.
If any important changes are made, we will provide notice on the public page or within the App.

12. Contact

For inquiries regarding this policy, please contact: