What This Thing Actually Is
Snapshots By Deku is a platform that lets you encrypt files and set release conditions tied to dates or external triggers. You upload photos, documents, video clips, messages, whatever you want to lock away, pick when it becomes accessible, and hand the decryption key over to a trusted contact or leave it in escrow. When the date hits or the condition fires, the data gets delivered. It is not a social network. It is not a cloud backup. It is a time-locked distribution system for personal data. The core workflow is straightforward but the implementation choices matter more than most people realize. You create an account, verify your identity through whatever KYC flow they run, then build a snapshot. During snapshot creation you choose your recipients, the payload files, the release timestamp or condition, and a trusted contact who can vouch for your identity if something goes wrong. The encryption happens client-side before the file ever leaves your machine. That is the part that actually matters. I have been setting these up for family members and for my own projects. The first time I tried using it for something meaningful, I hit a wall. I had compiled about 400 photos spanning three years of a family trip into a single snapshot, set to release on a specific date five years out. The upload process was fine, but when I went to decrypt and review the final package before locking it down, the application froze. I spent two hours trying to recover the session. The workaround was simpler than the panic suggested: split the payload into chunks of no more than 50 files each, assign them to separate snapshots under the same release condition, and let the platform handle them individually. It cut the processing time down from something unworkable to roughly ten minutes per chunk.
The encryption model they use is standard AES-256 with keys managed through a combination of your password and a recovery phrase. That is good. Most people do not understand what that means in practice. It means if you lose your password and your recovery phrase, the data is gone. Not recoverable. Not by support. Not by anyone. I have seen this happen. A friend of mine set up a snapshot for his children with the wedding video and family documents. He moved houses, changed email providers, forgot the recovery phrase, and the entire thing became unrecoverable. He had backed up the recovery phrase on paper in a safe deposit box he no longer had access to. It is not a hypothetical scenario. There are limitations worth knowing about. The release window is not instantaneous. Once the trigger date arrives, there is typically a processing delay of anywhere from a few minutes to several hours depending on the size of the payload and the current load on the system. If you are planning something time-sensitive, like a conditional release tied to an event, do not count on it arriving within minutes. Factor in buffer time. Another issue is the supported file types. The platform handles images, videos, documents, and archives well. Audio files above a certain duration can cause problems. I ran into this with a collection of oral history recordings from my grandmother. Files longer than four hours caused the encryption step to fail silently. The workaround was to split audio files into two-hour segments before uploading. It adds a step but it prevents data loss during the upload phase.
The pricing structure is tiered based on storage capacity and the number of concurrent snapshots you can maintain. Free accounts are limited. If you are doing this seriously, you will likely need a paid tier. The cost is reasonable for what you get, but it is recurring. Some people set up a snapshot and forget about the subscription, then wonder why their data stops releasing on schedule. The platform requires active payment to maintain the escrow service. Cancel the subscription and the snapshot does not delete, but it also does not release. It sits in limbo. For people who want something similar without the recurring cost, there are open-source alternatives. tools like age or ssh-based key scheduling can create time-locked encrypted archives if you are comfortable running commands in a terminal. They are more work to set up but they give you full control and no vendor lock-in. If you are not technically inclined, Snapshots By Deku is probably the easier path. If you are comfortable with the command line, the DIY route saves you money and dependency. The real value of these systems is in the planning, not the technology. I spent more time deciding what to include than I did configuring the actual snapshot. The hardest part is choosing what matters enough to lock away for years. People tend to overpack. They include everything because it feels safer. That strategy backfires because larger payloads mean more failure points during upload and decryption.
Get the Full Details
You should also consider what happens if the platform ceases to exist. No company lasts forever. If Deku shuts down in five years, your snapshots could become unreachable even if your encryption keys are intact. I keep a local copy of every recovery phrase and a text file explaining the process for accessing the platform. It is not elegant but it is practical. The alternative is hoping a service survives indefinitely, which is a gamble most people do not realize they are taking. If you want to try it, you can find the platform by searching for Snapshots By Deku. The signup process is standard. Do not skip the identity verification step. It adds security and it prevents account recovery issues later. Write down your recovery phrase in two places. Keep one at home and one somewhere else. Lose both and your time capsule becomes a brick.
