Skip to main content
Rifflo
Sign in

Privacy Policy

How Rifflo handles accounts, audio processing, cloud providers, storage, cookies, and privacy requests on voice-remover.com.

Last updated: 2026-11-05

Rifflo privacy policy

This policy describes the Rifflo audio tools at voice-remover.com. For privacy questions or requests, contact support@voice-remover.com. The customer-facing service name is Rifflo; the payment merchant display name is voice remover.

What stays on your device

Browser audio editing, playback, measurements, and local project storage use your device. A locally opened file is not automatically sent to an AI service merely because you play or edit it. Browser storage can be cleared by your browser or device, so keep your own copies of important recordings and exported results.

Some features require a server. Choosing cloud separation, cloud speech processing, a link import, transcription, sharing, or an online account can send information beyond your device. Check the feature description before using it with sensitive recordings.

Information used by each feature

  • Account: your email address, account name, authentication records, sessions, and account settings. Passwords are stored as hashes rather than readable passwords. If you choose Google sign-in, we receive the identity information you authorize through Google.
  • Cloud audio processing: your selected audio or video, the requested operation, relevant settings, job status, and output files. Cloud AI processing uses Replicate. The files required to perform that task are sent to the processing service.
  • AI-assisted editing: when enabled, your instruction and relevant audio measurements or settings are sent through OpenRouter to a model provider. This is separate from browser-only editing. Do not include confidential personal information in instructions.
  • Link import: the link you submit and the media needed for your requested operation. Only import material you are entitled to use. The source website can apply its own rules and logging.
  • Sharing and profiles: content you choose to share or publish becomes accessible through its public URL. A person with a link may save or redistribute what they can access; deleting a link cannot recall their copies.
  • Payments: if paid checkout is available, Stripe handles payment details. Rifflo keeps the order, subscription, payment status, and identifiers needed to deliver access and support billing. We do not receive your complete card number.
  • Support and service operation: the information you send to support, request and error information, and usage records needed to prevent abuse, enforce allowances, and diagnose failures. Anonymous usage counters use hashed network-address identifiers; our infrastructure also processes network connection information.

We use this information to provide the feature you request, secure accounts, enforce published limits, process authorized payments, and respond to support or privacy requests. We do not sell uploaded audio. Rifflo does not use your uploaded recordings to train its own models. Processing providers have their own terms and privacy practices; this statement does not replace them.

Hosting and other providers

Cloudflare provides the website infrastructure, database, file storage, and transactional email delivery. Replicate provides cloud audio inference. Google provides optional identity authentication. OpenRouter is used for enabled AI-assistant features. Stripe is used when paid checkout is enabled.

Relevant provider notices: Cloudflare, Replicate, Google, OpenRouter, and Stripe. Providers can process information in multiple countries. We do not promise that all processing remains in your country or that a provider follows a shorter retention period than its own terms allow.

Storage and retention

Our application distinguishes temporary processing files from saved or published work. Its scheduled cleanup targets the following periods:

  • cloud result cache and imported media: 24 hours;
  • abandoned temporary upload files: 24 hours; completed job inputs are removed when their task finishes;
  • shared files and video cache: 30 days;
  • completed tool-job records: 1 hour; completed import-job records: 24 hours;
  • usage counters: 35 days.

These are application cleanup schedules, not a guarantee that every infrastructure copy disappears at exactly the same instant. An interrupted server or failed cleanup can delay removal. Saved account content, published profiles, billing records, support correspondence, provider-held data, and backups follow their own lifecycle and are not all covered by the temporary-file timers. Billing records are not currently erased by an automatic short-term retention timer.

Keep your own source recordings and exports. Temporary processing storage is not a permanent backup service.

Cookies, browser storage, and security

Cookies and browser storage support authentication, language or appearance preferences, local projects, and the operation of the tools. Security and infrastructure services may also set cookies needed to protect the website. Clearing them can sign you out or remove local work.

We use HTTPS, access controls, hashed credentials, and encryption for configured service secrets. These measures reduce risk but do not make storage or transmission infallible. Do not upload recordings you are not authorized to disclose to the selected cloud processor.

Your choices and requests

You can use available browser tools without creating an account, choose whether to use cloud features, and remove local data through your browser. Account controls provide account deletion; a live subscription must be cancelled first. Account deletion does not erase copies already downloaded by other people or automatically override a provider's legal retention requirements.

Contact support@voice-remover.com to request access, correction, deletion, or information about your account data. We may need to verify that a request concerns your account. The rights and exceptions that apply depend on your location and circumstances. This page does not limit mandatory privacy rights.

Rifflo is intended for people able to agree to the Terms of Service. Do not submit recordings containing another person's private information without appropriate permission. We update this page when our practices change and display the revision date above.