Privacy Policy

What OBO is

OBO is a personal assistant that runs inside Telegram. It keeps a to-do list, answers questions about your calendar, reminds you of what is coming, and helps you find restaurants, flights and hotels. It is operated by Yokr Partners.

OBO is sold through advisors. If you were invited by an advisor, that advisor can see that you are their client and how much you use the service. They cannot read your messages, your saved notes, or your calendar.

Google user data

Connecting your calendar is optional. Nothing below happens unless you send the /calendar command and grant access on Google's own consent screen.

What we request. One scope only: https://www.googleapis.com/auth/calendar.events. We do not request access to your Gmail, your Drive, your contacts, or your other Google data.

What we do with it. We read your upcoming events so OBO can answer questions about your schedule, send you a morning summary, and remind you before an appointment. We create events when you ask for one, and delete events that OBO created when you ask it to.

Why not a narrower scope. A read-only scope would prevent OBO from creating the appointments you ask it to create, which is a core function of the service.

How it is stored. Your Google credentials are encrypted with AES-256-GCM before being written to our database. Calendar events are held only briefly to answer your request or build your morning summary.

What we never do. We do not sell Google user data. We do not use it for advertising. We do not use it to train, retrain or improve any generative AI model. We do not allow humans to read it, except where you explicitly ask us to help you with a problem, where the law requires it, or where it is necessary to investigate abuse or a security incident.

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

Other data we hold

• Your Telegram account — the numeric identifier, first and last name, and username that Telegram gives us when you first write to the bot.
• Your conversation — what you write to OBO and what it replies, so it can follow a conversation rather than start from nothing each time.
• What OBO remembers about you — preferences and facts you tell it, and which you can list with /memory and erase with /forget.
• Usage counts — how many messages and how much model capacity you consume, which is how the service is metered and billed.

Who else processes it

We use the following providers. Each receives only what it needs to do its job.

• Telegram — carries the conversation itself.
• Google (Gemini API) — generates OBO's replies. Your message and the relevant context are sent to produce an answer.
• Google Calendar API — as described above.
• Pinecone — stores the mathematical representations that let OBO recall what matters to you. The underlying text is encrypted before it is sent; Pinecone holds ciphertext, not readable content.
• Supabase — hosts the database. Render — hosts the service.
• Amadeus and Yelp — searched when you ask for flights, restaurants or activities. They receive the search terms, never your identity.
• Stripe — handles payment if you are billed. We never see or store your card details.

Deleting your data

Send /deleteaccount to the bot. This removes your account and everything attached to it — conversations, saved notes, tasks, stored Google credentials, and usage records — across every table that references you. It is immediate and it cannot be undone.

To disconnect your calendar without deleting your account, revoke OBO's access at myaccount.google.com/permissions.

Contact

Questions about this policy, or about the data we hold on you: privacy@yokrpartners.com.