Unqork · Privacy & Data

Unqork privacy & data

Read from Unqork's own page on 2026-11-10. 20 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.

Role

value: both
Unqork processes Personal Data both as a Processor and as a Controller, as defined in the Directive and the GDPR
Read from Unqork's own page on 2026-11-10

Data categories

category: contact
contact information, such as your name, e-mail address, company name, address, phone number
Read from Unqork's own page on 2026-11-10
category: communication
Meeting recordings may capture: names, email addresses, video and audio recordings, chat transcripts and AI generated summaries.
Read from Unqork's own page on 2026-11-10

Purposes

purpose: respond to requests and questions
We use information to respond to your requests or questions.
Read from Unqork's own page on 2026-11-10
purpose: improve products and services
We use information to improve our products and services.
Read from Unqork's own page on 2026-11-10
purpose: security and fraud protection
Protecting against security threats, abuse, and illegal activity.
Read from Unqork's own page on 2026-11-10
purpose: use of service providers
Use of service providers. Unqork shares information with service providers to perform services on our behalf
Read from Unqork's own page on 2026-11-10

Retention

scope: personal information generally
We keep personal information as long as it is necessary or relevant for the practices described in this Policy.
Read from Unqork's own page on 2026-11-10
scope: customer-collected information
Personal Information provided by you is anonymized within Unqork Services upon signed submission of the product or service application and acceptance by the customer.
Read from Unqork's own page on 2026-11-10

Residency

region: United States
For Client Users with accounts in the Unqork US Data Region, Unqork processes data solely in data centers located in the US.
Read from Unqork's own page on 2026-11-10
region: Canada
For Client Users with accounts in the Unqork Canada Data Region, Unqork processes data solely in data centers located in Canada.
Read from Unqork's own page on 2026-11-10
region: Singapore
For Users with accounts in our Asian Pacific Data Region, Unqork processes data solely in data centers located in Singapore.
Read from Unqork's own page on 2026-11-10

International transfers

mechanism: other
We may process and store information in the United States. Information we collect from you will be transferred to, processed in, or stored in the United States or another destination outside of the European Economic Area
Read from Unqork's own page on 2026-11-10

Subprocessors

Data processing agreement

available: true
Unqork has a data processing agreement in place with its provider, ensuring compliance with the Directive.
Read from Unqork's own page on 2026-11-10

Deletion

route: contact privacy@unqork.com
You may also request that we remove your personal information from our system
Read from Unqork's own page on 2026-11-10

Data subject rights

right: access
You may also request a description of the personal information we have collected about you, or to receive a copy of your collected data.
Read from Unqork's own page on 2026-11-10
right: correction
or that we rectify your personal information if the personal information we have stored is incorrect or incomplete.
Read from Unqork's own page on 2026-11-10
right: withdraw consent
If you have provided us with your consent to collect or use your personal information, you may withdraw your consent at any time and for any reason
Read from Unqork's own page on 2026-11-10
right: opt out of marketing
You can opt out of receiving our marketing and newsletter emails.
Read from Unqork's own page on 2026-11-10

Sale or sharing

stance: prohibited
We will never sell your Personal Information to any third party.
Read from Unqork's own page on 2026-11-10

Document

Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page