What reTorHub collects, why it needs it, where it goes, and how to get rid of it.
reTorHub exists to work out when a group of people can actually meet. To do that it needs to know two things about you: what you are interested in, and when you are busy. Everything it collects serves one of those two purposes.
Your calendar is the sensitive part, so it is worth saying plainly up front. Calendar events are read to find your free hours. They are stored in this app's own database and read by this app's own matching code. They are never sold, never used for advertising, never used to train any AI model, and never sent to any other company.
| What | Why it is needed |
|---|---|
| Your account | A username, an email address and a hashed password. The address is where proposed times are sent. |
| Your interests | What you would like to be invited to, held separately for each workspace you belong to. |
| Your hours | Working days, the earliest and latest you will meet, and anything you write in plain words about when you would rather not. |
| Your CV, if you paste one | Turned into a list of expertise areas so the matcher can tell what you know. Pasting one is optional. |
| Connected calendars | For each calendar account you link: the provider, the account's identifier and address, and the token that lets the app refresh it while you are offline. |
| Calendar events | From thirty days back to ninety days ahead: title, location, start and end, whether you are free or busy, whether it is private, whether it is cancelled, how many people are on it, and the first part of the description. |
| Your gatherings | The reTors you propose, your replies to invitations, messages you write on them, and any private note you leave about why a gathering does not suit you. |
| Request records | Address, browser, referring page and time, kept for ninety days. Failed sign-in attempts are recorded separately for the same period. |
An event you have marked private keeps its title to itself. The app stores it, but shows it as a private event everywhere, and the matcher only ever needed to know that the hour was taken.
When you connect a Google calendar, the app asks Google for permission to see your name and email address, and to read the events on your primary calendar. It asks for read access only. It cannot create, change or delete anything in your calendar.
Limited use. reTorHub's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
In practice that means Google calendar data is used only to work out when you are free and to propose times. It is not transferred to anyone else, not used for advertising, not sold, and not used to train generative AI models. No human reads it, except you.
Your events are stored rather than read live because the matcher runs on a schedule, usually while you are asleep, and has to see your week without you being signed in. They are refreshed about once an hour and the stored copy always reflects the current state of your calendar.
You can end this at any time. Disconnecting a calendar on your profile page deletes every event synced from it and tells Google to revoke the permission, so the grant disappears from your Google account too. You can also revoke it yourself from your Google account's third-party access page, which stops any further syncing immediately.
reTorHub is not an advertising business and has nothing to sell. Data reaches other companies only where the service cannot work without them:
Nobody else. Your data is not sold, rented or shared with advertisers, and there is no analytics tracker on this site.
Workspaces are separate worlds. People in one workspace never see the interests, gatherings or availability of people in another, even where the same person belongs to both.
Within a workspace, other members can see your name, the gatherings you propose and your replies to theirs. They cannot see your calendar. They see only that a proposed hour works for you, never what is in your diary, and never the private note you may have left about why something does not suit you. That note is read by the matcher and by nobody else.
Your profile, gatherings and connected calendars are kept until you remove them or delete your account. Calendar events are replaced on every sync and deleted outright when you disconnect the calendar they came from. Request records and failed sign-in attempts are deleted after ninety days.
You can see and correct most of it yourself on your profile page. Beyond that you can ask for a copy of everything held about you, ask for it to be corrected, or ask for it to be deleted. Deleting your account removes your profile, your connected calendars, every event synced from them, and the gatherings you organise. It is hidden at once and erased for good after 30 days; signing in before then restores it.
If you are in the UK or the EU, the law also gives you the right to object to processing and to complain to a supervisory authority. In the UK that is the Information Commissioner's Office.
Questions about any of this, or a request about your own data, go to f.ventirozos@mmu.ac.uk.
If this policy changes in a way that affects what is collected or where it goes, the date at the top changes with it.