User-controlled recovery
Back up your recovery credential and keep it safe. Without the credential or another authorized key holder, a lost decryption key can mean losing access to protected content.
Privacy with clear choices
Share knowledge with the right people.
Some information belongs in public. Some belongs with the people doing the work. Daclify connects shared records and encrypted documents to your DAO, with clear choices about access and recovery.
Your rules. Your members. Your shared workspace.
Protect the content before storing it.
Private files are encrypted on the user’s device before upload. The stored file contains encrypted content; an eligible member needs the correct key to read it. A public storage link alone does not unlock the document.
- Keep signing keys separate from document encryption keys.
- Use version history to follow updates to a record.
- Check file integrity when retrieving stored content.
Know who holds the keys.
User-controlled accounts keep recovery credentials with the member. Managed recovery is a planned alternative and will carry a different trust relationship: a service that can recover decryption keys can also access them.
On the roadmap
Managed recovery
Planned service-assisted recovery will explain what the operator can recover and access. DAOs will need an explicit policy on whether they allow this mode.
Private documents do not make every action private.
Encryption protects document content. Membership references, vote records, transfers and other activity on a public blockchain may remain visible. Daclify does not promise anonymous membership or secret ballots.
- An authorized member can copy or share information they can read.
- Removing a member cannot erase information already received.
- Public chain history and third-party file copies cannot be recalled.
Plan for changes in membership.
A DAO needs rules for who can read historical documents and how future access changes when people join or leave. The roadmap includes fuller member-access and key-rotation workflows; the handbook describes the supported behavior for each deployment.
- Choose who should receive access to past records.
- Treat key rotation and member removal as related steps.
- Make recovery responsibilities clear before sharing sensitive content.
Keep records useful over time.
Compact information fits in contract records; larger documents use IPFS references. A content reference helps identify a file, while continued storage and access still depend on the configured provider and retained keys.
- Keep essential recovery credentials backed up.
- Understand your deployment’s file-storage configuration.
- Use the handbook for current document and access procedures.
DACLIFY
Give your community a place to move forward.
Explore DAOs in the app, find the tools your community needs and use the handbook to learn how they work.