Information you provide
Depending on the workflows you use, the platform stores account and profile details, institution membership, course enrollments, assignments and submission records, attendance, research drafts and references, publication content, discussions and preferences. The contact form stores your name, email, topic and message in a restricted support inbox. Do not submit unnecessary sensitive information.
Technical and activity information
Authentication sessions, IP addresses in relevant security and activity records, device/browser information, audit events, notification subscriptions, search and discovery signals, and AI usage records can be processed to operate and protect the service. The contact inbox does not separately store your IP address; infrastructure and abuse-prevention logs may still process it.
Why information is used
Information supports account access, academic workflows, collaboration, publishing, personalization where enabled, support, billing, notification delivery, moderation and security. Your institution and the platform operator determine the applicable purposes and lawful grounds in their context. Optional capabilities depend on configuration and permissions.
Visibility and sharing
Public profiles and publications can be visible to other visitors according to their visibility settings. Restricted academic and institutional records use role and institution access rules. Authorized administrators and service providers may process information needed for their responsibilities. Review publication audiences before sharing; public material can be copied by others.
AI, payment and delivery providers
When an AI tool is used, authorized prompts, document excerpts or related context may be sent to the configured provider. Payment initiation sends transaction details to the configured gateway; this application records references and outcomes rather than asking for card details in the contact form. Email and browser-push providers process the information needed for delivery. Provider identities, locations and terms depend on this installation and should be confirmed with the operator.
Storage and retention
Records and uploads are stored in the database and configured file storage. Retention varies by record type, institution requirements, security needs and the operator’s policies; the application does not apply a single automatic deletion period to all data. Contact messages remain in the support inbox until an authorized operator deletes them; marking a message closed does not delete it. Backups and infrastructure logs may have different retention periods.
Your choices and requests
Use available profile visibility, recommendation and notification controls to manage your experience. You can ask the operator about access, correction, deletion, restriction, objection or portability rights where applicable through the contact form. Identity may need to be checked, and academic, financial or other legal obligations can affect what can be removed. The form is a request channel, not an automatic account-deletion tool.
Security and browser storage
The application uses authenticated access, permissions, institution scoping and other security controls. Protection also depends on hosting, configuration and operational practices; no system can promise absolute security. See the Cookie Policy for sessions, local storage, offline caches and browser notifications.
Questions and changes
Use the contact page for privacy questions and identify the relevant institution when appropriate. Do not include confidential records in the initial message. The operator must publish any additional jurisdiction-specific rights, complaint routes and material policy changes relevant to its deployment.
A question about what this means for you?
The platform team can clarify the arrangements for this installation and your institution.
Get in touch ↗