Privacy Policy
This Privacy Policy explains how AudioTextly collects, uses, handles, and protects information in connection with its website, audio transcription tools, and related services.
About This Policy
This policy covers information connected with website visits, support inquiries, uploaded recordings, generated transcripts, service providers, cookies, retention, security, disclosures, and privacy requests. Some disclosures depend on AudioTextly’s actual technical configuration and must be verified before this policy is published as a legally operative document.
1. Introduction
AudioTextly operates the website at https://audiotextly.com/ and provides an online audio-to-text conversion experience. This Privacy Policy describes the information practices associated with accessing the website, submitting recordings for transcription, using available website functionality, and contacting the AudioTextly support team.
This policy applies to the AudioTextly website and the related services operated under the AudioTextly brand. It does not establish AudioTextly as the legal name of the responsible business operator. If applicable law requires the identity and contact details of a controller, business, or other legally responsible operator, verified business information must be added before publication.
By using the website, visitors acknowledge that information may be handled as described in this policy, subject to the service’s verified technical operation and any choices or rights available under applicable law.
2. Information We Collect
The information associated with AudioTextly depends on how a visitor uses the website and which features are active. The categories below describe information that may be relevant to the service. Each category must be checked against the website’s actual configuration.
A. Information You Provide
When you contact AudioTextly through its Contact page or by email, you may voluntarily provide your name, email address, message subject, message content, and any other information you choose to include in your inquiry. AudioTextly should collect account, subscription, or billing information only if those capabilities are active and disclosed to users.
B. Audio Content
You may submit an audio recording for transcription. Depending on its contents, a recording may include voices, names, conversations, opinions, professional information, or other information relating to identifiable people. You are responsible for ensuring that you have the rights, authority, notices, and permissions required to upload and process a recording.
C. Transcription Results
A generated transcript may reproduce information contained in the submitted audio. It may therefore contain personal or sensitive information even when AudioTextly did not request that information directly. The precise storage, availability, and deletion behavior of transcripts must match the implemented transcription workflow and should be confirmed before sensitive recordings are submitted.
D. Technical Information
WordPress, the website’s hosting environment, security tools, and other relevant infrastructure may process technical information needed to deliver, maintain, and protect the service. Depending on the actual configuration, this may include an IP address, browser type, device information, requested pages, timestamps, referral information, access logs, error records, and service diagnostics. AudioTextly should disclose only the categories actually processed by its systems and providers.
3. Audio Uploads and Transcription Processing
When a user submits a recording through the audio-to-text converter, the file is made available to the systems required to perform the transcription. The specific processing flow—such as whether the file is uploaded to AudioTextly’s server, transmitted directly to an external transcription provider, or handled through another architecture—must be confirmed from the production implementation.
AudioTextly must verify and accurately disclose whether temporary files are created, where recordings and transcripts are processed, whether either is retained after processing, and what events trigger deletion. Until those details are confirmed, users should not be told that files remain only in their browser, are deleted immediately, or are never stored.
If an external speech-recognition or transcription provider receives a recording, the provider’s identity, role, relevant processing terms, and privacy information should be disclosed where required. The same applies to any cloud storage, hosting, or infrastructure provider that can access submitted recordings or generated transcripts.
Whether uploaded recordings or generated transcripts may be used to develop, train, evaluate, or improve artificial intelligence or speech-recognition models depends on AudioTextly’s configuration and its provider agreements. No statement excluding such use should be published until the relevant technical settings and contractual terms have been verified.
Users may contact support@audiotextly.com to ask about deletion of information associated with them. Whether a particular file can be located or deleted will depend on the actual storage architecture, available identifiers, applicable law, and any legitimate retention requirements.
4. How We Use Information
Subject to the website’s verified operation, information may be processed when necessary to provide requested audio transcription functionality, return or display transcription results, respond to support inquiries, maintain website features, diagnose technical problems, prevent misuse, protect the service, and comply with applicable legal requirements.
Technical and usage information may also be used to understand performance and improve usability where suitable tools are implemented and the required notices, consent mechanisms, or opt-out controls are provided.
This policy does not state that personal information is used for advertising, behavioral profiling, marketing, personalization, or model training. If any such activity occurs, it must be specifically verified and described before publication.
Where applicable law requires a legal basis for processing, AudioTextly must identify the basis that applies to each verified activity. Depending on the facts and relevant jurisdiction, a basis may involve performance of a requested service, legitimate interests, compliance with a legal obligation, or consent. Consent should not be presented as the basis for every activity unless that accurately reflects the service and applicable law.
5. Third-Party Service Providers
Operating a website and transcription service may require providers that perform technical functions on AudioTextly’s behalf. Depending on the active configuration, relevant categories may include website hosting, audio transcription, email delivery, analytics, security services, cloud storage, and—if offered—payment processing.
A provider may receive only the categories of information required for its particular function. For example, a transcription provider may need access to an uploaded recording, while an email provider may process contact details and message content submitted in a support inquiry.
AudioTextly must verify the providers actually in use, their purposes, the information they receive, their retention terms, and any restrictions on their use of submitted content. Provider identities and links to relevant privacy information should be added where required. No provider name has been included here without verification.
7. Data Retention
Retention periods must reflect AudioTextly’s actual systems and operational requirements. Relevant records may include contact inquiries, uploaded audio, generated transcripts, technical logs, and—if applicable—account or billing information.
AudioTextly has not supplied verified retention schedules for these categories. Exact periods must therefore be established and added before this policy is treated as legally complete. Arbitrary periods such as a fixed number of hours or days should not be published without evidence that the production systems enforce them.
When setting retention periods, AudioTextly should consider the purpose for which information was collected, storage design, provider settings, security needs, support requirements, applicable limitation periods, and any legal recordkeeping obligations. Information should be deleted or anonymized when it is no longer required, where technically feasible and legally appropriate.
8. Data Security
AudioTextly should use technical, organizational, and administrative safeguards appropriate to the information it processes and the risks presented by the service. Relevant safeguards may include encrypted transmission, access restrictions, secure infrastructure, maintained software, and monitoring for technical or security issues, but only measures that are implemented and verified should be represented as current practices.
No website, transmission method, storage system, or service provider can guarantee complete security against every risk. Users should exercise care when choosing the recordings and information they submit online.
This policy does not claim any security certification, independent audit, or end-to-end encryption arrangement. Any such statement would require current, documented verification.
9. Information Sharing and Disclosure
Information may be disclosed to service providers that perform necessary functions, subject to the actual arrangements described in this policy. This service-provider processing is distinct from disclosures made for a provider’s own independent purposes.
Information may also be disclosed where reasonably necessary to comply with applicable law or valid legal process; investigate fraud, abuse, or security incidents; protect users, the service, or others; or establish, exercise, or defend legal claims.
If ownership or control of the service changes through a merger, acquisition, financing, reorganization, sale of assets, or similar transaction, relevant information may be transferred as part of that transaction where legally permitted. This possibility should remain in the policy only if it is appropriate to the operator’s circumstances.
AudioTextly should not claim that information is never sold or shared for advertising purposes until analytics, advertising, embedded content, and all other third-party integrations have been audited under the definitions of applicable privacy laws.
10. International Data Processing
Website infrastructure or service providers may process information in countries other than the country where a visitor is located. Whether international processing occurs depends on AudioTextly’s hosting location, transcription provider, support tools, analytics services, and other verified arrangements.
AudioTextly must identify actual processing locations and determine whether applicable law requires contractual protections, adequacy findings, consent, risk assessments, or other transfer safeguards. No hosting country or international transfer mechanism is asserted in this policy without verification.
11. Your Privacy Rights
Privacy rights vary according to a person’s location, the nature of the information, AudioTextly’s role, and the laws that apply. Depending on those circumstances, a person may have rights to:
- Ask whether personal information relating to them is being processed.
- Request access to eligible personal information.
- Request correction of inaccurate or incomplete information.
- Request deletion in circumstances recognized by applicable law.
- Object to or request restriction of certain processing.
- Request eligible information in a portable format.
- Withdraw consent where processing is based on consent.
- Exercise applicable choices relating to advertising or profiling.
These rights are not universal or unconditional. Exceptions may apply, and AudioTextly may need to retain certain information or decline a request where permitted or required by law.
To submit a privacy-related request, email support@audiotextly.com. Include enough information to identify the relevant interaction without sending unnecessary sensitive information. AudioTextly may reasonably request additional details to verify the requester’s identity and authority.
Requests should be handled within the periods required by the law that actually applies. This policy does not promise a universal response deadline.
12. Children's Privacy
AudioTextly’s intended audience and minimum-age requirements must be established in its Terms and operating policies. This Privacy Policy does not invent a minimum age or claim compliance with a particular children’s privacy regime without a verified basis.
A parent or guardian who believes that information involving a child has been submitted to AudioTextly may contact support@audiotextly.com. AudioTextly should evaluate the request, applicable age rules, consent requirements, and any necessary deletion or restriction measures under the relevant law.
13. External Websites
AudioTextly may contain links to websites or services operated by other parties. Those external services may collect information and apply privacy practices that differ from AudioTextly’s practices.
This policy does not govern an external website merely because AudioTextly links to it. Visitors should review the privacy information supplied by each external service they choose to access.
14. Changes to This Privacy Policy
AudioTextly may revise this Privacy Policy when the service, its information practices, its providers, or applicable requirements change. The “Last Updated” date should be revised whenever an updated policy is published.
Where applicable law requires an additional form of notice or consent for a material change, AudioTextly should use an appropriate verified mechanism. This policy does not promise that every visitor will receive an individual email.
Last Updated: 18 October 2026
15. Contact Us
Contact AudioTextly if you have a question about this Privacy Policy, want more information about relevant privacy practices, or wish to submit a privacy-related request.
- Website
- https://audiotextly.com/
- support@audiotextly.com
- Contact Page
- https://audiotextly.com/contact/
If applicable law requires the name, address, or other details of the legally responsible operator, those details must be obtained and added using verified business information.