Privacy and data retention

Your information in StudyCrew

StudyCrew is an independent collaboration workspace. A self-entered course or a verified email address does not establish university endorsement or current enrolment.

Who can see your information

Current project members can see the shared tasks, meetings, resources and contribution records of their project. Your recovery email, account sessions and notification preferences are private. Site moderators may access support cases and moderation records to operate the service; their changes are recorded.

Your choices

You can update your profile, mute a project, change notification preferences, leave a project, download your personal records and close your account in Security and privacy.

Transfer projects you own before closing your account. Closing an account immediately disables access and removes editable profile information and current memberships.

Shared work and retention

Account closure does not erase other members' shared work or immutable collaboration and moderation evidence. These records are retained for project accountability and dispute handling under the operator's retention policy. Contact support for a reviewed deletion or de-identification request. Existing audit identifiers are not claimed to be anonymous.

  • Evidence export files expire after 24 hours and are removed by the maintenance worker.
  • Non-security mail content is cleared after 30 days.
  • Unconfirmed support requests expire after 24 hours.
  • Backups require a separate retention schedule; deletion is applied again when a backup is restored.

External services

Emails use the configured mail provider. External document links remain controlled by their owners and providers. The app does not send your project materials to an AI provider or connect to a university learning system automatically.

Operational records

Rate limits use keyed account or network digests. Request metrics record route groups, status and duration, without request bodies. Security and support records are available only to authorised operators.

The operator must publish its contact details, hosting location, suppliers and actual retention schedule before accepting public users. These deployment-specific facts cannot be established by the local app.