Drive & the vault

Two layers

This device (always)
├── files/inflow-vault-cache.json
└── files/media-local/   (before / without Drive)

Google Drive (optional)
└── InFlow/
    ├── inflow-db.json
    └── attachments/

Continue without Drive seeds a local vault immediately. Capture still works. Pending media waits on the device until Drive is available.

What inflow-db.json is

A JSON document of your vault: user profile fields, workspaces (folders), views, entries, tags, entry types, custom fields. Media bytes are not in this file — only metadata and Drive file ids. Schema version is migrated in the app. Current documented shape is in the skill pack schema.

OAuth scope

InFlow requests https://www.googleapis.com/auth/drive.file — only files it creates. It cannot list a vault you uploaded by hand or that another app identity created. If discovery finds nothing readable, restore a backup ZIP or create a new Drive vault.

Connect and conflicts

After Google authorization, the app lists accessible InFlow/inflow-db.json files before creating anything. A new Drive vault is created only after you confirm. One valid vault is offered as Continue with Drive vault; several are listed as choices. Blank or malformed files never replace the local cache.

If this device and Drive both changed since last sync, you get a conflict sheet: keep device or keep Drive. No silent overwrite.

What Drive is not

Not an InFlow-hosted database. Not a team Drive we operate. Files in Drive are covered by Google's privacy policy and your Google Account settings. Disconnecting does not delete the folder — you delete InFlow/ in Drive and revoke access under Google Account → Security → Third-party access. See privacy and backup.