We do not store your files. We only process them.
This Privacy Policy explains how Vislun ("we", "us") collects, uses, and protects data when you use the Vislun application and related services. Vislun is an AI-powered meeting intelligence service.
For privacy matters, contact us at support@vislun.online or through the in-app help feature.
This policy applies to all users — registered and guest — and, to the extent described in Section 10, to individuals whose conversations are processed through Vislun. It forms an integral part of our Terms & Conditions.
Name and email address when you register; if you sign in with Google, we receive your name, email, and Google account identifier. We never receive your Google password.
Audio files, live recordings, meeting bot recordings, imported documents, pasted text, and links you provide — handled strictly under the No-Storage Design described in Section 4.
Transcripts, summaries, and analyses generated from your content, together with session metadata (session name, date, duration).
A log of each per-session recording confirmation you make, with timestamp and session identifier.
Google Play informs us of your subscription or credit purchase status (product, order state, expiry). We never receive your card number, bank details, or any payment credentials.
IP address, device and app version information, and service logs generated when you use the app — used for security, abuse prevention, and troubleshooting.
We do not access your device's contacts, photos, or files beyond what you explicitly submit, and we do not access your location. We do not use advertising or tracking SDKs.
We use data solely to:
We do not sell your data. We do not use your data for advertising. We do not use your content or output to train AI models. We have selected sub-processors whose terms state that customer data is not used to train their models.
We do not store your files. We only process them.
Vislun is deliberately engineered so that the files you submit never remain on our systems:
Audio files you upload, live recordings, meeting bot recordings, and imported documents (PDF, Word, PowerPoint). Deletion happens as soon as transcription of that session is complete — on every session, on every plan, without exception. Deleted files cannot be recovered by you, by us, or by anyone else.
Original audio playback does not exist in Vislun. Once your transcript is ready, the source recording is gone. If you need the original file, keep your own copy.
Pasted text, and text retrieved from links you provide, require no transcription — the text itself directly becomes the session transcript. It is therefore stored as output (see Section 6), not as a source file.
Only the output — transcripts, summaries, analyses — and basic session metadata (session name, date, duration). You can delete any session, or your entire account, at any time.
For any summary, you may enable the auto-delete option, which permanently deletes that session's output 30 days after activation. Once enabled, auto-deletion cannot be cancelled or reversed — the deletion is scheduled immediately and is final. Deleted output cannot be recovered by you, by us, or by anyone else.
If a processing job fails partway, any residual file is removed by an automated cleanup mechanism within 24 hours.
Data that is not stored cannot be leaked, stolen, or misused. This is our core security principle — the safest place for your recordings is nowhere.
We use a small number of trusted service providers ("sub-processors") that process data solely on our instructions to operate Vislun. Sub-processors are bound by data processing agreements and may not use your data for their own purposes.
| Sub-processor | Purpose | Location |
|---|---|---|
| Google Cloud | Infrastructure, storage, AI analysis | Asia-Pacific region |
| Groq, Inc. | Audio transcription | United States |
| Google Play | Payment processing | Per Google's infrastructure |
Because audio transcription is performed in the United States, audio you submit is transferred there for the duration of processing only and is deleted upon completion under the No-Storage Design in Section 4. Transfers are protected by encryption in transit and by our sub-processors' contractual data protection commitments. Stored output and account data reside on Google Cloud infrastructure in the Asia-Pacific region and are not transferred elsewhere.
We may add or replace sub-processors from time to time. This list is kept current in this policy; material changes will be notified to users before taking effect.
| Data | How long we keep it |
|---|---|
| Submitted files (audio, recordings, documents) | Deleted immediately upon transcription completion; residual files from failed jobs removed within 24 hours |
| Output (transcripts, summaries, analyses) | Until you delete the session or your account; sessions with auto-delete enabled are permanently deleted 30 days after activation |
| Output after paid access ends (Inactive status) | Read-only for 12 months, then permanently deleted (with email notice beforehand) |
| Guest session results | Not stored; available only during the active session |
| Account data | Until account deletion |
| Dormant free accounts (no sign-in for 12 months) | Deleted after email notice and a 30-day response window |
| Consent confirmation logs | Retained after account deletion, for legal compliance and dispute defense |
| Technical logs | Retained for a limited period for security purposes, then deleted or anonymized |
Deletion under this policy is permanent: deleted data cannot be recovered by you, by us, or by anyone else.
One transparent limitation: consent confirmation logs are retained after account deletion, as described in Section 6, because they serve as legal evidence of recording confirmations. They contain confirmation events — not your meeting content.
We protect data through encryption in transit and at rest, strict access controls, network-level protections, and the structural safeguard that matters most: files that are deleted cannot be breached. Our data minimization design means the most sensitive material — your recordings — exists on our systems only for the minutes it takes to process them.
No system is absolutely secure. You are responsible for keeping your account credentials confidential. If we become aware of a personal data breach affecting you, we will notify you and the relevant authorities as required by applicable law.
Vislun is not intended for individuals under 17, and by creating an account you confirm that you meet this requirement. We do not knowingly collect data from children, and we do not proactively verify the age of our users.
If you believe an account belongs to a child under 17, you may report it to support@vislun.online. Reports must include a reasonable basis — we do not act on unsubstantiated reports, and third-party reports alone never result in automatic deletion.
Where we obtain credible evidence that an account holder is under 17, we handle it with care rather than penalty:
A child's misstatement of age is treated as a reason to end the relationship gently — never as misconduct to be penalized.
Vislun processes conversations, and conversations involve people other than our users. This section is addressed both to our users and to anyone whose voice or words may have been processed through Vislun.
You act as the party responsible for the meetings you record. Before recording or submitting any conversation, you must inform all participants and obtain any consent required by applicable law, and you confirm this before every session. Vislun processes participants' data (voices, spoken words, names mentioned in conversation) solely on your instruction, as a processing tool.
A Vislun user may have recorded a meeting you attended. You should know:
When the Vislun meeting bot joins an online meeting, it appears as a visible, identifiable participant. It cannot join without being admitted by someone in the meeting.
We may update this policy from time to time. Material changes will be notified via in-app notification, push notification, or email before taking effect. The "last updated" date at the top of this policy always reflects the current version, and previous versions are archived.
Questions: support@vislun.online