Privacy Policy

Effective Date: July 20, 2026

1. Data Controller

ViLine is operated by Andrii Tretiakov.
Ovanesa Tumanyana 3, Kyiv, Ukraine
Contact: support@viline.info

2. Information We Process

Account and contact information

When you create an account, sign in, recover a password, contact support, or send feedback, we process your email address, account identifier, authentication tokens, password recovery token, and the message you submit. Passwords are stored as password hashes, not plaintext.

Device, technical, and usage information

The app sends a randomly generated installation identifier and technical information needed to operate the service, such as app version, device model and manufacturer, Android version, SDK level, locale, language, region, timezone, device type, emulator status, and available memory. Our backend may record the IP address, date and time, account or guest identifier, and technical information for authenticated activity and support purposes.

Subscriptions and notifications

If applicable, we process subscription platform, subscription identifier, plan, status, and relevant subscription dates. If you enable notifications, we process the notification subscription endpoint or device token needed to deliver them.

Content you choose to submit for online processing

The app sends audio, video, text, subtitles, captions, and related processing settings only when you select an online feature, including audio restoration, denoising, transcription, video stabilization, text splitting, and text-to-speech. We process the content to provide the requested result.

Analytics and crash reporting

The Google Play version uses Firebase Analytics and Firebase Crashlytics. These services process app-instance, installation, advertising, and crash-reporting identifiers; masked-IP-derived approximate location; app lifecycle and interaction data; crash stack traces; relevant app state; and device metadata. We use this information to understand app usage and diagnose stability issues.

Third-party searches

When you use GIF or sticker search, your search query and standard request metadata are sent to Giphy. When you use music search or streaming, your search query and standard request metadata are sent to Jamendo.

3. How We Use Information

4. Service Providers and Recipients

We do not sell personal data. We use service providers to operate the app, including:

These providers process information under their own terms and privacy policies. We may also disclose information when required by law or necessary to protect rights, safety, or security.

5. Security

Public ViLine API traffic uses HTTPS. Authentication tokens are stored by the Android app using Android Keystore encryption. No method of transmission or storage is completely secure, but we use reasonable technical and organisational measures to protect information.

6. Retention

We retain information for as long as necessary to provide the service, meet legal obligations, resolve disputes, and enforce agreements. Retention by Firebase, Google Cloud, OpenAI, Giphy, Jamendo, email, notification, and other service providers is governed by their applicable policies.

7. Your Rights and Deletion Requests

Depending on your jurisdiction, you may have rights to access, correct, delete, restrict, or obtain a copy of your personal information, or to object to certain processing. To request account or personal-data deletion, email support@viline.info from the email address associated with your account. We may retain information where required by law or for legitimate security purposes.

For account-deletion instructions, see Delete your ViLine account.

To request deletion of specific data without deleting your account, see Request deletion of your ViLine data.

8. Children's Privacy

ViLine is not directed to children under 14. If you believe that a child has provided personal information, contact us and we will review the request for deletion.

9. Changes to This Policy

We may update this policy when our practices or legal obligations change. The current version is published on this page with its effective date.