Your ledger.
Your backup.

The access you grant

When you use /connect_google_drive, Google asks you to authorize Elmden Finance. We request the drive.file permission to create and manage files used by this app. We do not request access to all the files on your Drive, your Gmail, or your Google password.

The integration creates a private folder called “finance.elmden.app”. It uploads database snapshots and downloads them again to check their integrity. It does not change the folder's sharing permissions.

What is stored, and where

The operator's VPS stores your Telegram owner ID, Google account email and identifier, access and refresh tokens, the backup folder ID, and backup status, file IDs, checksums and timestamps. Credentials are kept in service-restricted files outside the source repository and are not passed to the assistant model.

Your Google Drive receives an SQLite copy of the ledger, including its financial records. This backup has no additional encryption or database password. Anyone you give access to the file can read it. Network connections to Google use HTTPS.

The uploaded backup does not include the bot's chat history, memory, OAuth tokens or other application secrets. This notice does not describe the separate Telegram or assistant services.

How the data is used

Google account data and tokens are used only to connect the selected Drive account, run backups and report their status. The backup service does not sell this data, use it for advertising, or send it to language models or use it to train them. The service operator can administer the VPS; Google stores the uploaded files in your account.

Elmden Finance' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Your control and retention

You can revoke Elmden Finance in your Google Account's third-party connections settings to stop future access. Existing backup files remain in your Drive until you delete them; the service does not automatically prune them.

Revoking Google access does not itself erase the credentials and status records already on the VPS. Ask the deployment operator, through your existing private Telegram conversation, to disable backups and remove those records. The configured owner administers this deployment and can also remove them directly. A short-lived browser cookie is used only to secure the Google connection flow; it is not an advertising or tracking cookie.