Privacy Policy

Scope of this policy

This policy applies to swifttool.org, app.swifttool.org, cloud.swifttool.org, SwiftTool support tools, administrative systems and any official SwiftTool Telegram bot or automation flow connected to the service.

• The main website explains the product and receives support requests.
• The web app handles login, registration and future user workflows.
• The cloud endpoint supports private server-side download and processing jobs.

Account and profile data

When accounts are enabled, SwiftTool may process your name, email address, username, password hash, authentication method, Google OAuth identifier, avatar URL, language, timezone, consent choices and account status.

• Registration requires acceptance of the applicable terms and policies.
• Google login uses information returned by Google after you approve the sign-in flow.
• Session and security records help keep your account signed in and protected.

Telegram bot data

If you use an official SwiftTool Telegram bot, the service may process Telegram user ID, username, display name, chat ID, message text, commands, files, URLs, language, support messages and timestamps needed for the requested action.

• Bot data is used to run commands, send workflow updates, deliver support replies and notify administrators.
• Telegram controls Telegram accounts, chats, message delivery and platform-level privacy settings.
• Do not send the bot media, links or personal information you are not allowed to process.

Media, uploads and generated outputs

SwiftTool may process files, URLs, subtitles, captions, transcripts, translations, separated vocals, audio stems, converted files, thumbnails, metadata, job identifiers, queue status and generated download links.

• Media is processed to provide the workflow you requested.
• Generated outputs may be temporarily stored so you can download or review them.
• Large or failed jobs may keep operational metadata for debugging and support.

Support, feedback and not-bot checks

Support and feedback forms may collect your name, email address, message content, selected topic, platform, priority, not-bot confirmation, IP address, user agent and submission timestamp.

• Support messages can be forwarded to the configured Telegram administrator.
• Not-bot confirmations help reduce spam and automated abuse.
• Include a job ID, account email or Telegram username only when it helps support identify your request.

Technical and security data

SwiftTool may collect technical records such as IP address, browser user agent, device type, requested URL, referral data, timestamps, cookie consent state, login attempts, CSRF events, admin actions and download endpoint access logs.

• These records are used for security, debugging, analytics, reliability and abuse prevention.
• Admin activity can be logged to protect site content, settings, users and uploads.
• Sensitive runtime files should remain outside public web roots.

How information is used

Data is used to provide SwiftTool services, run media processing workflows, authenticate users, operate the Telegram bot, answer support requests, send service notices, enforce limits, detect abuse and comply with legal obligations.

• Run subtitle, translation, separation, conversion, download and automation jobs.
• Show dashboard status, job history, queue progress and future web app features.
• Protect accounts, admin areas, cloud endpoints and private processing infrastructure.

Cookies and local storage

SwiftTool uses necessary cookies and browser storage for sessions, CSRF protection, consent choices, interface preferences and accessibility settings. Optional analytics or marketing tools should only load after consent where required.

• Necessary security cookies cannot be disabled from the site controls.
• Accessibility and interface preferences may be stored locally in your browser.
• You can change cookie choices from the footer when the cookie controls are available.

Sharing and processors

SwiftTool may use service providers for hosting, infrastructure, Telegram bot delivery, Google OAuth, email or support delivery, payments, analytics, AI processing, media conversion and security monitoring depending on the final production setup.

• Only connect processors that are needed for the service.
• Review third-party terms before sending sensitive media to external systems.
• Telegram and Google process data under their own policies when you use their platforms.

Cloud endpoint and downloads

cloud.swifttool.org is used as a private endpoint for download and processing infrastructure. It should not expose public directory listings, private storage, configuration files or unrelated server data.

• Authorized links or backend rules may control access to generated files.
• Download requests may be logged for security, debugging and abuse prevention.
• Unknown visitors should use the main SwiftTool website instead of the cloud endpoint.

Retention

Retention periods depend on the production configuration, account status, active jobs, support needs, legal obligations and security requirements. Raw media and generated private outputs should generally be retained only as long as needed.

• Temporary uploads and generated files should be cleaned on a scheduled basis.
• Support and security logs may be kept longer when needed to investigate abuse or protect the service.
• Account deletion requests are handled where legally and technically possible.

Your choices and rights

You can contact SwiftTool support to request access, correction, export or deletion of personal data where applicable. You can also stop using the bot, delete local browser storage or change cookie preferences.

• Some records may be retained when required for security, fraud prevention, accounting or legal compliance.
• Deleting Telegram messages may not remove copies controlled by Telegram or other chat participants.
• Requests should include enough information to identify the relevant account, bot user or job.

Children and sensitive content

SwiftTool is intended for users who can lawfully use media processing tools and accept the applicable terms. Do not upload highly sensitive personal data unless the workflow is approved for that purpose.

• Do not upload private third-party content without permission.
• Do not use SwiftTool to create harmful, deceptive, illegal or abusive material.
• Parents or guardians may contact support about privacy concerns involving minors.

International processing

SwiftTool infrastructure, Telegram, Google and other processors may operate in different countries. By using connected services, data may be processed where those systems operate.

• Production deployments should document real processor locations.
• Use appropriate agreements and safeguards where required.
• Enterprise customers can request deployment-specific information before launch.

Changes and contact

This policy may be updated when SwiftTool adds features, changes infrastructure, adjusts retention, connects processors or updates Telegram bot behavior. For privacy, security or support questions, contact support@swifttool.org or use the support page.

• Material changes should update the last updated date.
• Keep a copy of production-specific processor and retention settings.
• This policy is a starter template and should be reviewed by a qualified professional before production launch.

Questions or corrections?

Send feedback if this page should reflect a production configuration, processor list or policy update.

Contact support