Last updated 2026-10-22
MYupgrade Staff is an internal tool used by the staff of MYupgrade. It is not a public service and it has no sign-up: an account exists only if somebody already on the team added your email address to it.
It tracks what the company pays for, the clients and events it works with, and the tasks the team must not forget.
We use Google only to prove who you are. When you sign in, Google tells us your email address and basic profile information. We store the email address, because that is what decides whether you are allowed in and whose name goes against a change.
We do not read your Gmail, your contacts or your own calendar, and we never ask Google for permission to.
When somebody attaches a file to a client record, the app uploads it into one folder of a shared Google account, and stores a link to it.
The permission the app holds is drive.file, which is per-file access to files the app itself created. It cannot open, read or list anything else in that Drive, including files put in that same folder by hand.
An uploaded file starts as only people with access. Changing it to anyone with the link is a deliberate act by a person, and it is recorded in the change history with their name and the time.
Removing an attachment removes our link to it. The file itself stays in Drive, because it is the account owner’s own business record and not ours to destroy.
The app keeps one calendar of its own, named myUpgrade, in the same shared Google account, and copies into it our events, client deals past the first contact (with their stage, except lost ones) and tasks, open or finished, so the team can see them in Google Calendar. It is shared with the staff to read, not to edit.
The permission the app holds is calendar.app.created: it can only see and change calendars the app itself created. It cannot read anybody’s own calendar, and nothing typed into Google Calendar comes back into the app.
What is copied is a title, a date or a time, and a link back to the record; a client deal also carries the client’s name and city. Notes and contact details are not copied, although a task’s title is copied as it was typed.
About the team: email addresses, name, job title, phone number, access level, and a Telegram username and account id if the bot is used.
About clients: company name, contact details, notes written by the team, the events they relate to, and information gathered by our own research process from publicly available sources.
About the company: what we pay for, to whom, and how much.
A history of changes: who changed what, when, and through which door — the website or the Telegram bot.
Conversations with the Telegram bot are kept briefly so the bot can follow a thread, and are trimmed as they age.
Google — for sign-in, for the Drive folder and the calendar described above, and to read the research spreadsheet the client list is imported from.
Google Gemini — when somebody pastes a note, a bill or a photograph for the assistant to read, that text or image is sent to Google’s Gemini API and the answer is used to fill in a form. The picture is not kept afterwards.
Telegram — messages sent to our bot travel through Telegram, under their terms.
Railway — our hosting provider, which runs the application and its database.
Nothing here is sold, and nothing is shared for advertising.
Removing somebody from the team takes away their access to the app immediately, and also deletes their conversation with the bot. Their access to the shared Google calendar is removed by hand, in Google: the app cannot change who it is shared with.
Deleting a client deletes that client’s record, the notes about them, the tasks about them, their change history and our links to their files. What survives is a single line saying a deletion happened, with their name and nothing else, because a deletion nobody can see is its own problem.
If you are a client and want to know what we hold about you, or want it removed, write to the address below.
Write to myupgrade.staff@gmail.com.