Data & permission

Privacy policy

Effective 13 September 2026. Franky is an owner-operated, personal-use Telegram assistant. This policy describes the assistant and this information website.

Information processed

• Incoming Telegram text, photos, voice messages and action-button interactions, together with identifiers needed to restrict access to the owner.
• Conversation history, transcribed speech, generated image descriptions and memories the owner explicitly approves.
• Reminder instructions and the last interaction timestamp used for inactivity check-ins.
• When Google Calendar is connected: event titles, dates, times, descriptions, locations, guest information and other event fields returned by Google for the configured calendar.
• Google authorization credentials required to maintain the authorized connection.

Why Google data is used

Calendar data is used only to provide requested calendar assistance: finding events, answering scheduling questions, checking conflicts and preparing changes. Approved changes are sent to Google Calendar. Event invitations and updates may notify guests when the owner confirms the relevant action.

Franky does not sell Google user data, use it for advertising, or use it to develop or train generalized AI or machine-learning models. Franky's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Services involved

Telegram carries the private bot conversation. The bot runs on Railway and uses a persistent database. OpenAI processes messages, relevant calendar tool results, photos and audio to provide the requested AI functions. Google processes calendar requests and authorization. Web searches use minimal relevant search terms; private memories and calendar details are not intended for web searches without an explicit request.

The bot's OpenAI Responses requests disable stored responses through the API's store setting. This does not mean that all provider security or abuse-monitoring records are disabled. Each provider's own data handling also applies. Telegram bot chats are not end-to-end encrypted Secret Chats.

There is no automatic sharing of memories with ChatGPT or a separate Make bot. No Notion connection is currently configured; any future connection requires separate setup and permission.

Storage and retention

Conversation history is configured for 30 days and is periodically pruned. Calendar details included in saved conversation messages or action records may remain for that period. Approved memories are stored separately until removed. Reminder records may remain until separately removed; there is no automatic retention deadline for those records.

Audio is processed temporarily; its transcript can remain in conversation history. Photos are represented in stored history by generated descriptions rather than the original image bytes. Authorization credentials remain in the hosting service's protected configuration until removed. The inactivity timestamp and whether a check-in was attempted persist across restarts.

Control and deletion

The owner can inspect approved memories with /geheugen, request removal of individual memories, and confirm /wisgesprek to clear local conversation history or /wisalles to clear history and approved memories. These commands do not delete Telegram messages, Google Calendar events or scheduled reminders. Reminders must be cancelled separately.

Google access can be revoked through Google Account connections. Revoking access prevents further authorized Calendar requests; it does not erase information already in local history. For full removal of remaining records and stored credentials, contact the operator using the support email displayed on Google's consent screen.

This website

This information site contains no forms, advertising, analytics scripts or embedded bot conversation. The hosting and delivery providers may process technical request data, such as IP addresses and access logs, to deliver and secure the pages. No calendar data or bot credentials are embedded in this site.

Changes and contact

This policy will be updated when data practices change. Questions and deletion requests can be directed to the operator at the support email shown on Google's consent screen.