Delete your data
Last updated: September 4, 2026 · See also: Privacy Policy
AssetVault does not operate an account-linked inventory cloud or synchronize your complete saved vault. Core inventory is on your device, while optional services may process the limited records described below. This page explains how to delete each type.
Inventory data (items, photos, serial numbers, documents)
Stored: in the app's local SQLite database and app storage. The live SQLite database is not separately encrypted by AssetVault; it relies on the operating system's app sandbox and device-data protections. AssetVault's lock uses authentication configured on your device.
To delete: uninstall the AssetVault app. Your operating system removes the database, photos, and documents along with the app.
To remove an individual item, open AssetVault → tap the item → trash icon, then permanently delete it from Trash. To remove all trashed items, use Settings → Trash → Empty Trash. Trash does not currently auto-purge.
Uninstalling or emptying Trash does not remove files you previously exported or shared, such as backups, ZIP archives, PDFs, email attachments, cloud-drive copies, or operating-system backups. Delete those separately from their destination.
Crash and session diagnostics
Stored: on our self-hosted Sentry-compatible service. Crash events and session-health diagnostics can include app version, device and OS details, stack traces, timestamps, and technical metadata. Performance tracing is disabled. The app is configured to remove inventory-related request bodies, breadcrumbs, and extra fields from crash events before transmission, but diagnostic scrubbing is not an absolute guarantee.
To request deletion: email support@crldigital.com with the subject Delete Crash Data. Include in the body:
- Your device type (e.g. "iPhone 14 Pro")
- iOS / Android version
- Approximate dates the crash(es) happened, if known
We use that information to try to locate matching reports. Because identifiers are minimized, we may be unable to associate a particular event conclusively. We respond within the period required by applicable law.
Purchase history
Stored: by Apple (App Store) or Google (Play Store), and by RevenueCat which we use to verify your purchase status. RevenueCat receives a pseudonymous App User ID, store receipts, entitlement and transaction information, and related technical information. For requests using the 1.2.2 catalog-side paid-service controls after deployment, AssetVault hashes the current App User ID into an app reference and RevenueCat's canonical original App User ID into a stable billing reference. The catalog stores those references with entitlement status, environment, period type, expiration and check times, webhook event type, source and receipt times, affected-user count and sequencing, and per-feature usage date, count, and update time. These records support access verification, trial and daily limits, anti-abuse controls, and service-cost controls. The catalog does not store raw RevenueCat App User IDs or webhook bodies. CRL Digital does not receive your full payment-card details.
To delete or modify purchase history:
- Apple: Settings → [your name] → Media & Purchases → Account Settings → "Manage" subscriptions
- Google: Google Play → Profile → Payments & subscriptions
- RevenueCat and AssetVault catalog-side billing records: in AssetVault, use Settings → Share Support ID and email that ID to support@crldigital.com with a request to delete the RevenueCat record and, if a 1.2.2 catalog-side entitlement or metering record exists, that record as well. Apple and Google may retain purchase records under their own policies.
Retention: after the 1.2.2 catalog-side paid-service controls are deployed, hashed webhook-event records and paid-feature usage-meter rows are deleted after 90 days. Fully refreshed inactive entitlement-mirror rows are deleted after 90 days; active or unreconciled rows remain while needed for access verification. Catalog database backups rotate after 30 days, so a deleted service record may remain in a disaster-recovery backup until that copy expires.
Catalog contributions and correction feedback
If you explicitly submitted a public-reference catalog entry or tapped "Wrong?" on an AI result, contact support@crldigital.com with the exact submitted fields and approximate date. These records are not stored against an AssetVault account, so identification may require those details.
AssetVault 1.2.2 submissions remain private and are not automatically deleted. There is no enabled publication route in this release. Rejected review metadata and any historical promoted-review metadata are deleted after 90 days, and the submission quota ledger is deleted after 31 days.
Marketing site (this website)
The website does not intentionally set advertising or analytics cookies. Hosting and network providers may still process standard request data such as IP address, user agent, timestamp, and requested path for delivery, security, and operations. Email support if you have a request concerning records controlled by CRL Digital.
What about my serial numbers?
The serial-number field is stored in the local database and is not included in catalog contributions. If a serial number or other sensitive text is visible in a photo you choose to send to an AI feature, that visible content travels with the image. Crop or avoid sensitive details before using an online photo-processing feature.
Verification
If you need written confirmation of a deletion (for a regulator, a Subject Access Request, etc.), say so in your email and we'll respond with a confirmation message documenting the action and date.
Contact
CRL Digital
Email: support@crldigital.com