Ovation · Privacy & Data
Ovation privacy & data
Read from Ovation's own page on 2026-11-10. 23 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Role
Data categories
category: identifying
Personal details such as your name, email address, address, mobile number, birth date, and other similar information.Read from Ovation's own page on 2026-11-10
category: financial
Data required to set up contracts and process payments, such as payment card numbers, bank account details, billing and shipping information, and the names of transacting parties.Read from Ovation's own page on 2026-11-10
category: device
Details about your device, such as hardware model, operating system and version, unique device identifiers, mobile network information, and interactions with our Services.Read from Ovation's own page on 2026-11-10
category: location
This may include GPS data and device location information during your use of the Services.Read from Ovation's own page on 2026-11-10
category: behavioral
Data about how you interact with the Services, including accessed features, browser type, language, other applications on your device, and time spent on specific webpages or applications.Read from Ovation's own page on 2026-11-10
category: communication
Information shared when responding to surveys, submitting inquiries, or contacting our support team.Read from Ovation's own page on 2026-11-10
Purposes
purpose: Providing and maintaining Services
To deliver the Services you have requested.Read from Ovation's own page on 2026-11-10
purpose: Research and development
To enable us to improve the Services and better understand our customers and the markets in which we operate.Read from Ovation's own page on 2026-11-10
purpose: Communicating with users
To send communications via email, including, for example, responding to your comments, questions and requests, providing customer support, and sending you technical notices, service updates, security alerts.Read from Ovation's own page on 2026-11-10
purpose: Enhancing security
To keep our Services and associated systems operational and secure, including, for example, verifying activity, monitoring and investigating suspicious or fraudulent activity and to identify violations of our terms and policies.Read from Ovation's own page on 2026-11-10
Retention
scope: Personal data generally
We will retain your information for as long as it is reasonably needed for the purposes outlined in ‘How We Use Your Personal Data and Why ‘.Read from Ovation's own page on 2026-11-10
Residency
region: United States
The Services are maintained in the United States of America.Read from Ovation's own page on 2026-11-10
region: United States, Japan, European Union
These providers may operate in locations such as the United States, Japan, the European Union, or other countries.Read from Ovation's own page on 2026-11-10
International transfers
The page states nothing on this.
Subprocessors
Our sub-processors may access your Personal Data to help us develop, maintain and provide our Services and help manage our customer relationships.Read from Ovation's own page on 2026-11-10
Data processing agreement
Deletion
route: Contact us using the contact details in ‘Who we are and how to contact us’.
If you want to exercise any of the rights described above, please contact us using the contact details in ‘Who we are and how to contact us’.Read from Ovation's own page on 2026-11-10
Data subject rights
right: Correction
Request correction of the Personal Data that we hold about you.Read from Ovation's own page on 2026-11-10
right: Objection
Object to processing of your Personal Data.Read from Ovation's own page on 2026-11-10
right: Restriction
Request the restriction of processing of your Personal Data.Read from Ovation's own page on 2026-11-10
right: Portability
Request the transfer of your Personal Data.Read from Ovation's own page on 2026-11-10
Sale or sharing
The page states nothing on this.
Document
Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page