This beta collects only what is needed to deliver and protect a voice training run or voice conversion: a random browser journey ID, a pseudonymous browser-scoped participant ID, a one-way network quota identifier, submitted audio, selected settings, job status and diagnostics, generated model files, timestamps, and basic request information used for security and rate limiting. The network quota identifier helps enforce welcome-credit and conversion allowances without storing a raw IP address in the NiceVois job record.
Owner activity monitoring
The beta owner can see a private timeline showing pseudonymous visits, public pages viewed, broad referral categories such as Google or ChatGPT, audio selection, upload, training stages, completion, failure, and model-file downloads. If NiceVois asks how you found the service and you tap an answer, that answer is shown separately from the browser-observed referral category. If you answer the optional question about what you hoped to accomplish, the selected reason, any text you enter under “Something else,” the point where the question appeared, and later product outcomes are linked to your pseudonymous participant in a durable product-research record without a fixed automatic expiry or response cap. Do not put sensitive or identifying information in that free-text answer. For voice conversions, the dashboard may also record whether the normal or NiceVois-cleaned result was played, aggregate playback seconds, repeated plays and download selections, conversion type and pitch setting, processing time, and privacy-safe cleaning diagnostics such as how many consonant or breath regions were restored. The ordinary journey timeline is kept in the same pseudonymous form without a fixed automatic expiry, so that NiceVois can understand how the product is used over time; the owner dashboard reads the most recent 90 days by default. Conversion usage, technical results, and normal-versus-cleaned engagement are kept in a separate durable product ledger without a fixed automatic expiry or event-count cap so that NiceVois can compare product versions over time. This monitoring does not contain source audio, converted audio, playback position, IP addresses, raw audio filenames, full referring URLs, search-query text, or microphone data. An account email may appear in the private owner dashboard when a pseudonymous participant has chosen to sign in.
Agent account connections and agreement receipts
When you connect NiceVois to a coding agent or chat plugin, Auth0 handles sign-in and may process your account email, profile, OAuth consent, and session data. NiceVois receives an OAuth account identifier and permission scopes, derives a pseudonymous participant identifier for private jobs and beta limits, and records that a job came through an agent connection. NiceVois may give the authenticated agent a short-lived private account link that signs the browser into that same pseudonymous NiceVois identity for balance checkout and job access; the link expires after ten minutes and contains no Auth0 access token. If you accept the standing voice-training agreement, NiceVois stores that pseudonymous identifier, the agreement version, acceptance time, and connection type so you are not repeatedly asked to accept unchanged terms. The receipt does not contain your audio or model. It is kept while needed to provide the connected service and document the agreement, and may be retained afterward where reasonably necessary for security, disputes, or legal obligations. You can revoke the connection through the client or identity provider and may request deletion through contact NiceVois.
How the data is used
The data is used to train the RVC voice model you request, show progress, provide downloads, compare the usefulness of normal and NiceVois-cleaned conversion results, apply capacity and safety limits, prevent abuse, diagnose failures, notify the beta owner about important service milestones, and measure demand, reliability, and cost. It is not sold and is not used to advertise to you.
Support messages and AI chat
If you use the contact form, NiceVois stores the name you provide, your email address, your message, an optional job reference, and the pseudonymous browser identifiers associated with the request. This information is kept in a private support inbox for up to 180 days so the owner can reply and investigate issues. AI support questions, answers, the NiceVois page where the question was asked, and pseudonymous browser identifiers are stored privately for up to 90 days so NiceVois can understand common questions and improve support. Do not include passwords, payment details, or other sensitive information. You can instead email info@nicevois.com.
Completion emails and product updates
If you ask to be emailed when a model is ready, we store your email address, the related job identifier, signup time, the page where you joined, your pseudonymous browser identifiers, and the consent wording version. We use the address for the one-time completion alert and add it to the NiceVois product update list for major training improvements, new capabilities, and availability updates, as stated beside the form. We record delivery attempts so failed alerts can be retried without sending duplicates. We do not sell your email. Product update emails will include a way to unsubscribe; you may also ask info@nicevois.com to remove you at any time. Signup records are kept until you unsubscribe or the update list is retired.
Sharing rewards and referrals
If you use a personal NiceVois referral link, we store the referral code, the pseudonymous accounts connected by that link, attribution and completion timestamps, qualifying training-job identifiers, credits issued, and anti-abuse signals such as whether both accounts used the same one-way network quota identifier. When you request the public-mention reward, we also store the public post URL, platform, your disclosure confirmation, review status, review note, and reward record. The owner uses the submitted URL only to verify the mention and required disclosure. NiceVois cannot identify or collect every independent mention of the service. These records are retained as needed to operate the program, prevent duplicate rewards, and maintain the balance audit trail.
AI support
When you use NiceVois Support, your recent chat messages and the NiceVois page you are viewing are sent to OpenAI to generate a product-support reply. NiceVois does not send your source audio, model files, email address, job record, or private browser identifier in that request. OpenAI states that API data is not used to train its models unless the account holder explicitly opts in, but prompts and replies may be retained for up to 30 days for abuse monitoring. NiceVois may review chats for safety and to improve support quality. Do not include passwords, payment details, private audio, or other sensitive information in chat.
Voice processing, storage, and deletion
NiceVois analyzes vocal characteristics in submitted audio to train the requested voice-conversion model. It does not use the audio for login, authentication, or matching a person against an identity database, although some laws may regulate voice characteristics or voiceprints as biometric data. After successful validation, NiceVois removes the full-resolution source upload and temporary training files but keeps a private, compressed listening preview with the trained model. That preview is shown only to the model owner and follows the same retention and deletion lifecycle as the model. Failed jobs may retain source audio long enough to support a retry. For a free training, the listening preview and the generated .pth, .index, and ZIP package are deleted seven days after creation; a model trained on a paid plan or pass is kept for as long as the account exists. The job record itself - model name, settings, timings, and outcome, never audio - is kept as part of the account's history and is removed when the account is deleted. If you bring an existing RVC model to the converter, NiceVois privately stores the selected .pth and any matching .index from the ZIP so that model remains available to your browser or signed-in account. It is not added to a public catalog or used to train another model, and you can remove it from the converter at any time. Signed file and audio links should not be shared. Without sign-in, your private model library is tied to this browser and clearing site data may remove access. Signed-in website accounts and connected coding-agent accounts use their account identity instead.
Retired image-model experiment
NiceVois no longer offers image-model training. For an image-model run made while that experiment was open, NiceVois privately stores the permitted images you submitted (any common still-image format; exotic formats were converted to PNG on arrival), the subject category, a generated trigger word, captions created for the training dataset, job diagnostics, and the resulting portable package. The images are used only to perform the requested job, are not added to a public catalog, and are not used to train a general NiceVois model. Source images and local artifacts are scheduled to expire after seven days; aggregate funnel, timing, failure, download, and estimated-cost records remain so NiceVois can measure whether this workflow is useful. The private owner dashboard marks owner benchmarks separately from customer demand.
Processors
The service uses cloud hosting, private object storage, cloud GPU providers, OpenAI for AI-generated product support, Resend for opted-in transactional email delivery, and—when enabled—a private owner-notification endpoint to process and store the data. Data may therefore be processed in locations selected by those providers.
Your choices
Do not upload sensitive audio that you are unwilling to send to cloud providers. Download your package before expiry. To request deletion of a model, its associated pseudonymous conversion analytics, or other account data, or to report a privacy concern, contact NiceVois and include the model name and approximate creation time; do not send the audio again.