InFlow Privacy Policy

Short version

InFlow is a notes and capture app that stores your vault on this device. Google Drive backup is optional. If you connect Drive, files go into your Google account under InFlow/, using the drive.file scope (only files InFlow creates). The developer does not run an InFlow server, does not sell data, and does not use ads or analytics SDKs.

You can use the app without signing in (Continue without Drive).

Who this policy covers

This policy applies to the Android app InFlow (com.inflow.vault) published on Google Play.

InFlow does not create its own user accounts. If you choose Connect Google Drive, Google authenticates you and InFlow receives a token limited to https://www.googleapis.com/auth/drive.file.

1. Content you create

You can type notes, paste links, attach files, take photos or video, and record voice notes.

Without Drive: this content stays in app-private storage on the device (vault cache and local media).
With Drive: the same content is uploaded to your Google Drive folder InFlow/ (inflow-db.json for the vault, attachments/ for files).

The developer does not host a copy of your vault.

2. Profile fields you enter in the app

You may enter a display name, email, and avatar choice in Profile. Those values are stored in the local vault JSON. If Drive is connected, they are included in inflow-db.json on your Drive.

3. Google account details (only if you connect Drive)

When Drive is connected, InFlow may read basic Google account fields from the Drive API (about.get, user fields): display name, email address, and profile photo URL. These are used to show who is connected. They are not sent to an InFlow backend (there is none).

4. Link previews

If you save a web URL and the device is online, InFlow may fetch that page to read public Open Graph / Twitter title, description, site name, and image URL. The request is a normal HTTPS GET from the device to that website. Preview images stay as remote URLs; they are not copied into Drive.

5. Device permissions

Requested only when a feature needs them:

Permission	Why
Internet / network state	Drive sync, link previews, optional Wi-Fi-only upload
Camera	Take a photo or video for an entry
Microphone	Record a voice note
Foreground service (microphone)	Keep an in-progress voice recording alive if the screen turns off, with a visible notification
Notifications	Reminder alerts and the voice-recording notification
Schedule exact alarms / boot completed	Fire and reschedule reminders you set
Vibrate / wake lock	Notifications and recording

InFlow does not request location, contacts, SMS, call log, all-files access, or the advertising ID. Photo and file attach uses the system picker or camera; the app does not request broad READ_MEDIA_* library access. Camera and microphone are optional hardware. The app still installs on phones without them.

6. What we do not collect

InFlow does not include advertising, analytics, crash-reporting, or third-party tracking SDKs. Android backup of app data is disabled. The developer does not receive your notes, media, or Google token on a developer-operated server.

Where data is stored

This device
  files/inflow-vault-cache.json     vault
  files/media-local/                media before / without Drive
  files/media-cache/                cache of Drive attachments

Your Google Drive (optional)
  InFlow/inflow-db.json
  InFlow/attachments/

Sync uses HTTPS to Google APIs. Files in Drive are covered by Google's privacy policy and your Google Account settings.

Sharing

InFlow does not sell personal information and does not share vault content with advertisers. Data leaves the device only when:

You connect Google Drive, so InFlow can read/write files it created in your Drive.
You save a URL and the app fetches public preview metadata from that site.
You use Android Share to send content into InFlow from another app, or you export a vault backup you chose to save.

Google acts as a service provider for Drive, under your Google account, not as an InFlow-hosted database.

Retention and deletion

In the app: entries, workspaces, and related items use soft delete (Trash). Restoring keeps media. There is no permanent purge button in this version.
On the device: uninstalling InFlow, or clearing the app's storage in Android settings, removes the local vault cache and media cache.
On Drive: InFlow does not delete your Drive folder when you stop using the app. To remove cloud copies, delete the InFlow folder (and attachments) in your Google Drive, and revoke InFlow under Google Account → Security → Third-party access.
Disconnect: this version reconnects Drive from Profile but does not ship a dedicated sign out / delete account screen, because InFlow does not operate its own accounts. Clearing app data plus deleting the Drive folder and revoking access is the full wipe.

Exported ZIP/JSON backups that you save are under your control.

Children

InFlow is not directed at children under 13. Do not use it to collect information from children.

International users

Processing happens on your device and, if you connect Drive, on Google's infrastructure for your Google account. Google's terms and location of processing then apply to those Drive files.

Changes

If this policy changes in a way that affects how InFlow handles information, the last-updated date at the top will change and the Play listing / OAuth consent URL will point at the new text.

Contact

Privacy questions about InFlow (com.inflow.vault):

Email: thisisganesh353@gmail.com

You can also use Android Settings → Apps → InFlow → Storage to clear local data, and Google Drive / Google Account settings to remove Drive files and OAuth access as described above.