SiSTEM UKOpen the Hub

SiSTEM UK · Your information

Hub privacy notice

A clear look at what we collect, who can see it, and the choices you have in our shared SiSTEM space.

Last updated 22 October 2026

Your work, supported.

Information helps us run the team, record agreements and support your learning.

Access has boundaries.

Different records have different audiences. Private chats are limited to their participants through the Hub.

Your voice matters.

Ask a question, correct a detail or request a review of information we hold.

This public page explains the Hub’s data handling. It does not give visitors access to member profiles, contracts, messages or the internal team handbook.

Who looks after your information?

SiSTEM UK operates the SiSTEM Intern Hub and is responsible for how personal information is used through it. The Hub supports our voluntary team, community and creative work. For privacy questions or requests, contact sisstemuk@gmail.com, marked “Hub privacy”, for SiSTEM leadership.

What we collect, and why

  • Your account and profile: name, email, department, role, profile picture and the profile details you provide. Leadership may import your name, email and department from your signup response to invite you and organise the team.
  • Onboarding and work: training answers, progress, leadership feedback and strengths reviews; tasks, event and meeting participation; content drafts, uploads and approvals. These help us support your development and coordinate SiSTEM work.
  • Agreements and records: your signed contract PDF, typed name, drawn signature, signing time, account identifier, browser information and document checksums. We use these to retain evidence of the agreement. CVs you upload are kept as team administration records.
  • Community activity: messages, posts, stories, photos, reactions and other content you choose to share, plus chat read/view and online-presence information used by the social features.
  • Support and feedback: bug reports, screenshots and feedback you submit in writing, by voice note, or both. Availability and break status are optional; you do not need to give a diagnosis or medical explanation.
  • Technical information: account/session identifiers, notification subscriptions, browser/device information and service logs needed to run, secure and troubleshoot the Hub.

Your name, email, department and required onboarding records are needed for Hub access. Optional social features, photos, voice notes and notifications are your choice.

Why we are allowed to use it

We rely on our legitimate interests in running and securing the SiSTEM team, coordinating voluntary work, supporting learning and retaining appropriate records, while considering members’ privacy. We use information where needed to meet a legal obligation, and rely on consent where an optional use requires it. A signed volunteer agreement does not automatically make every use of your data necessary for a contract.

You can object to processing based on legitimate interests. Contact us and we will consider your circumstances. Where we rely on consent, you can withdraw it without affecting earlier lawful use. Device permission for a camera or microphone is separate from consent to other uses of personal information.

Who can see what?

Profile and community information is visible to the members who can access the relevant Hub space. Shared team or event chats are visible to their authorised audience. Private chats are available through the Hub to their participants; another leader does not automatically receive access simply because they are a leader.

Leadership can access onboarding, training, signed agreements and administration records for their role. Launch feedback, including voice notes, is available to its author and Donna’s designated feedback inbox, rather than to all leadership. Training strengths summaries support human review and task allocation.

Authorised technical support may need limited access to investigate faults, protect members or maintain the service. The Hub’s chats are not end-to-end encrypted. SiSTEM does not have access through this Hub to your private WhatsApp conversations or other chats outside it.

Content is not automatically public just because it is uploaded to the Hub. Approved content may be shared on SiSTEM’s external channels through the publishing workflow.

Google Drive and connected services

The Hub’s Google Drive integration uses a Google account authorised by leadership to archive CVs and signed agreement PDFs in designated SiSTEM folders. It creates files, checks for existing copies to prevent duplicates and records file identifiers and links. Access follows the Drive folder permissions; this process does not intentionally create public contract links.

If Drive is unavailable, a signed PDF can remain securely saved in the Hub until its Drive copy is retried. Signing does not require an intern to connect their personal Google Drive.

Google access credentials are handled on the server. Google data obtained through this integration is used for these disclosed records functions, not advertising, sale or training general-purpose AI models. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Leadership can revoke the Google connection through the connected account’s Google settings; revoking it does not itself delete files already archived.

Service providers include Supabase for account/database/file functions, Netlify for Hub hosting, Google for Drive records and browser push services for enabled notifications. Optional GIF search uses GIPHY; search terms and normal network information may reach that provider. External links and connected publishing services operate under their own privacy notices. We do not sell your personal information.

Providers may process information outside the UK. Contact us for the locations, applicable transfer arrangements and copies of relevant safeguards for your information.

How long we keep things

Stories stop being available in the story viewer after 24 hours; this is not a promise that every stored file or backup is erased at that moment. Account, work, chat and learning records are kept while needed to run the team, maintain shared work and support members. Signed agreements and CV records may remain after access ends where needed for administration, safeguarding concerns or legal claims.

Retention depends on the purpose of the record, whether membership has ended, unresolved concerns, applicable obligations and whether the information can be deleted or anonymised without losing necessary shared records. Backups may take longer to expire. Pausing access or archiving a chat does not delete its records. Ask us to review or delete information you no longer want us to hold.

Your choices and rights

You can ask to access or correct your information, request deletion or restriction, object to relevant uses, and request portability where that right applies. Some records may need to be retained for a valid reason; we will explain this rather than promise automatic deletion.

Turn off push notifications in your browser/device settings. Camera and microphone access is requested for features that use them; a written feedback option is also available. Browser storage supports sign-in, preferences, caching and saved Studio work. Some project drafts can remain in that browser until you remove them.

Training completion automatically controls the onboarding access gate. Leadership remains responsible for team access, permissions and interpreting strengths reviews; these reviews are not an automated hiring or selection decision.

Contact sisstemuk@gmail.com to make a request or raise a concern. You can also complain to the Information Commissioner’s Office (ICO). We will update this notice when the Hub’s data handling changes.