Minutyx

Trust Center

Security & data protection

Last updated 16 October 2026

Minutyx turns your meetings into transcripts, summaries and answers — which means your most sensitive conversations pass through it. Protecting that data is foundational, not an afterthought. This page explains, plainly, how we handle it. Security questions or want to report an issue? Email nshabalala@aisoft.co.za.

Our principles

You own your data

Your recordings, transcripts and summaries are yours. We never sell them and never use your content to train AI models.

Private by design

Your data is stored in the European Union and isolated per account, so one user can never reach another’s meetings.

You stay in control

Export everything or delete it — a single meeting or your whole account — whenever you want, from inside the app.

Compliance & standards

Minutyx is built and operated to align with the data-protection laws that apply to us and our customers. We believe in being precise about what that means, so here is exactly where we stand:

POPIA — aligned GDPR — aligned DPA available PAIA manual SOC 2 — roadmap HIPAA — roadmap
Being straight with you: Minutyx is designed to meet South Africa’s POPIA and the EU/UK GDPR, we provide a Data Processing Addendum for business customers, and we maintain a PAIA manual. We are not yet SOC 2, ISO 27001 or HIPAA certified — those require independent third-party audits, and we’ll pursue them as we grow into larger organisations rather than claim them before they’re real. If a formal certification is a requirement for your team, tell us and we’ll talk about timelines.

Data ownership & privacy

Where your data lives

Your account, meetings, transcripts, summaries and audio files are stored on Google Firebase / Google Cloud infrastructure in the European Union (europe-west1, Belgium). Transcription and AI summarisation are performed by a third-party provider in the United States; payments are handled by Paystack. These trans-border flows are disclosed and governed in our Privacy Policy and Sub-processors list.

How we protect it

We apply reasonable and appropriate technical and organisational measures across the service:

Infrastructure & hosting

  • Google Cloud / Firebase infrastructure
  • Data stored in the EU (europe-west1)
  • Encryption in transit (TLS/HTTPS)
  • Encryption at rest by the cloud platform

Application & access

  • Per-account data isolation, enforced server-side
  • Hardened database & file-storage rules
  • Time-limited signed URLs for audio playback
  • Live audio proxied through our own relay — long-lived provider keys never reach the browser

Accounts & authentication

  • Firebase Authentication (Google or email + password)
  • Passwords are hashed by our auth provider — we never see them
  • Sign-in restricted to authorised domains

Payments

  • Processed by Paystack, a PCI-DSS compliant provider
  • We never receive or store your full card number
  • Only a card brand + last four digits are shown to you

You’re in control of your data

Sub-processors

We keep our sub-processor list short and transparent — a third-party speech-to-text & AI provider (United States), Google Firebase / Google Cloud (European Union) and Paystack (payments). The full breakdown of what each processes and where is on our Sub-processors page, which we update before material changes.

Reporting a security issue

If you believe you’ve found a security vulnerability or a data-protection concern, please email nshabalala@aisoft.co.za with the details and steps to reproduce. We’ll acknowledge your report, investigate, and keep you updated. Please give us a reasonable chance to remediate before any public disclosure. If a security compromise ever affects your personal information, we’ll notify you and the Information Regulator as POPIA requires.

Frequently asked

Who owns my meeting data?

You do. As between you and us, you retain all rights in your recordings, transcripts and summaries. We process them only to provide the Service to you, and we never use them to train AI models. See Terms, section 6.

Where is my data stored?

On Google Firebase / Google Cloud in the European Union (europe-west1, Belgium). To transcribe and summarise, audio and transcript text are sent to a third-party provider in the United States. See the Privacy Policy.

Do you use my recordings to train AI?

No. Your content is used only to generate your transcript, summary and answers. We do not use it — or your voice — to train, fine-tune or improve any AI model, ours or our providers’, and we never sell or license it.

What happens when I delete something?

Deleting a meeting removes its record and its stored audio from our active systems. Residual copies in routine backups are overwritten in the ordinary course. You can also request full account deletion. Billing records are kept only as long as tax and financial-record law requires. See the Privacy Policy, section 7.

Are you SOC 2 or HIPAA certified?

Not yet. We’re POPIA- and GDPR-aligned and offer a DPA, but we don’t hold SOC 2, ISO 27001 or HIPAA certifications today — and we won’t claim certifications we don’t have. They’re on our roadmap as we serve larger organisations. If you need one, contact us to discuss.

Am I allowed to record the people in my meetings?

Only if you have the right and any consent the law requires. You’re responsible for getting consent to record and process each participant’s personal information — see our Acceptable Use Policy.