Questions about JUNIQ?
Start with a clear answer.

JUNIQ does not use your private recordings, transcripts, Vault files or prompts to train a shared JUNIQ model. JUNIQ’s current AI-assisted processing uses Cloudflare Workers AI. Cloudflare states that Customer Content submitted to Workers AI is not used to train AI models or improve Cloudflare or third-party services without explicit consent. Relevant content is processed only as needed to provide the feature you request.

JUNIQ does not currently claim SOC 2 certification. JUNIQ is designed around recognised security, availability and confidentiality principles, but a framework reference is not the same as an independent certification. We will only describe JUNIQ as SOC 2 certified after the relevant independent assessment has been formally completed.

JUNIQ does not currently claim HIPAA compliance and does not currently offer a HIPAA Business Associate Agreement. Organisations handling protected health information should contact JUNIQ before using the platform for regulated healthcare data.

JUNIQ currently supports JUNIQ account authentication plus Google and Microsoft OAuth sign-in where enabled. Broader enterprise SSO and SAML requirements should be discussed with JUNIQ before deployment so we can confirm the exact current capability for your organisation.

The current public sign-in pathways support Google and Microsoft OAuth where enabled. JUNIQ does not currently advertise providers such as Okta, Entra ID SAML, Google Workspace SAML, JumpCloud, OneLogin, Ping, Oracle or other enterprise identity systems as universally production-ready unless they have been confirmed for the specific deployment. Contact hello@juniq.com.au with your identity-provider requirements.

JUNIQ processes the information needed for the workflow you choose. Work you deliberately save can be associated with your signed-in account in My Vault so you can return to it later. JUNIQ is designed so users control what they save, download, send or remove.

JUNIQ uses cloud infrastructure and storage services to operate account, AI and My Vault functions. Current production architecture uses Cloudflare services, including private database and object-storage capabilities where configured. Some service providers may process information outside Australia depending on the specific feature and provider configuration. See Data Handling and Privacy for more detail.

As between you and JUNIQ, you retain the rights you already hold in content you provide. You give JUNIQ the limited permission needed to host, process, transmit and otherwise handle that content to provide the features you request, operate the service and meet applicable legal obligations.

Yes. Supported My Vault items can be removed using JUNIQ controls. You can also contact JUNIQ about account deletion, access, correction or other information you want reviewed. Some operational, transaction, security or legal records may need to be retained where reasonably required.

JUNIQ recording is designed to begin when the user chooses to start a recording and the browser or device grants the required permissions. JUNIQ does not rely on a hidden recording process. If a future meeting integration uses a different workflow, that workflow should tell the user clearly.

Recording and consent laws vary by jurisdiction and circumstance. You are responsible for deciding whether you may lawfully record a conversation and whether notice or consent is required. Only record, upload, process, translate, save or share information when you have the rights, permissions or other lawful basis to do so.

JUNIQ is built as a responsive web application and installable PWA for modern phones, tablets and computers, including iPhone, iPad, Android, Windows and Mac. Browser and operating-system permissions can affect microphone, system-audio and background-recording capabilities.

Yes. JUNIQ Languages is designed for transcription, translation and multilingual workflows across 100+ supported languages, subject to the capabilities of the active language and AI services.

Yes. JUNI Voice is designed to read supported translated or generated text aloud so a user can hear the result and, where appropriate, use JUNIQ to support two-way communication.

JUNI Agent is the practical-work layer of JUNIQ. You give JUNI an outcome and approved source information, such as a recording, transcript, file or saved Vault content. JUNI can then prepare notes, follow-up emails, documents, action plans and other requested work for you to review.

JUNI Agent is designed around review and user control. Consequential actions such as sending, changing or sharing information should require the user to review and approve the work and, where necessary, authenticate the connected service before anything external happens.

My Vault is the private JUNIQ workspace for items you choose to save. It is designed so signed-in users can keep, search, review, download and remove supported recordings, uploads, transcripts, summaries and generated work.

Yes. JUNIQ provides a free-access pathway for people with genuine disability, accessibility or communication needs. The pathway may include an application or verification step so the program can remain focused on people who need it.

The applicable plan, launch price, billing frequency and trial terms are shown before purchase. If you choose a paid plan, the checkout flow shows the amount and billing terms before payment is completed. If an account no longer has active access, some online AI or paid features may be restricted until access is renewed.

Yes. JUNIQ offers Pro, Business and Enterprise pathways for meetings, calls, client work, professional workflows and team use. Enterprise requirements can be discussed directly with JUNIQ.

JUNIQ supports download, email and sharing workflows and currently has Google and Microsoft sign-in pathways where enabled. Broader Gmail, Outlook, Calendar, Drive, OneDrive, CRM and enterprise integrations should only be treated as live where JUNIQ explicitly marks them as connected and production-ready. Contact JUNIQ for a current integration assessment.

JUNIQ uses Stripe for eligible subscription and payment processing. Sensitive payment-card handling is performed through Stripe’s payment infrastructure rather than being displayed or stored directly in the JUNIQ interface.

JUNIQ can help explain, organise, summarise and prepare information, but AI outputs can be incomplete or inaccurate. Review important outputs before relying on them. JUNIQ is not a substitute for qualified professional advice where professional judgement is required.

Email hello@juniq.com.au or use the Contact page. You can also use the Help Centre and System Check for product, browser, microphone or recording support.