Upload once
Encrypt supported files on the device before opaque object storage.
← All features
Files
One encrypted file, reusable across your system.
Store common documents, images, audio, video, archives, text, and data files in folders, then reuse them across connected records.
Purpose
Why Files exists.
Files is the canonical asset layer for Tomozi. Reusing one encrypted object avoids duplicate uploads and keeps every connection visible.
PRODUCTIVITY EFFECTStop hunting across device folders and repeated attachments; find an asset by name, type, folder, or where it is used.
How you will use it
Useful from the first action to the next.
Organize and find
Use folders, categories, local filename search, and connection labels.
Reuse everywhere
Attach the canonical File to supported features without paying storage twice.
In real work
Different roles. A specific advantage.
These examples show how the same feature can remove a different kind of friction depending on the work around it.
Freelancer
Reuse the same brief across its Project, Tasks, Notes, and client Meeting.
Student
Keep course documents organized and connected to the work they support.
Engineer
Store diagrams and specs once, then reference them from implementation context.
Data & privacy
What it uses. What it stores. Where the boundary sits.
The file you select, its encrypted name/metadata, folder, size, and connection relationships.
Encrypted bytes live as opaque cloud objects; the database stores encrypted metadata and operational size/quota state.
Decryption, compatible previews, and downloads happen on the authorized client. Object storage does not receive the raw key.
Connected system
Files becomes more useful beside…
Make it part of one system
Start with Files. Connect the rest when it helps.
No imported complexity. No privacy compromise.