Cloudflare Enterprise
Front-door protection for JUNIQ: SSL, firewall, DDoS protection, bot protection, caching, API protection and Zero Trust access controls.
✦ JUNIQ Secure Vault
Protect every file, recording
Protect every file, recording
and private JUNI answer.
The Secure Vault is JUNIQ’s enterprise security direction: private accounts, protected uploads, encrypted storage, consent records, transcripts, notes and business files — built for students, professionals, teams and organisations.
Important: this page prepares JUNIQ for secure cloud storage. Private file saving should only go live once the AWS/Cloudflare backend, authentication and access controls are connected.
Built around AWS Enterprise + Cloudflare Enterprise.
For JUNIQ to safely store personal information, disability-support information, recordings, transcripts, student files and business files, the platform should use a secure backend — not public website files.
AWS Enterprise backend
The secure cloud core for accounts, private storage, databases, server-side APIs, audit logs, backups and security monitoring.
Private identity and login
Users should sign in through secure identity such as AWS Cognito, Auth0 Enterprise or Okta. Every user only sees their own vault.
Encrypted file storage
Recordings, transcripts, PDFs, notes and uploads should be stored in private S3 buckets, encrypted by KMS or CloudHSM-backed keys.
Database permissions
A secure database should store file metadata, owners, consent records, sharing permissions, audit events and data-retention settings.
JUNI through backend only
OpenAI and other AI keys must sit behind AWS Lambda or Cloudflare Workers. No private API key should ever be placed inside public HTML or JavaScript.
A private vault for real life.
Recordings
Lectures, tutorials, meetings, phone calls, appointments and professional conversations.
Transcripts
Searchable transcripts for students, professionals, teams and organisations.
JUNI summaries
Plain-English summaries, action lists, tutorial notes, meeting notes and study guides.
Uploaded files
PDFs, Word documents, study material, business records, legal notes and professional files.
Sharing settings
Clear permissions, saved records, controlled sharing and review steps for important information.
Consent records
Who recorded, what was recorded, when it was recorded and what the user agreed to save or share.
Users stay in control.
Download my data
Users should be able to export their files, transcripts, saved notes and account records.
Delete my data
Users should be able to request deletion, subject to lawful retention obligations and account settings.
Share safely
Files should only be shared by explicit permission, expiring links, role-based access or team-controlled policies.
Audit history
JUNIQ should record uploads, downloads, sharing events, consent, admin access and material account changes.
Never store private data inside the public website.
The public JUNIQ site is for pages, design and user interface. Personal information, uploads, recordings, transcripts and AI keys must be handled by secure backend services.
Do this
- Use secure login before saving files.
- Store files in private encrypted cloud storage.
- Run JUNI AI requests through a backend only.
- Use consent, retention and audit logs.
Do not do this
- Do not put API keys in HTML, CSS or browser JavaScript.
- Do not save private files in the website folder.
- Do not use public file links for private recordings.
- Do not let users see each other’s vault data.
Privacy, security and trust at the centre.
JUNIQ is being built for people who need help learning, speaking, reading, recording, understanding and organising their life. That means security is not an add-on. It is part of the product.
Built to keep your vault safe.
JUNIQ Secure Vault is designed to sit on enterprise-grade backend infrastructure, with AWS handling private storage, encrypted databases, identity, backups and audit logging, and Cloudflare protecting the public edge. This is the security foundation needed for recordings, transcripts, files, consent records and saved JUNI answers.
Private storage
Files and recordings should be stored privately, never as public website assets.
Access control
Every user, team and business should only access the information they are authorised to see.
Audit trail
Enterprise clients need a record of uploads, downloads, sharing, deletion and agent-prepared actions.