Privacy policy

Data we access

When you connect Google, myjournal requests openid, email, profile, and https://www.googleapis.com/auth/drive.file. It uses your Google account identifier and email to identify your connection and show the connected account. Google may return basic profile information during sign-in; myjournal does not need your profile photo to provide journaling. OAuth access and refresh tokens allow the app to act on your permission. Drive access covers files and folders created by the app or explicitly made available to it through that permission, rather than your entire Drive.

How we use your data

myjournal uses your account information and tokens to sign you in, maintain your Google connection, and keep accounts separate. It processes journal text, file identifiers, dates, folder metadata, and content versions to load, save, list, preview, and trash your entries and detect conflicting edits. Data is used to provide these journaling features, not for advertising, profiling, or training AI models.

Where data is stored

Saved entries are UTF-8 plain-text files in your Google Drive, under myjournal/entries/<year>/YYYY-MM-DD.txt. Requests pass through the myjournal server so it can communicate with Google. The app has no production journal or user database. It temporarily processes entry content in memory and retains bounded in-memory entry content, previews and date indexes for up to two minutes; a process restart clears these caches. Your writing is not end-to-end encrypted by myjournal.

Cookies and browser drafts

Your account connection, including refresh credentials, is held in an encrypted, authenticated HttpOnly cookie with a fixed maximum lifetime of 30 days from sign-in. Google permission can expire or be revoked sooner. A separate encrypted login cookie lasts up to ten minutes. Cookies use Secure on production HTTPS. Unsaved recovery drafts are stored separately for each account, date, and tab in sessionStorage; they may survive reloads and same-tab navigation, but are not an offline sync service. Acknowledged saves, confirmed trash, or successful sign-out remove the relevant drafts. Failed operations can retain drafts for recovery. The app also stores your chosen theme and browser time zone. Your language preference is stored in a separate browser cookie for up to one year and remains after sign-out.

Sharing and service providers

Google provides sign-in and Drive storage. Railway hosts the app and processes requests passing through the service. myjournal does not sell Google user data, share journal content with advertisers, or use tracking or analytics scripts. Data is transferred as needed to provide the service or when required by law. Hosting providers may process network information such as IP addresses under their own policies. Do not include journal content or credentials when contacting support unless you intentionally choose to share them.

Operational logs and security

Application request logs record method, query-free path, response status, duration, and request ID; paths can include entry dates. The app avoids logging journal text, credentials, whole cookies, and OAuth callback query values. Encryption protects the connection cookie, and HTTPS protects production traffic. Platform-level log retention is controlled by the hosting provider; myjournal does not promise a particular platform retention period or absolute security.

Retention, disconnect, and deletion

Your saved files remain in Google Drive until you remove them. Moving an entry to trash in myjournal uses Drive Trash, not permanent deletion. You can manage or permanently delete files and empty Trash in Google Drive. Settings → Disconnect revokes myjournal’s Google access and signs you out after revocation succeeds; it does not delete saved files. Sign out alone clears the app session without revoking Google access. You can also revoke access in your Google Account. Successful sign-out clears this account’s drafts in the active tab and notifies other open tabs; inspect other tabs or clear site data if cleanup fails. Clear site data to remove remaining browser storage. Support cannot erase files from your Drive after access is revoked.

Google API Limited Use

myjournal’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Google API Services User Data Policy

Contact and policy updates

For privacy questions or help with data deletion, contact support@myjournal.ink.

Changes to these practices will be reflected on this page with an updated date. Review this policy before reconnecting if the requested permissions change.