Privacy Policy

Company

Dream Collection Hall LLC
Sheridan, Wyoming, United States
Contact: support@dch.asia

Apps Covered

• OneThing
• Decided
• InCase

OneThing

The current version of OneThing does not collect personal information. No account registration is required, and user data is stored locally on the device.

In future versions, OneThing may introduce optional features such as leaderboards or online sync. If such features are enabled, minimal data may be collected to provide the service.

Decided

Decided uses Firebase (by Google) to store your decision records in the cloud, so your history is preserved across app sessions.

Data We Collect

• Anonymous User ID — A randomly generated identifier created by Firebase Anonymous Authentication. This ID is not linked to your name, email, or any personally identifiable information.
• Decision Content — The options, reasons, fears, tags, and timestamps you enter when making a decision.

How We Use It

• To save and display your decision history within the app.
• To associate your data with your anonymous session so only you can access it.

What We Do Not Collect

• Name, email address, or phone number
• Location data
• Device identifiers or advertising IDs
• Any information that can identify you as a real person

Important: Data and Device Change

Your anonymous session is tied to your device via the system keychain. Uninstalling and reinstalling the app will not affect your data — it will still be there when you reinstall. However, if you switch to a new device or fully reset your device, your anonymous ID cannot be transferred and your decision history will not be accessible on the new device. We recommend sharing important decisions before switching devices.

InCase

InCase is a time-triggered encrypted digital delivery system. It allows users to create encrypted capsules containing messages or information, which are automatically delivered to designated recipients under user-defined conditions.

Data We Collect

• Email Address — Used for account registration, login authentication, and delivering capsules to recipients. Email addresses are linked to your account identity.
• User ID — A unique identifier generated by Firebase Authentication, used to associate your capsules and account data. Linked to your account identity.
• Capsule Content — The messages and information you enter into capsules. All content is encrypted on your device using AES-256 encryption before being uploaded. We cannot read your content. The encrypted data is stored on our servers solely to fulfill your delivery instructions.
• Recipient Email Addresses — Email addresses you provide for capsule delivery. Used solely to send delivery notifications when your capsule is triggered.
• App Usage Data — General interaction data such as check-ins, capsule creation, and delivery events. Used in aggregate and anonymized form to improve app performance and reliability.
• Crash Data — Technical crash logs collected anonymously to help us identify and fix issues. Not linked to your identity.

How We Use It

• To authenticate your account and enable app functionality.
• To store your encrypted capsules and deliver them to recipients at the designated time.
• To send push notifications for check-in reminders, delivery confirmations, and recipient activity.
• To send system emails including delivery notifications and service reminders.
• To monitor app stability and improve performance.

What We Do Not Collect

• Your name, phone number, or physical address
• Location data
• Device advertising identifiers
• Your key phrase — it never leaves your device and we cannot recover it
• The plaintext content of your capsules — all content is end-to-end encrypted

Zero-Knowledge Encryption

InCase uses AES-256-CBC encryption with PBKDF2 key derivation (100,000 iterations, SHA-256). All encryption and decryption occurs on your device. Your key phrase is never transmitted to our servers. We store only the encrypted ciphertext and cannot access the content of your capsules.

If you lose your key phrase, we cannot recover your content.

Data Sharing

We do not sell, rent, or share your personal data with third parties for advertising or marketing purposes. Data is shared only with the following service providers as necessary to operate the app:

• Firebase (Google LLC) — Authentication, database storage, cloud functions, and push notifications.
• Resend — Transactional email delivery for capsule delivery notifications and system emails.

Data Retention

• Capsule content is retained until you destroy the capsule, or until 30 years after the capsule is triggered, whichever comes first.
• Free capsules require annual confirmation to continue storage. Unconfirmed capsules are deleted after a 30-day grace period.
• Account data is retained while your account is active. Accounts with no activity for more than 2 years will receive deletion warnings before any data is removed.

Important Notice

InCase is a time-triggered information delivery system. It is not a legal will, testament, or financial instrument and has no legal standing. InCase is not a bank, asset custodian, or financial institution. For legal matters, please consult a qualified professional.

Third-Party Services

Our apps use Firebase (Google LLC) for authentication, cloud data storage, and push notifications. Firebase may collect limited technical data such as IP addresses for security and service reliability purposes. For more information, see Firebase Privacy and Security.

We do not use third-party advertising networks or data brokers.

Data Sharing

We do not sell, rent, or share your data with third parties for advertising or marketing purposes. Data is only shared with service providers as necessary to provide app functionality.

Data Deletion Request

If you wish to request deletion of any data associated with your usage, please contact: support@dch.asia. We will delete your data from our systems within 30 days.

Children's Privacy

Our apps are not directed at children under the age of 13. We do not knowingly collect personal information from children.

Policy Updates

This policy may be updated when new features are released. Changes will be published on this page. Continued use of our apps after changes constitutes acceptance of the updated policy.

Effective Date

Effective date: 2026-04-03