Privacy at MyUniTree

Who looks after your information

Ben Mooney, a sole trader operating MyUniTree, is the controller responsible for your personal information.

Contact info@myunitree.com. This mailbox is monitored for support and privacy requests.

What we use and why

• Account and sign-in: your name, email, sign-in identifier, account settings and any optional phone/profile details you choose to provide. Firebase Authentication handles sign-in credentials. We use this information to provide the account service you request, relying on performance of our agreement with you.
• Plans and private memories: saved events, attendance, likes, ratings, notes, optional memory photos and brief friend names or nicknames. These support your requested saved-plan and memory features. Friend email addresses are not collected by this feature and no friend invitation is sent. Please avoid sensitive information or another person's contact details in notes.
• University access: your primary or linked university email, verification attempt records and proof of mailbox ownership. This enables the access you request. It confirms ownership of the inbox, not current enrolment.
• Recommendations: chosen interests, plans, likes and limited signed-in event signals help suggest relevant events. We rely on our legitimate interest in making these suggestions useful, with an option to turn personalisation off in saved-plan preferences. Recommendations do not make decisions with legal or similarly significant effects. Optional starting area, budget, days and goals help make suggestions practical. If you separately opt in to community recommendations, we compute anonymous relationships between event topics, formats and verified organisers from positive saves, plans and feedback. No individual history is shown. You can turn this off; the aggregate model is invalidated and rebuilt without your contribution. Device coordinates remain in the browser session. We do not add anonymous behavioural analytics.
• Service messages and security: requested verification/reset messages, opted-in event updates, limited delivery status, abuse-prevention records and deletion records help run and protect the service. Essential account messages support the service you request; security and reliability use legitimate interests.
• Private in-app feedback: your feedback text, account identifier, page, build and submission time help us investigate and improve the service. Submissions are private to you and authorised owner reviewers. We do not automatically attach diagnostics, tokens or private page contents. We rely on legitimate interests in supporting and improving the service.
• Support and event reports: information you send us helps answer your request or review a listing. We use legitimate interests in responding and maintaining a trustworthy catalogue. Public event details come from the organiser/source linked on each listing.

An email and sign-in credentials are needed for an account; you can still browse public listings without them. Phone details, private notes and friend labels are optional.

Who receives information

Google Firebase provides sign-in, account storage, functions and hosting. Google Workspace supports our monitored mailbox and the planned service email transport. The shared site stylesheet requests a typeface from Google Fonts; that service can receive connection information such as your IP address. We do not sell personal information or send unsolicited friend invitations.

Optional WhatsApp reminders: when available, you can connect your own WhatsApp number and request reminders for your Going plans. We send through Meta’s WhatsApp Business Platform using Zernio for the connection. Meta and Zernio receive your number, reminder time, event link and the event details included in the reminder; incoming messages are checked only for connection codes and requests to stop reminders, and ordinary chat content is not stored by UniTree; Reminders can show the event name and venue in notification previews. Restricted and detected support events use discreet details instead. This is optional. Stop in your profile or reply STOP. Connection codes expire after ten minutes, delivery records last up to 30 days, and removing your number or deleting your account removes the connection. We do not treat a reminder as proof of booking or attendance.

Memory photos are stored privately with your account. You can deliberately download or share a rating card; your name, notes, companion names and photo are included only if you select them. Sharing through another app subjects that copy to the recipient app’s privacy practices.

Ticketmaster event artwork is loaded directly from its image service. That service receives the browser connection information needed to deliver an image, such as your IP address. Booking links open the relevant provider website, whose privacy and cookie policies apply there.

Private notes and history photos are not public catalogue data. Where you take part in a university or society event, authorised organisers can receive the participation information needed to manage their own events. Public popularity summaries contain counts rather than your private notes or friend details.

Opening an organiser's booking link takes you to its separate service and privacy notice. Saving Going on MyUniTree does not buy a ticket or send payment information.

The staging account database is configured in London. Other Google service operations or support may take place outside the UK. Exact provider locations, applicable transfer safeguards and copies of those safeguards will be confirmed and made available through our contact address before release; we do not claim that all data remains in the UK.

How long information stays

• Account details and university access stay while the account is in use, or until you delete it. Accounts showing no recorded activity for two years are flagged for a necessity review rather than silently deleted.
• Upcoming saved plans stay available. Ended-event plans, participation records, ratings and private memories normally expire two years after the event ends. If the event is no longer available, an existing dated rating or saved-plan creation date provides the reference. Undated older records require review rather than guessed deletion.
• Optional viewing and booking-interest signals expire after 90 days. Friend recipient addresses and old invitation lists are removed when existing records are minimised; your other memory notes and photos follow the separate history period.
• University codes are valid for ten minutes; challenge data is removed after a further day. Email request/rate-limit records last one to 30 days according to their abuse-prevention purpose.
• Queued email content lasts no longer than one day and is removed sooner when accepted, cancelled or terminal. Limited delivery metadata, security event records and event report details normally last 30 days.
• In-app feedback expires after 180 days. Feedback abuse-control counters expire after two days. Optional followed-entity notification batches expire after seven days; publication work expires after two days. Following and partial onboarding choices remain with your account and are included in export/deletion.
• Support correspondence is reviewed for deletion 90 days after resolution. A relevant, documented dispute or legal requirement may justify keeping limited records longer; we record and review the reason.
• Completed deletion diagnostics last 90 days. A minimal sign-in identifier marker remains for at least 90 days after completion and until backup and token checks show it can safely be removed. It prevents restored data reopening your deleted account.

Daily staging database backups are configured to expire after 35 days. Deleted backup data must stay beyond ordinary use, and any restoration must reapply the separate deletion ledger before accounts can be accessed. The isolated staging restore and deletion-ledger replay have been rehearsed. Production backup configuration and complete release rollback remain launch checks.

Necessary email suppression records may remain while they prevent unwanted or failed deliveries, with a yearly necessity review. They are not used for marketing. A minimal event moderation decision can remain while it is needed to avoid republishing a removed listing; detailed reports and reviewer identifiers have shorter retention.

Your browser and email choices

The site uses browser storage for sign-in, a short-lived action you requested, public listing cache, and display choices such as theme. Requested actions expire after 30 minutes. Account-specific browser state is cleared when you sign out, switch accounts or finish deletion. You can clear website data through your browser; doing so may sign you out or reset display choices.

Public browsing does not create an anonymous behavioural profile. We do not add advertising trackers. Providers may process necessary connection/security information such as IP addresses. Any future non-essential device tracking or marketing will require a separate choice where required by law.

Optional reminders, event messages and followed-organiser updates require explicit account choices. Following an entity alone does not enable email notifications; the bell control and Notifications settings manage these choices. You can turn them off. Security or account messages you request are separate from marketing; provider acceptance is not proof that a message reached your inbox.

Your choices and rights

You can export your account information and request deletion from Account. You can also email us to ask for access, correction, deletion, restriction or, where applicable, a portable copy. We may need proportionate information to confirm that the request is yours.

You can object to processing based on legitimate interests, including recommendations. Turn personalisation off in saved-plan preferences or contact us. If we rely on your consent for an optional purpose, you can withdraw it without affecting earlier lawful use.

We aim to respond without undue delay and normally within one month. Rights can depend on the purpose and lawful basis; we will explain any applicable limitation or lawful extension.

You can complain to the Information Commissioner's Office, the UK data protection regulator. Contacting us first can help resolve a concern, but is not a condition of complaining.