What the Journal reads, keeps and never does.

• Google data the Journal accesses
• How Google data is used
• Google Limited Use
• Storage and encryption
• How long data is kept
• Sharing
• Other services
• Disconnecting and deletion
• Changes and contact

Google data the Journal accesses

Each Google account is connected separately by the owner, on Google’s own consent screen, and only the permissions below are requested. Calendar permission never grants mail access, and each mail permission is requested only when the owner turns that feature on for a specific mailbox.

The Journal cannot create, change or delete calendar events. It does not delete, archive, label or move email, and it does not create mail filters or forwarding rules.

How Google data is used

• Google data is used only to provide the Journal’s features to the owner: showing her calendars, meetings, mail, attachments and follow-ups, and sending or drafting messages she approves.
• Nothing is sent automatically. Before any message is sent or saved as a Gmail draft, the Journal shows the sending account, recipients, subject, body, attachments and action, and acts only on her approval of that exact message. A message is shown as sent only after Gmail confirms it.
• Sorting mail into parts of her life (“worlds”), spotting bills and suggesting follow-ups is done by simple rules inside the Journal. Google data is not sent to any AI or machine-learning service.
• No person other than the owner reads her Google data through the Journal. The only exceptions would be with her explicit permission for a specific item, when necessary for security (for example, investigating abuse), or to comply with applicable law.

Google Limited Use

Jana’s Juggle Journal’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, Google user data is:

• used only to provide and improve the owner-facing features described above;
• not transferred to others except as described under Sharing, as needed to provide those features, for security, to comply with law, or as part of a merger or sale with notice;
• never used for advertising, never sold, and never used to determine creditworthiness or for lending;
• never used to develop, improve or train generalized or non-personalized AI or machine-learning models.

Storage and encryption

• The Journal runs on Cloudflare (Workers, Pages and a D1 database). All traffic uses HTTPS, and every private page and data request is checked against the owner’s Cloudflare Access sign-in on the server.
• Google access permissions (refresh tokens) are encrypted with AES-256-GCM before they are stored, under a key held as a Cloudflare secret and never placed in the application code.
• Calendar: so the schedule loads quickly, events in the selected calendars are copied to the database with their titles, places, attendees and descriptions encrypted the same way. Only times and identifiers needed for ordering are stored unencrypted.
• Gmail: message bodies and attachments are read from Gmail when the owner opens them and are not stored by the Journal. What is stored, encrypted, is limited to what she creates: follow-up reminders, world corrections, links to her own tasks, meetings and notes, and saved references (subject, sender, date and her own note). When she sends or drafts a message, the Journal keeps an encrypted log of the account, recipients, subject and Gmail’s message id.
• If the owner saves a mail item to a note, the note holds the sender, mailbox, subject, a link back to Gmail and whatever she writes, not the message body. Notes are encrypted in the database.
• The owner’s own browser may keep a local copy of her notes and Mailroom settings so the Journal works offline.
• The Journal has no analytics, advertising or tracking code.

How long data is kept

• Calendar events are kept for a rolling window, about the past month and the next four months, and are refreshed or removed as Google reports changes. Events of a calendar or account are deleted when that calendar is turned off or the account is disconnected.
• Gmail and Calendar permissions are kept until the owner disconnects the account, or until Google ends the permission.
• Mailroom notes, references, follow-ups and the sent-message log are kept until the owner deletes them or asks for them to be deleted.
• One-time sign-in records are deleted as soon as they are used; unused ones are cleared at the next sign-in.

Sharing

Google data is not sold, rented or shared with anyone. It is processed only by Cloudflare as the hosting provider, on the owner’s behalf. When the owner herself chooses to create a task in her own ClickUp workspace from a meeting note, the task text she approves is sent to ClickUp; nothing is sent there automatically.

Other services

• Zoom, if connected: read-only access to who is connected and the meetings that user hosts (topics, times, length, repeats, join links). Meeting details are read when needed and not stored. Recordings, transcripts, summaries and AI Companion data are never requested.
• ClickUp: the owner’s own tasks, read with her personal token; status changes and new tasks only when she makes them.
• Weather: the approximate location of Jackson, Mississippi, or of the device if she allows it, is sent to Open-Meteo for a forecast. No account data is sent.

Disconnecting and deletion

• Each Google or Zoom account can be disconnected inside the Journal. Disconnecting deletes the stored permission (and, for calendars, the cached events) and asks the provider to revoke it.
• Access can also be removed at any time from the Google Account’s Third-party connections page.
• To have any remaining Journal data deleted, write to the contact address below; it will be deleted within 30 days.

Changes and contact

If this policy changes, the new version will be posted here with a new effective date before any new use of Google data begins.

Contact: jana@byjmw.com