Privacy Policy

1. What we collect.

Account information (name, email, hub). Session metadata (participants, times, durations, language pair, selected voice). Session content generated during use (transcripts, chat messages, shared files, AI summaries, host notes, and computer-generated translated audio). Billing records (credits, charges, promo redemptions). Security and audit records: when you sign in or take a significant action in a hub, we record the event together with the IP address and browser user agent the request came from. If you join a call as a guest, we handle the display name given for you and the content of that session, but you have no account and we do not create a profile for you.

2. What we never do.

We do not sell your information. We do not share your conversations with advertisers or data brokers. We do not use your call content to train AI models. We do not show third-party advertising, and we run no advertising or third-party tracking cookies.

3. Artificial intelligence and automated processing.

MAIK Voice is built with AI, and AI is embedded in the service itself. Automated systems process your sessions for one purpose: to deliver the service — speech recognition, translation, voice synthesis, transcription, and post-call summaries. Summaries are generated by an AI provider from the session transcript. We want to be precise about what we do not do: we run no automated content moderation, no safety classifier, and no abuse detection over your conversations. Nothing automatically flags, scores, or reports what you say, and no system transmits your content to authorities on its own. By using the service you acknowledge the automated processing described here.

4. Human review, reports, and staff access.

We do not listen to or read your conversations in the ordinary course, and there is no staff tool for browsing another hub's session content. There is one path by which our staff can see conversation content: if a user or guest reports a conversation to us, the report is stored with a snapshot of the reported messages and sent to our staff, who read it in order to act on it. Reports are filed by people, never by an automated system. Separately, our staff can access account, hub, and billing records to operate and support the service, and we may access content where we are legally compelled to. We may report unlawful activity to competent authorities and respond to lawful requests from them.

5. Retention — most of your conversation expires.

We separate what you say from what you pay. Your live voice is processed in real time and is never stored as a recording. The computer-generated translated audio kept for replay is deleted about 24 hours after a session ends, by a sweep that runs every hour. Transcripts, chat messages, shared files, and host notes are deleted 30 days after the session ends, together with the underlying stored files. Two things outlive that window and you should know it: AI-generated session summaries and session metadata (duration, participants, cost) are kept for the life of the hub, not 30 days. Export what your records require before the 30-day window closes. Ended session links stop working the moment a session ends. Financial and account records contain no conversation content and are kept for as long as your account exists and afterwards as accounting and legal obligations require. Security and audit records are also retained. To keep the service fair we record usage measures such as total meeting minutes per month.

6. Information security.

Traffic between your browser and the service travels over encrypted connections (TLS/HTTPS, and encrypted websockets for live sessions). Data at rest is encrypted by the infrastructure our database, storage, and hosting run on. Each hub's data is separated at the database level by row-level security policies, so one hub's rows are not readable by another; operations that must cross that boundary run only in server-side code behind an authorization check, never in your browser. Stored session audio and shared files live in private storage buckets that are not publicly readable. Administrative credentials are held server-side only and are never exposed to the browser. Raw participant audio is never written to storage. The retention sweeps described above run automatically. We hold no security certifications and we make no certification claims.

7. Service providers.

We use specialist service providers to operate MAIK Voice. Each processes data only to deliver the service on our instructions, under contract, and is not permitted to use it for its own purposes. We describe them below by the function they perform and the data they receive; which companies we contract with is commercially confidential and is not published here. A category may cover more than one provider — we run a primary and a backup for both speech recognition and voice synthesis — and the providers behind a category may change as the service evolves. The categories below are current as of the date above.

Real-time call infrastructure

Carries live audio and video between participants; no recording is enabled.

Speech recognition

Receives live session audio and returns text.

Machine translation

Receives session text and returns it in the other language.

Voice synthesis

Receives the translated text to be spoken and returns audio.

AI summarization

Receives the session transcript text to produce the post-session summary.

Payments

Processes credit purchases. Receives payment details; we never receive or store full card numbers.

Database, authentication and storage

Holds account, hub, session, and billing records and the stored session files.

Hosting and delivery

Serves the application, and provides the cookieless aggregate web analytics described in section 9.

Transactional email

Receives recipient addresses and the content of service emails.

Error monitoring

Receives technical error reports, configured to strip request contents, user identifiers, and context before sending.

8. International processing.

MAIK Voice operates from Mexico. The providers described above run on infrastructure located in the United States and other countries, so your information — including session content during its retention window — is processed and stored outside Mexico. Where personal data is transferred across borders, those transfers rely on the contractual safeguards in our agreements with each provider, which oblige them to process the data only on our instructions and to protect it. Our retention and no-selling commitments apply regardless of where the data is processed.

9. Cookies and local storage.

We use only first-party cookies. Essential cookies keep you signed in, keep the service secure, and let an invited guest join a single session. If you arrive through a partner's referral link we also set one first-party cookie (mv_aff, 60 days) recording only which partner referred your first visit, so a referral credit can be attributed; it holds no personal data, only the first referrer is ever kept, and it is never used to track you across other sites. Your browser also stores interface preferences on your device (things like sidebar state and sound settings) — these stay on your device and are not profiles. Our web analytics is cookieless and aggregate: we keep country-level visit and click counts derived from a network-level country signal, and we do not use your IP address for analytics or build per-visitor profiles. We do record the IP address and browser user agent in our security and audit records when you sign in or take a significant action, which is a security measure rather than analytics. We use no advertising or third-party tracking cookies.

10. Isolation and access.

Each hub is a fully isolated workspace, and each account belongs to exactly one hub. Access to the service is by invitation only. Within a hub, what a person can see and do depends on their role — administrators manage members, settings, and credit; team leaders run sessions; members take part in them. Sensitive operations are restricted to server-side code.

11. Security incidents.

If a security incident affects your data, we will notify affected hubs in writing within 72 hours of confirming it.

12. Children.

MAIK Voice is not intended for users under 18 and we do not knowingly collect personal data from minors. If you believe a minor has given us personal data, write to us at the address below and we will delete it.

13. Your rights and choices.

You may request access to, correction of, or deletion of your personal data, object to its processing, or revoke consent you have given, by writing to contact@maikvoice.com (rights of access, rectification, cancellation, and opposition — "ARCO" — under Mexican data protection law, and equivalent rights under other applicable laws). You can also delete your account from Settings: deletion closes the account immediately and it stays recoverable for 30 days, after which it is permanently purged. After that purge, billing and ledger records and session metadata are retained in de-identified form — with the acting person's identity removed — because accounting and legal obligations require it, and security and audit records are retained. Separately, a hub with no activity for 11 consecutive months receives a warning email at its administrators' addresses, and is disabled 30 days later if it is still inactive, at which point any remaining credit balance is zeroed; activity during those 30 days cancels the closure. We keep a record of that warning — an audit entry, and a delivery log entry naming the address it was sent to — for as long as the hub exists.

14. Changes and privacy contact.

We update this policy as the service evolves; the current version always lives at this page and carries the "last updated" date above. Our Privacy Contact for any question or request under this policy, including data-subject rights requests, is contact@maikvoice.com.