Application content
Documents, assets, tables, notes, events, files, and backups form the application’s personal context.
Personal context is stored locally on the user’s device and remains within the private side of Enti.
Bounded technical services
Some functions may communicate with server infrastructure when this is necessary for them to work.
Those interactions should remain limited in purpose and in the amount of data they transmit.
Personal context remains stored on the user’s device.
Public website
The public website is used for information about the project, the product, and its ideas.
Its operation may involve ordinary technical web-request data and limited website usage statistics.
This processing belongs to the public side of Enti and remains separate from personal context inside the application.
Downloads and email
Application files may be distributed through separate download infrastructure.
Email is used for correspondence with Enti.
Email correspondence remains separate from personal context inside the application.
Passwords, seed phrases, private keys, and other sensitive information should not be sent by email.
This page describes the current boundaries between the private application, technical services, and Enti’s public resources.
As the product and infrastructure evolve, this description will be updated.