A LITTLE CLARITY

Your details.
Your space.

This is an early preview of StudentStudioCollab, for people aged 18 and over.

What you share

We store your name, university email, creative interests, profile photos and any profile details you choose to add, together with your projects, applications and project messages, including their sender and time. Photo uploads are resized and re-encoded; embedded location metadata is removed. We also record when you joined and confirmed you are 18 or over. Passwords are stored as protected hashes.

Who can see it

Signed-in students can see available projects and the organiser’s profile and photos. When you express interest, that organiser can review your introduction, profile and photos. Withdrawing or being declined ends that application’s access to your profile; other active collaborations may still provide access. Applicants cannot see each other’s introductions or profiles through the project. The project conversation is shared with the organiser and all currently accepted participants, including their names and accepted roles. New participants can read earlier messages. Pending or declined applicants cannot read it; withdrawing from every accepted role removes access. A cancelled project keeps a read-only conversation for its remaining team. Your email is kept private. The preview cast gallery contains only clearly labelled fictional people and AI-generated test portraits. The app’s operator can access stored information when maintaining the service. Please use only details you are comfortable sharing for this trial, and keep contact details and exact addresses out of your bio.

The student email check

The private browser preview requires an invitation to your own university address ending in .ac.uk, followed by email confirmation. This checks mailbox access; it does not independently prove current enrolment or age.

Account emails

We use Postmark for invitations, confirmation and password-reset emails, with SendGrid retained as an alternative provider. The selected provider receives the recipient address and email content. Delivery, bounce and complaint events help us see whether the receiving server accepted mail and stop further messages to affected addresses. Server acceptance does not confirm inbox placement. Your administrator can see the recipient and delivery status, but private account links and message bodies are not shown in the admin pages. We disable email click and open tracking.

Queued email content is encrypted and cleared when sending finishes, or when its queue lifetime expires (at most 24 hours). Recipient delivery records are kept for 30 days; invitation and account-link records are removed 30 days after expiry. A hash of a suppressed address is retained to prevent repeated failed or unwanted mail.

Reporting a concern

You can report a profile, project, photo or message you can access. We keep your account reference, reason and explanation, together with a copy of the reported item and any reported image. Only Studio’s MFA-protected administrator can review the report and record a decision; it is not shared with the reported person. Reports, evidence and decisions remain private records if the original content or an account is deleted. During this restricted preview they are retained for manual review; a retention schedule will be agreed before wider launch. Contact studiocollab@codemagician.co.uk for help or to question a moderation decision.

Blocking and leaving a team

Your blocked list is private. We store the two account references and when you blocked someone until you unblock them or either account is deleted. A block prevents access to each other’s profiles and projects and prevents joining the same team. The confirmation lists roles that will end: their roles on your projects, and your roles on their projects or shared projects run by someone else. We do not send a block notification; other organisers can see a normal team-change update. People may infer that access changed. Existing messages remain available to people who still belong to the team, and blocking cannot retract material already seen or saved. You can also leave all your roles without blocking. Leaving ends chat and private shoot-plan access; unblocking does not restore roles.

Optional phone notifications

If you enable notifications in the iPhone or Android app, we store a protected device token, installation reference, your notification choices and delivery status, linked to your signed-in session. Apple (iPhone) or Google Firebase Cloud Messaging (Android) receives the device token, generic alert text and opaque routing references to deliver alerts. We do not include names, project titles, message text or meeting addresses in notification payloads. Notifications are optional; you can change categories or turn them off in the app and your phone settings. Updates remain available inside Studio.

Notification delivery records are normally removed after seven days and inactive device registrations after 30 days; cleanup can pause while the service is disabled. Signing out clears local alerts and queues removal of the device association. Offline sign-out reaches our server when the app reconnects, and an alert already in transit may still arrive. Reading on another device may not immediately clear a sleeping phone’s badge. Deleting your account removes its active device registrations and delivery records.

Your device

We use essential cookies to keep you signed in and protect forms. We don’t use advertising or analytics trackers. Adding the app to your home screen saves its public offline page; your account and profile need an internet connection.

Changing your mind

Edit your profile whenever you like. You can change your password or delete your account in account settings. Deletion removes your active account, profile, photos, applications and any projects you organised, including applications to those projects. Messages are retained as a project record after withdrawal or account deletion; your displayed sender name becomes “Former member” when you delete your account. Message text may still contain details you chose to share. When the organiser deletes a project through account deletion, its conversation becomes unavailable to participants and remains a private operational record. Messages have no edit/delete or disappearing-message feature. Moderators can hide messages from participants while preserving the reported evidence. The wider retention policy remains to be completed before a wider launch. Encrypted operational backups can retain earlier copies after account deletion, under the recovery retention schedule (14 local archives and up to six monthly off-site snapshots).

Updated 23 September 2026. This preview will develop as we learn from feedback.