Engram privacy

Who uses it

Engram has one user, its owner. Only the owner's Google account can sign in; every other account is refused.

What it stores

The notes, decisions, facts, commitments and project checkpoints the owner's assistants save, a history of changes (so changes can be undone), and sign-in records for the apps the owner connected (stored as hashes). It does not sell, share or analyse this data, and it shows no ads.

Google data it uses

• Sign-in (openid, email): to check that the person signing in is the owner. Engram keeps the account's stable Google id and email address, nothing else from the Google profile.
• Google Drive (drive.file), only if the owner connects it: Engram can see and change only the files it created itself, in one folder named "Engram Backups". It cannot see any other file in the owner's Drive. It writes encrypted backups there; they can be read only with a key the owner keeps offline, not on the server.

Retention and deletion

Data stays until the owner deletes it. A deletion removes it from the live database at once. Encrypted Drive backups keep deleted data until they age out (up to 12 months), and any restore from a backup re-applies the deletion. Server disk snapshots are kept for a few days. The owner can disconnect Drive at any time on the Drive page, which revokes Engram's access, and can remove the app's access in their Google account settings.

Contact: jdcasper@gmail.com