Security and data governance
GlossKit is being developed for research workflows where access, permissions, review, and responsible data handling matter from the beginning.
Note: This page describes the current design direction for the separate GlossKit application. Final technical and policy details will be published after backend audit and deployment review.
Project Access and Permissions
GlossKit organizes work around projects, collaborators, consultants, texts, and analysis modules. The platform is designed with authenticated project workspaces and role-aware collaboration in mind, while broader deployment hardening and service-boundary review remain active development concerns.
Data Storage and Deployment Configuration
GlossKit uses dedicated backend services and storage layers for different parts of the documentation workflow. Production deployments require environment-specific configuration, restricted service access, secret management, backup planning, and review of storage policies.
Deployment-specific storage configuration remains under active review.
Controlled Access
Many documentation projects involve materials that should not be treated as public by default. GlossKit is being designed to support controlled-access workflows, but access decisions, consent terms, and archive-specific restrictions remain the responsibility of project teams and their institutions.
Human Review of Automated Outputs
One of the most important safeguards in GlossKit is not purely infrastructural. Transcription suggestions, syntax initialization, and other machine-assisted steps remain subject to human review before they should be treated as settled analytical outputs.
Responsible AI and Model Development
GlossKit currently supports queue-backed transcription workflows and is being developed toward more careful adaptation and feedback loops. Model training and automated analysis are not presented here as replacements for review, provenance, or community governance.
Current Hardening Status
The backend audit confirms real module functionality while also identifying deployment and security hardening work still in progress. For that reason, this website describes security and governance as design priorities, not as completed third-party-audited guarantees.
Security posture depends on deployment configuration and ongoing backend review.
Questions about security?
We understand that language documentation projects often have specific stewardship, access, and review requirements. If you need more context for institutional review or project planning, please get in touch.
Need to discuss stewardship or access requirements?
Request beta access or contact the GlossKit team to discuss security expectations, permissions, and project context.