Oravys, Inc., a Delaware corporation (8 The Green, Suite 4000, Dover, DE 19901, USA), is the controller for this website, the free checks and individual accounts. When a business customer sends us audio of its own customers or staff under a signed agreement, that customer is the controller and we act as its processor under a Data Processing Addendum; the customer's own privacy notice then applies first. Oravys, Inc. has no establishment in the European Union or the United Kingdom; the appointment of a representative under GDPR Article 27 is in progress, and until it is published all requests go to the privacy address above.
Security details beyond the summary in "Security" below (Data Processing Addendum, sub-processor agreements, security report, SLA) are available on request at . Everything this policy is required to disclose under GDPR Articles 13 and 14 is published in full below, not gated behind a request.
To provide our AI voice intelligence services, we collect and process the following categories of data:
Audio files you upload or record through our platform. These recordings are processed by our automated analysis, which derives voice characteristics from the sound signal in order to estimate whether the voice is real or machine-made. These derived characteristics are biometric data within the meaning of GDPR Article 9. We do not transcribe or store the semantic content of your speech.
Email address, name, and authentication credentials provided during registration or Google OAuth sign-in. This data is used for account management, report delivery, and service communication.
All payment transactions are processed securely through Stripe. ORAVYS does not store your full credit card number, CVV, or banking details. We retain only transaction identifiers and purchase history necessary for order fulfillment and refund processing.
IP address, browser type, device information, operating system, session identifiers, and interaction timestamps collected automatically when you use the platform. This data supports security, performance monitoring, and abuse prevention.
Pages visited, analysis requests submitted, features used, and interaction patterns. Collected via Google Analytics (with IP anonymization enabled) only after you accept analytics cookies (Section 7.2).
When you ask for a demo, a quote, a job, or the newsletter: your e-mail address, the page you came from, the text of the consent you accepted, the date, your IP address, and an unsubscribe token. When you use the free voice check by e-mail: your e-mail address, a hash of the IP address used to confirm it, the confirmation dates and the consent texts you accepted.
If you publish a signed audio asset through VoiceSign: the audio file, its fingerprint (hash), the identity you declare (shown publicly as self-declared, not verified by us), publication and expiry dates, and a consent record (hashed identity, hashed IP address, browser type, date). If you use the free signing page (/protect-my-voice and /verify-voice): the audio file and the name you type are processed in memory to build or check the signature and are not stored. We keep only aggregate daily counts of signatures and checks.
When you use the analysis flow accessible from oravys.com (the public Audit Yourself and deepfake detection pages), the following fields about your request reach our application logs and observability systems. This list is exhaustive for that flow:
Fields not listed here are not logged for analysis requests on this flow.
If you ask for and sign our non-disclosure agreement through the NDA page:
Voice data is uniquely sensitive. ORAVYS implements specific protections for audio recordings:
Real-time (live stream) analysis is not offered. The Service analyzes recorded clips that you submit, and the retention rules of Section 3.2 apply to them.
When two voice samples are submitted for comparative analysis:
For enterprise customers using forensic or insurance-related analysis:
Your information is used exclusively for the following purposes:
ORAVYS does not sell, rent, or trade your personal data or voice recordings to third parties for advertising, marketing, or any other purpose. This applies to all service tiers without exception.
To maintain platform stability, enforce fair use policies, and protect the Service for all users, ORAVYS collects and processes the following additional categories of data:
ORAVYS monitors and records metrics related to your use of computational resources, including but not limited to:
Compute and resource usage data is processed for the following purposes:
ORAVYS employs automated systems to enforce fair use policies and protect platform stability. These systems may automatically:
Automated enforcement actions are not considered "automated decision-making producing legal effects" under GDPR Article 22, as they are technical measures necessary for contract performance and do not produce legal effects beyond temporary service management. If you believe an automated enforcement action was applied in error, you may contact for human review.
Compute and resource usage data is retained as follows:
By default, no audio retention is performed without explicit opt-in. Audio submitted to the analysis flow accessible from oravys.com is processed in memory and the buffer is freed at the end of the call. See Section 1.1.8 for the fields logged during analysis and Section 1.2 for the broader processing posture. Training-data sources and methodology are described separately on the How ORAVYS trains its detection models page.
The Research Contribution opt-in is currently paused (30-Sep-2026). The checkbox is not shown on the public site and no new audio is collected under this program while it is paused; the description below states the condition under which the program would ever apply, not a feature you can currently use. Samples collected before the pause keep the rights described here (access, withdrawal, deletion).
If you tick the Research Contribution box, the recording you submitted is written to our EU storage and kept, linked to the e-mail address you gave, so that it can be used to improve detection accuracy. It is not anonymised. The opt-in is unchecked by default, separate from your general terms acceptance, and revocable at any time by writing to ; the sample is then deleted within 30 days. The following posture applies across plans:
If you provide feedback (such as rating a report or flagging a false positive/negative in deepfake detection), that specific interaction may be used to improve detection accuracy and service quality, with notice at the time of feedback. Feedback and content submitted through safety reporting mechanisms may also be used to maintain and improve the safety and reliability of the Service, so that critical signals (such as detection errors that could affect platform integrity) can be addressed.
We retain personal data only for as long as necessary to fulfill the purposes described in this policy. In summary, for the analysis flow on oravys.com: Audio is deleted after analysis. Reports are kept at least 30 days, then deleted automatically (35 days after creation; 30 days for full and expert reports); you can ask us to delete them sooner. The exceptions (Research Contribution, VoiceSign, the free voice check by e-mail, and API jobs) are listed in the granular schedule below.
Audio submitted to analyses started on our site is processed in memory and not written to storage. Where a file is written to storage, the cases and durations are these:
When a retention period ends or you ask for deletion, the data is deleted from our live systems within thirty (30) days. Enterprise customers may request a written confirmation of deletion under their DPA.
| Data Category | Retention Period | Legal Basis |
|---|---|---|
| Voice recordings (analyses started on the site) | In-memory only, freed at end of call | Contract (Art. 6(1)(b)) and explicit consent (Art. 9(2)(a)) |
| Voice recordings (free check by e-mail) | Deleted within 48 hours of upload | Consent (Art. 6(1)(a)) and explicit consent (Art. 9(2)(a)) |
| Voice recordings (API jobs) | Discarded when the result is written | Contract (Art. 6(1)(b)) and explicit consent (Art. 9(2)(a)) |
| Research Contribution samples | Until withdrawal, then deleted within 30 days | Explicit consent (Art. 9(2)(a)) |
| Analysis reports | At least 30 days; deleted automatically after 35 days (full and expert reports: 30 days); sooner on your request | Contract (Art. 6(1)(b)) |
| Account data | Life of the account; removed within 30 days of deletion request | Contract (Art. 6(1)(b)) |
| VoiceSign assets | 30 days by default, or until deletion if published permanently | Contract (Art. 6(1)(b)) |
| Contact, lead and newsletter records | Until unsubscribe or deletion request | Consent (Art. 6(1)(a)) |
| AI transparency register (file hash, answer, model version) | No fixed end date today; 24-month limit planned | Legitimate interest (Art. 6(1)(f)), accountability |
| Billing records | 10 years | Legal obligation (Art. 6(1)(c)) |
| NDA signature records (Section 1.1.9) | Term and survival period of the agreement, plus the limitation period for claims | Contract (Art. 6(1)(b)) and legitimate interest (Art. 6(1)(f)) |
| Technical/security logs | 90 days | Legitimate interest (Art. 6(1)(f)) |
You may request early deletion of your data at any time by contacting . Deletion requests are processed within 30 days.
The default analysis posture described in Sections 1.2 and 3.2.1 already covers the audio sample itself: the buffer is freed at the end of the call unless the Research Contribution opt-in is engaged. Enterprise customers may negotiate, in their Data Processing Addendum, stricter settings for operational metadata and reports (for example a shorter log retention or a contractual ban on the Research Contribution path). These settings are contractual commitments implemented per customer, not a self-service mode. Contact .
We share data only with the categories of service providers we need to operate the platform. They act as our processors, on our instructions:
Each provider processes data under its data processing terms, which include the obligations of GDPR Article 28. We do not share data with third parties for their independent marketing purposes.
Transfers to the United States: the payment, e-mail delivery, network security, sign-in and statistics, and AI text drafting providers are based in the United States, as is Oravys, Inc. These transfers are covered by the safeguards described in Section 5.1.4 (the EU Standard Contractual Clauses and, where the provider is certified, the EU-U.S. Data Privacy Framework).
No third-party AI processing of audio: ORAVYS does not use third-party AI services, external large language models, or cloud-based machine learning APIs to process your voice recordings. All voice analysis is performed by ORAVYS's own software. No audio data is transmitted to any external AI provider. The single exception concerns text, not audio: for Enterprise forensic reports, a narrative summary may be drafted by an external language model from anonymized labels, and the report records this method in its analysis-method field.
List of sub-processors: The named list of our sub-processors is sent on request to our privacy address and provided to customers under contract. Write to . ORAVYS informs customers under contract at least 30 days before engaging any new sub-processor that processes personal data. Enterprise customers with active DPAs may object to a new sub-processor within 15 business days of notification.
ORAVYS implements a layered consent framework designed to comply with the most stringent data protection requirements across all jurisdictions in which it operates.
Before submitting any audio recording for the first time, you must provide explicit, affirmative consent acknowledging that: (a) your audio will be processed by automated, AI-based analysis; (b) voice characteristics that constitute biometric data will be derived from your recording; (c) an authenticity result will be generated; and (d) you have read and understood the data processing described in this Privacy Policy. This consent is captured by unticked checkboxes on the upload form and verified by our servers on every analysis request. For the free check by e-mail and for VoiceSign we also store the consent text you accepted, the date and a hash of your IP address; for other analyses we do not keep a separate consent archive today.
Because voice data constitutes biometric data under GDPR Article 9, the Illinois Biometric Information Privacy Act (BIPA), and equivalent biometric privacy laws, ORAVYS obtains a separate, specific consent for biometric processing that is distinct from the general terms of service acceptance. This biometric consent: (a) specifically identifies that biometric identifiers will be collected and processed; (b) describes the purpose of biometric data collection; (c) states the retention schedule for biometric data; and (d) may be withdrawn at any time without affecting other Service features.
For users located in the European Economic Area, biometric data processing is authorized exclusively under GDPR Article 9(2)(a) (explicit consent). ORAVYS does not rely on any other Article 9 exception for biometric voice processing. The consent flow: (a) separates the biometric consent from the general data processing consent and from the optional Research Contribution; (b) uses plain language to describe the processing; and (c) can be withdrawn at any time by writing to , without affecting the lawfulness of processing before withdrawal.
By submitting any audio recording, you warrant and represent that: (a) you have obtained all required consents from every individual whose voice appears in the recording; (b) in jurisdictions requiring two-party or all-party consent for audio recording (including but not limited to California, Illinois, Florida, Washington, Pennsylvania, and equivalent jurisdictions globally), you have complied with all applicable consent requirements; and (c) the recording was not obtained through illegal wiretapping, covert surveillance, or any other unlawful means. ORAVYS is not responsible for verifying the consent status of submitted recordings and relies entirely on your representation.
If you are located in the European Economic Area (EEA), the United Kingdom, or any jurisdiction with equivalent data protection laws, the following provisions apply:
The human voice constitutes biometric data under GDPR Article 9. ORAVYS processes voice recordings exclusively for the declared analysis purposes under the following framework:
Data minimization and purpose limitation principles are strictly applied: voice data is used solely for generating your analysis report and is never used for speaker identification or surveillance.
You have the right to:
GET /api/account/export endpoint.To exercise any of these rights, write to . We answer within one month, extendable by two months for complex requests as GDPR Article 12 allows, and may ask you to confirm your identity.
For the analysis flow accessible from oravys.com, audio is processed in memory inside our EU compute region (Google Cloud, europe-west1, Belgium) and the buffer is freed at the end of the call (see Sections 1.2 and 3.2.1). Where retention is engaged through the Research Contribution opt-in or an enterprise contract, the retained sample is stored in the same EU region. Analysis results delivered as reports remain in the EU region for the retention durations described in Section 3.2.
Account data (name, email) may be processed by our sub-processors (Stripe for payments, Google for authentication) in jurisdictions outside the EEA. Where such transfers occur, they are governed by:
You may ask for information on these safeguards, including a copy of the applicable clauses, by contacting .
ORAVYS provides programmatic API endpoints for exercising your GDPR rights:
These endpoints require authenticated access: GET /api/account/export for export, POST /api/account/delete for erasure. If an endpoint is unavailable to you for any reason, you may exercise every right listed above by writing to , and we will act on it within the statutory deadline.
For all GDPR-related inquiries, write to . ORAVYS has not designated a Data Protection Officer under GDPR Article 37; this address is read by the founder. If you believe your data protection rights have been violated, you have the right to lodge a complaint with a supervisory authority in your country of residence (GDPR Art. 77), for example the CNIL in France or the ICO in the United Kingdom.
ORAVYS acknowledges the European Union Artificial Intelligence Act (Regulation (EU) 2024/1689) and its risk-based classification framework.
This Service uses artificial intelligence to process biometric data. Voice recordings submitted to ORAVYS are analysed by automated, AI-based software that derives voice characteristics (biometric data) from the recording and generates automated assessments. Users interacting with this system are hereby informed that they are interacting with an AI system, not a human analyst, and that all outputs are AI-generated.
ORAVYS has self-assessed its voice authenticity service, as offered on this site and through the API, as an AI system whose intended purpose is to estimate whether a recording is authentic, as decision support for a human. It is not placed on the market for the high-risk uses listed in Annex III of the AI Act (for example employment decisions, access to credit or insurance, law enforcement). A customer that nevertheless uses a result for such a purpose acts as a deployer, must inform ORAVYS under its agreement, and bears the obligations the AI Act attaches to that use. This self-assessment has not been reviewed by a regulator or by outside counsel. We label every output as produced by an AI system whether or not Article 50 strictly requires it for a detection system.
ORAVYS no longer offers voice-based personality or emotion profiling. The feature is switched off for every plan, free and paid. No personality trait assessment, Big Five, DISC, HEXACO, MBTI or emotion profile is produced, displayed, stored or sold. The underlying software remains in our codebase but is not exposed; re-enabling it would require an explicit configuration change and a new consent flow.
The sections below describe how the feature worked while it was offered. They are kept because they document processing that took place before that date, and because they would apply again if the feature were ever re-enabled.
ORAVYS offered an optional personality profiling feature that generated behavioral and personality trait assessments from voice characteristics derived from the sound signal. This feature involved automated processing as defined by GDPR Article 22.
Until 14 September 2026, personality profiling was processed exclusively under explicit, separate consent (GDPR Art. 9.2.a combined with Art. 22.4). That consent was distinct from the general bio-acoustic analysis consent and could be granted or withdrawn independently. All other ORAVYS features were usable without consenting to personality profiling. No such consent is requested or acted upon today.
Personality assessments were derived exclusively from characteristics of the sound signal (how the voice sounded, its rhythm and its dynamics), which are biometric data under GDPR Article 9. The semantic content (words, language, meaning) of your speech was never analyzed for personality profiling.
Those characteristics were processed by our software to generate personality trait indicators across multiple dimensions (communication style, stress resilience, leadership patterns, emotional expressiveness, and others). These indicators were probabilistic and represented tendencies, not definitive characterizations. Confidence levels were displayed alongside each indicator. No such indicator has been produced since 14 September 2026.
In accordance with GDPR Recital 63 and the EU Trade Secrets Directive (2016/943), ORAVYS provided meaningful information about the logic, significance, and consequences of profiling without disclosing proprietary algorithms, model weights, or mapping databases. This balance between transparency and trade secret protection is recognized by EU data protection authorities.
POST /api/v1/user/request-human-review, or by writing to . You may also submit your perspective on why you disagree with the assessment. Human reviews are conducted by a qualified reviewer with access to the raw data and the authority to modify or delete the automated profile. Reviews are completed within 30 days.POST /api/v1/user/profiling-opt-out, or by writing to . Opting out does not affect other analysis features.Each right above lists an email address alongside its API endpoint on purpose: an endpoint that moves or breaks must never make a right unexercisable. The email is the path of record.
Personality deduction texts were generated client-side in your browser and were not transmitted to or stored on ORAVYS servers unless you explicitly chose to save or share your report. No such text is generated today, in the browser or on our servers.
In compliance with the EU AI Act Article 5(1)(f), ORAVYS infers no emotional state and no personality trait in any context, workplace and educational contexts included, since 14 September 2026. Enterprise customers deploying ORAVYS for employment decisions (recruitment, evaluation, promotion) remain subject to enhanced compliance requirements including mandatory fundamental rights impact assessments, formal human oversight protocols, and enhanced logging, which apply to the acoustic authenticity outputs that are still offered.
ORAVYS analysis results are provided as informational and decision-support tools. No decision producing legal effects or significantly affecting any data subject is made solely on the basis of automated processing by the Service. The user is solely responsible for any decisions taken based on analysis results and must exercise their own professional judgment. ORAVYS does not engage in decision-making based solely on automated processing or profiling in a manner that produces legal effects concerning the data subject.
A user may submit a recording that contains your voice. In that case the user, not ORAVYS, chose to submit it and is required by our Terms to have the right to do so; ORAVYS cannot identify you from the audio and does not know who you are unless the user tells us. The recording is processed as described in Sections 1.2 and 3.2 and is not kept beyond the durations stated there. If you learn that your voice was analysed and want to object, ask for deletion, or know what was processed, write to with the details you have (date, report identifier, who submitted it); we will act on it within one month.
ORAVYS provides reversible consent controls. The analysis flow accessible from oravys.com surfaces a consent gate at the point of upload that maps to the following form fields, all enforced server-side:
consent_data_processing): Default OFF. Required to run any analysis. Without it, the request is rejected.consent_voice_processing): Default OFF. Required to run any analysis. Without it, the request is rejected.consent_research_optin, alias voice_optin): Default OFF. Opt-in is what engages the retention path described in Sections 3.2.1 and 3.2.4. Revocable at any time.Required consents must be granted at the point of upload. The Research Contribution opt-in is unchecked by default; without it, the audio buffer is freed at the end of the analysis call.
The default in-memory posture described in Section 1.2 applies across all tiers for the analysis flow accessible from oravys.com. Tier differences relate to retention scope, the consent surface, and contractual coverage:
ORAVYS automatically detects and honors the Global Privacy Control (GPC) signal from your browser. When GPC is enabled:
If you are a California resident, the California Consumer Privacy Act (as amended by the California Privacy Rights Act) grants you the following rights:
To exercise any of these rights, contact us at or use the automated rights endpoints described in Section 5.1.5. We will respond within 45 days of receiving a verifiable request. You may also designate an authorized agent to make a request on your behalf.
Categories of Personal Information Collected (preceding 12 months): Identifiers (name, email, IP address), commercial information (payment records), internet activity (usage logs), audio data (voice recordings, treated as sensitive personal information), and inferences drawn from the above (analysis reports). See Section 1.1 for complete details. We have not sold or shared personal information, as those terms are defined by the CCPA/CPRA, in the preceding 12 months, and we do not use sensitive personal information for purposes other than providing the Service.
The human voice may constitute a "biometric identifier" under the Illinois Biometric Information Privacy Act (740 ILCS 14). ORAVYS provides the following disclosures and commitments in compliance with BIPA:
Before collecting any biometric identifier or biometric information from an Illinois resident, ORAVYS provides written notice (via the in-application consent mechanism) that biometric identifiers are being collected and stored, and the specific purpose and duration of such collection and storage. ORAVYS obtains a written release (electronic signature or affirmative click-through consent) from each individual whose biometric identifier is collected.
Biometric identifiers and biometric information derived from voice recordings of Illinois residents are retained in accordance with the following schedule:
ORAVYS does not sell, lease, trade, or otherwise profit from biometric identifiers or biometric information. Biometric data is used solely for the purpose of providing the Service as described in this Privacy Policy.
Biometric identifiers and biometric information are stored, transmitted, and protected using a standard of care that is at least as protective as the standard used for other confidential and sensitive information, including encryption in transit (TLS 1.2 or higher) and at rest (AES-256) and access controls.
Consent records. Every analysis request is refused by our servers unless the two required consents are present. For the free check by e-mail we store the consent text you accepted with its date; for VoiceSign we store a consent record (action, hashed identity, hashed IP address, browser type, date). These records are kept as long as the related contact or asset record (Section 3.2). We do not keep a separate per-scan consent archive for other analyses today.
Third-party voices. If audio you submit contains the voice of any individual who is not you, your submission is governed by the Consent Representation and Warranty in Section 3.1.1 of the Terms of Service. You warrant that you have lawful authority to submit such voice for biometric analysis. ORAVYS does not independently verify the identity of voices in submitted audio. Liability for ORAVYS's own analytical outputs (deepfake scores, authenticity verdicts, analysis reports) is not subject to U.S. Communications Decency Act § 230, Digital Services Act Article 6, or DMCA § 512(c) safe harbors; that liability is governed exclusively by Section 5.2 of the Terms of Service.
Why consent records are kept. Keeping the consent text and date lets ORAVYS demonstrate consent as GDPR Article 7(1) and BIPA require. The records contain no audio, and the IP address is stored only as a hash.
Subprocessor chain. All subprocessors that may handle biometric data are contractually bound to equivalent collection, retention, and deletion obligations and are included in the named list of sub-processors, which is sent on request to our privacy address (Section 4.1). ORAVYS gives customers under contract at least thirty (30) days' notice before adding or replacing any biometric subprocessor, the same period as for all other subprocessors (Section 4.1), and customers may object during the notice window by terminating their account; if no objection is received the change takes effect at the end of the notice period.
Deletion confirmation. When you ask us to delete your data, we confirm in writing once it is done. You may request that confirmation by emailing .
No sale, no profit (BIPA § 15(c)). ORAVYS does not sell, lease, trade, or otherwise profit from biometric identifiers or voiceprints. This commitment applies equally to its subprocessors. Breach of this commitment constitutes a material breach of these Terms.
If you are a Delaware resident, the Delaware Personal Data Privacy Act (effective January 1, 2025) grants you the following rights:
Voice recordings and biometric data are classified as sensitive data under the DPDPA and require opt-in consent before processing, which ORAVYS obtains through the consent mechanisms described in Section 4.2. To exercise your Delaware privacy rights, contact . We will respond within 45 days.
For users in Israel, this policy is also the notice required by section 11 of the Privacy Protection Law 5741-1981, as amended by Amendment 13 (in force August 2025): the purposes of the processing, the fact that giving your data is voluntary except where a purchase requires it, the recipients listed in Section 4.1, and your rights of access, correction and deletion, which you may exercise by contacting . Voice recordings are information of special sensitivity under that law and are processed only with your consent. Whether the amended law requires ORAVYS to appoint a privacy protection officer is being assessed; none has been appointed to date. Israel benefits from an EU adequacy decision (reaffirmed January 2024), which allows lawful data transfers between the EEA and Israel.
In compliance with Article 50 of the EU Artificial Intelligence Act (Regulation (EU) 2024/1689), ORAVYS provides transparent labeling of all AI-generated and AI-analyzed outputs:
X-AI-Analysis: true and Content-Credentials: ai-generated=true; type=ai-analysis, so that integrators can label results downstream.If you believe an output has been mislabeled or stripped of its AI disclosure, please report it to .
ORAVYS applies the following security measures to protect your data:
While we implement commercially reasonable measures to protect your data, no internet transmission or electronic storage method is 100% secure. We cannot guarantee absolute security against unauthorized intrusion.
ORAVYS sets the following first-party cookies and browser storage:
__Host-session): keeps you logged in and carries the CSRF protection token. Expires when the session ends.oravys_ref): set only when you arrive through a referral link, so the referrer can be credited; first-party, no advertising use.Third-party cookies: Google Analytics (with IP anonymization) is loaded only after you accept analytics; if your browser sends the Global Privacy Control (GPC) signal, analytics stays off. The Cloudflare Turnstile bot challenge, used on the voice check and on the free check by e-mail, is a security service strictly necessary to protect these forms against automated abuse: it loads before any consent choice, is not used for analytics or advertising, and may set Cloudflare's own security cookies. We do not use advertising cookies, cross-site tracking pixels, or trackers that share data with advertisers.
To prevent third-party data leakage to font, script, or analytics providers, ORAVYS serves all critical web assets from its own infrastructure:
oravys.com/static/fonts/. ORAVYS does not load fonts from fonts.googleapis.com or fonts.gstatic.com, which would otherwise transmit your IP address to Google on every page load (a documented EU GDPR Art. 6 / Schrems II concern).oravys.com/static/js/vendor/. No request is made to cdn.jsdelivr.net or unpkg.com for these libraries.The Voice DNA Profile is a visual pattern generated from voice characteristics derived from your recording. Because these inputs constitute biometric data under GDPR Art. 9, the Voice DNA card is subject to the following safeguards:
sessionStorage for the current browsing session only; closing the tab revokes consent.In the event of a personal data breach that is likely to result in a risk to your rights and freedoms:
The Service is for adults. You must be 18 or older to use it, to create an account or to submit a recording, and you must not submit recordings of children (persons under 18). We do not direct the Service to children and do not knowingly collect their data. If we learn that we have processed a child's data, we delete it without delay and, where we have contact details, inform the parent or guardian. Today we rely on this rule and on the consent you give; we do not run an age check at sign-up.
ORAVYS does not knowingly collect, use, or disclose personal information from children under 13, as the U.S. Children's Online Privacy Protection Act (15 U.S.C. 6501-6506) requires.
We may update this Privacy Policy from time to time. Material changes will be communicated via email and/or a prominent notice on the platform at least 30 days before they take effect. The "Last Updated" date at the top reflects the most recent revision. Your continued use of the platform after changes take effect constitutes acceptance of the revised policy.
When ORAVYS modifies its pricing, subscription plans, service features, or fair use policies (as described in our Terms of Service, Sections 2.2, 2.3, and 1.3), we may process the following data:
Data processed in connection with pricing and service changes is retained in accordance with the retention periods specified in Section 3.2 of this Privacy Policy and applicable tax/accounting retention requirements.
If ORAVYS is involved in a merger, acquisition, reorganization, bankruptcy, or sale of all or substantially all of its assets, your information and any associated consent records may be transferred to the acquiring entity, provided that:
For privacy inquiries, data access requests, or concerns:
General:
Privacy and data rights:
Enterprise and DPA:
Oravys, Inc.
Delaware, USA
"ORAVYS" is a registered trademark (INPI No. 25 5212037, classes 9 & 42).